The strongest current reference for the Cold War [APC] 0.7-era map set names Khokhlovka, Siniysk, Valley View, Vavidas, and Wukong Delta. The same reference system places Fulda Gap in an older 0.7 group and KCWD Regional in an archive group. Those status labels matter: a documented map name is not automatically proof that it is in today’s public-server rotation.
Always use the live voting screen, loading screen, and objective panel to confirm the map and mode you are actually playing.
Current reference map index
Current 0.7 reference
Khokhlovka
Confirm the active objectives, vehicle access, weather, and routes in the current server before applying a remembered plan.
Current 0.7 reference
Siniysk
Use the live minimap to connect spawn, objective, cover, and reinforcement paths rather than treating the name as a fixed layout guide.
Current 0.7 reference
Valley View
Evaluate elevation and exposed crossings from the round itself. Weather and mode can change which lane matters.
Current 0.7 reference
Vavidas
Read the valid sector and friendly concentration first. Do not follow a route learned under a different objective sequence automatically.
Current 0.7 reference
Wukong Delta
Plan movement around the current objective, terrain, and vehicle threat. The map label alone does not establish today's best route.
These entries are current-reference identities, not promises about rotation frequency or per-mode layout.
Older and archived records
Older 0.7 record
Fulda Gap
Keep it separate from the current reference set unless a live server or creator announcement confirms its return.
Archive record
KCWD Regional
Treat archived documentation as historical context, not evidence of present availability.
If either name appears in a current official announcement or live vote, record the date and context. Until then, labeling them as current would collapse an important version boundary.
Read a map in the first minute
At spawn, identify the map name, game mode, active or valid objective, friendly concentration, vehicle availability, and obvious terrain barriers. Then choose a route that can contribute within the next minute. A route that is excellent for Conquest may be irrelevant when Advance & Secure activates a different sector.
Use the minimap to see where teammates stop moving or cluster. That can reveal a contested lane, but it can also reveal overcrowding. If one approach is saturated, choose a parallel route close enough to support it rather than a distant flank that removes you from the fight.
Notice weather and light. Current event coverage says the experience includes weather and day/night variation, but the exact combinations and gameplay effects need live observation. Visibility should change your pace, spacing, and sightline choices.
Build a route from four anchors
Start with your spawn or current safe position. Add the active objective, one protected intermediate position, and one fallback. The path between them should avoid the longest observed exposure and leave room to change direction.
For infantry, choose cover that breaks several angles rather than one thin object in an open field. For vehicles, account for turning space, narrow passages, likely anti-vehicle lanes, and a protected dismount. For marksmen and support gunners, ensure the firing position sees a route tied to the objective.
When the objective moves, rebuild those anchors. Do not defend an empty area because it was important five minutes earlier.
Learn landmarks without overclaiming a layout
Give landmarks short, distinctive names that teammates can recognize: color plus building, road direction, bridge, ridge, field edge, or objective label. Use the game’s labels when visible. A precise call is more useful than a memorized fan nickname that new teammates do not know.
This guide avoids publishing unverified point names, dimensions, or exact vehicle spawns for each map. Those details can vary by mode or update. Create your own dated notes from the current build and remove a claim when the live map disproves it.
Map knowledge is not only remembering positions. It is understanding how spawn, objective, cover, and time connect under the mode being played.
Account for vehicles and mounted fire
Before crossing a road or open field, scan for light vehicles, APCs, fighting vehicles, tanks, and mounted weapons. Listen and watch where friendly players take cover. If armor controls a lane, report it and wait for smoke, anti-vehicle support, or an alternate covered path.
Drivers should avoid forcing a remembered route when the objective, weather, or enemy control has changed. Stop passengers before the obvious kill zone. Mounted gunners should cover the dismount or reinforcement lane rather than drawing fire onto the infantry cluster.
The Vehicle List identifies the ten currently documented platforms, and the Minimap guide provides a repeatable map-reading loop.
Verify rotation claims
To confirm a map is current, prefer a live official server, recent creator announcement, or an updated structured directory with explicit version status. A video upload date alone does not prove the footage used the current build. A wiki page without a status boundary can mix retired and active material.
Record the map name exactly, current mode, date, and whether it appeared in voting or only in an archive. That small discipline prevents old guides from silently becoming current claims.
Evidence status
Khokhlovka, Siniysk, Valley View, Vavidas, and Wukong Delta are labeled in current 0.7 reference records. Fulda Gap is separated as older 0.7 material and KCWD Regional as archive material. Rotation frequency, layouts, objectives, vehicle spawns, weather, and availability remain live details requiring current verification.