Tower Creator Advanced Parts

Advanced parts make Tower Creator routes move, react, transport, speak, play audio, change lighting, or alter the player. Add them only after the static route works. Build one object in a visible test area, inspect its current properties, connect only the required references, and verify activation, reset, multiplayer behavior, and persistence before copying it into the tower.

Choose an advanced part by outcome

For surface motion, start with a Conveyor. For a platform that travels along a designed path or range, inspect the current X-Pusher. For hanging traversal, compare Swing and Vine. For guided travel between linked points, inspect Zipline. For a direct destination change, use the current Teleporter flow.

For player-state changes, look at jump, gravity, speed, health, and slope objects documented in the live catalog. For communication, use Dialog Part or a display-oriented button. For presentation, inspect Music Part, Sound Trigger, Lighting Changer, glow, skybox, camera, and shake effects.

For a physical puzzle object, Clone Object Reference and its remover are central to community pushbox patterns. For projectile systems, the community documents Turret and Bullet Velocity Changer. Every one of these systems needs a clear player reason; do not add it only because it is available.

Check the currently requested advanced systems

These cards are a decision index, not a promise that every system appears unchanged in every Tower Creator version. If the current Parts panel does not contain the named object, do not substitute a similarly named object or force an old configuration into the slot. Confirm the editor path, then choose the nearest supported outcome from the Parts List.

Moving platforms and traversal objects

Place a moving object in open space and mark its start and destination with ordinary geometry. Confirm orientation before changing speed, force, easing, limits, or physical response. A platform that clips a wall or outruns its landing is a geometry problem before it is a property problem.

For X-Pusher, community Rescripted notes describe travel limits and physics-related fields. Use a slow visible test and confirm which axis the current object follows. For Conveyor, check direction from both approaches and ensure visual cues match movement. For Swing and Vine, provide a safe dismount and recovery surface.

Rescripted-era documentation says Ziplines depend on linked points for curved paths. Add a simple two-point route first. Confirm pickup, direction, dismount, momentum, and loop behavior where those options exist. Add extra points only after the direct route survives a rejoin.

Buttons, teleporters, and linked actions

A button should make one obvious change. Link it to a visible test platform, trigger it once, wait for any timer, and trigger it again. Check inversion and reset only after direct activation works. If the button accepts different interaction types, test the one players will actually use.

For a Teleporter, place the destination on a safe, unobstructed landing with enough headroom. Mark the entrance and destination. Trigger it from multiple approach angles and confirm the player cannot arrive inside a wall or immediately fall. When multiple locations are supported, add destinations one at a time.

Use Trigger Button when a current client object expects a trigger-style activation source. Label or color inputs consistently. The Triggers hub explains stop, resume, delay, repeated activation, and rejoin tests.

Zones, health, and movement changes

Design a visible boundary for every zone. A player should know where gravity, speed, jump, health, slope, or music behavior begins and where normal behavior returns. Use geometry and labels in addition to color so the route remains understandable under different graphics and accessibility needs.

Build a straight safe corridor for the first test. Enter slowly, enter while jumping, and enter off-center. Leave the zone, reset, and confirm the effect ends as intended. Add difficult obstacles only after the transition itself is predictable.

Pair changer and resetter objects where the current system provides them. Without a clear reset, a temporary obstacle can affect the rest of the tower and make later sections impossible to evaluate.

Dialogue, music, and lighting

Dialog Part is documented as displaying text and supporting more detailed text effects in Rescripted notes. Keep dialogue concise, readable, and optional when the current properties allow. Test whether another player receives the same sequence and whether it can be skipped or repeated.

Music Part is documented as playing preset music within an area, with community claims about submissions through Discord. The exact catalog, SoundID rules, and submission process are not first-party confirmed here. Use only audio accepted by the live experience and follow current creator rules. Provide non-audio cues for every essential route change.

Lighting, glow, skybox, shake, and camera effects can disorient players. Use them to establish a scene or highlight direction, then return to a stable baseline. Test on a lower graphics level and avoid rapid changes that obscure the next obstacle.

Xen's Rescripted Music Parts video is a useful visual reference for the object. Confirm the current catalog and controls in your own session.

Clone references, pushboxes, and projectiles

Community documentation describes Clone Object Reference as creating clones of linked objects through activation, with a remover object for cleanup. This pattern supports pushboxes and resettable puzzle pieces. Start with one source object, one trigger input, one spawn position, and one remover area.

Give the clone room to move and make its collision visible. Test one spawn, repeated input, simultaneous objects only if supported, removal, player reset, and rejoin. The Pushbox tutorial provides a focused build order.

For Turret and Bullet Velocity Changer systems, define projectile direction, collision, lifetime, activation, and safe boundaries using the current fields. Test away from the main route and other players. Do not use old extreme values or undocumented properties.

Advanced-part troubleshooting

Current confidence boundary

The named object families on this page are supported by current community Parts, Properties, and Rescripted documentation checked September 15, 2026. Exact menus, numeric ranges, limits, custom audio, and multiplayer state require live confirmation. Use the current interface and omit an unsupported setting rather than guessing.

References

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