Confirm placement and zoom out
Make sure the hatch completed, then find the endpoint on the tactical map.
SOURCE-AWARE ISSUE GUIDE
NVA tunnel will not connect on the tactical map
Most "tunnel won't connect" cases are workflow problems: unfinished placement, wrong map zoom, bad endpoint selection, or a full four-connection network — not a missing faction feature. Claims of fixed 100m/400m ranges, cooldowns or permission gates are Pending until shown in the current build or an official note.
Workflow issue · verify current build · Reviewed Sep 9, 2026
QUICK ANSWER
Workflow issue · verify current build
Official materials establish NVA tunnel networks and a launch connection maximum of four (reduced from five on July 30). Hotfix 1.4.2 resolved an issue that allowed players to connect tunnels to pre-placed Garrisons without distance restrictions; official notes do not publish new distance values. Hotfix 1 / Patch 1.2 addressed tunnel-related server crashes; they do not replace the tactical-map connection workflow.
DO THIS FIRSTConfirm the tunnel placement finished before opening the tactical map.PLATFORMNVA players · All platformsEVIDENCEOfficial update
PLATFORMNVA players · All platforms
STATUSWorkflow issue · verify current build
EVIDENCEOfficial and dated sources
SOURCE POSITION
What the sources establish
Official materials establish NVA tunnel networks and a launch connection maximum of four (reduced from five on July 30). Hotfix 1.4.2 resolved an issue that allowed players to connect tunnels to pre-placed Garrisons without distance restrictions; official notes do not publish new distance values. Hotfix 1 / Patch 1.2 addressed tunnel-related server crashes; they do not replace the tactical-map connection workflow.
MATCH THE SYMPTOM
Use this page when
- Tunnel placed but no connection highlight
- Cannot select tunnel or Garrison on the tactical map
- Tutorial will not advance after placing a tunnel
- Map icon missing after build
CHOOSE YOUR CURRENT STATE
Find where the tunnel workflow stopped
Placement, map visibility, endpoint selection and the connection cap fail at different stages.
Clear and reselect the pair
Select one endpoint and the intended anchor; reverse the order once if the current highlight does not appear.
Prune an obsolete route
The documented launch maximum is four connections; remove a stale link before rebuilding.
REVERSIBLE CHECKS FIRST
What to do
- 01
Confirm the tunnel placement finished before opening the tactical map.
- 02
Zoom out and find the network icon; a missing icon usually means placement failed.
- 03
Select one endpoint, then the intended Garrison or tunnel; if nothing highlights, clear selection and reverse the order once.
- 04
In the tutorial, wait for the spoken instruction and use the prebuilt endpoint rather than spamming new hatches.
- 05
Check whether four connections are already in use; remove a stale link before adding another.
- 06
Travel the route once. If the exit is useless, replace the link instead of stacking more hatches.
- 07
If the whole server crashes during destroy/reconnect, confirm Hotfix 1 / Patch 1.2+ and file a new report with build and repro steps.
IMPORTANT LIMITS
Before changing more
- Do not treat every failed highlight as a game-breaking bug before checking zoom, placement and selection order.
- Do not invent a fifth connection after the July 30 reduction to four.
- Separate this workflow issue from the fixed RCON/tunnel server-crash path.
QUICK ANSWERS
NVA tunnel will not connect on the tactical map questions
Why won't the tunnel connect?
Most cases are workflow problems, not missing faction features. Verify placement finished, zoom out to find the network icon, select one endpoint then the other (reverse order if needed), wait for tutorial instructions, and check the connection cap. Hotfix 1.4.2 resolved connecting tunnels to pre-placed Garrisons without distance restrictions; official notes do not publish new distance values. Hotfix 1 / Patch 1.2 fixed tunnel-related server crashes but did not replace the tactical-map connection workflow.
What are the distance, cooldown and permission requirements for tunnels?
Pending. Claims of fixed 100m, 400m or specific cooldown values remain Pending until verified in the current build or an official note. The documentation establishes a tactical-map connection workflow and a four-connection maximum but does not publish fixed distance or permission gates.
What is the connection cap and upper limit?
Four connections is the launch maximum. The official July 30 balance update reduced the maximum from five to four connections. Check whether four connections are already in use and remove a stale link before adding another.
Is this the same as a server crash?
No. This is a workflow issue: placement, map zoom, icon visibility, selection order, tutorial endpoint, or connection-cap limit. Hotfix 1 / Patch 1.2 addressed separate tunnel-related server crashes (RCON broadcasts and destroy/replace/reconnect crashes). Do not treat every failed connection as the fixed server-crash path.
Sources and evidence
Official current-build hotfix · September 8, 2026Hotfix 1.4.2 | Live NowOfficial tunnel connection-limit and balance updateRoad To Launch Update | Crossplay Playtest ReviewOfficial August 16 hotfix notes · superseded for AMD current statusHotfix 1 | Live NowPost-launch player reportCommunity tunnel connection workflowCommunity troubleshootingTunnel tutorial connection discussionOfficial living launch and hotfix threadDev Comms Thread & Launch Updates