Skip to content

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

  • Basics


    Basic setup, editor testing, publishing

  • Player Specs


    Sizes and speeds of the player and their baseline movement capabilities

  • Spawns


    Player & weapon spawns

  • Props


    Adjust prop behavior for your needs

  • Movement


    Movement types and traversal helpers

  • I/O


    Input/Output wiring concepts

Mapping Tools

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.