StaffAuth
StaffAuth protects staff accounts marked by a permission until they authenticate after joining. Passwords are stored as BCrypt hashes in a Typewriter artifact; plaintext passwords are never accepted through commands or chat.
Entries
- Staff Auth Config — permissions, security limits, messages and timeouts.
- Staff Auth Menu — keypad GUI and Typewriter layout configuration.
- Staff Auth Data — BCrypt password storage. Keep the generated artifact ID stable after deployment.
Commands
/staffauth or /staffauth login opens the authentication interface for the player. The other supported subcommands are:
/staffauth register/staffauth logout/staffauth status/staffauth reset <player>— requires the configured admin permission./staffauth force-logout <player>— requires the configured admin permission.
Passwords must be entered in the GUI/Dialog interface. StaffAuth does not expose password arguments in commands or chat.
Permissions
| Permission | Purpose |
|---|---|
security.admin | Marks a player as staff and requires authentication. |
security.staffauth.admin | Allows password reset and force logout operations. |
Distribution variants
| Variant | Typewriter | Java bytecode | Placeholders |
|---|---|---|---|
| Public | Official published Typewriter API | Built with JDK 25, target Java 21 | Official PlaceholderAPI |
| Custom | BTC/local Typewriter API | Java 25 | BTC MiniPlaceholders |
The public build may run on servers where legacy compatibility is permitted, but StaffAuth itself does not include a legacy fallback. Both variants use the modern Paper/Folia-safe integration.