> ## Documentation Index
> Fetch the complete documentation index at: https://pyrelight.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> What actually happens the first time each kind of player connects.

rLogin needs no configuration to work. This page is here so you know what to
expect — and so you can tell whether it is behaving correctly.

## A premium player connects

They see the vanilla **"Encrypting…"** screen for a moment, then land in the
world with a message:

> Premium account detected — you were logged in automatically.

No commands, no password, nothing to remember. Behind that moment, rLogin:

1. Held their login packet and asked Mojang whether the name is a real account.
2. Sent an encryption request, which their client answered by contacting
   Mojang on its own — the standard exchange every online-mode server does.
3. Confirmed with Mojang's `hasJoined` that this client really owns the account.
4. Handed the server the **real UUID and signed skin** that came back.

<Check>
  Turn on `general.debug` in `config.yml` to see each of those decisions
  explained in the console, one line per connection.
</Check>

## A non-premium player connects

They arrive frozen where they spawned, and are told to register:

> Register with /register \<password> \<repeat password>

Until they do, they cannot move, chat, break blocks, take damage or run any
command other than the ones in `limbo.allowed-commands`. After `/register`,
every later visit is just `/login <password>`.

<Note>
  If they take longer than `limbo.login-timeout-seconds` (60 by default), they
  are disconnected. A connection parked forever at the login prompt still holds
  a player slot.
</Note>

## They come back ten minutes later

They are not asked again. A player who logged in and reconnects from the same
address within `session.remember-me-minutes` gets their session restored.

Read [Sessions](/rlogin/features/sessions) before raising that window — it
trusts an *address*, and addresses are shared.

## Someone takes a premium name

By default they can't. `premium.protect-premium-names` refuses `/register` on
any name that belongs to a real Minecraft account, so its owner never loses the
ability to auto-login with it.

If you turn that off, rLogin still keeps the two apart:
[the real owner and the impostor end up as separate
accounts](/rlogin/features/cracked-auth#when-a-name-is-already-taken), and
`/rlogin changeuuid` can move data between them.

## Try it yourself

<CodeGroup>
  ```bash Check your own status theme={null}
  /premium
  ```

  ```bash See an account (admin) theme={null}
  /rlogin info Notch
  ```

  ```bash Reload config and messages theme={null}
  /rlogin reload
  ```
</CodeGroup>

## Next

<CardGroup cols={2}>
  <Card title="Premium auto-login" icon="circle-check" href="/rlogin/features/premium-auth">
    How verification works, and which UUID players end up with.
  </Card>

  <Card title="All commands" icon="terminal" href="/rlogin/reference/commands">
    Player and admin commands in one table.
  </Card>
</CardGroup>