Docs / Overview

LitheraRP Creator docs

Everything you need to run a LitheraRP community server: how to launch it, how to configure it, how to customize it, and how to debug it when something looks off. The gamemode is a DarkRP-inspired roleplay mode for s&box.

Early access · community hosting is experimental

LitheraRP is in open beta and ships frequent updates. The save schema is not yet frozen. Take a manual backup of your Data folder before every planned restart. Watch the Discord for breaking-change announcements.

Who this is for

This documentation is for community owners, server admins, technical operators, and anyone planning to host LitheraRP for their own players. Player-facing how-to-play content lives on litherarp.com instead.

Quick facts

  • Gamemode. LitheraRP, a DarkRP-inspired roleplay mode for s&box.
  • Officially supported map. RP Downtown. Custom maps are feasible through the in-game tools (see Custom map).
  • Config model. JSON files written into the server Data folder on first boot. The in-game /config workspace is the recommended editor.
  • In-game admin workspace. Open with /config in chat.
  • Addons. Data and asset packs published as .litrpaddon manifests. See addons.json.
  • Source of truth. English is the canonical language. Translated strings live in localization JSON packs.
  • Default theme. default. A shipped example community theme is minimal-serious-rp.

Learn the shape

If you have never set up the server before, read these in order:

  1. Getting started. Requirements, the first-launch checklist, and the supported-map warning.
  2. Where configs live. The Data folder layout, what gets seeded on first boot, and how the in-game workspace is the safest editor.
  3. Configuration reference. Per-file reference pages for every config the gamemode reads.
  4. Common workflows. Concrete recipes such as adding a new RP name, a new emergency service, a runtime map door, or installing an addon.
  5. Troubleshooting. What to check when a value does not seem to take effect or a localization key shows on screen.

How the docs are laid out

The sidebar groups every page by intent:

  • Getting started. Overview, first launch, file layout.
  • Configuration. One page per top-level configs/*.json file, including addons.json, map_doors.json, and map_glass.json.
  • Economy. One page per configs/economy/*.json file.
  • Customization. Themes, localization, and custom map integration.
  • Operations. Console commands, common workflows, troubleshooting.
  • Reference. Useful ID lists (jobs, modules, shop items, weapons, food, vehicles, themes).

Conventions

Doc-wide patterns to keep in mind:

  • All IDs are lowercase. Letters, numbers, -, and _ only.
  • Code, file paths, and command names use monospace.
  • Warnings cover live-reload caveats: some changes apply instantly, others need a server restart or map reload.
  • English keys are authoritative. Translations override values, not keys.