top of page

Foxhole 0.4.10 Hotfix Release Notes

We will be rolling out the update to servers in stages in the next 24 hours. Servers that have not been updated yet will appear greyed out in the server browser. During the rollout period, you can still access the 0.4 client by switching to the "Update-0.4" branch on Steam via the "Betas" properties tab.​

IMPORTANT: This update fixes the many critical issues with Amphibious Warfare. We will continue to resolve additional issues in the coming weeks. Thanks for the patience.

New Content

  • New World Structure: Dock

  • Allows Barges to dock and release cargo

  • Exists on multiple beachheads on Farranac Coast

Gameplay Features & Changes

  • All structures other than the following can no longer be built on sand (beaches) on Farranac Coast

  • Barbed Wire

  • Tank Traps

  • Sandbags

  • Barracks

  • Landing APC can no longer move if encumbered passengers are on the back

  • Landing APC can no longer be repaired by passenger on the back

  • Anti-Tank Mines can no longer be deployed on transition areas between water and sand (wet sand)

  • Anti-Tank Mines can longer be deployed from Barges

Game Balance

  • Landing APC speed on land decreased by 15%

  • Landing APC now requires Technology Level 2

  • Barge health increased by 50%

  • Barge Basic Material cost increased from 150 to 170

  • Barge critical damage threshold increased (it takes more damage now to stop it from moving)

Major Bug Fixes

  • Gun Turrets no longer fire through walls to hit build sites

  • Landing APC passengers no longer get killed randomly during transport

  • Players can now consistently target water from an Landing APC or Barge

  • Component node at L1 on Farranac Coast now respawns consistently

Known Issues

  • On rare occasion, players can be pushed off of a moving Landing APC or Barge during poor network conditions if crouch/stand is spammed continuously. The easy way to avoid this is the stand still when these vehicles are moving over water. We will be working to resolve this issue in the next update.


bottom of page