rs2b0t manual
How the client works, how to run it, and how to write bots for it.
Target: rs2b2t only. This is not an official client for the pure Lost City or 2004scape projects and is not maintained for those targets.
Start here #
| If you want to… | Read |
|---|---|
| Write a bot | Scripting API, then the script template |
| See what already exists | Bundled scripts |
| Run it locally | Running locally |
| Change the client itself | Architecture, then Testing |
| Maintain the deployment | Dev and deploy |
Pages #
| Page | Covers |
|---|---|
| Running locally | the path from a cold clone, and ports |
| Architecture | the layers and the ABI boundary, then design, namespaces and fences |
| Scripting API | the surface, split by subsystem; start with write a bot |
| World-walking | pack, pathfinding, doors, teleports, walker |
| Map tile picker | Pick on Map: display modes, then reference and baking |
| Quests | engine, provisioning, primitives, eligibility, adding one |
| Clue scrolls | database, mechanics, host yielding, tracing a failure |
| MultiBox | the wall, then reference, telemetry honesty and diagnosis |
| Bundled scripts | catalog of the shipped bots and their settings (generated) |
| Testing | suites, why it is testable, writing a harness, seeding, the tools/e2e boundary, case manifest |
| Dev and deploy | the three run modes, then live wall, build targets, maintainer infra |
| Loc identity | why a loc is a placement, not an ID |
| Loc state in the client | what the client does with locs that change state, and the gaps |
| Nav operator tools | transport coverage, client-vs-pack path paint, live nav harnesses |
| Doc migration | in-progress rewrite of this manual to one-type-per-file; delete when the table is all ✅ |
Design specs and implementation plans are working notes, not part of this manual, and
are not committed, see .gitignore.