Mapping
This section is for creators who want to make a new TTT map, add TTT support to an existing map they made, or build custom map interactions with our mapping tools on s&box.
Start Here
Mapping Tools
-
Pick the right tool before you start wiring things together
-
Player-use controls and role-gated trap controls
-
Role checking rooms, indicators, and tester outputs
-
Enable targets, disable targets, and count signals
-
Rotating doors, sliding doors, and door control patterns
-
Two-position moving objects
-
Multi-stop platforms, elevators, and call buttons
-
Player ride paths for ziplines and slides
-
Trigger boxes, teleports, and push volumes
-
Hurt volumes, break outputs, damage surfaces, and glass
-
Explosive props, explosion targets, and barrels
-
Spawn or consume map objects
Authoring checklist
- Add enough player spawns for the server sizes you expect (32+, ideally).
- Add enough weapon spawns to support a variety of player counts. Prefer random weapon and ammo spawners unless a map wants deliberately consistent placements.
- Name interactive targets clearly when wiring map I/O by name.
- Test map logic as both host and client if possible. Speeds, in particular, for different map components can behave a little differently when you're not the host- so in-editor the timing is right, but with a client instance it isn't.
Good map support is mostly predictable reset behavior
TTT maps are played over repeated rounds. Doors, traps, spawns, buttons, disabled objects, and moving platforms should return to a clean authored state every round.