What the Tactical Map Does
Devlog #2 calls the map a living system built around bearings, distances, impact points and intel. Targets, impacts and recon markers share the same map space, allowing the displayed relationships to reflect the situation rather than a single permanently scripted arrangement.
The Devlog says those relationships remain coherent even when units move, arrive or disappear and when new intel reacts to events. The map's role in that account is to make the current spatial relationships readable through elements that share the same map space.
Bearing Line
A bearing line expresses direction around the map. The Devlog names bearing lines and uses 083° as an example of how such information may be formatted. That number demonstrates degree notation only; it is not a standing direction for a target, a Campaign objective or a value to carry into another run.
Read a bearing together with the points or marker context that gives the line meaning. A direction detached from its origin, destination or current intel can no longer describe the intended relationship. Also keep bearing separate from elevation: both can be written in degrees, but one is horizontal map direction and the other is vertical gun angle.
Distance Readout
The Devlog names distance readouts and illustrates the format with 1.25 km. A distance describes separation between relevant points in the shared map space. It is not a bearing, grid address or elevation, even when all of those values contribute information to the same assignment.
Preserve both the numeric value and its kilometer unit when reading the current display. More importantly, preserve what the measurement connects. The example 1.25 km is useful for recognizing a decimal distance and unit label, but it says nothing about the distance in a live mission.
Grid Coordinate
Grid coordinates provide a location reference in the map's grid system. Devlog #2 gives B9 4:2 as an example of the displayed format. Treat the letters, numbers and punctuation as parts of one reference rather than extracting a single digit and assuming it has meaning by itself.
A grid coordinate answers a different question from a bearing or distance. The coordinate identifies a map location through the grid convention, while bearing and distance describe directional or spatial relationships. The sample B9 4:2 is not tied here to any target, mission or correct response.
Targets and Impact Points
The developer names targets and impact points as elements living on the same map plane. A target marks the object or location currently represented by the scenario. An impact point records where a shell event is represented on the map, providing result information that can be read after firing.
Do not collapse those two markers into one. An impact point describes an event location, while a target represents the object or place being considered. Their relationship can help the Operator review what the map reports, but this guide does not interpret a particular impact as mission success or tell you how to correct a later shot.
Recon Markers and Updating Intel
Recon markers are another element named in Devlog #2. The developer explains that unit locations become visually revealed when reconnaissance photographs overlap their actual map positions. This makes recon information part of how the current situation becomes visible rather than a permanent promise that every location is always shown.
The same Devlog describes intel arriving in a paced queue and reacting to mission events. New information can therefore change what the map communicates. Read the latest visible marker and its context as current intel; do not assume that an earlier marker, screenshot or remembered layout remains authoritative after the situation updates.
What to Verify
First verify the element type: bearing line, distance readout, grid coordinate, target, impact point or recon marker. Then verify the attached unit or format and the points, marker or intel context that gives the value meaning. Finally, verify that the information belongs to the active map state rather than an example or earlier update.
The three Devlog examples—083°, 1.25 km and B9 4:2—are safe aids for recognizing formats, but none is a universal task value. The map was described as responsive and capable of varied layouts. Current information must therefore come from the current display.
When a map measurement moves into fire control, carry its label and context with it. If two values disagree or a marker's identity is unclear, return to the live order and map. This page does not supply a route, hidden location, mission solution or correction procedure.
- Element type and label
- Unit or coordinate format
- Referenced points or marker identity
- Current intel state
- Whether a number is live data or a Devlog example
