Tower Creator Parts Guide

Tower Creator parts range from plain geometry to objects that move players, change physics, display dialogue, play audio, alter lighting, or activate another system. Choose a part by the outcome you need, not by how impressive its name sounds. Place it in a small test area, inspect the current Properties panel, add required links, and verify it outside Edit Mode before copying it into a floor.

Community documentation checked on September 15, 2026 says its main Parts page covers the Rescripted-era catalog and explicitly separates older Legacy material. That makes it a useful working index, but exact ranges, availability, and limits still need a current in-game check.

Pick the right Parts guide

Use the Parts List when you know the desired effect but not the object name. Use Properties when the right object is selected but its appearance or behavior is wrong. Use Advanced Parts when the object depends on movement, links, attachments, triggers, reset rules, or multiplayer testing.

Understand the main part families

Basic geometry builds the route. Community documentation lists the ordinary Part alongside seat-like, slippery, trip, truss, and beam functions. Start here for floors, walls, landings, rails, ladders, and visual direction. A basic route is easier to tune than one made entirely from moving objects.

Movement and interaction objects include documented conveyors, X-Pushers, swings, vines, ziplines, wall-jump surfaces, teleporters, turrets, and clone-object helpers. These can change the player’s position or create dynamic obstacles. Their useful behavior often depends on orientation, collision, an endpoint, or an explicit link.

Boosters and zones change movement or player state. Community lists include jump, gravity, speed, health, slope, music, and dialogue-related objects. Place a clear entrance and exit around every zone so players know when the effect begins and ends.

Buttons, lighting, and triggers change other objects or the presentation. Do not add them until the physical path works. A button or trigger should have an obvious input, a limited set of outputs, and a visible reset plan.

Meshes and decoration create recognizable shapes and theme, but they must not hide collision or the next landing. Decorative density also affects performance. Use detail to clarify the tower before using it to fill every empty space.

Read shared properties before unique behavior

Community Properties documentation lists common fields such as collision, shadow casting, color, material, surface, transparency, reflectance, and mass. Start with appearance and collision because they immediately affect route readability and movement. Then inspect the part-specific fields that create its unique action.

Do not assume a transparent part is non-collidable or a visible object is solid. Test both appearance and physics. If a property accepts a number, make a small change and observe the result. Avoid extreme values copied from old videos; current validation or server behavior may differ.

For a complex part, record the current object name, properties that differ from defaults, linked objects, activation source, reset behavior, and last successful rejoin test. That record is enough to diagnose most breakages without reproducing an entire tower.

Build linked objects as a small graph

Think of a linked system as nodes and arrows. One node receives player input, another transforms or gates the signal, and an output creates the visible result. Select each node in order and confirm the current link view. Use names or colors that make references easy to trace.

Begin with one input and one output. Activate it twice if repetition matters, then reset and rejoin. Add delays, stop/resume logic, multiple outputs, or chained triggers only after the direct connection survives. The Triggers hub gives focused workflows for camera, cutscene, and pushbox systems.

A copied advanced object may preserve properties or references you did not intend to share. After cloning, inspect every unique field and link. Test the original and copy separately before allowing both into the same sequence.

Choose parts for player readability

Players need to know what is safe, dangerous, movable, interactive, or decorative. Use a consistent visual language: one color family for the route, one for danger, one for optional interaction, and enough contrast around text or portals. Do not communicate an essential difference by color alone; shape, placement, motion, or labels should reinforce it.

Show the start and result of a moving system. A zipline needs an understandable pickup and destination. An X-Pusher needs space for its travel. A teleporter needs a landing that does not trap the character. A gravity or speed change needs a clear boundary and a way to understand when normal movement returns.

Camera and lighting effects should support direction, not obscure the obstacle. Test them with ordinary camera control and on a second device when possible. Offer visual rest between strong effects.

Keep performance and part budget in mind

Public community sources disagree or age quickly on exact part limits, slot sizes, and purchases. Read the current in-game counter or message before planning a tower around a numeric maximum. Leave room for fixes, indicators, and reset parts rather than using the entire budget on decoration.

Reduce repeated invisible geometry, distant animation, dense effects, and unnecessary moving systems. Test a complex floor in the same kind of crowded server a player may use. The Settings guide describes scene-reduction options, but a visitor should not need a hidden setting just to understand the route.

A safe part-testing worksheet

What still requires current verification

The exact total number of parts, numeric ranges, part budget, custom music process, current material set, and Legacy compatibility can change. This hub deliberately uses a “currently documented” index rather than claiming completeness. When the current game disagrees with a community page, follow the live object name and record the date.

Start with Tower Creator Parts List, then open Part Properties for the selected object. If it needs explicit activation or sequencing, continue to Tower Creator Triggers.

References

• Community Parts reference
• Community Properties reference
• Community Rescripted reference