GoreBox 27

Guide

The GoreBox 27 Editor: Build a Map, Play It Immediately

The in-game map editor explained: layout thinking for a physics game, testing with bots, and sharing your arena with a session.

Face to face with NPCs in GoreBox 27

The editor is GoreBox 27's quiet superpower: build a map inside the game and play it the moment it exists. This guide covers building with the simulation in mind, from our own map tests for GoreBox 27 APK.

Design for physics, not screenshots

A good GoreBox map is a machine for incidents: heights things can fall from, materials that contrast (one wall that stops rounds, one that only pretends to), water for the chaos it guarantees, and at least one structure whose collapse is a scheduled event in every match.

Test with bots early

Drop bots in before the map feels finished. They find the dead corners, the unfair sightlines and the spawn that drops someone into a lake, and they find them in minutes. Difficulty settings let you grade how rude the test should be.

Ship it to a session

Host the map with friends, watch where fights actually happen, and move one wall. Maps here are conversations, and the editor's immediacy, build, play, adjust, is why the community's arenas keep getting stranger and better.

Sightlines and second positions

The difference between a frustrating arena and a beloved one is exits. Every strong position needs a second position behind it, because the first thing a good player does to a camper is penetrate the cover or flank it, and a room with no retreat becomes a coffin with a view. Build sightlines in layers: a long lane for the rifles, broken ground for the rushers, one interior where shotguns and arguments both get louder. Then interrogate the result with the Reality Crusher guide in hand: if a structure cannot be grabbed, thrown or torn in an interesting way, it is scenery, not a set piece.

Finishing details that players feel

Set the time of day deliberately, because night matches play slower, quieter and more paranoid than noon ones, and your layout should know which it is hosting. Give water a job: a lake as a shortcut for the brave, a moat for the careful, never just decoration at the map's edge. Spread spawns so nobody materialises inside someone else's sightline. Finish by populating the place, because an empty arena is a diagram and a populated one is a neighbourhood: our custom character creator guide builds a cast your map deserves.

Map size discipline

Beginner maps sprawl; good GoreBox 27 maps compress. Every metre of empty ground is a metre where nothing can happen, and in a physics game nothing happening is the only real failure state. Shrink your first arena until incidents collide with each other, then earn extra space one tested room at a time. GoreBox 27 veterans judge a layout by travel time between decisions: if a player can walk ten seconds without choosing anything, the map has a hole wearing a corridor's clothes. Build small, test crowded, and let the map grow by evidence. Your future GoreBox 27 sessions will feel the difference in the first minute.

Quick Answers

Do I need to export or publish maps separately?

No: maps are built and played in the game itself, including in hosted sessions.

What's the most common beginner map mistake?

One open field. Add interiors, heights and material variety and incidents design themselves.

Can bots test my map?

Yes, and they should: bots are the cheapest playtesters in game design.