Guides, tutorials, and tips for game server hosting. Everything you need to get the most out of your server.
Enshrouded 1.0 lands on Steam and PS5 on 15 October 2026 — without crossplay. What Keen has said (Eurogamer.de interview), when Xbox comes, and what it means for a group deciding where to buy.
1.0 on Steam on 15 October 2026, the price rise of 8 September, the performance pass and the skill reset — and the list of things Keen has not said about dedicated servers, other platforms and a Linux build among them.
The savegame folder, the 10-minute autosave, why characters never move (Keen stores them client-side), the four-step transfer, what goes wrong, and the backup to take before and after.
Where user groups came from, the five flags, Keen’s Admin/Friend/Guest examples, reserved slots, the retired top-level password key, and why a fresh server ships closed with randomised passwords.
Keen’s numbers are 4.4 GB idle, 100 MB per player and no more than 6 GB, which is why 4 GB does not exist. What the figures cover, Keen’s CPU and disk guidance, what none of it tells you, and how to choose 6, 8 or 12 GB.
SteamCMD app 2278520, every key in enshrouded_server.json, UDP 15636 and 15637 on IPv4, how players join by name and role password, and the update routine that keeps the server on the players’ build — from Keen’s own articles.
1.0 on 15 September 2026: platforms, the crossplay option Jagex added to dedicated servers, invite codes, and what the 1.0.0.4 and 1.0.0.5 patch notes mean for anyone running a server.
One .sav file and a rule about its name: the Windows save path, the server’s Savegames folder, why you must not rename the file, and why world rules travel in the save rather than the INI.
Where the Player ID is, what putting it in Owner ID unlocks, what an admin can and cannot do, why there is no whitelist, and the community disagreement over Player ID versus EOS ID.
Jagex’s rule is 2 GB plus 1 GB per player, which puts a full six-player server at 8 GB. What the formula covers, what it leaves out, and the measurements we will publish once we have them.
A running server that nobody can find: check the build mismatch and the wrong-case world name first. The checklist: version in the log vs the game, exact-name search, restart after a patch, INI reset, and the Steam-invite known issue.