Tower Creator difficulty labels are community communication, not an objective official score. The community Towers reference says its portal colors are mostly agreed conventions and explicitly notes that builders are not required to use them. Rate the playable route from entrance to finish, explain unusual spikes, and retest after changes to movement or advanced parts.
Judge the route rather than the decoration
A dark frame, intense music, or dramatic camera does not make a tower mechanically difficult. Focus on the actions players must perform: jump distance, platform width, timing, precision, camera control, moving objects, punishments, recovery, and required techniques.
Test outside Edit Mode with ordinary movement. Do not use Noclip, Freecam, Teleport, or a builder spawn near the hard section. Complete the route from the real entrance and record failures by section.
Separate sustained difficulty from one spike. A mostly easy tower with one extreme trick is not described well by averaging everything into a vague label. Either rebalance the spike or mention it clearly next to the overall rating.
Read the community ladder as broad bands
The community page documents a long EToH-inspired sequence beginning with Easy, Medium, Hard, Difficult, and Challenging, then continuing through Intense, Remorseless, Insane, Extreme, Terrifying, Catastrophic, Horrific, Unreal, and a nil label. It also associates colors with these names.
Use those names only when they appear in the current game or are understood by your intended audience. Exact colors and portal options can change, and dark shades may be hard to distinguish under different lighting. Pair color with text.
For most first projects, the early labels are enough. Higher labels imply specialized techniques, severe punishment, or consistency demands that should be demonstrated by multiple qualified testers, not chosen because the name sounds impressive.
Compare the factors that create difficulty
Difficulty should rise because the required movement is harder, not because the route is invisible, the camera clips, collision is misleading, or a trigger fails randomly. Those are design or technical problems.
Run a useful test session
Choose testers familiar with nearby difficulty bands. Do not explain every jump. Ask each tester to note where they failed, why they thought it failed, how long recovery took, and whether the next action was visible. A clear but demanding obstacle is better evidence than confusion.
Run several full attempts. A single successful clear can hide inconsistency; a single failure can reflect unfamiliarity. Compare how quickly testers learn the route and whether later attempts become repeatable.
Test on the current version and record the date. Moving parts, physics, camera, triggers, and device performance can change the result. A tower built in Legacy may need a new rating in the root Rescripted-era experience.
Calibrate an uneven tower
Map the route section by section. Give each a broad difficulty estimate and mark recovery cost. If one section stands far above the rest, decide whether it is a deliberate finale, an optional route, or an unintended spike.
Reduce accidental difficulty first: fix invisible collision, cramped camera, unclear starts, delayed loads, unreliable resets, and misleading colors. Then adjust geometry, timing, or punishment. Retest the complete approach because a difficult section feels different after several demanding floors.
Use rest platforms and recognizable milestones to support longer towers. Length and difficulty are separate. A long route of moderate obstacles can demand endurance without containing an extreme individual jump.
Label and describe the final result
Show a text difficulty label near the entrance and use a current community color only as reinforcement. Include approximate length, route type, required techniques, unusual camera or visual effects, and the hardest sustained section. Mention an isolated spike rather than hiding it.
Avoid decimal precision unless the community process that produced it is explained and current. “High Challenging with a short Intense spike” communicates more honestly than an unexplained two-decimal score.
When feedback disagrees, record the tester experience rather than choosing the highest label. A specialized technique may feel easy to an expert and impossible to a new player. The intended audience should shape the final description.
Common rating mistakes
- Rating from individual obstacles without completing the full route.
- Using portal color as proof of difficulty.
- Treating bugs, lag, or unreadable collision as legitimate challenge.
- Ignoring the time lost after a fall.
- Copying a Legacy rating after mechanics or parts changed.
- Calling a community convention official or mandatory.
- Increasing the label to make the tower sound more prestigious.
- Hiding a sharp spike inside a lower overall category.
Retest after meaningful changes
Retest when geometry, timing, movement properties, checkpoints, resets, camera, or a major Tower Creator update changes. Keep the old rating as historical when players still share an older ID. Update the tower record with version and date.
Use Play and Share Towers to attach that record to the exact tower ID. Use Tower IDs to distinguish a current tested destination from an old community lead.
Current confidence boundary
The ladder names and portal-color concept are community reported from the Tower Creator Towers page. The page itself says the convention is mostly agreed and not required. Current selectable labels, exact colors, enforcement, and cross-version consistency require live verification.