BloogBot

Debugging workflow for BloogBot/WWoW codebase. Use when investigating bugs, errors, unexpected behavior, or service failures.

Add or generate compiled activity-catalog rows (ActivityDefinition) from the leveling-guide source and keep them passing the catalog invariant tests + MaNGOS cross-validation. Use when adding an Activity to the catalog.

Creating or modifying WoW class/spec combat profiles. Use when adding a new class profile, fixing combat rotations, or adjusting bot behavior for a specific specialization.

Add an IBotTask behavior-tree task that orchestrates Actions to drive one minute state change, with FG+BG parity, tests, and live-validation. Use when implementing a new bot behavior (move/loot/interact/cast/gather/etc.) as a Task on the LIFO task stack.

Add an IConfigSubscriber for a new reloadable config section so a running service applies changes without restart, with ACK/rollback. Use when a config section must hot-reload (the feature-flag / live-tunable path).

Author a new activity coordinator (Dungeon/Raid/BG/Quest/Economy/etc.) in WoWStateManager that orchestrates multiple bots through an Activity by emitting Objectives from snapshot state. Use when a multi-character Activity needs server-side coordination.

Capture a WER dump, root-cause a reproducible WoW.exe (FG) crash, and ship a hardening patch + regression guard, documented as a crash cluster. Use when the foreground client crashes repeatably.

Add a new worker service / container to the WWoW stack with metrics + log rotation, and wire it into the .NET Aspire AppHost. Use when adding a background job or a new runnable service to the orchestrated stack.

Map a new failure path to the canonical FailureReason enum, keeping it in 1:1 sync with the error-taxonomy spec (enforced by a drift test). Use when code needs a failure classification that does not yet exist.

Drive the ForegroundBotRunner→BackgroundBotRunner physics parity loop using the replay validator + bake pipeline, so headless movement matches the live client. Use when BG physics (ground Z, falls, slides) diverges from FG.

Package a WWoW-proven pattern as a portable, game-agnostic skill in the monorepo-shared registry, with a cross-game smoke test. Use when a repo-local skill is mature enough to reuse in another game repo.

Author a LiveValidation integration test that exercises the full StateManager → BotRunner loop against the live MaNGOS stack. Use when adding an end-to-end behavior test that drives an Activity and asserts on bot snapshots.

Convert a leveling-guide spec into a CharacterBuildConfig / loadout template (level, spells, skills, gear, reps, quests, talents) that the bot applies via LoadoutTask. Use when defining what a character should know and wear.

Identify noisy log categories and apply level overrides / burst suppression per the logging spec, plus container log rotation. Use when logs are too verbose or a category floods the output.

Add new meters / counters / histograms with spec-compliant names and bounded label cardinality, exported via OpenTelemetry. Use when a service needs new observability metrics.

Add a StateManager mode handler (Test / Automated / OnDemandActivities / new) that decides what bots do at world-entry, per snapshot, and on external requests. Use when adding or changing a top-level StateManager operating mode.

Iterate tools/MmapGen per-tile bake config to close a navmesh fidelity gap, respecting the pathfinding freeze (mesh fixes in MmapGen, no managed repair). Use when a route clips static geometry or a tile has a hole.

Add a CMSG/SMSG WoW protocol opcode handler in WoWSharpClient (with packet-capture tests), and—when the change crosses the IPC wire—regenerate the protobuf contract. Use when the headless bot must parse a new server message or send a new client message.

Generate and validate a static route pack for a long fixed leg, gated by the long-pathing route tests. Use when a frequently-traveled static route should be precomputed and cached.

Extend the WPF operator console (WoWStateManagerUI) with a new panel/view bound to a StateManager summary, following MVVM + UI-thread + state-gating rules. Use when adding a UI component or page to the desktop dashboard.