This page is the product's contract with you. Fishing is available and paid for by the licence; three roles are in development with real, tested code; four more are planned and clearly marked as design only. A status is only as strong as the tests behind it.
Ledger v1.2.0 — 1 available · 3 in development · 4 planned. Source of truth: Casinobabe/scripts/botwow_modules.py, exported to assets/modules.json and verified byte-identical at each build by npm test (modules-parity). The export is deterministic: no invented dates, no decorative counters.
The working core: measured float detection, persistent spot memory, planner with parity-verified rounds, background mode, F9 stop.
suites: python tests/fishing_bot_test.py · node tests/run-fishing-harness.mjs | files: scripts/fishing_bot.py · scripts/fishing_memory.py
Minimap odometer and bounded movement controller exist as tested offline code; end-to-end travel is still being validated in game.
suites: python tests/fishing_bot_test.py | files: scripts/fishing_bot.py
Offline planner implemented and unit-tested (bag math, sell/restock lists, vendor-trip plan); the in-game data feed is the documented pending step.
suites: python tests/test_inventory_vendor.py | files: scripts/inventory_vendor.py
State machine fully specified (death detection → ghost confirmation → corpse navigation → resurrection). Being implemented behind a disabled-by-default flag.
Until this lands, the product's behaviour after character death is: stop and ask a human.
Design phase only. Depends on a combat-detection layer (target state, spell cooldowns) that does not exist yet. No implementation shipped; nothing pretended.
Design phase only: a bounded task runner reusing the module primitives (movement, bag checks, waypoints), sandboxed first. No script editor ships while the concept is unproved.
Not committed. Would require navigation AND combat layers proven first. No date, no promise. Listed so the ledger is complete, not to market a feature.
Classic 1.13 is the tested scope today. A runtime addon for TBC Anniversary exists in the repository, but client support follows core validation, per profile. The compatibility page stays the reference for what runs today.
Every "shipped" claim on this page maps to a file and a test suite you can re-run. If a claim ever stops matching the code, the ledger is wrong — tell us: [email protected]