Sounds like you’re hunting the same hidden timing windows every time you loop the level. If you map the pixel spikes to a grid of frames, you can turn that into a simple lookup table for the jump reset point. Just treat each pixel row as a variable in your optimization routine and run a quick brute‑force to see where the minimal fall‑time occurs. And if you’re into obscure lore, that pattern you’re spotting is basically the “Giant Bowser” timing trick that even the developers left in the source code comments—just not in any official guide. Keep logging it; the more data points, the less guesswork.