Governor bounce 5 (2026-08-28) repaired finding by finding: 1. Tool purchase is now executable end to end: new a10 ge_open before any ge_buy; a12 wait-ge-fill is BOUNDED (one 3-6 min fill window) and on no-fill/partial-fill TIMEOUT cancels the resting offer -> a13 collects/refunds -> fail closed via recover (3 loops -> failed); a resting offer is never re-placed indefinitely. Actions renumbered a11..a17. 2. min_level 1 copper/tin below-15 path now has STRUCTURED fallback rows (mine_sites se-varrock-copper / se-varrock-tin, level 1, 17.5 xp, safe East Varrock) added to mining_modes.fast-xp.sites; level-1 and level-14 selections are pinned in a new mining_selections block and recomputed by a new select_fast_site() validator gate (+ 3 committed selftest fixtures). 3. a2 no longer advertises silver/coal/gold/mithril banked targets: it restricts banked-income to the declared rows (iron @ se-varrock-bank, adamantite @ al-kharid-south-adamantite); superheat-coal technique is marked informational-only. New ge_open/ge_offers_done/ge_collect validator gate (+ 1 fixture). Modeled below-15 rate 6,300 XP/hr (was the unbacked '~8,800' prose) recomputed from the bronze cadence midpoint. Validator: 2 entries, 0 errors, 1 pre-existing WARN; --selftest 17 PASS; git diff --check clean. |
||
|---|---|---|
| codex | ||
| docs | ||
| schemas | ||
| tools | ||
| README.md | ||
OSRS Codex
One source of truth for everything that can be botted in OSRS.
Every bot-able activity — alching, mining, slayer, bosses, trading — is described here once, in a strict client-agnostic YAML structure: requirements, execution order (state machine), the exact action sequence, economics, best-in-class setup, and anti-ban notes.
AI agents building scripts do not re-learn the game. They read a codex entry and translate it into the target client API (DreamBot / Microbot / Storm / RuneLite plugins / …). The game knowledge lives in this repo; the client glue lives in whatever script is being written.
client-agnostic client-specific (NOT in this repo)
+----------------+ +-------------------+
| codex entry | translate | DreamBot Java |
| (YAML, strict) | ---------> | Microbot JS |
| actions: verbs | | RuneLite plugin |
+----------------+ +-------------------+
Layout
codex/<domain>/<entry-id>.yaml # one entry per activity
economy/ trading, alching, flipping
training/ skill grinds (magic, mining, woodcutting, ...)
combat/ bosses
combat-slayers/
quests/ quest entries (referenced by requires_quest)
transport/ teleport/teleport-reach recipes (shared by many entries)
meta/ account rotation, world hopping, break scheduling
docs/schema.md # the entry contract (read this first)
docs/action-grammar.md # the universal verb vocabulary
docs/data-sources.md # where every fact must come from + how to verify
schemas/entry.schema.json
tools/validate.py # the gate: python3 tools/validate.py (must exit 0)
The rules (short version)
- One entry = one activity. State machine + action list, both mandatory.
- Every fact carries a source. Wiki-cited or
researched <date>(a TODO: follow-up issue must land the proper citation). Live prices are re-verified againstprices.runescape.wikion every bump. - Best-in-class setup is mandatory (
best_practice). Top-operator execution: staff of fire for alchemy, noted items, shortest routes. Translators adopt it by default; deviating requiresimprovised: true. - Anti-ban is first-class. Every action declares delay bounds and
movement style; entries carry
risk.ban_level+ notes. - The gate must pass before a PR merges:
python3 tools/validate.py. - Never mix in client knowledge. No DreamBot/Microbot/Storm API names in entries. Translations live in script repos, referencing the entry id.
Entry lifecycle
draft → verified (all facts sourced, prices re-checked, validator
clean) → stale (facts > 30d old or prices moved materially). Stale
entries are skipped by translators unless explicitly allowed.
Contributing
This repo is issue-driven: all content is specified in Gitea issues
(acceptance criteria + source URLs + expected output path), implemented in
branches, and gated by tools/validate.py in CI. No direct pushes.