COCOAUTH V1.0.0 — COMPLETE MASTER DEVELOPMENT PROMPT
- PROJECT OVERVIEW
Develop a professional, production-ready Minecraft authentication and account-security plugin named CocoAuth.
Brand: CocoAuth Version: 1.0.0 Tagline: Secure Every Connection.
Plugin Type: Minecraft Server Authentication & Security Plugin Primary Language: Java Build System: Gradle or Maven Main Goal: Deliver a fully functional, compiled, installable ".jar" file.
CocoAuth must be a complete authentication system with advanced account security, CAPTCHA verification, premium authentication, email recovery, IP and device intelligence, session management, teleportation controls, an in-game admin GUI, database support and a developer API.
This is a complete V1.0 release. Do not postpone any feature listed in this specification to future versions.
---
- IMPORTANT DEVELOPMENT RULES
- Build actual working functionality, not mockups or placeholder classes.
- Do not create a website, web dashboard or external control panel.
- Do not add Discord integration, Discord account linking or Discord verification.
- Do not add Guardian Mode.
- All player-facing administration must be available inside Minecraft.
- Keep the architecture modular, secure, maintainable and performance-efficient.
- Never store plaintext passwords, email verification tokens or session secrets.
- Use asynchronous database and email operations where appropriate.
- Do not block the main server thread with database, network or file operations.
- Every command, permission, GUI action and configuration option must work.
- Provide meaningful error messages and proper exception handling.
- Do not claim compatibility with a platform or Minecraft version unless it has actually been built and tested.
- Do not include fake features or simulated security checks.
- If a feature cannot be implemented reliably, document the limitation instead of pretending it works.
---
- AUTHENTICATION SYSTEM
Implement the following player commands:
- "/register <password> <confirm-password>"
- "/login <password>"
- "/logout"
- "/changepassword <old-password> <new-password>"
- "/unregister"
- "/auth help"
Requirements:
- Secure password hashing using BCrypt or Argon2.
- Never save plaintext passwords.
- Configurable minimum password length and password-strength rules.
- Password confirmation during registration.
- Prevent duplicate account registration.
- Configurable registration and login timeouts.
- Configurable authentication messages.
- Password changes must invalidate existing trusted sessions.
- Secure account deletion with confirmation.
- Prevent unauthenticated players from accessing protected server features.
- Handle database failures safely.
---
- CAPTCHA VERIFICATION SYSTEM
Create a custom six-character CAPTCHA system.
CAPTCHA format
- Exactly 6 characters.
- Uppercase English letters and numbers.
- Avoid confusing characters where possible.
- Generate a different CAPTCHA for each verification attempt.
CAPTCHA display
- Display the CAPTCHA using a Minecraft filled map.
- Implement a custom map renderer.
- Use a clean, readable CAPTCHA design.
- Do not expose the correct CAPTCHA answer to the client.
- The player must read the map and submit the code through the plugin's verification interface.
Verification flow
- Player joins the server.
- Player is teleported to the configured CAPTCHA location.
- A filled map containing the CAPTCHA appears.
- Player enters the six-character code.
- The server validates the answer.
- If correct, display "Verification Successful!".
- Teleport the player to the authentication lobby.
- Display the welcome and login interface.
CAPTCHA security
- Configurable maximum attempts.
- Configurable CAPTCHA expiration.
- Configurable timeout.
- Generate a new CAPTCHA after an incorrect answer.
- Prevent CAPTCHA bypass through commands, inventory manipulation or client-side modifications.
- Allow CAPTCHA to be independently enabled or disabled.
- Log CAPTCHA failures and suspicious activity.
Keep CAPTCHA location completely separate from the login location.
---
- WELCOME AND LOGIN INTERFACE
Create a professional authentication interface.
Include:
- Welcome title and subtitle.
- Player name placeholders.
- Login and registration instructions.
- Action bar messages.
- Boss bar.
- Sounds and visual feedback.
- Optional inventory-based GUI.
- Configurable colors and formatting.
- Custom messages and language files.
- Optional hologram integration where supported.
Use configurable messages such as:
"Welcome to the server, %player%!"
"Please login using /login <password>."
"Verification Successful!"
"Player Already Online!"
Do not claim that a normal server plugin can display a native operating-system popup. Use supported Minecraft interfaces.
---
- PREMIUM AND OFFLINE ACCOUNT SUPPORT
Support both:
- Premium Minecraft accounts.
- Offline/cracked Minecraft accounts.
Premium authentication
- Automatically authenticate legitimate premium players when their identity has been verified by the trusted server authentication system.
- Never trust a client-provided premium claim.
- Support online-mode identity verification.
- Prevent username impersonation.
Offline authentication
- Support normal registration and login using passwords.
- Store account information securely.
- Prevent account duplication and unauthorized access.
Premium authentication must be configurable.
---
- ADVANCED SESSION MANAGEMENT
Implement a secure trusted-session system.
Features:
- Remember trusted devices/sessions.
- Configurable session duration.
- Session expiration.
- Session revocation.
- Revoke all sessions for a player.
- Multiple-session detection.
- Session history.
- Secure random session identifiers.
- Invalidate sessions after password changes.
- Detect suspicious login patterns.
- Allow administrators to inspect and revoke sessions.
Do not rely on IP address alone to identify a trusted device.
---
- FAILED LOGIN AND ACCOUNT PROTECTION
Default security policy:
- Maximum incorrect password attempts: 3
- After the third incorrect attempt: kick the player.
- Rejoin cooldown: 120 seconds.
- No permanent account lock.
Requirements:
- Configurable attempt limits.
- Configurable cooldown.
- Server-side enforcement.
- Log failed login attempts.
- Track repeated suspicious activity.
- Apply rate limits to login and registration requests.
- Design account-based restrictions carefully so attackers cannot permanently lock out another user's account.
---
- DUPLICATE USERNAME PROTECTION
Implement strict duplicate-login protection.
If a player with the same authenticated account is already online:
- Reject the new connection.
- Do not disconnect the original player.
- Do not replace the original player's session.
- Display "Player Already Online!".
- Log the duplicate-login attempt.
For proxy networks, implement network-wide session coordination and stale-session cleanup.
---
- IP INTELLIGENCE — ADMIN ONLY
Provide administrators with account IP intelligence.
Features:
- IP address.
- Approximate country.
- Approximate region/state.
- Approximate city, when available.
- ISP, when available.
- First login IP.
- Last login IP.
- Previous IP history.
- Login history.
- IP change alerts.
- Suspicious network activity.
Requirements:
- Use a configurable IP-geolocation provider.
- Cache lookup results.
- Handle provider failures gracefully.
- Keep geolocation information approximate.
- Never claim that IP intelligence reveals a player's exact home address or live physical location.
- Do not expose IP information to ordinary players.
- Restrict sensitive commands with permissions.
- Audit administrator lookups.
- Provide configurable data-retention policies.
---
- DEVICE INTELLIGENCE
Collect only information that is legitimately available through the server or supported integrations.
Features:
- Java or Bedrock identification.
- Minecraft version.
- Client type, when detectable.
- Operating system, only if reliably available.
- Device category, where supported.
- First seen and last seen.
- Trusted-session information.
- Device/session history.
- Session revocation.
Do not implement invasive hardware fingerprinting or invent unavailable device identifiers.
Support Geyser/Floodgate integration where compatible.
---
- EMAIL VERIFICATION AND ACCOUNT RECOVERY
Email is the only external account-recovery method.
Do not implement Discord integration.
Features:
- Email registration verification.
- Email verification tokens.
- Password recovery.
- Password reset.
- New-device login notifications.
- Suspicious-login notifications.
- Account-change confirmation.
- Recovery verification.
- Configurable email templates.
- SMTP support.
Security requirements:
- Secure SMTP credential storage.
- Expiring, single-use verification tokens.
- Rate limiting.
- Secure token generation.
- Never store recovery tokens in plaintext where avoidable.
- Use generic public recovery responses to prevent account enumeration.
- Handle SMTP failures without corrupting account data.
Provide a complete configurable "email.yml".
---
- TELEPORTATION AND LOCATION MANAGEMENT
Support independently configurable locations:
- CAPTCHA location.
- Authentication/login location.
- Main server spawn.
- First-join spawn.
- Fallback spawn.
- Custom post-login destination.
Post-login destination modes
- Last saved player location.
- Server spawn.
- Custom configured location.
- Player home integration, if a supported external plugin is installed.
Requirements
- Save the player's previous survival location before entering the authentication process.
- Never save the CAPTCHA or login lobby as the player's previous survival location.
- Independently configure last-location restoration and spawn behavior.
- Validate world and destination availability.
- Handle deleted or unloaded worlds.
- Provide safe teleportation and fallback handling.
- Support multiple worlds.
- Support configurable teleport delays.
- Prevent unauthorized teleportation before authentication.
Provide commands to set each location.
---
- UNAUTHENTICATED PLAYER RESTRICTIONS
Before successful authentication, configurable restrictions must prevent:
- Movement.
- Chat messages.
- Inventory access.
- Block breaking.
- Block placing.
- Item pickup.
- Item dropping.
- Unauthorized commands.
- Unauthorized interactions.
- PvP.
- Receiving or dealing damage where appropriate.
- Unauthorized teleportation.
Allow only essential authentication commands and CAPTCHA interactions.
Additional options:
- Hide unauthenticated players from authenticated players.
- Configurable restriction messages.
- Configurable exceptions.
- Correctly handle player disconnects and reconnects.
Ensure restrictions do not interfere with the CAPTCHA or authentication interface.
---
- IN-GAME ADMIN GUI
Create a complete inventory-based administration GUI.
There must be no web dashboard.
Main GUI sections
- Player Management.
- Authentication Statistics.
- Active Sessions.
- IP Intelligence.
- Device Intelligence.
- Login History.
- Security Logs.
- CAPTCHA Statistics.
- Location Management.
- Email Settings.
- Database Information.
- Plugin Information.
Player Management
Administrators should be able to:
- Search for players.
- View account information.
- View registration status.
- View authentication status.
- Inspect login history.
- Inspect trusted sessions.
- Revoke sessions.
- Reset passwords through a secure administrative process.
- Unregister accounts with confirmation.
GUI requirements
- Pagination.
- Navigation buttons.
- Back buttons.
- Confirmation screens for destructive actions.
- Permission checks for every sensitive action.
- Configurable item names, descriptions and materials.
- Refresh functionality.
- Proper handling of offline players.
- No unauthorized inventory manipulation.
---
- DATABASE SYSTEM
Support:
Use a clean database abstraction layer so additional database engines can be supported later.
Requirements:
- Prepared statements.
- Connection pooling where appropriate.
- Database migrations.
- Automatic table creation.
- Database backup support.
- Asynchronous database operations.
- Connection failure handling.
- Configurable database credentials.
- Data cleanup and retention policies.
Suggested database tables:
- users
- sessions
- login_history
- security_logs
- player_locations
- devices
- email_verifications
- password_resets
- captcha_statistics
Provide a complete "database.yml".
---
- DEVELOPER API
Provide a documented API for other plugin developers.
Include:
- Check whether a player is authenticated.
- Check whether a player is registered.
- Force player logout.
- Revoke player sessions.
- Register authentication listeners.
- Register logout listeners.
- Register CAPTCHA completion listeners.
- Register failed-login listeners.
- Listen to registration events.
- Add custom authentication restrictions.
Requirements:
- Proper Java interfaces.
- Events and callbacks.
- API documentation.
- Example integration code.
- Stable public API.
- No direct dependency on internal implementation classes.
---
- COMMANDS AND PERMISSIONS
Player commands
- "/register"
- "/login"
- "/logout"
- "/changepassword"
- "/unregister"
- "/auth help"
Administrator commands
- "/auth reload"
- "/auth help"
- "/auth info <player>"
- "/auth playerinfo <player>"
- "/auth ipinfo <player>"
- "/auth deviceinfo <player>"
- "/auth sessions <player>"
- "/auth loginhistory <player>"
- "/auth unregister <player>"
- "/auth changepass <player>"
- "/auth revoke-device <player>"
- "/auth setlogin"
- "/auth setcaptcha"
- "/auth setspawn"
- "/auth setfallback"
- "/auth destination <mode>"
- "/auth captcha enable"
- "/auth captcha disable"
- "/auth stats"
Permissions
- "cocoauth.admin"
- "cocoauth.reload"
- "cocoauth.bypass"
- "cocoauth.unregister"
- "cocoauth.changepass"
- "cocoauth.location"
- "cocoauth.stats"
- "cocoauth.ipinfo"
- "cocoauth.deviceinfo"
- "cocoauth.sessions"
Every sensitive command must have permission checks and security audit logging.
Provide a complete "plugin.yml" or the relevant platform descriptor.
---
- CONFIGURATION FILES
Create clean, documented configuration files.
Required files:
- "config.yml"
- "messages.yml"
- "database.yml"
- "email.yml"
- "captcha.yml"
- "locations.yml"
- "security.yml"
- "sessions.yml"
- "gui.yml"
- "premium.yml"
Every configurable feature must have:
- A clear setting name.
- A sensible default.
- A description.
- Validation.
- Safe fallback behavior.
Do not hardcode settings that administrators should be able to configure.
---
- SERVER PLATFORM ARCHITECTURE
Use a modular architecture with a shared authentication core and platform-specific adapters.
Bukkit-family support
Build and verify support for compatible versions of:
Additional support
- Folia through a dedicated region-safe scheduler implementation.
- Velocity through a separate proxy module.
- BungeeCord through a separate proxy module.
- Geyser/Floodgate integration where compatible.
Fabric, Forge and NeoForge require separate mod implementations. Do not describe them as ordinary Bukkit plugins.
Minecraft version support
Design the architecture for:
- Minecraft 1.20.x.
- Minecraft 1.21.x.
- Minecraft 26.x, where the platform APIs and Java runtime permit.
Verify the exact supported versions against actual server APIs and Java requirements.
Do not claim that one compiled JAR supports every platform and every version without testing.
Where necessary, provide separate compatible JAR builds using the same shared core.
---
- PERFORMANCE AND SECURITY REQUIREMENTS
- Avoid unnecessary repeating tasks.
- Avoid synchronous database queries on the main thread.
- Use secure password hashing.
- Validate all player input.
- Protect against SQL injection.
- Protect against command abuse.
- Rate-limit sensitive operations.
- Prevent session-token leakage.
- Secure email recovery.
- Audit administrator actions.
- Handle server shutdown safely.
- Clean up player sessions and listeners.
- Avoid memory leaks.
- Use safe concurrency practices.
- Handle proxy disconnections and reconnects.
- Make the plugin compatible with normal server restart procedures.
---
- PROJECT STRUCTURE
Use a clean modular project structure.
Suggested layout:
"CocoAuth/"
- "core/"
- "api/"
- "platform-bukkit/"
- "platform-paper/"
- "platform-folia/"
- "platform-velocity/"
- "platform-bungeecord/"
- "database/"
- "security/"
- "captcha/"
- "email/"
- "gui/"
- "integrations/"
- "docs/"
- "tests/"
Adjust the structure if a better architecture is justified.
Do not place every class in one package or one source file.
---
- TESTING REQUIREMENTS
Before release, test:
- First-time registration.
- Correct login.
- Incorrect password.
- Three failed attempts and kick.
- 120-second rejoin cooldown.
- Password change.
- Account deletion.
- CAPTCHA generation.
- CAPTCHA verification.
- CAPTCHA expiration.
- CAPTCHA retry.
- Premium authentication.
- Offline account authentication.
- Duplicate username protection.
- Trusted sessions.
- Session expiration.
- Session revocation.
- Email verification.
- Password recovery.
- Database connection failure.
- SQLite operation.
- MySQL operation.
- MariaDB operation.
- Teleportation and fallback.
- Unauthenticated restrictions.
- Admin permissions.
- GUI navigation.
- IP intelligence provider failure.
- Server restart and recovery.
- Proxy session coordination, where implemented.
Add automated unit and integration tests wherever practical.
Do not mark an untested feature as successfully tested.
---
- FINAL DELIVERABLES
The final output must include:
A. Installable plugin
A real compiled JAR file:
"CocoAuth-1.0.0.jar"
Place the verified build in:
"build/libs/CocoAuth-1.0.0.jar"
B. Complete source code
- Full Java source.
- Gradle/Maven build files.
- Platform adapters.
- API.
- Database layer.
- Configuration resources.
- Plugin descriptors.
- Tests.
C. Documentation
Create:
- "README.md"
- "INSTALLATION.md"
- "CONFIGURATION.md"
- "COMMANDS.md"
- "PERMISSIONS.md"
- "DATABASE_SETUP.md"
- "EMAIL_SETUP.md"
- "API_DOCUMENTATION.md"
- "COMPATIBILITY.md"
- "CHANGELOG.md"
D. Release information
Clearly provide:
- Plugin version.
- Supported Minecraft versions.
- Supported server platforms.
- Required Java version.
- Required dependencies.
- Optional integrations.
- Installation instructions.
- Configuration instructions.
- Known limitations.
- Tested features.
- Untested features.
---
- FINAL BUILD AND RELEASE INSTRUCTIONS
Follow this development sequence:
Phase 1: Project architecture and core authentication.
Phase 2: CAPTCHA and player authentication flow.
Phase 3: Premium authentication and session management.
Phase 4: Email verification and recovery.
Phase 5: IP intelligence and device intelligence.
Phase 6: Teleportation and unauthenticated restrictions.
Phase 7: Admin GUI and management commands.
Phase 8: Database implementations and developer API.
Phase 9: Platform adapters and compatibility testing.
Phase 10: Security testing, bug fixing and final release.
Do not stop after generating source code.
Run the actual build process, resolve compilation errors, execute available tests and verify that the output JAR exists and is a valid plugin artifact.
If the environment supports Minecraft server testing, install the JAR on a test server and verify the core player flows.
If you cannot compile or test a particular feature or platform, clearly state that limitation. Never create an empty, fake or renamed JAR and present it as a working plugin.
FINAL OBJECTIVE
Deliver CocoAuth V1.0.0, a complete, professional Minecraft authentication and account-security plugin.
All features included and also add discord integration for server owners so that they can keep track of logging activities in their discord server