- CICADAMATA speedrun routes should begin with a clearly defined category and ruleset.
- Level practice is the fastest way to isolate mistakes before attempting a full session.
- Glitch settings change the route, so compare unrestricted and glitchless runs separately.
- Split tracking helps identify where time is lost across repeated attempts.
- Leaderboard review gives your personal best a clear competitive reference.
CICADAMATA Speedrun Basics
A successful CICADAMATA speedrun starts with category discipline. The current leaderboard structure separates full-game attempts from individual levels and also divides runs by objective, difficulty, and glitch rules. Before practicing, decide whether you want a fast completion, a challenge-focused clear, or a route that targets every enemy.
The leaderboard snapshot dated August 24, 2026 lists 31 levels and several Sphere Rush categories. These include Any%, DMND%, 100%, AllEnemies%, and Low%. Difficulty and glitch filters further divide the available results, with Normal difficulty and both Unrestricted and Glitchless options shown.
Video Highlights:
- A 3-1 CASCADE demo demonstrates a sub-30-second level attempt.
- The recorded time is 29.983 seconds.
- The run is useful for studying movement rhythm and finish-line consistency.
- Treat the demonstration as a reference point, not as a universal route for every category.
| Speedrun Element | What It Changes | Recommended Starting Point |
|---|---|---|
| Full game | Measures a complete route across the game | Use after learning individual levels |
| Level | Focuses on one stage and one target time | Best for early practice |
| Any% | Prioritizes completion speed | Choose a ruleset before routing |
| AllEnemies% | Adds an enemy-clear objective | Track required encounters carefully |
| Glitchless | Excludes accepted glitches | Good for consistent route development |
| Unrestricted | Allows the category’s permitted techniques | Use only with matching leaderboard rules |
Start with one level category and one ruleset. Changing objectives during practice makes split comparisons less useful and can hide the reason an attempt improved.
Level Learner
- Practice one stage at a time
- Build reliable openings
- Compare attempts by split
Route Builder
- Map the full sequence
- Record required objectives
- Separate safe and risky options
Leaderboard Runner
- Match the listed rules
- Capture valid attempts
- Submit a clean personal best
Choose a Category and Build Your Route
Category choice determines what counts as a good route. Any% generally emphasizes speed, while AllEnemies% demands additional objective control. The listed Sphere Rush categories also include DMND%, 100%, and Low%, so runners should verify the exact category rules before treating a strategy as leaderboard legal.
Use the CICADAMATA leaderboard page on Speedrun.com as the rules and submission reference. The page provides separate tabs for leaderboards, levels, news, guides, resources, forums, streams, and statistics. It also shows the currently available category and filter structure.
| Category | Primary Focus | Practice Question |
|---|---|---|
| Any% | Fastest valid completion under the category rules | Which sections provide the largest safe time saves? |
| DMND% | Category-specific completion objective | Which route choices are required by the rules? |
| 100% | Broad completion target | What must be collected or completed before the finish? |
| AllEnemies% | Defeat or clear every required enemy | Can each encounter be handled without losing route speed? |
| Low% | Completion with restricted progression or resources | Which upgrades or actions are avoidable? |
When planning a route, divide each level into three parts:
- Opening: The first movement sequence, where hesitation can affect the entire attempt.
- Core section: The main route decision, objective, or hazard sequence.
- Finish: The final approach and timing point, where rushed inputs can invalidate a strong run.
Do not optimize every section at once. First, find a stable route that you can repeat. Then test one adjustment at a time. A route that saves a small amount but causes frequent resets may be weaker for real attempts than a slightly slower line with better consistency.
Never transfer a technique between Any%, AllEnemies%, 100%, Low%, Glitchless, and Unrestricted boards without checking the matching ruleset. A fast route is only useful when it belongs to the category you are running.
| Route Draft Stage | Goal | Evidence to Record |
|---|---|---|
| Baseline | Finish the level consistently | Completion time and reset points |
| Safe optimization | Remove hesitation and unnecessary movement | Best stable split |
| Risk testing | Try a faster but less reliable option | Success rate across attempts |
| Final route | Select the best repeatable line | Chosen route and category rules |
Step-by-Step Practice Workflow
Practice should convert a long run into small, measurable decisions. Begin with the level that best matches your current skill and category goal. The listed board includes stages such as 1-1 AENSLAND, 1-2 MANDALA, 1-3 REVERIE, 4-2 HARE, and 6-1 ONEMORE, making level-based training practical even when a full-game attempt is not yet consistent.
Lock the Category
Select the exact objective, difficulty, and glitch setting before timing attempts. Write the ruleset at the top of your notes so every practice result remains comparable.
Record a Baseline
Complete the level using the safest route you know. Record the total time, major mistakes, and the point where the run stopped feeling controlled.
Divide the Level
Create splits for the opening, core section, and finish. If the stage has a major objective or encounter, give it its own split so the source of lost time is visible.
Test One Change
Change only one movement, encounter decision, or route choice per practice block. Repeat the section several times before deciding whether the adjustment is useful.
Run From the Start
Once the individual sections are stable, connect them into a complete attempt. Keep the route unchanged until you have enough results to judge consistency.
The most important practice number is not always your fastest isolated split. A strong route combines speed with repeatability. Track both your best time and your typical time for a section. If a technique saves time only under perfect conditions, label it as a risk option rather than making it the default immediately.
| Practice Metric | Meaning | How to Use It |
|---|---|---|
| Best split | Fastest recorded section | Shows the route’s potential |
| Average split | Typical performance across attempts | Measures consistency |
| Reset count | Attempts abandoned before completion | Identifies unstable sections |
| Mistake type | Repeated input or timing error | Guides targeted drills |
| Full clear | Completed level or run | Confirms the route connects |
Promote a risky shortcut to your main route only after you can repeat it without allowing one successful attempt to define the entire strategy.
Improve Level Times and Personal Bests
The public snapshot on August 24, 2026 shows active level competition, including a 29.216-second entry for 1-1 AENSLAND AllEnemies% Unrestricted, a 1:08.899 entry for 4-2 HARE AllEnemies% Glitchless, and a 25.849-second entry for 6-1 ONEMORE Any% Unrestricted. These examples show why comparisons must include the level, category, objective, and ruleset together.
A time from one board should not be used as a direct target for another board. Instead, use it to identify the scale of improvement available in a specific category. For example, a runner working on a level board can compare their own splits first, then study the leading result for route ideas.
Movement
- Reduce pauses
- Keep inputs deliberate
- Drill the opening
Objectives
- Know required targets
- Avoid missed conditions
- Preserve route order
Risk Control
- Mark dangerous shortcuts
- Use a safe backup
- Reset with purpose
Timing
- Maintain consistent splits
- Review weak sections
- Protect strong attempts
| Leaderboard Example | Category | Time |
|---|---|---|
| 1-1 AENSLAND | AllEnemies% Unrestricted | 0:29.216 |
| 4-2 HARE | AllEnemies% Glitchless | 1:08.899 |
| 6-1 ONEMORE | Any% Unrestricted | 0:25.849 |
| 1-3 REVERIE | Any% Unrestricted | 0:22.416 |
| 1-2 MANDALA | Any% Unrestricted | 0:20.983 |
Use the following improvement cycle:
- Review: Identify the largest time loss, not merely the most visible mistake.
- Rehearse: Repeat the relevant section without restarting the entire run.
- Connect: Practice the transition into and out of that section.
- Validate: Run the complete level and compare the result with your baseline.
- Document: Keep the route notes updated so successful changes remain consistent.
A personal best is more useful when you know why it happened. Record whether the improvement came from cleaner movement, a faster route, fewer resets, or better objective execution.
Leaderboard Readiness and Submission Checklist
The Speedrun.com page lists 25 followers, 143 runs, and 24 players in its August 24, 2026 snapshot. It also includes a “Submit run” option and separates full-game and level leaderboards. Before submitting, confirm that your recording, category, and time all match the board you selected.
A leaderboard-ready attempt should be easy to verify. Keep the recording focused on the run, preserve the visible timing information required by the rules, and avoid editing the file in a way that makes the result difficult to review. If the rules page requests additional proof, include it with the submission.
Leaderboard Readiness:
- Confirm the exact category, difficulty, and glitch setting
- Check that the recording covers the complete submitted attempt
- Verify the final time and level name before submission
- Add the correct leaderboard URL and run description
- Keep route notes for future personal-best attempts
| Submission Check | Why It Matters | Runner Action |
|---|---|---|
| Category match | Prevents invalid comparison or placement | Select the exact board before recording |
| Level or full game | Determines the required run length | Confirm the title shown on the leaderboard |
| Ruleset | Controls allowed techniques | Match Glitchless or Unrestricted settings |
| Time verification | Supports accurate ranking | Review the final timer and result |
| Proof quality | Helps moderators assess the run | Submit a clear, complete recording |
The board’s separate filters make organization especially important. Name your local files with the date, category, level, and attempt number. For example, use a format such as 2026-08-24_AnyPercent_1-3_Reverie_Attempt-01. Clear names make it easier to find the run that produced your best split.
Save the original recording and your route notes until the run has been reviewed. A clean archive helps resolve questions and makes future comparisons easier.
CICADAMATA Speedrun FAQ
Q: What is the best CICADAMATA speedrun category for a beginner?
A level-based Any% board is a practical starting point because it limits the practice area and gives you a clear completion target. Choose the difficulty and glitch setting before timing attempts.
Q: Should I practice full-game runs or individual levels first?
Practice individual levels first. Level attempts expose route problems quickly, while full-game attempts are more useful after the major sections can be completed consistently.
Q: What is the difference between Glitchless and Unrestricted runs?
Glitchless and Unrestricted are separate leaderboard filters. Glitchless excludes techniques classified as glitches, while Unrestricted permits the techniques allowed by that category's rules.
Q: Where can I submit a CICADAMATA speedrun?
Use the CICADAMATA leaderboard page on Speedrun.com and select the matching level or full-game board. Review the listed rules and submission requirements before uploading your attempt.
Do not compare times across different objectives or rulesets as if they were the same race. Category accuracy is part of speedrun accuracy.