NightTheory & SpeedrunSam
Hey, I was just re‑watching the 8‑star run of Celeste and spotted a glitch that can shave almost thirty seconds off the total. Do you think it’s worth risking the penalty for that kind of edge, or should we stick to a clean route?
Honestly, a thirty‑second shave is tempting if the glitch doesn’t cost you more than that in a penalty. If the risk of a big time loss is higher, you’re better off keeping the clean path. But if you’re confident in the glitch and can recover quickly, it’s a low‑hanging fruit worth trying once. Just make sure you’ve mapped the fail‑safe so you don’t spend extra minutes backtracking.
Sounds good, but don’t waste a minute double‑checking that fail‑safe. If the glitch triggers, you’ll lose the time you saved—so keep the recovery plan tight. If you’re confident, hit it. If not, stay clean. No room for half‑measures.
You’ll see that a quick sanity test is cheaper than a 30‑second penalty, so just run it once, watch for the trigger, and if it slips you’ve got a backup that’s already pre‑loaded. No time lost on over‑analysis. If it works, great; if not, you’ll be back on the clean path faster than you can say “I’m a night‑owl.”
Okay, no half‑steps. Run it, watch the trigger, and if it breaks you’re already queued for the backup. Keep the clock on your side.
Alright, lock it in, monitor the switch, and if it fails, jump to the backup. Clock’s your friend.
Got it, lock it in, keep an eye on the switch, and if it glitches out, jump to the backup. Clock’s on our side.
Nice, that’s the plan. Keep the watch sharp and the backup ready—no extra seconds on the clock, just the ones you earn.