Nuno M. Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Então, os jogadores conseguem executar diversos comandos, como: /tpa, /pay, /eco, etc.. mesmo antes de logarem no servidor.. Utilizo Authme como sistema de segurança.. que posso fazer para resolver isso?
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 forceKickAfterRegister: false # Does AuthMe need to enforce a /login after a successful registration? forceLoginAfterRegister: true acho q tem q ativar isso se nao me engano 1
Nuno M. Postado Outubro 21, 2018 Autor Denunciar Postado Outubro 21, 2018 8 minutos atrás, wDaark disse: forceKickAfterRegister: false # Does AuthMe need to enforce a /login after a successful registration? forceLoginAfterRegister: true acho q tem q ativar isso se nao me engano Já o fiz, e o problema se mantem..
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 na vdd deative isto aq restrictions: # Can not authenticated players chat? # Keep in mind that this feature also blocks all commands not # listed in the list below. allowChat: false deixe false # Hide the chat log from players who are not authenticated? hideChat: false 1
EduZeraH Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Scoreboard, provavelmente seja ela. Você faz ela atualizar por 'comandos' também? 1
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Agora, EduZeraH disse: Scoreboard, provavelmente seja ela. Você faz ela atualizar por 'comandos' também? é no authme mesmo allowChat: false
Nuno M. Postado Outubro 21, 2018 Autor Denunciar Postado Outubro 21, 2018 14 minutos atrás, wDaark disse: na vdd deative isto aq restrictions: # Can not authenticated players chat? # Keep in mind that this feature also blocks all commands not # listed in the list below. allowChat: false deixe false # Hide the chat log from players who are not authenticated? hideChat: false Então.. tenho isso como "false" também.. eis minha configuração: https://hastebin.com/vecuqahodo.http 14 minutos atrás, EduZeraH disse: Scoreboard, provavelmente seja ela. Você faz ela atualizar por 'comandos' também? A scoreboard é sistema próprio, e eu já experimentei retirar ele.. e o problema se mantem..
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Spoiler DataSource: # What type of database do you want to use? # Valid values: sqlite, mysql backend: 'sqlite' # Enable database caching, should improve database performance caching: true # Database host address mySQLHost: 'sql300.epizy.com' # Database port mySQLPort: '3306' # Username about Database Connection Infos mySQLUsername: 'epiz_22704887' # Password about Database Connection Infos mySQLPassword: 'barrilco1' # Database Name, use with converters or as SQLITE database name mySQLDatabase: 'epiz_22704887_authme' # Table of the database mySQLTablename: 'authme' # Column of IDs to sort data mySQLColumnId: 'id' # Column for storing or checking players nickname mySQLColumnName: 'username' # Column for storing or checking players RealName mySQLRealName: 'realname' # Column for storing players passwords mySQLColumnPassword: 'password' # Request mysql over SSL mySQLUseSSL: true # Column for storing players emails mySQLColumnEmail: 'email' # Column for storing if a player is logged in or not mySQLColumnLogged: 'isLogged' # Column for storing players ips mySQLColumnIp: 'ip' # Column for storing players lastlogins mySQLColumnLastLogin: 'lastlogin' # Column for storing player LastLocation - X mySQLlastlocX: 'x' # Column for storing player LastLocation - Y mySQLlastlocY: 'y' # Column for storing player LastLocation - Z mySQLlastlocZ: 'z' # Column for storing player LastLocation - World Name mySQLlastlocWorld: 'world' # Overrides the size of the DB Connection Pool, -1 = Auto poolSize: -1 ExternalBoardOptions: # Column for storing players passwords salts mySQLColumnSalt: '' # Column for storing players groups mySQLColumnGroup: '' # -1 means disabled. If you want that only activated players # can log into your server, you can set here the group number # of unactivated users, needed for some forum/CMS support nonActivedUserGroup: -1 # Other MySQL columns where we need to put the username (case-sensitive) mySQLOtherUsernameColumns: [] # How much log2 rounds needed in BCrypt (do not change if you do not know what it does) bCryptLog2Round: 10 # phpBB table prefix defined during the phpBB installation process phpbbTablePrefix: 'phpbb_' # phpBB activated group ID; 2 is the default registered group defined by phpBB phpbbActivatedGroupId: 2 # Wordpress prefix defined during WordPress installation wordpressTablePrefix: 'wp_' Converter: Rakamak: # Rakamak file name fileName: 'users.rak' # Rakamak use IP? useIP: false # Rakamak IP file name ipFileName: 'UsersIp.rak' CrazyLogin: # CrazyLogin database file name fileName: 'accounts.db' settings: sessions: # Do you want to enable the session feature? # If enabled, when a player authenticates successfully, # his IP and his nickname is saved. # The next time the player joins the server, if his IP # is the same as last time and the timeout hasn't # expired, he will not need to authenticate. enabled: false # After how many minutes should a session expire? # Remember that sessions will end only after the timeout, and # if the player's IP has changed but the timeout hasn't expired, # the player will be kicked from the server due to invalid session timeout: 10 # Should the session expire if the player tries to log in with # another IP address? sessionExpireOnIpChange: true # Message language, available languages: # https://github.com/AuthMe/AuthMeReloaded/blob/master/docs/translations.md messagesLanguage: 'br' # Log level: INFO, FINE, DEBUG. Use INFO for general messages, # FINE for some additional detailed ones (like password failed), # and DEBUG for debugging logLevel: 'FINE' # By default we schedule async tasks when talking to the database. If you want # typical communication with the database to happen synchronously, set this to false useAsyncTasks: true restrictions: # Can not authenticated players chat? # Keep in mind that this feature also blocks all commands not # listed in the list below. allowChat: false # Hide the chat log from players who are not authenticated? hideChat: false # Allowed commands for unauthenticated players allowCommands: - '/login' - '/register' - '/l' - '/reg' - '/email' - '/captcha' # Max number of allowed registrations per IP # The value 0 means an unlimited number of registrations! maxRegPerIp: 2 # Minimum allowed username length minNicknameLength: 5 # Maximum allowed username length maxNicknameLength: 16 # When this setting is enabled, online players can't be kicked out # due to "Logged in from another Location" # This setting will prevent potential security exploits. ForceSingleSession: true ForceSpawnLocOnJoin: # If enabled, every player that spawn in one of the world listed in # "ForceSpawnLocOnJoin.worlds" will be teleported to the spawnpoint after successful # authentication. The quit location of the player will be overwritten. # This is different from "teleportUnAuthedToSpawn" that teleport player # to the spawnpoint on join. enabled: true # WorldNames where we need to force the spawn location # Case-sensitive! worlds: - 'World' # This option will save the quit location of the players. SaveQuitLocation: false # To activate the restricted user feature you need # to enable this option and configure the AllowedRestrictedUser field. AllowRestrictedUser: false # The restricted user feature will kick players listed below # if they don't match the defined IP address. Names are case-insensitive. # Example: # AllowedRestrictedUser: # - playername;127.0.0.1 AllowedRestrictedUser: [] # Should unregistered players be kicked immediately? kickNonRegistered: false # Should players be kicked on wrong password? kickOnWrongPassword: false # Should not logged in players be teleported to the spawn? # After the authentication they will be teleported back to # their normal position. teleportUnAuthedToSpawn: false # Can unregistered players walk around? allowMovement: false # Should not authenticated players have speed = 0? # This will reset the fly/walk speed to default value after the login. removeSpeed: true # After how many seconds should players who fail to login or register # be kicked? Set to 0 to disable. timeout: 18 # Regex syntax of allowed characters in the player name. allowedNicknameCharacters: '[a-zA-Z0-9_]*' # How far can unregistered players walk? # Set to 0 for unlimited radius allowedMovementRadius: 1 # Should we protect the player inventory before logging in? Requires ProtocolLib. ProtectInventoryBeforeLogIn: true # Should we deny the tabcomplete feature before logging in? Requires ProtocolLib. DenyTabCompleteBeforeLogin: true # Should we display all other accounts from a player when he joins? # permission: /authme.admin.accounts displayOtherAccounts: false # Ban ip when the ip is not the ip registered in database banUnsafedIP: false # Spawn priority; values: authme, essentials, multiverse, default spawnPriority: 'authme' # Maximum Login authorized by IP maxLoginPerIp: 0 # Maximum Join authorized by IP maxJoinPerIp: 0 # AuthMe will NEVER teleport players if set to true! noTeleport: false # Regex syntax for allowed chars in passwords allowedPasswordCharacters: '[\x21-\x7E]*' # Threshold of the other accounts command, a value less than 2 means disabled. otherAccountsCmdThreshold: 0 # Command to run when a user has more accounts than the configured threshold. # Available variables: %playername%, %playerip% otherAccountsCmd: '' GameMode: # Force survival gamemode when player joins? ForceSurvivalMode: true unrestrictions: # Below you can list all account names that AuthMe will ignore # for registration or login. Configure it at your own risk!! # This option adds compatibility with BuildCraft and some other mods. # It is case-insensitive! Example: # UnrestrictedName: # - 'npcPlayer' # - 'npcPlayer2' UnrestrictedName: [] security: # Minimum length of password minPasswordLength: 6 # Maximum length of password passwordMaxLength: 30 # This is a very important option: every time a player joins the server, # if they are registered, AuthMe will switch him to unLoggedInGroup. # This should prevent all major exploits. # You can set up your permission plugin with this special group to have no permissions, # or only permission to chat (or permission to send private messages etc.). # The better way is to set up this group with few permissions, so if a player # tries to exploit an account they can do only what you've defined for the group. # After, a logged in player will be moved to his correct permissions group! # Please note that the group name is case-sensitive, so 'admin' is different from 'Admin' # Otherwise your group will be wiped and the player will join in the default group []! # Example unLoggedinGroup: NotLogged unLoggedinGroup: 'unLoggedinGroup' # Possible values: SHA256, BCRYPT, BCRYPT2Y, PBKDF2, SALTEDSHA512, WHIRLPOOL, # MYBB, IPB3, PHPBB, PHPFUSION, SMF, XENFORO, XAUTH, JOOMLA, WBB3, WBB4, MD5VB, # PBKDF2DJANGO, WORDPRESS, ROYALAUTH, CUSTOM (for developers only). See full list at # https://github.com/AuthMe/AuthMeReloaded/blob/master/docs/hash_algorithms.md passwordHash: 'SHA256' # Salt length for the SALTED2MD5 MD5(MD5(password)+salt) doubleMD5SaltLength: 8 # If a password check fails, AuthMe will also try to check with the following hash methods. # Use this setting when you change from one hash method to another. # AuthMe will update the password to the new hash. Example: # legacyHashes: # - 'SHA1' legacyHashes: [] # Number of rounds to use if passwordHash is set to PBKDF2. Default is 10000 pbkdf2Rounds: 10000 # Prevent unsafe passwords from being used; put them in lowercase! # You should always set 'help' as unsafePassword due to possible conflicts. # unsafePasswords: # - '123456' # - 'password' # - 'help' unsafePasswords: - '123456' - 'password' - 'qwerty' - '12345' - '54321' - '123456789' - 'help' registration: # Enable registration on the server? enabled: true # Send every X seconds a message to a player to # remind him that he has to login/register messageInterval: 6 # Only registered and logged in players can play. # See restrictions for exceptions force: true # Type of registration: PASSWORD or EMAIL # PASSWORD = account is registered with a password supplied by the user; # EMAIL = password is generated and sent to the email provided by the user. # More info at https://github.com/AuthMe/AuthMeReloaded/wiki/Registration type: 'PASSWORD' # Second argument the /register command should take: NONE = no 2nd argument # CONFIRMATION = must repeat first argument (pass or email) # EMAIL_OPTIONAL = for password register: 2nd argument can be empty or have email address # EMAIL_MANDATORY = for password register: 2nd argument MUST be an email address secondArg: 'CONFIRMATION' # Do we force kick a player after a successful registration? # Do not use with login feature below forceKickAfterRegister: false # Does AuthMe need to enforce a /login after a successful registration? forceLoginAfterRegister: true # Enable to display the welcome message (welcome.txt) after a login # You can use colors in this welcome.txt + some replaced strings: # {PLAYER}: player name, {ONLINE}: display number of online players, # {MAXPLAYERS}: display server slots, {IP}: player ip, {LOGINS}: number of players logged, # {WORLD}: player current world, {SERVER}: server name # {VERSION}: get current bukkit version, {COUNTRY}: player country useWelcomeMessage: false # Broadcast the welcome message to the server or only to the player? # set true for server or false for player broadcastWelcomeMessage: false # Should we delay the join message and display it once the player has logged in? delayJoinMessage: false # The custom join message that will be sent after a successful login, # keep empty to use the original one. # Available variables: # {PLAYERNAME}: the player name (no colors) # {DISPLAYNAME}: the player name (with colors) customJoinMessage: '' # Should we remove the leave messages of unlogged users? removeUnloggedLeaveMessage: true # Should we remove join messages altogether? removeJoinMessage: true # Should we remove leave messages altogether? removeLeaveMessage: true # Do we need to add potion effect Blinding before login/reigster? applyBlindEffect: false # Do we need to prevent people to login with another case? # If Xephi is registered, then Xephi can login, but not XEPHI/xephi/XePhI preventOtherCase: true permission: # Take care with this option; if you want # to use group switching of AuthMe # for unloggedIn players, set this setting to true. # Default is false. EnablePermissionCheck: false Email: # Email SMTP server host mailSMTP: 'smtp.gmail.com' # Email SMTP server port mailPort: 465 # Email account which sends the mails mailAccount: '[email protected]' # Email account password mailPassword: 'gabiminhavida' # Email address, fill when mailAccount is not the email address of the account mailAddress: '[email protected]' # Custom sender name, replacing the mailAccount name in the email mailSenderName: 'WicherNetwork' # Recovery password length RecoveryPasswordLength: 8 # Mail Subject mailSubject: 'Sua nova senha' # Like maxRegPerIP but with email maxRegPerEmail: 1 # Recall players to add an email? recallPlayers: true # Delay in minute for the recall scheduler delayRecall: 5 # Blacklist these domains for emails emailBlacklisted: - '10minutemail.com' # Whitelist ONLY these domains for emails emailWhitelisted: [] # Send the new password drawn in an image? generateImage: false # The OAuth2 token emailOauth2Token: '' Hooks: # Do we need to hook with multiverse for spawn checking? multiverse: false # Do we need to hook with BungeeCord? bungeecord: false # Send player to this BungeeCord server after register/login sendPlayerTo: '' # Do we need to disable Essentials SocialSpy on join? disableSocialSpy: false # Do we need to force /motd Essentials command on join? useEssentialsMotd: false GroupOptions: # Unregistered permission group UnregisteredPlayerGroup: '' # Registered permission group RegisteredPlayerGroup: '' Protection: # Enable some servers protection (country based login, antibot) enableProtection: false # Apply the protection also to registered usernames enableProtectionRegistered: true # Countries allowed to join the server and register. For country codes, see # https://dev.bukkit.org/projects/authme-reloaded/pages/countries-codes # PLEASE USE QUOTES! countries: - 'US' - 'GB' # Countries not allowed to join the server and register # PLEASE USE QUOTES! countriesBlacklist: - 'A1' # Do we need to enable automatic antibot system? enableAntiBot: true # The interval in seconds antiBotInterval: 5 # Max number of players allowed to login in the interval # before the AntiBot system is enabled automatically antiBotSensibility: 10 # Duration in minutes of the antibot automatic system antiBotDuration: 10 # Delay in seconds before the antibot activation antiBotDelay: 60 Purge: # If enabled, AuthMe automatically purges old, unused accounts useAutoPurge: false # Number of days after which an account should be purged daysBeforeRemovePlayer: 60 # Do we need to remove the player.dat file during purge process? removePlayerDat: false # Do we need to remove the Essentials/userdata/player.yml file during purge process? removeEssentialsFile: false # World where are players.dat stores defaultWorld: 'world' # Remove LimitedCreative/inventories/player.yml, player_creative.yml files during purge? removeLimitedCreativesInventories: false # Do we need to remove the AntiXRayData/PlayerData/player file during purge process? removeAntiXRayFile: false # Do we need to remove permissions? removePermissions: false Security: SQLProblem: # Stop the server if we can't contact the sql database # Take care with this, if you set this to false, # AuthMe will automatically disable and the server won't be protected! stopServer: true console: # Remove passwords from console? removePassword: true # Copy AuthMe log output in a separate file as well? logConsole: true captcha: # Enable captcha when a player uses wrong password too many times useCaptcha: false # Max allowed tries before a captcha is required maxLoginTry: 5 # Captcha length captchaLength: 5 tempban: # Tempban a user's IP address if they enter the wrong password too many times enableTempban: false # How many times a user can attempt to login before their IP being tempbanned maxLoginTries: 10 # The length of time a IP address will be tempbanned in minutes # Default: 480 minutes, or 8 hours tempbanLength: 480 # How many minutes before resetting the count for failed logins by IP and username # Default: 480 minutes (8 hours) minutesBeforeCounterReset: 480 recoveryCode: # Number of characters a recovery code should have (0 to disable) length: 8 # How many hours is a recovery code valid for? validForHours: 4 BackupSystem: # Enable or disable automatic backup ActivateBackup: false # Set backup at every start of server OnServerStart: false # Set backup at every stop of server OnServerStop: true # Windows only mysql installation Path MysqlWindowsPath: 'C:\Program Files\MySQL\MySQL Server 5.1\' tente essa config 1
Simply Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 # Can not authenticated players chat? # Keep in mind that this feature also blocks all commands not # listed in the list below. allowChat: false # Hide the chat log from players who are not authenticated? hideChat: false # Allowed commands for unauthenticated players allowCommands: - '/login' - '/register' - '/reg' - '/email' - '/captcha' Deixa deste jeito...
Nuno M. Postado Outubro 21, 2018 Autor Denunciar Postado Outubro 21, 2018 14 minutos atrás, wDaark disse: Mostrar conteúdo oculto DataSource: # What type of database do you want to use? # Valid values: sqlite, mysql backend: 'sqlite' # Enable database caching, should improve database performance caching: true # Database host address mySQLHost: 'sql300.epizy.com' # Database port mySQLPort: '3306' # Username about Database Connection Infos mySQLUsername: 'epiz_22704887' # Password about Database Connection Infos mySQLPassword: 'barrilco1' # Database Name, use with converters or as SQLITE database name mySQLDatabase: 'epiz_22704887_authme' # Table of the database mySQLTablename: 'authme' # Column of IDs to sort data mySQLColumnId: 'id' # Column for storing or checking players nickname mySQLColumnName: 'username' # Column for storing or checking players RealName mySQLRealName: 'realname' # Column for storing players passwords mySQLColumnPassword: 'password' # Request mysql over SSL mySQLUseSSL: true # Column for storing players emails mySQLColumnEmail: 'email' # Column for storing if a player is logged in or not mySQLColumnLogged: 'isLogged' # Column for storing players ips mySQLColumnIp: 'ip' # Column for storing players lastlogins mySQLColumnLastLogin: 'lastlogin' # Column for storing player LastLocation - X mySQLlastlocX: 'x' # Column for storing player LastLocation - Y mySQLlastlocY: 'y' # Column for storing player LastLocation - Z mySQLlastlocZ: 'z' # Column for storing player LastLocation - World Name mySQLlastlocWorld: 'world' # Overrides the size of the DB Connection Pool, -1 = Auto poolSize: -1 ExternalBoardOptions: # Column for storing players passwords salts mySQLColumnSalt: '' # Column for storing players groups mySQLColumnGroup: '' # -1 means disabled. If you want that only activated players # can log into your server, you can set here the group number # of unactivated users, needed for some forum/CMS support nonActivedUserGroup: -1 # Other MySQL columns where we need to put the username (case-sensitive) mySQLOtherUsernameColumns: [] # How much log2 rounds needed in BCrypt (do not change if you do not know what it does) bCryptLog2Round: 10 # phpBB table prefix defined during the phpBB installation process phpbbTablePrefix: 'phpbb_' # phpBB activated group ID; 2 is the default registered group defined by phpBB phpbbActivatedGroupId: 2 # Wordpress prefix defined during WordPress installation wordpressTablePrefix: 'wp_' Converter: Rakamak: # Rakamak file name fileName: 'users.rak' # Rakamak use IP? useIP: false # Rakamak IP file name ipFileName: 'UsersIp.rak' CrazyLogin: # CrazyLogin database file name fileName: 'accounts.db' settings: sessions: # Do you want to enable the session feature? # If enabled, when a player authenticates successfully, # his IP and his nickname is saved. # The next time the player joins the server, if his IP # is the same as last time and the timeout hasn't # expired, he will not need to authenticate. enabled: false # After how many minutes should a session expire? # Remember that sessions will end only after the timeout, and # if the player's IP has changed but the timeout hasn't expired, # the player will be kicked from the server due to invalid session timeout: 10 # Should the session expire if the player tries to log in with # another IP address? sessionExpireOnIpChange: true # Message language, available languages: # https://github.com/AuthMe/AuthMeReloaded/blob/master/docs/translations.md messagesLanguage: 'br' # Log level: INFO, FINE, DEBUG. Use INFO for general messages, # FINE for some additional detailed ones (like password failed), # and DEBUG for debugging logLevel: 'FINE' # By default we schedule async tasks when talking to the database. If you want # typical communication with the database to happen synchronously, set this to false useAsyncTasks: true restrictions: # Can not authenticated players chat? # Keep in mind that this feature also blocks all commands not # listed in the list below. allowChat: false # Hide the chat log from players who are not authenticated? hideChat: false # Allowed commands for unauthenticated players allowCommands: - '/login' - '/register' - '/l' - '/reg' - '/email' - '/captcha' # Max number of allowed registrations per IP # The value 0 means an unlimited number of registrations! maxRegPerIp: 2 # Minimum allowed username length minNicknameLength: 5 # Maximum allowed username length maxNicknameLength: 16 # When this setting is enabled, online players can't be kicked out # due to "Logged in from another Location" # This setting will prevent potential security exploits. ForceSingleSession: true ForceSpawnLocOnJoin: # If enabled, every player that spawn in one of the world listed in # "ForceSpawnLocOnJoin.worlds" will be teleported to the spawnpoint after successful # authentication. The quit location of the player will be overwritten. # This is different from "teleportUnAuthedToSpawn" that teleport player # to the spawnpoint on join. enabled: true # WorldNames where we need to force the spawn location # Case-sensitive! worlds: - 'World' # This option will save the quit location of the players. SaveQuitLocation: false # To activate the restricted user feature you need # to enable this option and configure the AllowedRestrictedUser field. AllowRestrictedUser: false # The restricted user feature will kick players listed below # if they don't match the defined IP address. Names are case-insensitive. # Example: # AllowedRestrictedUser: # - playername;127.0.0.1 AllowedRestrictedUser: [] # Should unregistered players be kicked immediately? kickNonRegistered: false # Should players be kicked on wrong password? kickOnWrongPassword: false # Should not logged in players be teleported to the spawn? # After the authentication they will be teleported back to # their normal position. teleportUnAuthedToSpawn: false # Can unregistered players walk around? allowMovement: false # Should not authenticated players have speed = 0? # This will reset the fly/walk speed to default value after the login. removeSpeed: true # After how many seconds should players who fail to login or register # be kicked? Set to 0 to disable. timeout: 18 # Regex syntax of allowed characters in the player name. allowedNicknameCharacters: '[a-zA-Z0-9_]*' # How far can unregistered players walk? # Set to 0 for unlimited radius allowedMovementRadius: 1 # Should we protect the player inventory before logging in? Requires ProtocolLib. ProtectInventoryBeforeLogIn: true # Should we deny the tabcomplete feature before logging in? Requires ProtocolLib. DenyTabCompleteBeforeLogin: true # Should we display all other accounts from a player when he joins? # permission: /authme.admin.accounts displayOtherAccounts: false # Ban ip when the ip is not the ip registered in database banUnsafedIP: false # Spawn priority; values: authme, essentials, multiverse, default spawnPriority: 'authme' # Maximum Login authorized by IP maxLoginPerIp: 0 # Maximum Join authorized by IP maxJoinPerIp: 0 # AuthMe will NEVER teleport players if set to true! noTeleport: false # Regex syntax for allowed chars in passwords allowedPasswordCharacters: '[\x21-\x7E]*' # Threshold of the other accounts command, a value less than 2 means disabled. otherAccountsCmdThreshold: 0 # Command to run when a user has more accounts than the configured threshold. # Available variables: %playername%, %playerip% otherAccountsCmd: '' GameMode: # Force survival gamemode when player joins? ForceSurvivalMode: true unrestrictions: # Below you can list all account names that AuthMe will ignore # for registration or login. Configure it at your own risk!! # This option adds compatibility with BuildCraft and some other mods. # It is case-insensitive! Example: # UnrestrictedName: # - 'npcPlayer' # - 'npcPlayer2' UnrestrictedName: [] security: # Minimum length of password minPasswordLength: 6 # Maximum length of password passwordMaxLength: 30 # This is a very important option: every time a player joins the server, # if they are registered, AuthMe will switch him to unLoggedInGroup. # This should prevent all major exploits. # You can set up your permission plugin with this special group to have no permissions, # or only permission to chat (or permission to send private messages etc.). # The better way is to set up this group with few permissions, so if a player # tries to exploit an account they can do only what you've defined for the group. # After, a logged in player will be moved to his correct permissions group! # Please note that the group name is case-sensitive, so 'admin' is different from 'Admin' # Otherwise your group will be wiped and the player will join in the default group []! # Example unLoggedinGroup: NotLogged unLoggedinGroup: 'unLoggedinGroup' # Possible values: SHA256, BCRYPT, BCRYPT2Y, PBKDF2, SALTEDSHA512, WHIRLPOOL, # MYBB, IPB3, PHPBB, PHPFUSION, SMF, XENFORO, XAUTH, JOOMLA, WBB3, WBB4, MD5VB, # PBKDF2DJANGO, WORDPRESS, ROYALAUTH, CUSTOM (for developers only). See full list at # https://github.com/AuthMe/AuthMeReloaded/blob/master/docs/hash_algorithms.md passwordHash: 'SHA256' # Salt length for the SALTED2MD5 MD5(MD5(password)+salt) doubleMD5SaltLength: 8 # If a password check fails, AuthMe will also try to check with the following hash methods. # Use this setting when you change from one hash method to another. # AuthMe will update the password to the new hash. Example: # legacyHashes: # - 'SHA1' legacyHashes: [] # Number of rounds to use if passwordHash is set to PBKDF2. Default is 10000 pbkdf2Rounds: 10000 # Prevent unsafe passwords from being used; put them in lowercase! # You should always set 'help' as unsafePassword due to possible conflicts. # unsafePasswords: # - '123456' # - 'password' # - 'help' unsafePasswords: - '123456' - 'password' - 'qwerty' - '12345' - '54321' - '123456789' - 'help' registration: # Enable registration on the server? enabled: true # Send every X seconds a message to a player to # remind him that he has to login/register messageInterval: 6 # Only registered and logged in players can play. # See restrictions for exceptions force: true # Type of registration: PASSWORD or EMAIL # PASSWORD = account is registered with a password supplied by the user; # EMAIL = password is generated and sent to the email provided by the user. # More info at https://github.com/AuthMe/AuthMeReloaded/wiki/Registration type: 'PASSWORD' # Second argument the /register command should take: NONE = no 2nd argument # CONFIRMATION = must repeat first argument (pass or email) # EMAIL_OPTIONAL = for password register: 2nd argument can be empty or have email address # EMAIL_MANDATORY = for password register: 2nd argument MUST be an email address secondArg: 'CONFIRMATION' # Do we force kick a player after a successful registration? # Do not use with login feature below forceKickAfterRegister: false # Does AuthMe need to enforce a /login after a successful registration? forceLoginAfterRegister: true # Enable to display the welcome message (welcome.txt) after a login # You can use colors in this welcome.txt + some replaced strings: # {PLAYER}: player name, {ONLINE}: display number of online players, # {MAXPLAYERS}: display server slots, {IP}: player ip, {LOGINS}: number of players logged, # {WORLD}: player current world, {SERVER}: server name # {VERSION}: get current bukkit version, {COUNTRY}: player country useWelcomeMessage: false # Broadcast the welcome message to the server or only to the player? # set true for server or false for player broadcastWelcomeMessage: false # Should we delay the join message and display it once the player has logged in? delayJoinMessage: false # The custom join message that will be sent after a successful login, # keep empty to use the original one. # Available variables: # {PLAYERNAME}: the player name (no colors) # {DISPLAYNAME}: the player name (with colors) customJoinMessage: '' # Should we remove the leave messages of unlogged users? removeUnloggedLeaveMessage: true # Should we remove join messages altogether? removeJoinMessage: true # Should we remove leave messages altogether? removeLeaveMessage: true # Do we need to add potion effect Blinding before login/reigster? applyBlindEffect: false # Do we need to prevent people to login with another case? # If Xephi is registered, then Xephi can login, but not XEPHI/xephi/XePhI preventOtherCase: true permission: # Take care with this option; if you want # to use group switching of AuthMe # for unloggedIn players, set this setting to true. # Default is false. EnablePermissionCheck: false Email: # Email SMTP server host mailSMTP: 'smtp.gmail.com' # Email SMTP server port mailPort: 465 # Email account which sends the mails mailAccount: '[email protected]' # Email account password mailPassword: 'gabiminhavida' # Email address, fill when mailAccount is not the email address of the account mailAddress: '[email protected]' # Custom sender name, replacing the mailAccount name in the email mailSenderName: 'WicherNetwork' # Recovery password length RecoveryPasswordLength: 8 # Mail Subject mailSubject: 'Sua nova senha' # Like maxRegPerIP but with email maxRegPerEmail: 1 # Recall players to add an email? recallPlayers: true # Delay in minute for the recall scheduler delayRecall: 5 # Blacklist these domains for emails emailBlacklisted: - '10minutemail.com' # Whitelist ONLY these domains for emails emailWhitelisted: [] # Send the new password drawn in an image? generateImage: false # The OAuth2 token emailOauth2Token: '' Hooks: # Do we need to hook with multiverse for spawn checking? multiverse: false # Do we need to hook with BungeeCord? bungeecord: false # Send player to this BungeeCord server after register/login sendPlayerTo: '' # Do we need to disable Essentials SocialSpy on join? disableSocialSpy: false # Do we need to force /motd Essentials command on join? useEssentialsMotd: false GroupOptions: # Unregistered permission group UnregisteredPlayerGroup: '' # Registered permission group RegisteredPlayerGroup: '' Protection: # Enable some servers protection (country based login, antibot) enableProtection: false # Apply the protection also to registered usernames enableProtectionRegistered: true # Countries allowed to join the server and register. For country codes, see # https://dev.bukkit.org/projects/authme-reloaded/pages/countries-codes # PLEASE USE QUOTES! countries: - 'US' - 'GB' # Countries not allowed to join the server and register # PLEASE USE QUOTES! countriesBlacklist: - 'A1' # Do we need to enable automatic antibot system? enableAntiBot: true # The interval in seconds antiBotInterval: 5 # Max number of players allowed to login in the interval # before the AntiBot system is enabled automatically antiBotSensibility: 10 # Duration in minutes of the antibot automatic system antiBotDuration: 10 # Delay in seconds before the antibot activation antiBotDelay: 60 Purge: # If enabled, AuthMe automatically purges old, unused accounts useAutoPurge: false # Number of days after which an account should be purged daysBeforeRemovePlayer: 60 # Do we need to remove the player.dat file during purge process? removePlayerDat: false # Do we need to remove the Essentials/userdata/player.yml file during purge process? removeEssentialsFile: false # World where are players.dat stores defaultWorld: 'world' # Remove LimitedCreative/inventories/player.yml, player_creative.yml files during purge? removeLimitedCreativesInventories: false # Do we need to remove the AntiXRayData/PlayerData/player file during purge process? removeAntiXRayFile: false # Do we need to remove permissions? removePermissions: false Security: SQLProblem: # Stop the server if we can't contact the sql database # Take care with this, if you set this to false, # AuthMe will automatically disable and the server won't be protected! stopServer: true console: # Remove passwords from console? removePassword: true # Copy AuthMe log output in a separate file as well? logConsole: true captcha: # Enable captcha when a player uses wrong password too many times useCaptcha: false # Max allowed tries before a captcha is required maxLoginTry: 5 # Captcha length captchaLength: 5 tempban: # Tempban a user's IP address if they enter the wrong password too many times enableTempban: false # How many times a user can attempt to login before their IP being tempbanned maxLoginTries: 10 # The length of time a IP address will be tempbanned in minutes # Default: 480 minutes, or 8 hours tempbanLength: 480 # How many minutes before resetting the count for failed logins by IP and username # Default: 480 minutes (8 hours) minutesBeforeCounterReset: 480 recoveryCode: # Number of characters a recovery code should have (0 to disable) length: 8 # How many hours is a recovery code valid for? validForHours: 4 BackupSystem: # Enable or disable automatic backup ActivateBackup: false # Set backup at every start of server OnServerStart: false # Set backup at every stop of server OnServerStop: true # Windows only mysql installation Path MysqlWindowsPath: 'C:\Program Files\MySQL\MySQL Server 5.1\' tente essa config Problema se manteve =\
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 vc esta usando algum pl q esta dando conflito Agora, RonaldoPT disse: Problema se manteve =\ 1
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 (editado) tente usar a versao mais rescente do authme reloaded Editado Outubro 21, 2018 por wDaark 1
Nuno M. Postado Outubro 21, 2018 Autor Denunciar Postado Outubro 21, 2018 7 minutos atrás, wDaark disse: vc esta usando algum pl q esta dando conflito Tem como eu saber qual é? Ou única forma é tirar todos e colocar 1 a 1 ? ;=;
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Agora, RonaldoPT disse: Tem como eu saber qual é? Ou única forma é tirar todos e colocar 1 a 1 ? ;=; qual a versao do seu authme? 1
Kodinha Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Tente troca de plugin use esse aqui acho que pode resolver https://dev.bukkit.org/projects/rdlogin 1
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 4 minutos atrás, Mark disse: Tente troca de plugin use esse aqui acho que pode resolver https://dev.bukkit.org/projects/rdlogin n recomendo pois tem bugs e é um pl bem antigo, sem atualizações
Kodinha Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 (editado) 4 minutos atrás, wDaark disse: n recomendo pois tem bugs e é um pl bem antigo, sem atualizações Caso ele não queira tem esses aqui https://www.spigotmc.org/resources/superlogin-a-login-system.20324/updates Esse aqui e 2k17 https://www.spigotmc.org/resources/lblogin-system-login-register.50751/ mas ele teve a atualização mysql, e comigo nunca deu bug Editado Outubro 21, 2018 por Mark Arrumando
Nuno M. Postado Outubro 21, 2018 Autor Denunciar Postado Outubro 21, 2018 15 minutos atrás, wDaark disse: qual a versao do seu authme? A ultima atualização.. 14 minutos atrás, Mark disse: Tente troca de plugin use esse aqui acho que pode resolver https://dev.bukkit.org/projects/rdlogin O plugin realmente é bom! Porém problema se manteve.. =\
wDaark Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 (editado) 2 minutos atrás, RonaldoPT disse: A ultima atualização.. O plugin realmente é bom! Porém problema se manteve.. =\ add dc wDaarkDNS#3584 Editado Outubro 21, 2018 por wDaark 1
Kodinha Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 2 minutos atrás, RonaldoPT disse: A ultima atualização.. O plugin realmente é bom! Porém problema se manteve.. =\ Olhe os 2 plugins acima, caso o problema persista e outro plugin que esta fazendo isso 1
DkGaming86 Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Para min também está tendo o mesmo erro...
TequilAxBr Postado Outubro 21, 2018 Denunciar Postado Outubro 21, 2018 Você não deu permissão do AuthMe para membros executarem comandos antes de logarem? .. 1
Nuno M. Postado Outubro 21, 2018 Autor Denunciar Postado Outubro 21, 2018 46 minutos atrás, TequilAxBr disse: Você não deu permissão do AuthMe para membros executarem comandos antes de logarem? .. Não.. @OFF: Agradeço ajuda de todos, porém eu acabei tirando todos plugins e testando 1 a 1.. o erro estava em um conflito entre o AuthMe e um plugin próprio feito exclusivamente para o meu servidor.. o mesmo já está a ser corrigido pelo criador!
Reset Postado Dezembro 15, 2018 Denunciar Postado Dezembro 15, 2018 Seu tópico foi marcado como Inativo. Para reverter está ação, entre em contato com a equipe de Moderação.
Posts Recomendados