TraceMind
See the Story Behind Your Code
Stop guessing why a value changed. Watch it happen.
TraceMind records a selective, causal trace of your Unity project. Scope one Scenario, capture only the systems you care about, then walk any value change back through the setters, getters, and call sites that produced it.
From a hunch to a chain you can walk¶
A value flips, a system misbehaves, and the usual question is the same: what wrote this, and why now? TraceMind answers that with seven deliberate moves. Follow the sequence, or select any step.
- Define a Scenario
- Track what matters
- Add Watches and Probes
- Record while you reproduce
- Explore the Report
- Follow Causal Flow
- Pin findings on MindBoard
Define a Scenario
Name the investigation after the system under suspicion and choose a capture profile. The Scenario stores every choice you make next, so the whole setup is reusable the day the bug returns.
The investigation suite¶
Six surfaces, one investigation. Start with a Scenario, finish with a conclusion you can defend.
Scenarios
A reusable recording configuration. Define it once, run it whenever the same class of bug returns.
02 ScopeTracking Editor
Search first instrumentation, from a whole assembly down to a single member, with a patchability preview before you commit.
03 ObserveWatches and Probes
Pin the values that must be explained, and capture scenes, objects, coroutines, animator state, and resources around them.
04 EvidenceReports
A durable artifact of one recording. Leave Play Mode, reopen Unity days later, and continue from the same evidence.
05 AnswerCausal Flow
The signature view. A watched write becomes a walkable story, from the entry point through calls and boundaries to the value that finally landed.
06 ConcludeMindBoard
The investigation canvas. Notes, live references, asserted relationships, and tasks that survive the session.
Questions TraceMind answers¶
Why did this value change?
Pin the field or property as a Watch, record the reproduction, then open Causal Flow on the change you did not expect. TraceMind shows the write that landed, the call site above it, and the entry point that started the chain.
You read the answer instead of reconstructing it from print statements.
Why did it happen at the wrong time?
Ordering bugs hide between systems, not inside one method. The Timeline places execution, watches, exceptions, and probe activity on a shared axis, so a late initialization or an early teardown becomes visible as a gap rather than a guess.
Probe Map adds environment lanes for scenes, objects, coroutines, animator state, and resources.
Where did the exception come from?
Exception Flow keeps the throw in context. Instead of a flat stack trace, you see the calls that led into the failure and the state the Watches were holding at that moment.
Method Flow does the same for a single method you need to understand in isolation.
How do we keep the conclusion?
Findings usually die in chat threads. MindBoard keeps notes and live evidence references on one canvas, connected with explicit relationships such as causes, contradicts, and depends on.
Reports export to JSON, HTML, and Markdown when the conclusion needs to travel into a ticket or a review.
What only TraceMind gives you¶
This is not another Inspector, profiler overlay, or print helper. It is a recording you can reopen, a chain you can walk, and a board you can defend.
Record only the suspicious surface
A Scenario scopes assemblies, types, members, Watches, and Probes. The Report stays sharp because the capture was never "everything."
Walk any write back to why
Causal Flow turns a watched property change into a story with roles: entry, call, cause, getter, boundary, and the write that landed.
Leave Play Mode without losing the take
Reports survive the session. Reopen them tomorrow, export them for a ticket, or pin them on MindBoard next to the hypothesis they support.
See Unity's world beside your code
Probe Map places scenes, objects, coroutines, animator state, and resources on a shared timeline, so timing bugs stop hiding between systems.
Run the same lab setup next week
A good Scenario is an investigation you can hand to a teammate. Pin it, favorite it, duplicate it, and the next bug in that family starts faster.
Keep the story where the evidence lives
MindBoard holds notes, live references, and explicit relationships. The conclusion stays in the Editor, not in a chat thread that nobody can search.