- Level
- Beginner
- Before you start
- A saved multiplayer scenario, such as courtyard_layout. No Editing Kit tags needed.
- You will make
- A tested teleporter pair and a map whose pickups, starts and mode filters have been checked in play.
Shortcuts use Ctrl; Cmd also works on macOS, and Alt is Option. Keep the pointer over the viewport for editing shortcuts. Save before switching projects.
Choose the game you are building for
Save a copy as courtyard_gameplay. Start with Slayer. Keep the base map's original starts and goals while learning: deleting a marker or objective before understanding its job can break modes that already work.
The game type filter in the viewport header helps inspect one mode's objects. It changes what you see in the editor. The game type chosen when hosting decides what actually plays.
Build a teleporter pair
- Place a senderSearch the object browser for a teleporter sender and drag it onto clear ground beside one end of your route. Select it and find Channel in its Forge properties.
- Pick a channelChoose Channel A, or another channel no existing teleporter uses. Sharing a channel with an existing pair can produce extra destinations.
- Place a receiverFind a receiver and place it at the other end. Give it exactly the same channel. Rotate it toward safe ground and leave room around it for a player to emerge.
- Check who can use itSet Takes for players. Add vehicles only if both ends have enough clearance. Check Place at start, Symmetry and Game types on both ends.
- Test the directionPress F5, walk into the sender and check where you emerge. A sender and receiver make a one-way link. Use additional appropriate nodes for a return route, then test that route separately.
Place pickups with a purpose
Return to editing and add a weapon in a location players can reach from more than one direction. Set its Respawn time and Spare clips. Check Place at start; turning it off delays its first appearance until its respawn time has passed.
Add one vehicle only if your route has space for it. Check its Abandoned delay and the clearance above it. Do not put a vehicle inside fixed cover: physics can destroy it where it stands, including in the compiled map.
Inspect starts and objectives
- Find the startsUse the outliner and View → Debug Drawing to inspect player starts. Frame one and check that its feet are over a walkable surface, with open space above it.
- Move one at a timeMove an existing start clear of the cover you added and turn it toward the playable area. Playtest after each change. Add a Player start from the Add menu only when you need another marker; new markers need a rebuilt map to reach the game.
- Inspect mode objectsFor a team or objective mode, select its existing goals and review Team, Game types, Spawn order and Boundary. A goal's type comes from its object tag; an ordinary crate does not become a goal just because it has a boundary.
- Test the chosen modeCompile the map, open the game separately and host it with your chosen game type. The Kit's standard multiplayer playtest is Slayer, so use a hosted game to check flag capture, scoring, team assignment and respawning.
Check the finished route
- Spawn and respawn several times. No start should face a wall, sit inside a block or drop the player out of bounds.
- Use every teleporter. Check the destination, facing and vehicle clearance where applicable.
- Pick up the added weapon and check its ammunition. Check that your mode places the intended objects, with the right team and symmetry settings.
- Walk around every goal boundary. Visual placement and the scoring volume can have different sizes.
| Problem | What to inspect |
|---|---|
| Teleporter does nothing | Matching channels, sender and receiver types, Takes, the active game type, and Place at start. |
| Object appears in one mode only | Its Game types and Symmetry settings. The viewport filter is only an editing aid. |
| Start or goal looks correct but behaves incorrectly | Test the compiled map in the intended game type. A successful Verify Map cannot prove gameplay rules. |
Next step
Light the route or compile, verify and share it. Reference: Forge properties, markers, Forge teleporters.
