Name Restrictions

AuthMe supports restrictions and so-called unrestrictions for usernames.

Name Restrictions

Names can be restricted to IP addresses or host names. An example in config.yml:

        # To activate the restricted user feature you need
        # to enable this option and configure the AllowedRestrictedUser field.
        AllowRestrictedUser: true
        # The restricted user feature will kick players listed below
        # if they don't match the defined IP address. Names are case-insensitive.
        AllowedRestrictedUser:
        - admin;127.0.0.1
        - admin;123.45.67.89
        - billy;34.56.78.90

This means that someone may only join as admin if he has the IP address 127.0.0.1 or 123.45.67.89. Attempts to join as admin from any other IP address will be refused. This setting is case-insensitive, i.e. the restrictions also apply for ADMIN, Admin, etc.

To "disable" certain usernames, you can add entries with an impossible address, e.g. "player;8.8.8.8" to refuse anyone joining as Player.

Name Unrestrictions

Conversely, name unrestrictions define usernames that AuthMe will ignore entirely. Example for config.yml:

        # 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!
        UnrestrictedName:
        - npcplayer
        - othernpc

This setting is also case-insensitive. If a player with such a name joins (e.g. npcplayer, or NpcPlayer), AuthMe won't ask the player to log in or register and won't block any commands or actions. This is typically a useful feature for plugins that add NPC players to the game.