> 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/readme.md).

# Welcome

FastLoginPlus (FLP) identifies **premium** players on **offline-mode** servers using authentication plugins and enables Mojang verification for **passwordless** login. It also offers anti-bot protection, premium skins and UUIDs, and an offline whitelist, with support for SkinsRestorer and Geyser/Floodgate.

## An example

Imagine your server uses an authentication plugin that asks players for a password. A premium player first logs in to their existing account with its password, then agrees to bind their premium identity. On later joins, FLP verifies that identity and, when server policy and account state allow it, the authentication plugin can log the player in without a password. Other players can continue to use password login.

Use the sidebar to explore supported platforms and authentication plugins, choose an installation guide for your server, and learn about account binding and configuration.

[Downloads and releases](https://github.com/Hayston1001/FastLoginPlus/releases) | [Changelog](https://github.com/Hayston1001/FastLoginPlus/blob/main/CHANGELOG.md) | [Issues](https://github.com/Hayston1001/FastLoginPlus/issues) | [Source](https://github.com/Hayston1001/FastLoginPlus)


---

# 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/readme.md?ask=<question>&goal=<user_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.