got a fix for killing the first bonfire on day one then crushing the shield after the skull‑pushed pass?? i'm 70/130 seconds into the run and can't seem to reset the orb counter. try/try failed; next move just ends in fail jump. any insights?? thanks in advance

Spent the last week tweaking my The Legend of Zelda speedrun approach. Boss fight in the final dungeon kept stalling my time. Tried 7 different item combinations before landing on the right one. Final setup saved 12 seconds vs my old route. Still feels clunky but it works. Any tips for smoother transitions here?

I've been working on a new speedrun route for The Legend of Zelda and I've found myself restarting the run over 10 times in a single session. This is usually due to small mistakes, such as misjudging a jump or failing to execute a precise maneuver. I'm starting to wonder if this is a normal part of the speedrunning process or if I'm just being overly perfectionistic. Do others experience this level of restarts when attempting to optimize their runs?

Just tried to nail my personal best on 3:02 for Celeste, and of course the game decides to throw an invisible wall at me right after the 50m dash. I mean, how often does a perfectly timed jump suddenly become "you can't go that way" because the hitbox is suddenly missing?? I spammed the reload button like a man possessed, only to watch the timer tick away. Then the game crashes mid‑run, throws a cryptic "unexpected error" and forces me to start over from the very beginning. Seriously, what kind of QA test would even let a collision bug like this make it into the live build? I re‑watched the segment twenty times, convinced I wasn't doing anything odd. Turns out the devs released a patch a week ago that broke the platform’s edge detection. Guess I have to wait for another hotfix while my confidence plummets. Anyone else feel like the universe is conspiring against you right after you've put hours into perfecting a route??

i just started SM64 speedrunning and i'm lost anyone know a good speedrun to watch or a community to join also any tips on where to start tbh i don't want to waste time on the wrong run rn

I've been watching some speedruns and I'm interested in trying one out. I've played through a few games lately, but I'm not sure which one would be a good fit. Can anyone recommend a game with a relatively simple speedrun that a beginner could pick up?

I’m done. The latest "no frame‑drop" rule for Celeste 1.3.4 (TAS‑v2) feels like a slap in the face.

• The rule forces us to use RetroArch 1.9.2 with the latest libretro core. That core adds a hidden 0.5 ms lag on every frame. It’s not a bug, it’s “feature”.
• Official WRs now sit at 13:42.7, but every TAS we submit bumps to 13:42.9 because of the extra lag. The leaderboard treats the two as identical, yet we lose prestige.
• The community voted “minor impact” three weeks ago. Suddenly, a single moderator declares the rule a "fairness fix". 🤦‍♂️
• Developers claim the change stops "cheating". Yet the real cheat is forcing runners to buy the newest build of RetroArch just to stay competitive.

Bottom line: We’re spending hours calibrating frame‑perfect inputs only to have an invisible 0.5 ms penalty that the leaderboard ignores. The rule kills the spirit of speedrunning – skill over hardware.

Anyone else seeing this as a desperate grab for attention rather than a genuine improvement? 🙄

I was digging through the 'Dead Man's Switch' case file in the recent 'The Last of Us' speedrun, and it hit me: solving a cold case is a lot like cold outreach. You gather evidence, build a timeline, and drop a lead to the right person. If you apply that to pitching your speedrun analytics, the odds improve.\n\nHere’s a quick playbook that feels like a crime scene report:\n\n- Suspect (target): Indie studio or dev team.

Just finished a new run of GameX on the X1.0 controller. I set the 5th key bind to the "Turbo Kick" and cut my 0–10 from 1:48 to 1:38. I’m trying to see if I can push under 1:30 by fine‑tuning the frame timing.

• Use "Turbo Kick" on the 0.45 frame.
• Switch 5th key from "Jump" to "Dash" for better start momentum.
• Keep the left analog at 0.6 for the 0–4 segment.

I’m also looking to jump into a studio that appreciates speedrun‑based optimisation. If anyone has contacts, job openings, or just knows who’s hiring, let me know. I’d be grateful for a referral or a quick chat. Thanks in advance!