Designing Better Battles

If every fight ends at the same doorway, you do not need more buildings. You need another decision.

A good arena lets players choose how to approach a fight, gives opponents a chance to read that choice, and makes retreat possible without making everyone impossible to catch. That balance comes from routes, cover, height, and the rules those features serve.

We will improve Switchyard, the simple two-team arena from Your First Playable Map. Keep its footprint. Change the decisions inside it.

Before you begin

Bring a saved map that can already run a complete match, a known ruleset, and a small group willing to swap sides and repeat a test. You should be comfortable moving, scaling, copying, and aligning pieces. These are documented Sandbox workflows.^[3][5]

Evidence boundary: editor capabilities are cited where used; route layouts and playtest methods are our recommendations. This guide is not an in-game verification of the current version. Historical tutorials can teach technique without proving today's bindings, limits, or default rules.

You will leave with:

• Before-and-after plans for the same arena.
• A ground route, a protected alternative, and a risky high route.
• Spawn exits checked against more than one enemy position.
• A comparison test that separates a stronger layout from a stronger player.

1. Write the battle you want

Use one sentence:

Two teams fight over a compact yard where the center is fast but exposed, the lower side route is safer but slower, and the upper route rewards movement without controlling every exit.

That sentence is a filter. A new tower that watches both spawn pockets does not fit it. Neither does a tunnel so safe that it replaces the rest of the map.

Keep the map small enough to understand. BigBox's launch interview explicitly advises builders not to fill the entire buildable space: smaller maps can play better.^[2] That is not a ban on large maps. It is a reason to earn every extra area with an actual gameplay purpose.

Use a route ledger before an object list:

If two routes offer the same experience, make one distinct or remove it.

2. Diagnose the old arena before rebuilding

Switchyard v1 has a central obstacle, cover blocks, and two ways around. That is enough to play. It does not yet prove that either route is interesting.

Before: a loop without a clear tradeoff

     WEST                                      EAST
 +--------------------------------------------------+
 |       C                               C          |
 | A   [screen]          [X]          [screen]    B   |
 |       C                               C          |
 +--------------------------------------------------+
       north and south are similar-length loops

Text alternative: two end spawns face screens, with a central obstacle and similar cover on both sides. The north and south loops have not been given different tactical roles.

Walk it and mark three things:

• Where the first enemy becomes visible. If this is the spawn exit, the protected starting pocket is not doing enough.
• Where players stop. A stop can mean useful cover, confusion, or an overwhelmingly strong angle. Ask which.
• Where players never go. An unused route may be too long, too exposed, hard to notice, or simply unnecessary.

These are questions, not measured findings. Do not report that v1 is “unbalanced” until a test actually shows the failure.

3. Rebuild with a fast route, a safe route, and a high route

After: Switchyard v2

                         NORTH / HIGH
 +--------------------------------------------------+
 |        U---[perch]       GAP       [perch]---U     |
 |        |       \         v         /       |      |
 | A  [S] |   C    +---[center]---+   C       | [S] B |
 |   \    |        |             |           |    / |
 |    +---+--[C]---+--[dogleg]----+---[C]-----+---+  |
 +--------------------------------------------------+
                         SOUTH / LOW

U = climb approach; test it with the match's movement rules
S = spawn screen, offset from the opposing exit
C = cover; the south dogleg blocks an end-to-end ground view
v = intended glide landing near center, not inside a spawn
GAP = no continuous high bridge spanning the whole arena

Text alternative: the revised arena keeps opposite spawns but offsets their exits. A dogleg creates a more protected southern route. Two separated northern perches provide elevation, each reached by a climb approach. Intended glide landings are near the contested center, not behind the opposing spawn.

The exact dimensions are yours to test. Do not treat this schematic as proof that a glide reaches the indicated point.

Make four changes, saving a checkpoint between them:

1. Offset the spawn exits. Remove the straight view from one team's easiest exit to the other's.
2. Bend the southern route. Use solid geometry to break the longest sightline. Keep the bend wide enough to move and fight around.
3. Build two separated perches. Give each a useful angle, but not ownership of the entire ground floor.
4. Leave the center legible. It remains the short route. Do not fill it with so much cover that nobody can tell where the fight is.

Use plain shapes until these changes work. Changing a cube is cheaper than rebuilding a detailed station facade.

4. Test cover as a relationship, not a prop

A crate is not automatically useful cover. It becomes cover relative to an opponent, a route, and the player's position.

Stand behind each planned cover block and check:

• Does it protect against the angle that matters, or only the angle used in the overhead drawing?
• Can I leave it without exposing myself to two unrelated firing positions at once?
• Can an opponent dislodge me, flank me, or contest my advantage?
• Does it accidentally let me climb into a dominant position?

A low barrier may interrupt ground-level fire while doing little against a perch. A tall barrier may protect a crossing while creating a blind ambush corner. Keep the benefit; test the cost.

Trace sightlines from player positions, including reachable high points. For each troublesome position, draw the longest uninterrupted view. Break the one that makes another route pointless, not every view in the level.

Do not make universal material promises. A textured shape that looks like a wall is not proof of the collision or protection you intend. Use actual play to confirm that your chosen objects behave correctly.

5. Design upward—and back down

In a movement-heavy map, a floor plan is only half the level. The other half is the collection of places players can climb to, see from, and land on.

Sandbox rules can change the intended movement experience; the firsthand launch review describes maps changing climbing and flying behavior.^[4] Record the chosen rules before testing. Do not compare a climbing-enabled version against a climbing-disabled version and call the difference a geometry improvement.

