Enshrouded Server Settings Guide

Configure your Enshrouded dedicated server with game difficulty, day length, combat modifiers, and survival settings from the MANAfuel dashboard.

1. 01

   Open the Server Configuration

   Navigate to your Enshrouded server in the MANAfuel dashboard and open the File Manager tab. The main configuration file is enshrouded_server.json in the server root directory. Click to edit it inline. The file uses JSON format with clearly named properties for each setting.

   ---

2. 02

   Set Difficulty and Combat

   Enshrouded offers configurable difficulty through combat modifiers. Adjust enemy damage multiplier, player damage multiplier, and enemy health scaling. For a casual co-op experience, reduce enemy damage to 0.75 and increase player damage to 1.25. For hardcore groups, increase enemy health and damage above the defaults. These modifiers apply globally to all enemies.

   ---

3. 03

   Configure Day and Night Cycle

   Control the day-night cycle length to match your group's play style. Longer days give more safe exploration time. Shorter nights reduce the high-danger period. The Shroud becomes more dangerous at night, so adjusting the cycle affects the overall game feel significantly. Most co-op servers extend days by 50% and keep nights at default.

   ---

4. 04

   Adjust Survival Mechanics

   Configure hunger and thirst rates, stamina regeneration, and fall damage scaling. For building-focused servers, reduce hunger and thirst drain so players spend more time constructing and less time gathering food. For survival-focused servers, keep defaults or increase the drain rates. Each setting is independent — you can mix casual combat with hardcore survival mechanics.

   ---

5. 05

   Apply and Verify Changes

   Save the JSON configuration and restart your server. Enshrouded reads the config on boot. After restarting, join the server and verify the changes by testing combat, checking the day/night cycle speed, and confirming survival mechanics. Bob detects JSON syntax errors in the config file and alerts you if the config fails to parse on startup — the most common mistake is a missing comma or bracket.