A Map That Matters
In FLANKED, the battlefield is not a backdrop. Terrain, visibility and routes shape every decision before the first shot is fired.
A map in FLANKED is not just the place where a match happens.
It defines where squads can move, where they can hide, what they can see, which routes are safe, where a defence can hold and where an attack is likely to fail.
Because FLANKED is played from a top-down perspective, map design has an even bigger role than it would in a traditional first-person shooter. The player can see more of the battlefield, so the battlefield itself has to provide meaningful choices.
Our goal is simple: looking at the map should already make you think about how you are going to fight on it.
A MAP STARTS BEFORE THE FIRST SHOT
Before weapons, vehicles or objectives are placed, there is terrain.
Roads, elevation, buildings, walls, open ground, vegetation and narrow passages determine how players will move through a level long before the first shot is fired.
A good position should exist because of the terrain, not because the game tells you that it is a good position.
A hill can provide observation over a road.
A group of buildings can protect infantry moving toward an objective.
A wall can turn an otherwise exposed field into a viable approach.
A narrow road between two pieces of difficult terrain can become a natural chokepoint.
These relationships are what we are looking for when building maps for FLANKED.
The objective is not to create one correct route through the level. We want several possible approaches, each with advantages and risks, so that squads have reasons to make different decisions.
FROM RELIEF TO ROUTE
One of the first questions when working on a map is very basic:
Where will players actually move?
The shortest path between two objectives should not automatically be the best one.
A direct route may be fast but exposed.
A road may allow vehicles to move quickly but make them predictable.
A forest or group of buildings may provide better concealment at the cost of speed.
Higher ground may offer excellent observation while also making a position easier to identify.
Those trade-offs are important because movement in FLANKED is supposed to be a tactical decision.
When objectives, roads and terrain work together, routes emerge naturally from the level instead of being artificially imposed on the player.
That also gives Squad Leaders and Commanders something meaningful to work with.
An order to attack from the north should mean something different from an attack coming through the south.
THE TACTICAL MAP IS PART OF THE LEVEL
FLANKED has another particularity: players do not experience the battlefield only through the game world.
They also experience it through the tactical map.
The tactical map is where information from the battlefield is turned into decisions.
Squads, objectives, orders, friendly positions and reported enemy contacts all need to remain understandable even when the situation becomes complicated.
That means the tactical map cannot simply be a screenshot of the terrain with icons placed on top.
It has to be designed alongside the level itself.
Roads have to remain readable.
Important terrain features have to be recognisable.
Objectives must be easy to locate.
The relationship between the tactical map and what the player sees on the battlefield should remain obvious.
If a player identifies a hill, road or village on the tactical map, they should be able to recognise the same place when moving through the level.
We are currently working on this visual language, including the icon system used for objectives, squads, orders, spawn points, FOBs and enemy reports.
The goal is to make the map dense with useful information without turning it into visual noise.
COVER HAS TO BE REAL
Top-down games have a particular problem with cover.
The player can see over the battlefield from above, but the soldier they control cannot necessarily see everything the player sees.
Walls, buildings and terrain therefore need to affect actual line of sight.
If an enemy is behind a building, knowing that the building exists is not the same thing as being able to see through it.
This distinction is fundamental for FLANKED.
Cover should not just be a statistical modifier or a decorative object.
It should physically influence what soldiers can see and where they can shoot.
That creates much more interesting situations.
A squad can move behind a wall without immediately exposing itself.
A machine gun covering a road may dominate one approach while being almost useless against another.
A Squad Leader using binoculars from elevated terrain can gain information that the rest of the squad does not have.
The top-down camera gives the player awareness, but it should not give them perfect information.
That difference is where a large part of the tactical gameplay comes from.
WHEN THE GROUND CHANGES
The battlefield in FLANKED is not completely static.
Explosions can physically affect the terrain. A grenade can leave a crater behind, changing the shape of the ground instead of simply playing a temporary visual effect.
Individually, these changes may be small. During a match, however, they can gradually alter how a position feels and how players move through it.
A crater can provide limited protection in an exposed area. Repeated explosions can make previously flat ground more difficult to cross. The battlefield starts to carry visible traces of the fighting that happened there.
Weather is another part of that idea.
Rain is planned as more than a cosmetic layer. It should change the atmosphere of the battlefield while remaining consistent with the tactical readability of the game.
Visibility, terrain contrast and the way players perceive distant areas all need to remain understandable even when weather conditions change.
The objective is not to turn FLANKED into a terrain simulation.
These systems exist to make the battlefield feel physical and persistent enough that combat leaves a mark on the level.
The map you finish a battle on should not always look exactly like the map you started on.
THE EDITOR IS WHERE THE PROMISES MEET
A large part of this work happens inside our map editor.
The editor already allows us to assemble levels using terrain, assets and gameplay elements and then test those decisions directly in the game.
That matters because FLANKED combines several systems that all depend on the same environment:
infantry movement,
objectives,
squads,
spawns,
vehicles,
visibility,
and eventually logistics and forward positions.
Each system can work perfectly on its own and still create problems once it interacts with the others.
The map editor is where those interactions become visible.
It gives us a fast way to build an idea, play it, find what does not work and change it.
That loop is going to remain an important part of development.
We are not trying to build maps that simply look like battlefields.
We want to build maps that create decisions.
Where do we move?
What can the enemy see?
Which route can our vehicles use?
Where should we defend?
Where can another squad support us?
Where would a forward position actually be useful?
If the terrain makes players ask those questions before the shooting even starts, then the map is doing its job.