Skip to content

Enshrouded 1.0: What Server Owners Know So Far

Enshrouded leaves Early Access on 15 October 2026. What Keen Games have announced about 1.0, what they have not, and what to do to your server before it.

August 19, 2026

Enshrouded leaves Early Access on 15 October 2026. Keen Games announced the date on Steam on 25 June 2026, in a post titled Enshrouded - 1.0 Release Date Reveal, and the wording is unambiguous: "Enshrouded releases out of Early Access on Steam on October 15th!"

That is very nearly the whole of what has been announced about 1.0's effect on a dedicated server.

This page is deliberately structured around that gap. Everything in the first half is something Keen have actually said, quoted. Everything in the second half is something they have not said — and the point of writing it down is that the questions server owners are asking are mostly in the second half, and the answers currently circulating are not coming from Keen.

This page was written before the release

It describes what Keen Games have announced, not what has been observed on a live 1.0 server. Nothing here is a description of how 1.0 behaves, because 1.0 does not exist yet. Where a question has no announced answer, this page says so instead of guessing.

What Keen Have Announced

The date. 15 October 2026, out of Early Access, on Steam. Announced 25 June 2026.

That more detail was coming. The same post: "We will bring you more news about improvements, optimization, QoL changes, as well as all the new stuff, later this summer!" Four days later, in the Hotfix #42 changelog of 29 June 2026, Keen were more specific: "More news in August."

That the team is working on optimisation and performance. In that Hotfix #42 post Keen pointed at the discussion thread under the reveal and summarised it: "you'll find mention of a lot of the stuff we're working on: optimization, performance, QoL changes, the dragon boss fight... if you think it could be better there's a good chance that we're working on it." That is a description of what developers are discussing, not a list of shipped features — but performance work is the item on it that matters most to a server owner.

That consoles come after completion, with no date. Keen's own FAQ states: "We will eventually bring the game to other platforms (namely, PlayStation 5 and Xbox X|S) and storefronts, after completion." No console release date has been announced, and 1.0 is described as a Steam release. If you are planning around console players joining your server, there is nothing announced to plan against.

That there will be no public test before it. Keen's FAQ: "At this stage, there is no other public testing planned of any kind." So there is no branch on which a server owner can stage 1.0, warm a world, or test a configuration in advance. Whatever happens on the day happens on the day.

That mod support is not promised. Also from the FAQ: "at this stage, we cannot make promises that the game will be moddable, but it is something we would love to implement in the future." Enshrouded has no plugin system for a dedicated server today and none has been announced for 1.0.

The state of Keen's news feed as this was written

Keen said in the 29 June 2026 changelog that more news would arrive in August. As of 19 August 2026 that has not happened: the newest post on Enshrouded's Steam news feed is still the 29 June changelog — 51 days of silence — and the latest announced build is v0.9.1.2, Hotfix #42, revision 1076226. With under two months to launch and under two weeks of August left, the promised August news is overdue. If you are reading this later, check the feed — the detailed 1.0 information this page is missing is most likely to appear there first.

What Keen Have Not Announced

These are the questions a server owner actually has. None of them has a published answer as this page is written. Anyone giving you a confident answer to one of them is not quoting Keen.

  • Whether an existing world carries into 1.0. Not announced.
  • Whether new 1.0 content appears in an already-explored world, or only in unexplored terrain. Not announced.
  • Whether a fresh world is recommended. Not announced.
  • Whether enshrouded_server.json changes shape — new keys, renamed keys, new difficulty values, changes to the role permission flags. Not announced.
  • Whether the server's hardware requirements change. Not announced. The published figures — about 4.4 GB of RAM idle, ~13 GB of installed files — are measured against the current build.
  • Whether characters are affected. Not announced. Precedent exists in both directions; see below.
  • Whether the sixteen-player ceiling moves. Not announced.
  • Whether the update requires a server restart to apply. Effectively certain, but Keen state this per-patch in the changelog rather than in advance.

What Precedent Suggests — And Why It Is Not a Promise

Keen have shipped two large updates recently, and both are useful as a shape of what a major Enshrouded update does to a live server. Neither tells you what 1.0 will do.

Update 8, Forging the Path (April 2026) reworked the skill tree, and Keen led the release note with a warning in capitals: "With Update 8, character skill trees will be reset, and skill points will be refunded when loading into a world for the first time with an existing character. This was a necessary step since the skill tree has been reworked significantly."

Two things are worth extracting from that sentence. The first is that a major update can forcibly reset part of a character, and Keen flag it loudly when it does. The second is quieter but more reassuring: the sentence is written in terms of "loading into a world for the first time with an existing character", which is the language of an update that expects existing worlds and existing characters to continue. That is a precedent, not a commitment about 1.0.

Update 7, Wake of the Water (November 2025) added water across the world and, on the server side, added an entirely new default role — Visitor — to the role system, along with new role permissions covering water gameplay. Keen's note at the time: "Server hosts can now set up a new default guest role called 'Visitor' … As always, dedicated server admins can freely add or remove the new setting in custom visitor roles."

