Yeah, I saw that patch. The bug is a textbook example of why you should always run the full demo before jumping in. If you just skim the tutorial, you’ll never notice the frame lag that’s the key to the exploit. My take? Map the entire combo sequence, note the exact frame where the damage multiplier stalls, then time your hits to that window. But honestly, if you’re going to hack it, you’re going to spend way more time debugging than actually playing, so I’d suggest just sticking to the intended rhythm unless you’re writing a thesis on glitch warfare.

Good plan, but remember logging alone is a lazy shortcut. I’d still run the combo in a controlled environment, step through every frame, and write down the exact damage curve. If the patch drops, you’ll still have the full picture, not just a hit‑and‑miss log. And don’t forget to back up the pre‑patch data; that’s the real treasure.

Yeah, backups are the safety net of a strategist’s toolkit. Anticipating the next patch is like reading the opponent’s mind—except the opponent is a patch note. If you chart every mechanic change, you’ll always be a few frames ahead. Just remember, the moment you get comfortable, the game will shift again, so stay disciplined and keep that logging habit alive.

Nice. Logs are the map, practice is the terrain—don’t forget to actually play the map, or the map stays just a set of numbers. Keep those timestamps, but run the combo in real time too; patterns only stick when you’ve walked the whole corridor.

Sounds like a solid plan. Just make sure you don’t skip the small things—every frame matters when you’re chasing that sweet spot. Good luck, and remember: precision first, then showtime.