Commanding the Front
Orders in FLANKED define intent, not every action. Squads, leaders and the tactical map turn individual firefights into a coordinated battle.
FLANKED is built around a simple idea: a battle should be more than a collection of individual gunfights.
Squads need objectives. Leaders need information. Orders need to mean something on the ground.
The command system is how those layers connect.
It starts with individual soldiers, grows into squads and eventually extends to the coordination of an entire team.
The goal is not to turn FLANKED into an RTS.
It is to make leadership matter without separating commanders from the same battlefield everyone else is fighting on.
ORDERS, NOT PUPPETS
Giving an order in FLANKED is not the same as directly controlling another unit.
A Squad Leader can tell a squad to move, attack or defend, but the soldiers still have to execute that order inside the same simulation as everyone else.
They have to move through the terrain.
They can encounter enemies.
They can be suppressed.
They can lose sight of a target.
They can be forced to retreat or find another position.
This distinction matters.
We do not want command to feel like dragging pieces around a board.
An order defines an intention.
What happens between the order being given and the objective being reached is where the game happens.
A CHAIN OF COMMAND
FLANKED already uses a hierarchical command structure internally:
Command.
Squad.
Unit.
Individual soldiers belong to squads, and squads provide the level at which larger tactical decisions can be made.
This structure is used by both players and AI.
Bots are not a separate simplified army operating under completely different rules. They are organised into squads and receive tactical objectives through the same command structure the game uses elsewhere.
Human players can also join persistent squads, and leadership can move between players when necessary.
This gives us a common foundation for both human and AI-controlled forces.
More importantly, it means that adding more advanced command features later does not require inventing a second game on top of the first one.
THE SQUAD IS THE TACTICAL UNIT
A squad should be more than a coloured group of player names.
It is the smallest level at which coordinated tactical behaviour begins to make sense.
A squad can be asked to hold a position.
It can approach an objective from a particular direction.
It can move while another squad attacks.
It can defend ground that another squad needs in order to advance.
Those decisions become much more interesting when the map itself supports them.
A command such as "attack from the north" only matters if approaching from the north creates a genuinely different tactical situation.
That is why the command system, squad system and map design cannot really be developed independently.
Each one gives meaning to the others.
THE MAP IS THE COMMAND INTERFACE
The tactical map is where the larger battle becomes understandable.
At the individual level, a player is concerned with immediate problems:
Where is the enemy?
Where is my cover?
Where is my squad?
At the command level, the questions change:
Which objective needs support?
Which squad is already committed?
Where is the enemy likely to be concentrating?
Which route should another squad use?
Where is the gap in our defence?
The tactical map needs to communicate those answers without becoming an unreadable wall of symbols.
FLANKED already uses it to display the state of the battlefield and to issue tactical orders.
As the command layer grows, the same interface will also have to support more information: squad positions, objectives, reported enemy contacts, forward positions, logistics and other team-level elements.
That is why we are treating the tactical map as a core gameplay interface rather than a secondary menu.
INFORMATION SHOULD HAVE A SOURCE
There is another important constraint.
Command should not mean omniscience.
A player looking at the tactical map should not automatically know the exact location of every enemy soldier because somewhere else on the battlefield another player saw them for half a second.
Enemy information needs to have context.
A contact may be reported.
It may be approximate.
It may become outdated.
A position that was occupied thirty seconds ago may already be empty.
This becomes especially important at higher levels of command.
The more of the battlefield a player can coordinate, the more important uncertainty becomes.
We want the map to help players share information, not magically replace reconnaissance.
LEADERSHIP WITHOUT MICROMANAGEMENT
There is a balance to find.
If leaders have too little influence, squads become little more than informal groups of players moving in roughly the same direction.
If leaders control every movement, stance and target, the game starts becoming an RTS.
FLANKED needs to sit between those extremes.
A leader should make decisions about intent:
Move here.
Defend this area.
Attack this objective.
Watch this route.
Build here.
The individual execution remains with the players and soldiers carrying out those orders.
That keeps leadership focused on coordination rather than micromanagement.
FROM SQUAD LEADER TO COMMANDER
The current systems give us the first part of that hierarchy.
Squads exist.
Orders exist.
AI can operate through the command structure.
The tactical map exists.
The next step is extending those systems upward.
The long-term commander role is intended to coordinate squads at the team level through the tactical map.
That means setting priorities, assigning objectives and eventually coordinating systems such as forward positions and logistics.
This part of FLANKED is still in development.
We are deliberately building it on top of the existing squad and order systems rather than creating a separate command game that only loosely interacts with the battlefield.
COMMAND SHOULD CREATE COOPERATION
The purpose of the command system is not to give one player more power than everyone else.
It is to create reasons for players to work together.
One squad attacking alone may fail.
A second squad approaching from another direction changes the situation.
A defended position becomes much more valuable if another squad depends on it.
A vehicle becomes more useful when its movement is coordinated with infantry.
A forward position matters because several squads may rely on it.
Those relationships are what make a battlefield feel organised rather than random.
FLANKED is still a game about controlling a soldier and fighting on the ground.
But the battle around that soldier should have structure.
And when that structure works, an order on the tactical map should eventually become something you can see happening on the battlefield.
