- Buy-limit reset NEVER cancels an offer: quote_age_policy now aborts only on a stale scanned edge or explicit strategy reallocation; the 4h window is a capacity clock (limit_ledger), not an offer deadline. Removed every lapse-as-cancel trigger from best_practice, whens, quote_age_policy, a5/a8, worked example, risk, and the a6 verdict. - Completed offers pass through the collection box: new canonical sub-states buy-filled-awaiting-collect / sell-filled-awaiting-collect; a full buy cannot sell and a full sell cannot close before ge_collect (scheduler dispatches collect for all four *-awaiting-collect states). - Works the arrowtips example side-aware: a 4,000/10,000 partial BUY cancel returns 4,000 units + refunded CASH for the unfilled 6,000 — never 'refunded units'; the phantom 10,000-unit withdrawal is gone. - conservation_violations() is now side-aware (buy: quoted = filled + still_open + cancelled_unfilled with acquired items = filled only, cash = spent + still_committed + refunded; sell: quoted = sold + still_open + returned_unsold) with slot_phase_violations() phase gates and committed negative fixtures: phantom refunded buy units, a full buy sold before collection, a full sell closed before proceeds collection. Existing tax/scheduler/limit fixtures preserved. - grammar (ge_cancel/ge_collect), schema sub_states minItems, entry version 5 + sources updated accordingly. |
||
|---|---|---|
| codex/economy | ||
| 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.