Enshrouded Get Enshrouded

enshrouded bugs

Enshrouded Bugs and Workarounds

Use the notes for your installed build, not an undated bug list. Hotfix 1.0.0.2 was published on 16 October 2026; corrupted characters are skipped during migration while Keen works on a repair.

Two armored characters look out at floating rocks and ruined towers
Two armored characters look out at floating rocks and ruined towers
Keen Games / Steam
Players raise a timber house against a ruined stone cathedral
Players raise a timber house against a ruined stone cathedral
Keen Games / Steam

Current warning and earlier workarounds

Hotfix 1.0.0.2 fixes world-settings configuration and the dense grey rendering fog on Nvidia cards. It also avoids a save-migration crash by skipping corrupted characters; Keen says a fix to repair and migrate those characters is still in progress. Keep backups rather than deleting the source saves.

The earlier 1.0.0.1 notes describe incorrect reverb and levels when master volume is below 100 percent. Their workaround is to leave the game master at 100 percent and adjust system volume. The 1.0.0.2 notes do not confirm this audio issue is resolved; this site has not retested it in-game.

The old Adventure Sharing subscription workaround for the world edit button belongs to 1.0.0.1. Update before using it: 1.0.0.2 explicitly fixes world-settings configuration. Chest-loot, encounter reset, boss projectile, and Quick Stash fixes belong to the original 1.0 changelog, not an undated list of current bugs.

Community reports, not confirmed

Falling through the world and terrain that fails to load show up in player posts. There is no official reproduction and no official fix to copy. Verify files, test without mods, and send the ticket to Zendesk if it repeats. This page will not tell you to edit a save to “clip back up.”

Questions

Is there an official bug list?

No standing page. Use the changelog for the build you are on.

Did 1.0 fix undo when the bag is full?

The 1.0 notes say terrain undo failed when the inventory was full, and that this was fixed. Update before you retest.

Continue

Sources

Advertisement