Tower Creator uses a claimable area in the active server as the place where you build, while your account may also choose among personal project slots. Confirm both before entering Edit Mode: claim an unoccupied area, then verify the intended saved project is loaded. Do not assume “slot” always means the same thing when reading an old tutorial.
Claim an in-server building area
Walk through the lobby and look for an unoccupied tower area. Community documentation describes holding or pressing the interaction prompt to claim it, with input differing between keyboard, mouse, touch, and other devices. Follow the prompt shown in your current session.
Check that the area now identifies you or your project before editing. If another player owns it, enter only to play unless they explicitly grant build access. Never try to bypass slot ownership through an external script.
When every visible area is occupied, join another server or wait for a supported opening. A public server-size value does not directly prove the number of buildable plots, so this guide does not turn server capacity into a slot count.
Select the intended personal project
Before placing or deleting a part, identify which saved project the claimed area is displaying. Use the current Tower Menu or project selector and read its name, number, thumbnail, banner, or other visible identity. Record the choice in your build notes.
Create a harmless marker, finish Edit Mode, and rejoin to test persistence when working with an unfamiliar project selector. Remove the marker after confirming the same project returns. This small test is safer than discovering after a long session that changes went to the wrong slot.
Community sources have published historical default counts, maximums, ticket costs, Robux purchases, and Rescripted changes. Those values are account- and update-sensitive. Read the current interface before spending currency or planning a fixed number of projects.
Check tickets, slots, and limits as separate live values
Do not combine old numbers into one economy rule. A ticket balance, a personal project-slot count, an in-server building area, and a per-project part limit answer different questions. Use the current account UI and record each result with a date before making a purchase or starting a large tower.
Tickets
Use: only the purpose shown by the current Tower Creator interface.
Current public status: community sources mention tickets, but acquisition routes and historical daily-streak claims conflict across eras.
Verify: visible balance, earning source, cooldown, version, and UTC date.
Amount and earning method need in-game testingPersonal project slots
Use: choose which saved tower project loads into a claimed server area.
Current public status: the project-slot concept is community documented; default count and maximum are not treated as current facts here.
Verify: account-specific count, selected project identity, add-slot action, and resulting total.
Concept documented · counts need testingExtra-slot offer
Use: only when the live purchase screen states the currency, price, and exact result.
Current public status: older ticket and Robux values are inconsistent and may not apply to the current root experience.
Verify: seller, currency, price, repeatability, account effect, and version before confirming.
No current price promisedPart limit
Use: plan enough budget for route fixes, indicators, resets, and final testing.
Current public status: search and community material show player interest, but no stable current limit was verified for this guide.
Verify: the live counter or warning in the exact project and version; check whether the total changes by slot or account.
No historical limit reusedIf the interface does not show one of these fields, leave it unknown. Do not spend currency to test a number from an old guide, and do not design against a maximum that was recorded for Legacy or another account.
Understand the starting template
The community Tower Slots page describes a classic tall tower template made from stacked hollow floors in a vertical frame. That is a useful reference for traditional obby construction, not a requirement that every project keep exactly the same height, floor count, or route shape.
Inspect the template’s entrance, portal, floor divisions, boundaries, and empty work area. Build near the bottom for the first test, and keep advanced systems away from slot edges until their movement is understood. A recovery platform below the early route saves time during testing.
Community documentation also gives historical plot dimensions and describes tall vertical space. Because current boundaries can change, move a disposable marker toward each edge and observe the live constraint rather than relying on a copied number.
Separate play access from build permission
A visitor may be able to enter or play your tower without permission to modify it. Build permission is more powerful. Use the current Team or Permission interface to grant the narrowest access required, and only to a player you trust.
Agree on the exact floor or system the collaborator will edit. Create a known-good milestone first, stay in the session for their first changes, and remove access when finished. If a player only needs to test, do not grant building privileges.
Review Save and Revert before collaboration. Community sources confirm a recovery concept but do not establish one stable backup count or confirmation flow across versions.
Decide when another personal slot is useful
Use another project for a genuinely separate tower, a version-safe experiment, or a disposable advanced-system lab. Do not purchase or unlock another slot merely because the current project is disorganized; rename sections, make a test corner, and protect milestones first.
Before any purchase, read the exact current price, currency, resulting slot count, and whether the transaction can be repeated. Do not rely on historical claims about tickets, Robux, weekly rewards, or maximums. Never buy through an external site or share account credentials.
For Legacy comparison, use a separate test project rather than moving a valuable current tower blindly. The Rescripted vs Legacy guide explains the evidence boundary around migration.
Slot troubleshooting
Finish a slot session cleanly
Complete a play test, leave Edit Mode, wait for any current save feedback, and record the project and milestone. Remove temporary collaborator permission. Rejoin after major work and confirm the intended project returns with its geometry, properties, and links intact.
When ready for visitors, use Play and Share Towers to prepare the entrance, difficulty description, ID, version scope, and verification date.
Current confidence boundary
The claimable-area concept, tower template, personal project slots, and permission relationship are community reported. Exact counts, plot dimensions, price, ticket economy, purchase limits, interaction keys, and cross-version behavior require live verification on the current account and build.