Section: a high route with a cost

                 [PERCH]
                    | \  sightline toward center
        climb face  |  \ . . . . [CENTER]
          /---------+    \ glide: test actual landing
 [cover] /                 [landing cover]
 -------- ground route ------------------------------

Text alternative: a perch sits above the ground route, reached by a climb face. Its intended view and glide lead toward the central fight, with cover near the landing. The climb, sightline, and landing are separate things to test.

Check each high route in three stages:

1. Approach: can a player reach the climb without being helpless the entire way?
2. Occupation: can the perch be challenged from somewhere other than its single entrance?
3. Exit: where can the player drop or glide, and what can see that landing?

Avoid the “best roof” problem: one easy-to-reach position that sees every important route and has no reasonable counter-route. Reduce its view, move its approach, or open another way to challenge it. Making the roof higher is not necessarily a nerf if height improves its firing angles.

OlafGolaf's build illustrates why normal-height checks matter: at 7:40–7:49, he leaves builder flight to check whether an opening can actually be passed.^[5] Repeat that habit for every intended entrance and vertical transition.

Study a captured vertical map

Open 5 LEVELS by zyro in the archive and trace routes between its spawn locations. The capture places spawns in five height bands at roughly 24, 50, 80, 114, and 144 map units. Its rules are round-based Team Deathmatch with climbing and flying enabled. That is evidence of a strongly vertical setup, not proof that every floor or route is fair. Use it to check whether each height offers a way up, a way down, a reason to visit, and a counter-angle.

6. Measure scale in journeys

A map can look compact from above and still feel empty on foot. Instead of guessing the perfect size in meters, measure the trips players actually make.

For each team, time the same journeys under the same rules:

• Spawn to first usable cover.
• Spawn to the center contest.
• Spawn to the nearest high-route entrance.
• One complete flank, from leaving the main fight to rejoining it.

Use a stopwatch or recording and write down your observations. The purpose is comparison, not a universal target. If one team reaches a powerful position much earlier, investigate the route before adding compensating weapon advantages.

Separate distance from delay. A short climb can take longer than a longer flat path. A corner may create a pause because players cannot read the exit. Make the next useful decision visible enough that players move intentionally.

7. Recheck spawns after adding height

A wall that protected a spawn in v1 may be visible over from a new perch. Repeat the spawn inspection after any large vertical change.

Use one player in the spawn pocket and another in each likely enemy holding position. Then swap. Test repeated deaths, not just the opening deployment. BigBox's May 2024 change list describes weighted selection among valid respawn points; it does not promise immunity from camping or explain every weight.^[9]

For each candidate point, record:

If an entire side fails, fix the pocket and its exits before scattering more points around the same exposed area. Do not assume “more spawns” is a cure for geometry that lets an enemy watch all of them.

8. Match weapons and rules to the lanes

A long open lane and a close corner produce different fights. Test your arena with the equipment it is meant to support, not only your favorite weapon.

Sandbox provides gameplay weapon objects; the Edit workflow can change rarity.^[3][18] Keep equipment equivalent across sides while comparing layouts. Later, if you intentionally introduce asymmetry, test whether the resulting advantage is fun and contestable rather than merely surprising.

Use a simple two-pass test:

• Layout pass: keep rules and equipment fixed while changing geometry.
• Loadout pass: keep the geometry fixed while changing equipment opportunities.

Do not tune both at once. If players start crossing the yard after you shorten the lane and remove a long-range weapon simultaneously, you will not know which change mattered.

For objective modes, build around the actual objective, not a deathmatch floor plan with a marker pasted into its hardest corner. BigBox added King of the Hill to the Game Type menu and Control Point objects to the Interactive category in March 2024.^[8] A control point creates a different reason to move; test approach choices, recapture, and the route after a death. Keep that as a separate variant of Switchyard rather than quietly changing the exercise midway through.

9. Run a comparison people can remember

Use the same players, player count, rules, and equipment for both versions when practical. Ask players to try every route, then let them play naturally. Swap sides. Short focused rounds are a recommended test format, not a claim about a required game setting.

Keep a record like this:

Version / date:
Rules and equipment:
Players per side:
Side swap completed:
Where did the first fight happen?
Which route was ignored, and why?
Which position felt too safe?
Where did a player die without a useful decision?
One change to test next:

Ask “Where were you when that happened?” before accepting “too open” or “too cramped.” A criticism attached to a position can become an edit. A general verdict cannot.

Do not fabricate numbers for a guide or release note. Empty observation fields are better than invented spawn-death rates, travel times, or claims that v2 is proven balanced.

Troubleshooting

Layout checklist

• □ Each route offers a different benefit and cost.
• □ The longest important sightline has been checked from reachable height.
• □ High positions have tested approaches, counters, and exits.
• □ Every spawn candidate has been rechecked after vertical changes.
• □ Comparable journeys have been timed from both sides.
• □ Before/after tests kept rules and equipment consistent.
• □ Players swapped sides and gave location-specific feedback.
• □ The next revision changes one clear hypothesis, not everything at once.

Next: make the world maintainable

Once the battles work, the job changes. You need repeatable construction, readable art, reliable rule behavior, and room to fix things without rebuilding the entire map.

Continue to Advanced Worlds & Optimization. We will turn a tested arena section into a reusable module, add a small documented event exercise, and build a release checklist that checks the actual saved map—not just a good-looking screenshot.

You can also study layouts in the public map archive. Use them to ask better route questions, then verify your own answers in the game.