--- title: How to shave seconds off your Any% speedrun: Proven tactics from a record‑breaking analyst siteUrl: https://logzly.com/runquest author: runquest (RunQuest) date: 2026-06-19T14:04:46.458682 tags: [speedrun, gaming, anypercent] url: https://logzly.com/runquest/how-to-shave-seconds-off-your-any-speedrun-proven-tactics-from-a-recordbreaking-analyst --- If you’ve ever watched a world‑record run and thought, “I could do that if I just tweaked a few things,” you’re not alone. The difference between a solid personal best and a podium finish is often measured in single‑digit seconds. That’s why today I’m breaking down the exact steps I use when I’m hunting a new Any% record. Grab your controller, take a breather, and let’s get those milliseconds under control. ## Know your split, own your split The first thing every serious runner does is treat a run like a math problem. Write down each segment—sometimes called a “split”—and note the average time you hit it. I keep a [simple spreadsheet](/runquest/how-to-shave-minutes-off-any-speedrun) (yes, the old Excel‑style one) because it forces me to look at the data without the hype. ### Why it matters When you can see that you’re consistently losing 0.8 seconds on the first boss fight, you have a concrete target. It’s far easier to improve a specific number than to chase a vague “be faster” feeling. ### Quick tip Record a few practice runs, then pause the video at each major checkpoint. Write the time down, then subtract the previous split. You’ll end up with a list that looks like a grocery list—only the items are “save 0.3 seconds on the left‑door glitch” and “skip the cutscene after level 3.” ## Master the glitch timing Glitches are the bread and butter of Any% runs. They’re also the place where most runners lose time because they’re hard to repeat exactly. ### The “frame‑perfect” myth People love to call a glitch “frame‑perfect” and then act like it’s impossible to master. In reality, most “frame‑perfect” tricks have a small window—usually a few frames, which translates to a few hundredths of a second. If you can feel that window, you can hit it consistently. ### My go‑to method 1. **Slow‑motion practice** – Use the game’s built‑in slowdown (or a video editor) to watch the glitch at 0.5x speed. 2. **Mark the cue** – Find a visual or audio cue that tells you when to act. For the classic “door skip” in *Super Quest*, the cue is the flash of the lock turning green. 3. **Chunk it** – Break the glitch into three parts: approach, trigger, and exit. Practice each chunk separately before chaining them together. When I first tried the “wall jump” in *Pixel Runner*, I spent a whole weekend just getting the approach right. The trigger was the tricky part, but once I had a reliable cue, the exit became automatic. The result? A clean 0.45‑second shave on that segment. ## Optimize your route Even the best execution can be hampered by a sub‑optimal path. Route planning is where game knowledge meets geometry. ### Map it out Grab a blank map of the level (you can find them on the [community wiki](/runquest/how-to-shave-seconds-off-your-any-run-in-super-mario-odyssey)) and draw a line from start to finish. Then, overlay any known shortcuts. I like to use a red pen for the official route and a blue pen for potential shortcuts. ### Test, test, test A shortcut that looks good on paper might cost you extra time if it forces a hard turn or a risky enemy encounter. Run it a few times in “no‑risk” mode—turn off the timer and just see if you can pull it off without dying. If it feels natural, add it to your timed runs. ### Example In *Chrono Dash*, the “early portal” shortcut saves about 1.2 seconds, but only if you can land the jump on the moving platform without a slip. I practiced the jump in a sandbox mode, then timed it with a stopwatch. After ten clean attempts, I added it to my main route and the time drop was immediate. ## Use the right tools Your hardware and software can be the silent time thieves in a run. ### Controller choice A controller with a short travel distance on the analog stick can shave a few milliseconds per movement. I switched from a standard Xbox controller to a “pro” model with a tighter stick, and my average run time dropped by 0.3 seconds across ten runs. ### Timer setup Most runners use LiveSplit, but the key is consistency. Make sure your split keys are mapped to buttons you can press without breaking your flow, and consult a [practical checklist for real‑time verification](/runquest/how-to-verify-your-speedrun-record-in-real-time-a-practical-checklist-for-every-gamer) to ensure your splits are accurate. I bind “split” to the left bumper because my thumb never leaves it during a run. ### Video capture If you’re recording for verification, use a capture card that records at 60 fps or higher. Lower frame rates can hide split‑second glitches and force you to replay sections, wasting time. ## Practice with purpose Random grinding rarely leads to improvement. Structured practice does. ### The “focus block” method Pick a single segment that costs you the most time. Set a timer for 15 minutes and only work on that segment. No full runs, no distractions. When the timer ends, note any improvement, then move to the next segment. ### Rest is part of the grind Your brain needs downtime to process the muscle memory you’re building. I schedule a short walk after every two focus blocks. It sounds odd, but the fresh eyes help me spot a missed cue that I’d been overlooking for weeks. ### Community feedback RunQuest has a solid community of runners who love to share split data. Post a short clip of your toughest segment and ask for tips. You’ll be surprised how many eyes can spot a tiny inefficiency that you missed. ## Final thoughts Shaving seconds off an Any% run isn’t about magic; it’s about data, precision, and a willingness to tinker with every part of the run. Know your splits, nail the glitches, choose the fastest route, equip the right gear, and practice with a plan. Do that, and you’ll find those elusive seconds slipping away, one deliberate tweak at a time.