Patch 1.6 changes the resource cost of basic construction and several interface or input paths. This guide focuses on those practical corrections and the later feedback that narrows them. Use it to check a current setup without treating a planned fix as an already installed feature.
- Separate a basic structure from its upgrade
- Check Engineer and team limits together
- Inspect the revised defensive layout
- Check persistent filters before assuming no servers exist
- Match mounted sensitivity to the named exception
- Use audio changes as cues, not exact detection formulas
- Keep current stability work in its stated scope
- Do not search for future menus as current features
1. Separate a basic structure from its upgrade
The construction overhaul makes all Level 1 buildables free to place and construct, while higher levels still need supplies. Compare the level you are trying to establish before diagnosing a missing resource. A plan based on an old first-level supply cost can be obsolete, but the change does not make every construction action free. Keep the team supply reserve and the intended upgrade distinct from the initial placement. The guide does not invent a faster building timer.
Sources: Released current patch
2. Check Engineer and team limits together
The patch sets barbed wire at two per Engineer with no team cap in that list, barricades at two per Engineer and fifty per team, and bunkers at one per Engineer and ten per team. A personal allowance and a shared team cap constrain different situations. Reaching the shared cap cannot be diagnosed only by counting your own placements. Free basic construction does not remove these limits or establish a separate unlimited bunker category.
Sources: Released current patch
3. Inspect the revised defensive layout
Patch 1.6 redesigns the structures to provide better cover and make passage or climbing less straightforward. Faction barbed-wire layouts differ, and upgraded barricades add a deterrent along the top. Inspect the current object and level instead of importing a route demonstrated on an older model. This describes the game-level change without graphic detail. A revised shape does not establish one universally safe arrangement for every sector or unit.
Sources: Released current patch
4. Check persistent filters before assuming no servers exist
The revised browser prioritizes fuller servers and remembers filters after restarting. Inspect the filter choices and favourites when a new session shows fewer results than expected. A saved filter can explain a different view without proving a regional outage. The developer describes official-server reductions alongside support for community servers, so the browser change should not be presented as a guarantee of a full official lobby in every time zone.
Sources: Released current patch
5. Match mounted sensitivity to the named exception
The patch changes several mounted-gun paths to use ADS sensitivity instead of the look value. The subsequent feedback names the Huey M60 as a remaining exception with an internal correction planned for 1.7. Check the actual mount and version before assuming a setting change controls it. Do not advertise the internal fix as released. One named exception also does not imply that every other mounted control has the same unresolved behavior.
Sources: Released current patch / Developer feedback and remaining work
6. Use audio changes as cues, not exact detection formulas
The update changes occlusion for outpost, garrison and tunnel sounds, reduces tunnel audibility range and separates ambient layers from player actions. It also adds vehicle-hit and near-end-of-match audio cues. These are documented presentation changes, not a verified exact detection radius or damage formula. Compare the cue in the current context and retain the objective information from the interface and unit communication rather than assigning invented distances to a sound.
Sources: Released current patch
7. Keep current stability work in its stated scope
Community Feedback 7 reports that AMD crashes have decreased after 1.6 while the investigation continues. The released update also contains stability and map fixes. A reduction is useful context, but it does not certify every driver, device or server session. If a problem remains, record the configuration, map, action and version. Avoid replacing a reproducible technical report with a blanket claim that the update removed all performance or reliability issues.
Sources: Released current patch / Developer feedback and remaining work
8. Do not search for future menus as current features
The feedback discusses saveable role loadouts, expanded statistics and interface work as future development, alongside later boat-engine behavior changes. Keep those announcements separate from the installed options. A missing planned menu is not evidence that your save is damaged. Use the current role roster, settings and server-browser behavior while comparing the specific released correction. Recheck a later official release before turning a development target into a present instruction.
Sources: Developer feedback and remaining work / Released current patch
| Current check | Rule or boundary |
|---|---|
| Defensive resource plan | Free basic level; supplied upgrades; two cap layers |
| Unusual aiming behavior | Named mount and later Huey exception |
| Missing feature or crash | Released scope versus remaining development |
Compare the exact structure level, mount or interface path. A general update headline can have a later named exception.
Related guides
Use the free first-level construction rule with current placement caps, inspect persistent browser filters and match sensitivity to the mount. Treat audio as contextual cues and future interface or stability work within its stated limits.
Sources checked October 14, 2026. Published facts are linked beside their explanations. Planning and practice suggestions are editorial advice rather than verified optimal builds.
Comment
No comments yet. Be the first to post one.