Effortless, Very Easy, Easy, and Medium are the first four official difficulty completion badges. A current all-stages walkthrough groups them into stages 1–20, 21–40, 41–60, and 61–80. Use those bands to organize practice, while treating the exact boundaries as community reported until the live course confirms them.
Official badge snapshot
Effortless
ID: 3570799709876979
Official description: Beat the Effortless difficulty.
Recorded awards: 1,907,950
Official · checked 2026-08-27Very Easy
ID: 1548218043980691
Official description: Beat the Very Easy difficulty.
Recorded awards: 1,487,657
Official · checked 2026-08-27Easy
ID: 3745411358397670
Official description: Beat the Easy difficulty.
Recorded awards: 1,222,656
Official · checked 2026-08-27Medium
ID: 706018561464225
Official description: Beat the Medium difficulty.
Recorded awards: 836,485
Official · checked 2026-08-27The counts are dated cumulative API values, not clear rates. Use them only to confirm that each badge has been awarded.
Effortless: make the setup automatic
In the community model, stages 1–20 teach the first band. Center each landing, choose a repeatable takeoff marker, and wait for stable contact before turning toward the next obstacle. The objective is to remove accidental camera and direction changes from your attempts.
Use this section to test the live respawn and stage counter. Public text does not specify exactly how each checkpoint or rejoin behaves, so observe the number before a fall and after returning. That early test protects later progress assumptions.
Very Easy and Easy: read full sequences
For the next two bands, plan beyond the first landing. Identify every safe contact, any moving cycle, and where the camera needs to point after each step. If an obstacle allows a pause, use it to release movement and frame the next target.
Watch one complete moving cycle before committing. Pick a visible cue and start from the same marker. If the result changes while the cue stays constant, review avatar alignment and camera height rather than changing the timing immediately.
When a jump misses, label it short, long, left, right, or hazard contact. Change the matching variable only. This practice is the bridge from Easy into Medium; rushing retries hides the reason for the miss.
Medium: preserve precision across attempts
The community stages 61–80 band is a useful place to shorten attempt sets. Make three controlled tries from the same setup, then pause and compare. If every attempt begins farther from the edge or with a different view, repeating it will not teach a stable route.
On mobile, separate the movement thumb, camera drag, and jump touch. On desktop, avoid a large mouse correction at the edge. Across devices, set the route first and input second.
Use Stages 1–100 for the current 1–121 walkthrough and range-specific troubleshooting. Match two consecutive obstacles before assigning a video number to the live stage.
Confirm a difficulty completion
When you believe a band has ended, wait for the live stage change and Roblox badge notification. If no notification appears, check the badge inventory before replaying. Delivery can be missed visually, and the API description does not state the exact trigger surface.
Do not infer the boundary only from background color. The official badge confirms the name and completion concept, but the color and exact stage division still need live observation. Record stage number and server date if the badge fires at a different point from the community twenty-stage model.
Mistakes that slow early progression
Chaining before landing
Secure contact first. Early camera movement can turn a correct first jump into a failed second one.
Changing every variable
Keep the marker and camera while adjusting one direction or timing choice.
Following a Coil route
Check for movement-changing Passes before copying a takeoff built around extra height or speed.
Assuming the badge failed
Check the Roblox badge inventory and live stage before repeating the completion obstacle.
Move on to Hard
After the Medium band, continue into Hard to Insane. Keep the same fundamentals, but shorten input chains and use smaller attempt sets. The route becomes more demanding; the solution remains evidence-based repetition rather than random speed.