Minecraft plugin AuthMe

🔌 About AuthMe

AuthMe — is a Minecraft plugin for servers that provides account authentication, session login, optional two‑factor authentication (2FA), and database-backed storage.

🎯 Purpose

AuthMe secures player accounts on Paper/Spigot Minecraft servers by requiring players to register and authenticate before they can interact with the world. It addresses username‑stealing on offline-mode servers and adds an extra layer of protection on online-mode servers.

AuthMe is suitable for servers that need: account protection, session control, multiple hashing algorithms, and database persistence.

⚙ Main features

• Player registration and login workflow (authentication gate on join). (Confirmed in official sources)
• Session Login: keep players authenticated for a session so repeated /login is not required. (Confirmed)
• Two‑factor authentication (2FA) support. (Confirmed)
• MySQL and SQLite backend support. (Confirmed)
• Multiple supported password hashing algorithms (SHA256, ARGON2, BCRYPT, PBKDF2, and others). (Confirmed)
• Importers/converters for older auth plugin databases and a built‑in converter (e.g., auths.db → SQL). (Confirmed)
• Country whitelist/blacklist (GeoIP integration via MaxMind). (Confirmed)
• Anti‑bot features and configurable protections for unauthenticated players. (Confirmed)
• Optional integration points: ProtocolLib required for some protections (inventory protection). (Confirmed)
• Admin tools: database converter commands and force‑login features. (Confirmed)

🧩 Who is it for

AuthMe is aimed at server owners and admins running Paper or Spigot (1.16.5+ recommended) who need an authentication gate, session handling, support for external databases, and optional 2FA. It is commonly used on offline-mode servers or on networks that want extra account safety.

🏗 Usage examples

• Use AuthMe to require /register and /login before players can move, place blocks, or access inventory.
• Store credentials in MySQL for multi‑server setups or use SQLite for a single server.
• Enable 2FA for staff accounts and session login for regular players.
• Run the built‑in converter to migrate an old auth database to the current schema: /authme converter. (Confirmed)

⌨️ Commands

Note: The plugin exposes more user and admin commands (register, login, logout, etc.). The complete, authoritative command list is provided in the official documentation and repository. Only confirmed commands are listed in this table.

🔐 Permissions

The plugin also defines many single permission nodes for fine‑grained control; refer to the official permission list for details.

⚙ Installation

📥 Installation

• Download the AuthMe jar from an official source.
• Place the jar into your server's plugins/ folder.
• Restart the server (full restart recommended).
• On first run, AuthMe will create its plugin folder and configuration files.

📦 Dependencies

• Java 17+ is required to run current releases. (Confirmed)
• Paper or Spigot (recommended minimum: 1.16.5+, per repository). (Confirmed)
• ProtocolLib — optional, required for some protections (e.g., inventory protection). (Confirmed)

🧾 Configuration

• AuthMe generates configuration and message files on first run (config files and translation files). (Confirmed)
• Configuration controls authentication behaviour, hashing algorithm, database settings, 2FA, GeoIP options, and session parameters. (Confirmed)
• Database support: SQLite (local) and MySQL (remote) are supported; MySQL is configurable in the plugin settings. (Confirmed)

🧠 Additional information

Known integrations and compatibility

• Officially compatible with many server plugins (Citizens2, CombatTag, ChestShop, etc.). (Confirmed)
• AuthMeBungee exists to bridge AuthMe with BungeeCord/Waterfall proxies for multi‑server setups. (Confirmed)
• GeoIP features rely on MaxMind data. (Confirmed)

Known limitations & notes

• Running a full server restart is recommended after install or config changes. Use of /reload is not recommended with many modern plugins (general best practice). (Community guidance; verify on your environment.)
• Requirements for modern releases include Java 17+ and a supported Paper/Spigot build. (Confirmed)

FAQ

Q: Does AuthMe support MySQL? A: Yes — AuthMe supports both MySQL and SQLite backends. (Confirmed)

Q: Does AuthMe support 2FA? A: Yes — Two‑factor authentication is supported. (Confirmed)

Q: Is ProtocolLib required? A: ProtocolLib is optional. Some features (like inventory protection until login) require ProtocolLib. (Confirmed)

Q: Can I use AuthMe with a Bungee/Velocity network? A: Yes — AuthMeBungee (bridge) exists to integrate AuthMe with BungeeCord/Waterfall proxies. (Confirmed)

Q: Does AuthMe collect anonymous usage statistics? A: Yes — AuthMe reports stats to bStats if enabled. (Confirmed)

Support & resources

AuthMe is open‑source and maintained on GitHub; official distribution pages and community support are available. (Confirmed)

⚠️ When to use AuthMe

Choose AuthMe when you need a mature, configurable authentication gate for Paper/Spigot servers with DB backends, 2FA options, session handling, and importer tools. AuthMe is widely used and actively developed; verify compatibility with your server core and Java version before deployment.