HLL Vietnam HQ Spawn Missing: Garrisons & Deployment Fixes

October 1 official checkpoint

Hotfix 1.5.2 introduced Iris replication fixes for server degradation that could affect missing HQs, spawns and other objects. October 1 feedback reports encouraging early server-owner results but keeps monitoring active. Check your installed build, distinguish missing existing spawns from rejected placement, and report remaining failures with server, map and platform. There is still no universal client-side workaround.

Identify which spawn problem you actually have

A missing HQ icon, an unavailable existing garrison and a rejected placement are different reports. Before retrying, note what is visible on the deployment screen and whether teammates see the same thing. If an existing spawn is missing to several players after multiple matches, that is useful context for the acknowledged replication investigation. It still does not prove the same cause for every incident.

Placement rules are not the same as a missing spawn

Update 1.5 blocks garrison construction within 15 metres of an enemy and blocks underwater placement for garrisons, outposts and tunnels. A failed placement in those conditions is not automatically a replication fault. Check the placement feedback and the current objective state before describing it as a missing HQ bug. Keep your report specific: “HQ icon disappeared after map change” is more useful than “spawns broken”.

• Current garrison placement and supply guide

Player checklist before leaving a match

These are reversible diagnostics, not a publisher-guaranteed fix. Record the installed version, faction, map, mode and server. Ask one squadmate whether the same spawn is visible. If another legitimate spawn is available, use it to regroup and notify the squad leader. Before disconnecting, capture the deployment screen and exact time so the server admin can compare reports.

• Note whether the failure followed a map or match transition.
• Separate a missing icon from an icon that cannot be selected.
• Keep any displayed error message verbatim in your private report.
• Do not delete tutorial or profile data to repair a server-side spawn issue.

Server-owner guidance and its limit

The developer recommends regular server restarts while investigating degradation across matches. The post does not prescribe a universal restart interval. Administrators should use their provider’s supported controls and communicate the interruption to players. Keep a note of uptime and map rotations before the incident. An ordinary player should contact the server team; local client restarts and server restarts are not interchangeable actions.

Why a fix in QA is not yet a fix you can use

The team has an internal replication cleanup fix under verification, but has not confirmed exactly which symptoms it resolves. Patch 1.6 is a target and some earlier work is being considered for 1.5.2. Follow the actual release notes before marking a report resolved. If the problem recurs after a later patch, compare the same recorded scenario rather than assuming all deployment failures share one root cause.

• Patch 1.6 and QA status
• Keep a local pre-match checklist