A simple app that tracks active GSC (Server Script) and CSC (Client Script) threads, wait loops, and memory leaks.
It works on both the official Steam version and the BOIII Community Client.
Important
This tool is 100% external and read-only. It only reads the game's active memory to trace script state and never writes data. It is completely safe to use, to check your thread count or dump variables during a high round game.
- Open the game and load into any match or map (the script VM only starts up once you are in-game).
- Open
Bo3-Debugger.exeand select GSC or CSC. - Click Scan to view active threads and variable pools.
- Enable Auto-Refresh to monitor thread loops and array in real-time.
Warning
If your game client requires administrator privileges to run, make sure to right-click and Run as Administrator on this app as well so it can connect.
Tip
Click Dump to Text File. This will generate a .txt dump file in the exact same folder where the app is running. Feel free to DM me these dump files on Discord (ojumpy).
- Switch directly between GSC and CSC.
- Automatically groups duplicate thread execution offsets. If a loop is leaking, you will see the exact count of stuck threads increase under that function.
- Scans the variables pool to detect bloated structures and arrays (such as the Gorod Krovi gauntlet punch leak or the mystery box leak). It resolves the exact name of the array so you can locate it instantly.
- Detects some variables to display the exact event strings (like
"grenade_fire") that suspended threads are waiting on.
Note
Because this tool is unsigned and reads the game's memory internally, some antivirus programs might flag it as a false positive. This is completely normal for custom memory debugging tools. You can view the clean scan results showing the file is completely safe below:
- lveez: Creator of the original bo3-debugger. Great credit to him for his original GSC memory structure research and base engine offsets.