Run any Skill in Manus with one click

debugging

Stars3

Forks1

UpdatedJune 2, 2026 at 10:23

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

QiMata

QiMata/BloogBot

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	debugging
description	Debugging workflow for BloogBot/WWoW codebase. Use when investigating bugs, errors, unexpected behavior, or service failures.
trigger	debug, investigate a bug, error, unexpected behavior, service failure, trace a request, bot not moving, crash, IPC issue, find root cause

Debugging in BloogBot

Goal

Localize and root-cause a bug, error, or service failure by identifying the execution mode and tracing the request through the layered architecture to the responsible component.

Inputs

The symptom and which execution mode it occurs in:
- ForegroundBotRunner (in-process) — injected into WoW.exe via Exports/Loader/dllmain.cpp; direct memory r/w via Services/ForegroundBotRunner/Mem/; native calls via Exports/FastCall/ (x86 fastcall).
- BackgroundBotRunner (headless protocol) — pure C# protocol emulation in Exports/WoWSharpClient/; no client; packet-level debugging via WoWSharpClient/Handlers/ and Client/.
IPC surface: all services talk Protobuf/TCP via Exports/BotCommLayer/ (PathfindingService 9002; WoWStateManager 9001 char-state, 9000 state-manager API — confirm current ports against the service appsettings).

Preconditions

Identify the execution mode first — the steps differ between FG and BG.
Reproduce the symptom (or have a log/recording that captures it).

Procedure

Trace IPC issues: check BotCommLayer/ProtobufSocketServer.cs for connection handling → the specific service's socket server/client → port availability and startup order.
Trace a request through the layers:
1. Entry point: ForegroundBotRunner or BackgroundBotRunner.
2. Into BotRunner/BotRunnerService.cs (core behavior tree).
3. Game state: GameData.Core interfaces → concrete implementations.
4. Movement → PathfindingService (9002) → Navigation.dll.
5. State change → WoWStateManager (9001/9000) → FSM transitions.
6. Protocol → WoWSharpClient/OpCodeDispatcher.cs → specific Handlers/.
Debug physics (complex C++): see docs/physics/README.md; key (large) files PhysicsEngine.cpp, PhysicsCollideSlide.cpp, PhysicsMovement.cpp, PhysicsGroundSnap.cpp — read in chunks / via Codex.

Verification

Reproduce the symptom, apply the fix, and confirm the symptom is gone.
Add a regression test or guard where feasible (.\scripts\test-fast.ps1).
Use repo-scoped process cleanup only — never blanket-kill dotnet/WoW.exe/Game.exe.

Outputs

A root-cause statement, the fix, and (where feasible) a regression guard.
A FailureReason/crash-cluster entry if the bug warrants one.

Failure modes and recovery

Common failure patterns and where to look:

Symptom	Likely cause	Where to look
Bot not moving	Pathfinding failure / stuck state	`Services/PathfindingService/PathfindingServiceWorker.cs` → `Exports/Navigation/PathFinder.cpp`
Physics glitch (falling through world)	Collision response	`Exports/Navigation/PhysicsCollideSlide.cpp`, `PhysicsGroundSnap.cpp`
Wrong spell cast	Profile rotation logic	`BotProfiles/<ClassSpec>/` spell priority
State machine stuck	Missing FSM transition	`Services/WoWStateManager/StateManagerWorker.cs`
Connection timeout	Protocol/network	`Exports/WoWSharpClient/Client/`, `Networking/`
DLL injection crash	Loader / CLR bootstrap	`Exports/Loader/dllmain.cpp`, `simple_loader.cpp`
Game objects not detected	ObjectManager sync	`Exports/WoWSharpClient/WoWSharpObjectManager.cs`
Decision engine wrong choice	ML model / input data	`Services/DecisionEngineService/DecisionEngine.cs`, `MLModel.cs`

Debugging the wrong mode wastes effort — confirm FG vs BG first.
Reading huge physics/packet files inline fills context — search first, read in chunks, or summarize via Codex.

Related skills

[[crash-cluster-triage]] — when the symptom is a reproducible WoW.exe crash.
[[fg-bg-physics-parity]] — when FG and BG physics diverge.
[[failure-reason-mapping]] — classify the failure you found.
[[botrunner-task-implementation]] — when the bug is in a Task.

