Getting started

Stand up a LitheraRP dedicated server, boot it once so the configs seed, log in as an operator, and verify the gamemode reports a clean status.

Early access

Community hosting is in open beta. Back up your Data folder before every planned restart. The save schema is not yet frozen.

Requirements

  • An s&box dedicated server install (Linux or Windows).
  • A machine you control to run it on (own hardware, a rented server, or a local host session for testing).
  • A LitheraRP Creator account with a server entry on the Dashboard and its signing key (see Register your server).
  • A map. RP Downtown is the recommended default; any custom map works as long as you wire its placements (see Custom map).
  • An account with operator or admin permission for configuration tasks.

Hardware sizing depends on the slot count you intend to support. Validate on a low-slot configuration first and scale up as you measure CPU and memory headroom.

First-launch checklist

  1. Start a server using LitheraRP as the active game with +game litherastudio.litherarp.
  2. Pick a map. RP Downtown (thieves.rpdowntown3t) is the recommended default; a custom map works too if you have wired its placements (see Custom map).
  3. Let the server boot once. The gamemode seeds default config files into the server Data folder.
  4. Join with an operator account.
  5. Open the admin menu with litherarp.admin or your configured admin bind.
  6. Open the Server Config workspace with /config in chat.
  7. Run litherarp.config_status from the server console and confirm no critical errors.

Install the dedicated server

The s&box dedicated server is published on Steam as app id 1892930 and pulled with SteamCMD.

1# Install the s&box dedicated server
2$ steamcmd +force_install_dir ./sbox-server +login anonymous +app_update 1892930 validate +quit
3
4# Launch with the LitheraRP gamemode
5$ cd sbox-server
6$ ./sbox-server +game litherastudio.litherarp thieves.rpdowntown3t
1# Run as administrator
2PS> cd C:\sbox-server
3PS> .\steamcmd.exe +force_install_dir C:\sbox-server +login anonymous +app_update 1892930 validate +quit
4
5PS> .\sbox-server.exe +game litherastudio.litherarp thieves.rpdowntown3t
Refer to s&box official docs

The exact dedicated server installation steps may evolve as s&box matures. Cross-check the launch flags against the official dedicated server documentation if your build behaves differently.

Register your server

Every LitheraRP community server authenticates with the backend through a signing key tied to a server entry on the Creator Dashboard. Create the entry, copy the key, paste it into your s&box server, then boot.

  1. Sign in at creator.litherarp.com/dashboard with Steam.
  2. Click New server, give it a name, leave the cluster key as default unless you have a reason to change it, and submit.
  3. The Dashboard shows the signing key exactly once. Copy it now: there is no way to read it back later.
  4. Apply the key to your dedicated server. Two options, both shown in the reveal panel right after creation:
    • In-game console: run the litherarp.creator.configure command the Dashboard generates for you (it embeds the backend URL, the authorization header, and the key).
    • Config file: drop the JSON the Dashboard displays into configs/creator_server.json in the server Data folder.
  5. Restart the gamemode if it was already running. The server starts sending heartbeats and appears as Online on the Dashboard within a few seconds.
Lost the key

Open the server entry on the Dashboard and use Rotate for a zero-downtime swap (the old key keeps working briefly while you apply the new one) or Regenerate to invalidate the old key immediately. The new key is shown once, same as the first time.

Supported map

RP Downtown ships as the default map. The current map package is thieves.rpdowntown3t. Custom maps are fully supported.

Other maps

The gamemode exposes map-override hooks for spawn points, NPC placement, doors, properties, taxi paths, and economy rules. Bringing a new map up is on you: place the doors, NPCs, spawns, and GPS points yourself, then wire the per-map overrides through the config files. See Custom map for the full workflow.