> For the complete documentation index, see [llms.txt](https://hayston.gitbook.io/flp-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hayston.gitbook.io/flp-wiki/understand-flp/introduction.md). # Features and boundaries FLP is an actively maintained fork of [FastLogin](https://github.com/TuxCoding/FastLogin). It integrates identity verification with an authentication plugin; it is not a replacement for that plugin or a way to give an unverified client a premium identity. ## What it does * Selects Java connections that need Mojang verification, then uses the server or proxy's login handshake to establish ownership. * Coordinates automatic registration and passwordless login where policy and account ownership allow it. Existing password accounts do not become ownerless just because their names match paid accounts. * Maintains premium/cracked records and optional admission for known offline names. * Selects premium or offline connection UUIDs, forwards skins, and respects supported SkinsRestorer custom skins. * Supports independent Bukkit/Folia servers and BungeeCord/Velocity networks. Fabric 26.2 uses a separate Velocity/EasyAuth backend integration. * Integrates Floodgate identities within each platform's supported limits. * Provides connection limits, English/Chinese messages, update checks and backend management commands. ## What it does not do * It does not sell or supply Minecraft accounts, authenticate a name by spelling alone, or turn an offline client into an authenticated Java client. * It does not automatically migrate inventories, worlds, permissions or other plugins' records between UUIDs. * It does not replace Geyser, Floodgate, the authentication plugin, forwarding configuration, firewall isolation, or a dedicated anti-DDoS service. * It does not promise that every Minecraft version, auth plugin release, Fabric modpack or database topology works identically. * Account switches do not automatically reconnect players. When needed, the player must reconnect manually to use the new login method. ## The three separate questions 1. **Admission:** may this player enter? For example, `offline-whitelist` rejects an unknown offline name. 2. **Identity:** has this connection proved a Java or Floodgate identity? 3. **Account access:** may that identity open this local authentication account without a password? Passing one question does not answer the others. Start with [requirements](/flp-wiki/understand-flp/requirements.md), then read [login methods](/flp-wiki/login-and-account-management/login.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hayston.gitbook.io/flp-wiki/understand-flp/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.