That is the precedent that matters most for configuration. A large Enshrouded update has previously added a new key to the role system in enshrouded_server.json. If 1.0 does the same, a config carried across from before the update will be missing it — which is exactly the situation Keen warn about elsewhere: "previous versions of the server.json can sometimes be incorrectly updated. In this case you can delete the file to let it be created freshly on the next startup."

What a Server Owner Should Actually Do Before 15 October

None of this depends on the announcements that have not arrived, which is why it is worth doing now rather than on the day.

1. Take a backup you have tested

Not a snapshot you assume works — one you have restored. Stop the server, take a panel backup, download a copy of savegame/ off the server, and know that you can put it back. Enshrouded server backups and restoring a world covers the four files a world consists of and the restore order.

Keep the pre-1.0 backup for longer than you would keep a routine one. If 1.0 does something to a world that you want undone, the window in which you notice may be days rather than minutes, and the game's own ten rolling copies cover roughly an hour and a half of play, not a week.

2. Write down your configuration outside the server

Specifically: your difficulty preset and any custom gameSettings values, your tags, your chat toggles, and the permission flags on each of your role groups. Not the passwords — those live on your control panel's Startup tab and are written into the file at every start — but the parts of the config that are genuinely yours.

The reason is Keen's own recommended fix for a config that upgrades badly: delete it and let a fresh one generate. That advice is only cheap if you can reapply your settings from a note rather than from memory. Enshrouded server settings and config file is the reference for what those values are.

3. Know which build you are on

Not the version string — the revision. Keen publish a revision number at the top of every changelog, and the version string is not unique: both Hotfix #41 and Hotfix #42 shipped as v0.9.1.2, distinguished only by revisions 1024233 and 1076226. Knowing your starting point makes "did the server actually update?" a question with an answer.

4. Decide your update window before you need it

The update will land while people are playing. Decide in advance whether you restart immediately or wait a day, and tell your group which it is. Both are defensible: restarting immediately gets you onto the build your players' clients will auto-update to; waiting a day lets someone else find the day-one problems.

What is not defensible is finding out at 8pm that half your group has updated, cannot join, and you have no backup. How to update your Enshrouded server after a patch covers the mechanics — Auto Update, Validate, and why your server log is deleted at every start.

5. Check your disk headroom

A release-scale update is a large download that has to stage before it replaces the installed files. Keen's stated recommendation of 30 GB free against ~13 GB of installed files exists precisely for this. Disk exhaustion mid-update turns a routine restart into a reinstall. Enshrouded server requirements has the full figures.

Do not resize your server on speculation

Keen have not published revised server requirements for 1.0. Every number in circulation about what a 1.0 Enshrouded server needs is extrapolated from the current build, including ours. Keeping sensible headroom is good practice; provisioning against a figure nobody has published is not.

On the Day

A short list, in order:

  1. Read the changelog before you restart. Keen state in every changelog whether dedicated servers need an update, and for a release that will certainly be yes — but the changelog is also where any config or world caveat will be written, and it is the one document that is definitely accurate.
  2. Stop the server cleanly rather than killing it, so the world is written on the way out.
  3. Take a final pre-update backup, separate from the one you took in advance.
  4. Start the server and watch the console for the Steam update, then for [Session] 'HostOnline' (up)!.
  5. Join before you announce it. A server that boots is not a server that accepts connections.
  6. Take a post-update backup, so your restore point is the new world rather than the old one.
  7. If something is wrong, stop and read the log before restarting. The log is deleted at every start.

FAQ

When does Enshrouded 1.0 release?

15 October 2026. Keen Games announced the date on Steam on 25 June 2026: "Enshrouded releases out of Early Access on Steam on October 15th!"

Will my existing Enshrouded world work after 1.0?

Keen have not announced this. Precedent from previous major updates is that existing worlds and characters continue — Update 8's release note describes what happens "when loading into a world for the first time with an existing character" — but that is precedent, not a statement about 1.0. Back up before the update.

Do I need a new world for Enshrouded 1.0?

Not announced. Nobody currently knows, including anyone telling you they do.

Will Enshrouded 1.0 be on PlayStation or Xbox?

Keen's FAQ states they will "eventually bring the game to other platforms (namely, PlayStation 5 and Xbox X|S) and storefronts, after completion". No console release date has been announced, and the 1.0 release is described as a Steam release.

Can I test 1.0 on my server before it launches?

No. Keen's FAQ states there is no other public testing planned of any kind, so there is no branch to stage it on.

Will Enshrouded have mod support at 1.0?

Not announced. Keen's FAQ says they cannot promise the game will be moddable, and there is no plugin system for a dedicated server today.

Will my server configuration still work after 1.0?

Not announced. A previous major update — Wake of the Water — added a new default role to the config, so it is reasonable to expect the file to gain keys. Keen's stated fix for a config that upgrades badly is to delete it and let the server generate a fresh one, which is only painless if you have written your settings down first.

Should I update my server the moment 1.0 goes live?

Either is defensible, as long as you decide in advance. Updating immediately keeps you aligned with clients that update automatically; waiting a day lets other people find the day-one problems. Back up either way.

Made with 💜 by GameServerKings