FastLoginPlus

中文→

Auto-detect and login premium Minecraft players on offline-mode servers — no password needed, no client mods required. Actively maintained fork of FastLogin.

Many Minecraft servers run in "offline mode" (no Mojang authentication) to allow cracked clients, but this forces all players — including those with paid accounts — to type a password every time they join. FastLoginPlus checks each player against Mojang's API on login: if they own the game, they skip the auth plugin entirely and get their real UUID and skin automatically.

Works with ProtocolLib. ForDetails→

Features

Core (from FastLogin)

• Auto-detect premium accounts via Mojang API — skip auth plugin login
• Premium UUID and skin forwarding
• Auto-register new premium players
• BungeeCord/Velocity proxy support
• Bedrock player support via Geyser/Floodgate

Improvements (new in FastLoginPlus)

• AuthMeReloaded 6.0 compatibility — auto-detects AuthMeReloaded version without user config
• Offline Whitelist — block unknown cracked players, allow premium via Mojang API. Replaces upstream switchMode which kicked new premium players
• Multi-layer anti-bot — per-IP rate limiting, burst detection, temporary IP ban, trusted IP whitelist, and FastLoginAntiBotEvent for plugin integration
• Folia support — dedicated module with Folia-compatible scheduler
• Auto update check — checks GitHub Releases on startup and periodically; notifies OPs in-game when a new version is available
• Multi-language — built-in English and Chinese, custom language files supported
• Per-platform config templates — Bukkit/Folia and BungeeCord/Velocity each generate their own config file: proxies get a trimmed template without backend-only keys, and backend comments mark the keys that lose effect behind a proxy
• SQLite on proxy platforms — BungeeCord and Velocity now bundle SQLite JDBC driver; upstream only supports MySQL/MariaDB on proxies
• Session retry — Mojang verification retries on network errors instead of failing immediately
• SkinsRestorer compatibility — no longer overrides skins set via SkinsRestorer
• Log readability — human-readable login flow messages instead of raw packet dumps

Quick Start

Spigot/Paper: drop FastLoginPlusBukkit.jar an Auth pl and ProtocolLib 5.3+ in plugins/ → set online-mode=false

Folia: drop FastLoginPlusFolia.jar an Auth pl and ProtocolLib 5.3+ in plugins/ → set online-mode=false

Proxy Configuration

When running behind a proxy (BungeeCord or Velocity), the proxy must be configured to forward player information to backend servers. FLP relies on this to deliver login commands via plugin messages.

Proxy ID setup (click to expand)

The backend only accepts login commands from trusted proxies. Each proxy has a unique UUID that must be added to the backend's whitelist:

• Velocity — FLP auto-generates a UUID to plugins/fastloginplus/proxyId.txt on first start. Copy the UUID from that file.
• BungeeCord — uses BungeeCord's own instance UUID from bungee/config.yml (the connection_uuid field).

Paste the UUID into plugins/fastloginplus/allowed-proxies.txt on every backend server, one UUID per line. Restart the backends after adding the UUID.

Velocity

Setting	Value	Why
velocity.toml → player-info-forwarding-mode	modern	Required. Without this, Velocity does not forward UUIDs, skins, or IPs — FLP's plugin messages will never reach the backend.
velocity.toml → online-mode	false	FLP handles authentication per-connection via forceOnlineMode(); the proxy should not authenticate by default.
Backend server.properties → online-mode	false	The proxy handles authentication; the backend must not repeat it.
Backend paper-global.yml → proxies.velocity.online-mode	false	Must match velocity.toml's online-mode.

BungeeCord

Setting	Value	Why
config.yml → ip_forward	true	Required. Without this, BungeeCord does not forward UUIDs, skins, or IPs — FLP's plugin messages will never reach the backend.
config.yml → online_mode	false	FLP enables per-connection via connection.setOnlineMode(true); the proxy should not authenticate by default.
Backend server.properties → online-mode	false	The proxy handles authentication; the backend must not repeat it.

Database Storage

In standalone mode (no proxy), the database (FastLogin.db by default) is stored on each backend server under plugins/fastloginplus/.

