Verification is the game’s completion requirement for uploading a created level; it is separate from receiving a star rating. For a Classic level, practise sections first and then complete the required full run in Normal Mode. Platformer checkpoints follow different rules. This guide separates creator verification from community “first verifier” credit.
» Verification for Creators
Verify the finished version before uploading. Passing the upload check does not guarantee that RobTop will rate the level or that every optional route is free of problems. Test those routes separately and review the official level FAQ for rating and upload issues.
The realistic process for verifying your own level:
- 1. Finish building and testing the level using Practice Mode to check difficult sections and transitions.
- 2. Practice the full level using checkpoints until you can consistently clear large sections without dying.
- 3. Lengthen your practice runs as consistency improves. For Classic verification, move toward a full Normal Mode attempt rather than relying on player checkpoints.
- 4. Attempt full Normal Mode runs once you’re able to reliably clear the level in Practice Mode without needing checkpoints.
- 5. Complete the finished Classic level in Normal Mode. Check that the game marks it verified before attempting upload; changes to the level may require another verification.
If you’re regularly failing the same section even in Practice Mode, that’s often a sign the level’s difficulty or spacing needs adjustment before it’s ready to publish, not just that you need more attempts.
» “First Verifier” on Hard and Demon Levels
For difficult, especially demon-rated, user-created levels, the “first verifier” is the player who first completes the level in Normal Mode often the creator themselves, but sometimes a skilled player the creator asks to test and verify a very hard level before release. This is a community credit, typically shown alongside the level, and it exists because verifying an extremely hard level can itself be a notable achievement, separate from having designed it.
This is different from simply completing a level after it’s published and already known to be beatable a first verifier proves it’s beatable at all, often after extensive practice on a level that had never been cleared by anyone before.
» Why Verification Matters
A completed run shows at least one playable route, not proof that every branch and trigger is correct. Test optional paths and transitions separately. Verification is part of preparing a level for upload; it does not guarantee a difficulty rating.
» Common Issues During Verification
- A section works in isolation but fails in full runs. Compare entry speed, gravity, mode, triggers and timing from the actual start. Fatigue may also matter; a successful isolated section does not rule out a layout problem.
- Inconsistent hitboxes discovered late. Sometimes a jump that looks fine visually has an unreliable timing window. This is exactly what verification is meant to catch before other players run into it.
- Verifying too early. Test transitions and optional routes before attempting repeated full runs. Keep your verification copy aligned with the version you intend to upload.
» Frequently Asked Questions
» Conclusion
Verify the final version, confirm upload eligibility and keep rating expectations separate. For publishing errors or questions about stars, use RobTop’s official level FAQ. A successful verification is not a promise of a rating.