You have installed the dedicated server and want to rename it, limit the slots and make sure players can reach it. The settings file is small, but one wrong comma makes it invalid. VarintKeel reads the file, proposes the edit as a diff and waits for your OK, so the change stays visible from the first line to the test in the game. You also keep a copy of the world folder before you start. You need only 3 things: the folder of the dedicated server, a model connected in the app and a moment when nobody is playing. The whole job takes 4 steps: open the folder, ask, review and test. Each step leaves a card in the chat, so you can scroll back and see exactly what was read, what was changed and what the command returned.
In VarintKeel, choose the folder that holds enshrouded_server.json as the chat's working folder, so the file tools see the settings and the logs. Copy the world folder now, before the first edit, with the backup steps described below. Write down the original name and slot limit, because you will want to compare them after the edit.
Type your goal, for example a new name and a slot limit, and switch to Plan only if you want the steps written first while nothing runs. A plan is cheap to read, and you can change the goal before the agent touches a single file. Plan only is a good first run for a folder you have not looked at in months.
In Ask first, read the proposed lines for the settings file, compare them with your copy, and accept or reject the change. If one line looks wrong, reject the whole edit and ask again with a clearer request; nothing is saved while the card waits. Names and slot limits are small values, so they make a good first edit.
Start the server, join it from the game and check the name, the slot limit and the connection before you delete any backup. If something is off, read the log with grep, fix one thing and test again. Keep the chat open, because the cards are your record of what was changed.
enshrouded_server.jsonread okenshrouded_server.jsonsavedqueryPort1 matchnetstat -an | findstr LISTENINGexit 0{
"name": "Example Survival Server",
"saveDirectory": "./savegame",
"logDirectory": "./logs",
"ip": "0.0.0.0",
"queryPort": 40001,
"slotCount": 4,
"gameSettingsPreset": "Default"
}This shortened sample uses made-up placeholder values and leaves out passwords. Take the real queryPort from your own file or from the official server documentation, never from this page, and copy the file before you edit it. The agent will show every change as a diff, so you can compare your own file with this layout line by line.
People who search for dedicated server setup help usually have the files but no map of them. list_dir shows the folder as a tree and glob finds every JSON and log file in it, so you learn where enshrouded_server.json and the logs actually are. read_file then opens the settings file and lists fields such as name, saveDirectory, logDirectory, ip, queryPort, slotCount and gameSettingsPreset. Nothing is changed in this phase, so Ask first has nothing to pause for. Compare the paths in the file with the folders on your disk before you go on, because a wrong saveDirectory is easier to fix now than after the first night of play.
The first enshrouded server config edit should be small, such as the name or slotCount. Stop the server, then ask the agent to change that one field. edit_file builds the change, and the card shows a diff with the old and the new line. In Ask first you accept or reject it, and a wrong comma or quote would stand out in the diff, because it makes the file invalid. Keep a copy of the original first. Then start the server and let grep search the log for the first error to see whether the file loaded. If the server starts but a value looks wrong, ask the agent to read the file again and compare it with your copy.
A blocked port is a common reason why friends cannot join. The server listens on the port numbers in its settings file, and players on the internet also need the port forwarded on your router to the server PC and allowed in the Windows firewall. The agent reads queryPort, and Shell lists the connections of this PC so you can see whether the server is listening. When a LAN only dedicated server shows high ping, read the log and the settings file before you touch a port. The router and the firewall stay your job. Compare each result with the official documentation before you change anything, and change only one port at a time, so you know which change helped. Write the new value next to the old one in your own notes.
A copy of the world folder makes every other change reversible. Stop the server and ask the agent to copy the folder named by saveDirectory with Robocopy through Shell; the card shows the real exit code. People who want to transfer a saved world to a dedicated server should first copy the folder the server already uses, so there is a way back, and then read the official documentation for the move itself with web_search or http_get. To test the backup, restore it into an empty folder and check with list_dir that the files are there. Then start the server on the restored copy to see that it loads. Repeat this test after every update, because a backup that worked last month says little about the one you made today.
