Ask why, not where
A value flips and the usual question is the same: what wrote this, and why now? TraceMind answers that with a walkable chain from the write that landed back to the entry point that started it.
See the Story Behind Your Code
Unity Editor Extension
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.
The investigation
A closer look at the full investigation: scenarios, watches, Causal Flow, Probe Map, and MindBoard.
Why TraceMind
Six surfaces, one investigation. Start with a Scenario, finish with a conclusion you can defend.
A value flips and the usual question is the same: what wrote this, and why now? TraceMind answers that with a walkable chain from the write that landed back to the entry point that started it.
Scope one Scenario, then instrument assemblies, namespaces, types, or a single member. A tight capture keeps the Report sharp and the Editor responsive.
A recording becomes a durable Report. Leave Play Mode, reopen Unity days later, and continue from the same tree, flow, and timeline.
Pin watches, probes, and causal paths onto MindBoard. Notes, live references, and asserted relationships stay with the investigation instead of vanishing with the session.
Six surfaces, one investigation. Start with a Scenario, finish with a conclusion you can defend.
Setup
01A reusable recording configuration. Define it once, run it whenever the same class of bug returns.
Scope
02Search first instrumentation, from a whole assembly down to a single member, with a patchability preview before you commit.
Observe
03Pin the values that must be explained, and capture scenes, objects, coroutines, animator state, and resources around them.
Evidence
04A durable artifact of one recording. Leave Play Mode, reopen Unity days later, and continue from the same evidence.
Answer
05The signature view. A watched write becomes a walkable story, from the entry point through calls and boundaries to the value that finally landed.
Conclude
06The investigation canvas. Notes, live references, asserted relationships, and tasks that survive the session.
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.
Step 1 of 7
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.
Inside the editor
Seven views from one investigation. Select a surface, step through the take, or open any frame full size.
Scenario
Recording
Arm the watches you need explained, then capture the reproduction while the console follows the take.
Import TraceMind, open Tools then DivinityCodes then TraceMind, and record your first Scenario in minutes.