Review the cause, not just the crash
A Survive The Slope run review should find the first decision that meaningfully reduced your chance of survival. The final impact is easy to remember, but it may only be the last link in a longer chain. An early poor landing can remove the safe line for the next obstacle and lead to a crash several seconds later.
The one-minute checklist
After each important run, answer these questions:
- What distance did I reach compared with my typical result?
- Where did the first major loss of control begin?
- Was the cause visibility, timing, route choice, landing, recovery, or accumulated damage?
- Did a recent upgrade appear relevant?
- What one action will I change on the next run?
Keep the answer short. The review should produce a test, not a long diary.
Distinguish three kinds of result
| Result | Meaning | Next step |
|---|---|---|
| Better distance with cleaner control | The change may be working | Repeat it for confirmation |
| Better distance with chaotic control | Possible lucky run | Test again before adopting it |
| Worse distance with a clear new mistake | The test may still be valid | Correct the mistake and repeat |
This prevents one score from deciding everything. A tactic becomes reliable when it improves both results and control across multiple attempts.
Evaluate upgrades fairly
If you purchased an upgrade, compare a small group of runs before and after it. Keep the route strategy and practice goal as similar as possible. Otherwise, a change in play style can hide the upgrade’s effect.
Read the current upgrade names and effects in the live menu. Note the exact problem each purchase is supposed to solve.
Find the earliest useful correction
Suppose the final crash occurs at a wall. Ask what happened before it. Did you enter the area from a bad angle? Did a previous collision force that angle? Did you notice the open route but commit too late? Move backward through the chain until you find an action you can change.
The best correction is usually earlier and smaller than the final emergency response. “Scan earlier before the approach” is more useful than “avoid the wall.”
Keep a compact session log
Use four fields: distance, first major error, run purpose, and next change. A sample entry could read: “Record attempt; below typical distance; late route commitment; choose the wider line as soon as it appears.”
After five entries, look for repetition. If the same cause appears three times, make it the only goal of the next practice block. If the causes are scattered, improve general awareness before chasing a specialized fix.
FAQ
Do I need to review every run?
No. Review meaningful practice, upgrade tests, and record attempts. Routine earning runs can use a shorter mental check.
What if I cannot remember the first mistake?
Slow down your next attempt and focus on one section at a time. The goal is observation, not a record.
Should I change several things after a bad run?
Change one variable when possible. Multiple changes make the result difficult to interpret.
How many runs should I compare?
Three-run groups provide a practical starting point. Use more when results vary widely.
What is the most important review question?
Ask which earlier decision left you without a safe recovery. That usually reveals a more useful correction than the final collision alone.