Governor-review bounce (PR #10) fixes on issue-5: 1. Timing units + rates: one OSRS tick = 0.6s so a 3-tick cast is 1.8s, not 5.4s as both action comments claimed. The mandatory 1.6-3.4s post-action delay (mid ~2.5s) allows ~1,440 casts/hr before overhead; rates are now pinned at 1,400 casts/hr: LA 43,400 / SII 74,200 / HLA 91,000 xp/hr (was 55,800 / 95,400 / 117,000 @ 1,800). The old 1,800 figures were unreachable under the entries' own pacing. 2. Nature rune limit unified to 18000 (mapping 'limit' + Module:Exchange agree, fetched live 2026-08-27): low-alch-f2p 12500 -> 18000, matching magic-alch-handoff. tools/validate.py gains a cross-entry supply-fact consistency check (same item+source must agree on ge_limit; run on every gate invocation) plus --selftest regression fixtures: diverging limits must fail, agreeing limits must pass, missing ge_limit is not gated. 3. SII tier is now phase-aware and translatable: actions split into cast-alch (LA/HLA -> cheapest alch candidate, noted stack) and cast-superheat (SII 43-55 -> unnoted ore whose live bar margin is positive; never a noted stack, never a price-only pick; on_fail skip when no positive-margin ore). State machine pins each tier path (LA <43, SII window chosen/skipped 43-55, HLA >=55), bank_supplies banks smelted bars, buy-supplies restricts ores to positive-margin recipes. Tests: python3 tools/validate.py -> 2 entries, 0 errors, 0 warnings; --selftest -> 3 PASS; negative test (reintroducing 12500) caught by the new check; 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.