Small questions.
Revealing answers.
Read an investigation for its method, not just its result. These official case studies show how clues become explanations.
position → panDX-Ball: From screen position to stereo sound.
The official walkthrough follows a sound-panning helper from x86 instructions into a checked C implementation.
What to look for
Follow the caller to learn what a parameter means. Inspect the underlying instructions when pseudocode leaves out the calculation.
Read the official case study ↗Source: REA project · Reported by the project; not independently reproduced here.Notion: Follow a clipboard call across processes.
The official investigation connects a page-facing API to Electron’s clipboard writer through preload and main-process handlers.
What to look for
Trace both ends of an IPC channel. A renderer API name is only the beginning of the path, and wrapper functions can hide the actual receiver.
Read the official case study ↗Source: REA project · Reported by the project; not independently reproduced here.TH04: Recover the geometry behind a bullet ring.
The official case connects an original angle calculation to readable C++ and the reconstruction project’s compiler checks.
What to look for
Track units as carefully as control flow. A stored angle can use a game-specific scale rather than degrees or radians.
Read the official case study ↗Source: REA project · Reported by the project; not independently reproduced here.