More from this repository

same repository

activity-catalog-bootstrap

QiMata/BloogBot

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.

2026-06-013

bot-profile

QiMata/BloogBot

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.

2026-06-013

botrunner-task-implementation

QiMata/BloogBot

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.

2026-06-013

config-hot-reload-subscriber

QiMata/BloogBot

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).

2026-06-013

coordinator-implementation

QiMata/BloogBot

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.

2026-06-013

crash-cluster-triage

QiMata/BloogBot

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.

2026-06-013

Debugging in BloogBot

Goal

Localize and root-cause a bug, error, or service failure by identifying the execution mode and tracing the request through the layered architecture to the responsible component.

Inputs

The symptom and which execution mode it occurs in:

ForegroundBotRunner (in-process) — injected into WoW.exe via Exports/Loader/dllmain.cpp; direct memory r/w via Services/ForegroundBotRunner/Mem/; native calls via Exports/FastCall/ (x86 fastcall).
BackgroundBotRunner (headless protocol) — pure C# protocol emulation in Exports/WoWSharpClient/; no client; packet-level debugging via WoWSharpClient/Handlers/ and Client/.

IPC surface: all services talk Protobuf/TCP via Exports/BotCommLayer/ (PathfindingService 9002; WoWStateManager 9001 char-state, 9000 state-manager API — confirm current ports against the service appsettings).

Preconditions

Identify the execution mode first — the steps differ between FG and BG.

Reproduce the symptom (or have a log/recording that captures it).

Procedure

Trace IPC issues: check BotCommLayer/ProtobufSocketServer.cs for connection handling → the specific service's socket server/client → port availability and startup order.

Trace a request through the layers:

Entry point: ForegroundBotRunner or BackgroundBotRunner.
Into BotRunner/BotRunnerService.cs (core behavior tree).
Game state: GameData.Core interfaces → concrete implementations.
Movement → PathfindingService (9002) → Navigation.dll.
State change → WoWStateManager (9001/9000) → FSM transitions.
Protocol → WoWSharpClient/OpCodeDispatcher.cs → specific Handlers/.

Debug physics (complex C++): see docs/physics/README.md; key (large) files PhysicsEngine.cpp, PhysicsCollideSlide.cpp, PhysicsMovement.cpp, PhysicsGroundSnap.cpp — read in chunks / via Codex.

Verification

Reproduce the symptom, apply the fix, and confirm the symptom is gone.

Add a regression test or guard where feasible (.\scripts\test-fast.ps1).

Use repo-scoped process cleanup only — never blanket-kill dotnet/WoW.exe/Game.exe.

Outputs

A root-cause statement, the fix, and (where feasible) a regression guard.

A FailureReason/crash-cluster entry if the bug warrants one.

Failure modes and recovery

Common failure patterns and where to look:

Symptom

Likely cause

Where to look

Bot not moving

Pathfinding failure / stuck state

Services/PathfindingService/PathfindingServiceWorker.cs → Exports/Navigation/PathFinder.cpp

Physics glitch (falling through world)

Collision response

Exports/Navigation/PhysicsCollideSlide.cpp, PhysicsGroundSnap.cpp

Wrong spell cast

Profile rotation logic

BotProfiles/<ClassSpec>/ spell priority

State machine stuck

Missing FSM transition

Services/WoWStateManager/StateManagerWorker.cs

Connection timeout

Protocol/network

Exports/WoWSharpClient/Client/, Networking/

DLL injection crash

Loader / CLR bootstrap

Exports/Loader/dllmain.cpp, simple_loader.cpp

Game objects not detected

ObjectManager sync

Exports/WoWSharpClient/WoWSharpObjectManager.cs

Decision engine wrong choice

ML model / input data

Services/DecisionEngineService/DecisionEngine.cs, MLModel.cs

Debugging the wrong mode wastes effort — confirm FG vs BG first.

Reading huge physics/packet files inline fills context — search first, read in chunks, or summarize via Codex.

Related skills

[[crash-cluster-triage]] — when the symptom is a reproducible WoW.exe crash.

[[fg-bg-physics-parity]] — when FG and BG physics diverge.

[[failure-reason-mapping]] — classify the failure you found.

[[botrunner-task-implementation]] — when the bug is in a Task.