A desktop source browser, Java scratchpad and debugger for TotalDebug. Inspect the classes in your Minecraft instance, follow their references and experiment with the running game.
Minecraft source with an illustrated debugger pause and a nested Java evaluation result.
Open a block, entity or item from Minecraft with F6, then navigate its decompiled source. Companion includes class and member search, Find Usages, type hierarchies, editor completion and archive resource previews.
The workspace remains open when Minecraft exits. Source browsing and indexed navigation work offline while the runtime archives and Java installation remain available. Live tools reconnect when TotalDebug starts again.
Evaluate expressions or Java statement bodies, inspect their results, and save reusable code as scripts. Run scripts on the client or server according to the server's execution policy.
The debugger provides breakpoints, stepping, stack frames, variables, watches and breakpoint actions. Paused evaluation uses the selected frame. Code that invokes methods or changes fields can affect Minecraft, and cancellation does not undo those effects.
See usage and limitations for debugger attachment, supported evaluation contexts and cancellation behavior.
Companion requires Windows x64 and a full JDK 21. The application JAR contains its dependencies, but no Java runtime.
For coordinated source builds, follow TotalDebug's dependency build order, then run:
.\gradlew.bat build -PtotaldebugUseMavenLocal=true
java -jar build/libs/TotalDebugCompanion.jarTotalDebug can launch the same JAR from Minecraft. Standalone startup reopens the last profile when one is available.
For UI changes, the test harness renders named states without a game session:
.\gradlew.bat uiHarness -PtotaldebugUseMavenLocal=true '--args=--theme=islands-dark --scenario=search-results'
.\gradlew.bat uiHarness -PtotaldebugUseMavenLocal=true '--args=--list-scenarios'
.\gradlew.bat uiContactSheet -PtotaldebugUseMavenLocal=trueContact sheets and individual captures are written under build/ui-screenshots.
The MCP API exposes source queries, Java execution and debugger operations to trusted local clients. The storage guide describes scripts, settings, persisted debugger state and generated caches.