NeonRP
A world-simulation engine for AI role-play: let the model tell the story, let the world keep its rules.
Pure prompting drifts and agrees with everything; letting a model freely edit files corrupts state; a rule engine can't understand what a player actually says. NeonRP sits in between: the model proposes, the engine validates and writes, and the world, the player and every character keep their own agency.
NeonRP is the engine of WorldLines and is released under Apache-2.0.
What it does
- Two beats per turn. The player says what they want to do. In the planning beat the characters present answer and
a plan is agreed; when a judge says the talk is settled (Jev with a Worldlines account, otherwise the run's own model;
the player can also say 「定」 or
@dm), the resolve beat rolls the dice that apply, writes what happens and commits one validated state transition. State is written at once and re-checked in the background; a wrong value is corrected and the player is told. A turn is an orchestration graph that packs and templates can patch. - Three parties, isolated. World, player and characters each have their own agency. What the player says is an attempt, not a fact; characters decide for themselves.
- State is files. A world is a folder of JSON / Markdown you can read, diff and version. Closed schema (registered variables) and open schema (classes whose instances can grow during play), each change checked before it lands.
- Worldlines. Every turn is a commit; roll back, branch and compare timelines.
- Packs and templates. Rules live in packs (
rpg,pct,werewolf,monopoly, mixins such aseconomyandfactions); a template binds a world + souls + a pack + prompts, plots and asset slots, and is linted before it can be published. - An SDK. Register and subscribe to state from Python; a generated contract (TypeScript / GDScript) lets other front ends such as Godot talk to the engine.
Install
uv tool install neonrp # the engine + CLI + terminal UI
uv tool install worldlines # the WorldLines product (local web UI), brings neonrp with it
Python 3.10 or newer. pip install and pipx install work too. Both commands check for a new release at launch and update
themselves (/update mode prompt or notify inside the game to change that).
One-line installer / mirrors
curl -LsSf https://worldlines.gg/install.sh | sh # macOS / Linux (installs uv if missing, then worldlines)
irm https://worldlines.gg/install.ps1 | iex # Windows PowerShell
Behind a slow PyPI connection, point uv at a mirror first, e.g.
export UV_DEFAULT_INDEX=https://pypi.tuna.tsinghua.edu.cn/simple — neonrp self-update honors it too.
Play
neonrp # the launcher: pick a world (or your latest run) and play; a new run opens by itself
worldlines # the same library in your browser: http://127.0.0.1:8787/local
Nothing to install: play online at worldlines.gg or in the iOS app.
Inside a world folder (neonrp tui works on the current folder and opens in build mode; --play plays it):
neonrp validate # is this world playable? (JSON, souls, opening, lint)
neonrp tui --play # play it
neonrp commit --help # the commit graph: log, branch, roll back
Templates:
neonrp template list
neonrp template lint <dir>.template # every problem; blocks stop publishing
neonrp template build <dir>.template <run> # build a playable run
cd <run> && neonrp tui --play
Run neonrp --help for every command.
Documentation
- Specs — world · soul · template · contract · pack
- Concepts, creator and developer guides — docs.worldlines.gg
(source:
documents/site)
Develop
uv sync --all-extras --dev
uv run ruff check src tests
uv run pytest -q
License
Apache License 2.0 — see LICENSE and NOTICE. Copyright © 2026 worldlines-nikoloside, redoctober (Ludic Dynamics). "NeonRP" and "WorldLines" are names of Ludic Dynamics; the license does not grant rights to use them.
Metadata
Release files for neonrp 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neonrp-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / neonrp-1.0.4-py3-none-any.whl
| Download URL | neonrp-1.0.4-py3-none-any.whl |
|---|---|
| Size | 54.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e173def76c05fccca91de4088648aab20c6588827c7dc6d2a9d42289f72f2415
|
|
BLAKE2b-256 checksum How to use checksums |
649e761155a9097c7b9518ed194f2b3d830a3066388223ed29ceefeedb06b9b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for neonrp 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.