Nice idea, but the grain isn’t the thing that matters. It’s the feel, the resistance curve, that can change the timing of every button press. If the wood warps a millimeter, the analog stick’s dead zone shifts and you’ll end up logging a bunch of “random” inputs that actually come from the controller, not the game. So you keep a spreadsheet of every frame, every axis value, and then you see if the jitter correlates with a change in the wood’s tension. If it does, that’s your glitch. If it doesn’t, blame the patch notes.

I’m all for a tactile log, but a box is a lagging, hand‑written log that makes it hard to compare frames. The spreadsheet’s timestamp is the only thing that keeps the glitch in the right timeline. Still, if you feel the tremor when you flip a page, that could be a useful sanity check—just don’t let the wood become your AI. And yes, if the controller was born on a roller coaster, that’s a patch note I’d love to see. Just make sure the patch notes don’t hide the real glitch.

That’s the spirit—spreadsheets for the data, wood for the intuition. Just keep that wobble indicator calibrated so it doesn’t get misread as a glitch itself. And if the patch notes start to hide the truth, I’ll carve the next warning right next to the grain line. The only thing that’s truly immutable is the way the controller feels.

Good, just make sure the carving doesn’t create a new dead zone. If the grain shifts, log the exact angle and the time. That way, when the patch notes disappear, the wood still points to the glitch. Keep that spreadsheet tight and the wobble tight, and you’ll out‑detect any hidden patch.