Obby Builder Parts Ranked

Obby Builder does not publish a public part ID list, and this wiki will not invent one. Rank categories by the job they do on a live plot: can a runner spawn, rest, understand the route, and finish without guessing. Cash spent on a killbrick before a checkpoint is usually wasted. Cash spent on rainbow cosmetics before a spawn is always wasted. Use this list as a placement order, then follow how to build for gizmos, snapping, and playtest.

The live toolbox includes platforms, traps, checkpoints, buttons, teleporters, signs, music, lighting, and one-way moving platforms, plus later customization. R6 avatars in 10-player servers punish invisible hazards and missing rest points. Online co-op lets two builders place at once, which makes it more important to agree on the S parts before anyone starts decorating. For Robux spends, use the gamepass ranks page.

S tier: finishable bones

Checkpoints are S. A course without a rest point is a demo, not an obby people like. Place the first checkpoint after the opening jumps, then again after every harsh trap or long mover. Spawn and basic platforms are also S. If a runner cannot stand somewhere obvious at the start, they never see the rest of your work. These three jobs — spawn, platforms, checkpoints — are the only parts you must place before you copy a slot code or invite co-op.

A finishable line beats a clever line. Put a clear end pad or teleporter-to-lobby so the server knows the course is done. That finish feeds likes, Trending, and Beat an Obby for other players. If you skip S parts to chase a gimmick, you will rebuild later and still lack a route. The build checklist is the short version of this rule.

A tier: movers, buttons, teleporters, signs

One-way moving platforms are A. They add timing without a huge plot, and they are called out on the live game page. Use them as a single readable beat, not as a forest of invisible conveyors. Buttons and teleporters are also A: they gate a shortcut, send someone back to a checkpoint, or split easy and hard routes. They fail when the destination is unmarked or the button looks like a trap.

Signs are A for instructions, not for lore walls. One short line at spawn (difficulty, checkpoint policy) saves more likes than a paragraph in the sky. Runners on mobile and console need that sign. If you want the plot discovered outside your friends list, pair A parts with the thumbnail and fairness habits on get featured.

Situational and cosmetic parts

Killbricks are situational, not automatic S. A marked hazard that teaches a jump is good. A same-color floor that insta-kills is how you lose the like. Use contrast, a sign, or a preview gap so the trap is readable on first death. Spinning or moving killbricks belong later, after the static line is fair. If you keep dying on other people’s traps, use how to beat obbies rather than copying their worst brick into your slot.

Music and lighting sit at B. Advanced lighting can make a night tower feel finished, and music can sell a theme. Neither one makes a missing checkpoint acceptable. Turn lighting up after the route is beatable in default light, then check that killbricks still read on mobile. Rainbow and other cosmetic recolors are C. They are fine as a signature once the course is done. They are a bad first cash sink, and the Rainbow Parts gamepass does not change that rank.

How ranking changes by course type

A tower still wants S checkpoints every few floors; one-way movers become more valuable because vertical travel is slow. A long hallway wants signs at each new mechanic and fewer teleporters, or runners will skip the work you placed. A co-op showcase can use buttons that need two people, but always ship a solo path so a 10-player server can still finish. When a patch adds new parts, drop them into this job list instead of assuming new equals S. Place the S bones, playtest without coils, then add one A feature and one B mood layer.