In proxy mode (BungeeCord/Velocity), the database is stored only on the proxy. Backend servers do not create a database — they simply execute the login/register commands sent by the proxy via plugin messages. /flp premium and /flp cracked commands on the backend forward to the proxy, and the proxy handles all profile reads and writes.

Configuration Templates

FLP ships two config templates; each platform generates its config.yml from the one that matches its role:

Template	Used by	Contents
config.yml (backend)	Bukkit, Folia	All keys. Comments mark which keys have no effect (or only partial effect) when the server runs behind a proxy — e.g. database, anti-bot, Floodgate keys are ignored on a proxy backend because the proxy owns those functions.
config-proxy.yml (proxy)	BungeeCord, Velocity	Proxy-relevant keys only. Backend-only keys (verifyClientKeys, respectIpLimit) are omitted, and comments describe the proxy's role (decision maker: Mojang API queries, database, force-login forwarding).

The file on disk is always named config.yml. Copying a config file between a proxy and a backend is safe: each platform regenerates the file structure from its own template on startup while preserving your values, and keys missing from the new template are simply dropped (they had no effect there anyway).

Environment

Platform	Java	Notes
Spigot / Paper	8+	Requires ProtocolLib 5.3+
Folia	21+	Requires ProtocolLib 5.3+
BungeeCord / Waterfall	17+	—
Velocity	17+	—

An auth plugin is required on the backend (e.g. AuthMe, LoginSecurity, CrazyLogin). SeeFullList→

AuthMeReloaded Support

FastLoginPlus supports both AuthMeReloaded 5.x and 6.0. AuthMeReloaded 6.0 adds the preJoin dialog (Paper) and enablePremium configuration, for which FLP automatically enables enablePremium: true and unregisters AuthMe's own premium verification listener. No manual configuration is needed.

Geyser/Floodgate Support

FastLoginPlus works with Geyser to allow Bedrock players to join your offline-mode Java server.

• Geyser only — Bedrock players join without Xbox authentication. FLP treats them as regular Java players; premium auto-login works if the username matches a paid Java account.
• Geyser + Floodgate (recommended) — Bedrock players authenticate via Xbox Live, and their usernames are prefixed (e.g. Steve → .Steve). This prevents FLP from mistaking a Bedrock player for a premium Java account and avoids username conflicts between platforms.

Recommendation: Install Floodgate alongside Geyser for better security and identity separation. FLP does not require Floodgate to function, but it is strongly recommended when both Java and Bedrock players share the same server.

Version requirements: Geyser requires Java 21+ to run. Geyser-Spigot requires a Paper/Spigot server on 1.20.5 or above. Servers below 1.20.5 can still use Geyser by installing ViaVersion on the backend and running Geyser on a proxy (Velocity/BungeeCord), or by using Geyser-Standalone with ViaVersion. ViaVersion allows the server to accept newer Java clients, which Geyser uses as the translation target. See Geyser supported versions for details.

Commands & Permissions

Command	Description	Permission	Default
/flp premium [player]	Mark as premium	fastloginplus.bukkit.command.premium	true
/flp cracked [player]	Mark as cracked	fastloginplus.bukkit.command.cracked	op
/flp delete <player>	Delete player record	fastloginplus.bukkit.command.delete	op

Add .other suffix for targeting other players (default: op).

When a player switches from premium to cracked via /flp cracked, FLP will automatically purge the player’s records stored in AuthMeReloaded, ensuring the player can log in normally with their own password upon rejoining. Without this cleanup process, AuthMeReloaded will prompt the player for login credentials after they re-enter the server. However, when the player previously joined as a premium user, FLP automatically registered their account with a random password unknown to the player.
For login plugins other than AuthMe, FLP does not have equivalent handling logic for the time being, requiring manual intervention.

PlaceholderAPI

Placeholder	Values	Description
%fastloginplus_status%	Premium, Cracked, Unknown	Authentication status
%fastloginplus_is_premium%	true, false	Whether the player passed premium verification
%fastloginplus_floodgate%	Java, Bedrock, Linked, Unknown	Connection platform (Java vs Bedrock via Geyser/Floodgate)

License

MIT · Originally by games647 · Maintained by Hayston