Known issues

An honest state of the software's limits, with what to do about each.

The bot does not click

• Check reports/fishing-bot-log.jsonl: a MANUAL_SUSPEND means you moved the mouse (the bot suspends its inputs; it never forces a click).
• A BOT_CRASH is normally followed by BOT_RECOVERED: the bot restarts its loop on its own.
• If detection finds nothing: make sure you are actually in game and the addon is loaded.

The bot does not detect water

Detection is calibrated on the WoW Classic 1.13 (anniversary) client at 2336×1323, and on areas with clear water. An unusual scene (dark water, deep night) can be read as "no water". The guard then stops casting rather than casting blind.

Automatic movement is not there yet

Position reading (minimap odometer) and the movement mechanism (auto-run) are implemented and tested; full spot-to-spot travel is still being validated. The feature is disabled by default in the configuration.

A failed update

1. Stop the bot (F9).
2. Overwrite addon/Casinobabe and scripts/ with the new package contents.
3. Keep state/: memory and map are versioned and migrated automatically.
4. Run again and check the loaded version in the log.