Update 2 of Enshrouded brought additional options for players to set up their servers. The structure of the enshrouded_server.json file, which is used to configure the dedicated server, has been updated for this purpose.<\/p>\n\n\n\n
Depending on the previous configuration of the server, some changes may be necessary on your side.<\/p>\n\n\n\n
The password for a server was previously defined in line 3 of the \u201censhrouded_server.json\u201d file. This line is no longer<\/span><\/strong> used to set the password for dedicated servers!<\/p>\n\n\n\n However, from now on, if the game recognizes a password defined in line 3, it will create a new \u201cuserGroup\u201d called \u201cdefault\u201d that will use the password and automatically grant the same permission level that players were used to until Content Update 2.<\/p>\n\n\n\n Important<\/strong> This means that if the host (i.e. you) of a server does not change anything, the dedicated server is still protected by the same password and the players’ authorizations remain the same as before. <\/p><\/div>\n\n\n\n Authorizations for players to play on servers are now managed via user groups (\u201cuserGroups\u201d).<\/p>\n\n\n\n Each group can be configured in the \u201censhrouded_server.json\u201d file with a unique configuration of authorizations and an associated password that grants the logged-in player the authorizations.<\/p>\n\n\n\n By default, the \u201censhrouded_server.json\u201d starts with 3 user groups, which can serve as the basis for hosts (i.e. you). The default settings are:<\/p>\n\n\n\n Hint<\/strong> The authorizations are set with \u201ctrue\u201d and \u201cfalse\u201d (see also the example at the end of this wiki). <\/p><\/div>\n\n\n\n By default, NO passwords are assigned for these groups. You always have to assign a password manually and then add it. You will see a corresponding button in the basic settings of your server. If you want to use different user groups, we strongly recommend that you assign appropriate passwords so that nobody can do anything nonsensical on your server.<\/p>\n\n\n\n Important<\/strong> All user groups have full access to the game world outside the player bases and can take part in battles, collect resources, solve quests, etc. \u2026 <\/p><\/div>\n\n\n\n Important<\/strong> The above presets are only generated if the \u201censhrouded_server.json\u201d is recreated after updating Enshrouded with Content Update #2. If the game recognizes an already set password, only the \u201cdefault\u201d user group will be created with the permission configuration identical to the \u201cfriend\u201d preset from the presets above. <\/p><\/div>\n\n\n\n New and unique user groups can also be set up in the \u201censhrouded_server.json\u201d file. To do this, simply add a new user group section with a new name and set a password and the desired authorizations.<\/p>\n\n\n\n Another setting that can be configured for each user group is the number of reserved slots for this user group. Important<\/strong> If this option is not to used, this must be noted as follows: \u201creservedSlots\u201d: 0 <\/p><\/div>\n\n\n\n If 1 or more reserved slots have been set up, the lobby will be marked as \u201cfull\u201d for players trying to join the server with another user group, which would result in all session slots being full. This allows for example admins or friends to join even if there is a high demand for slots by \u201cguests\u201d.<\/p>\n\n\n\n Important<\/strong> Up to 10 user groups can be created. <\/p><\/div>\n\n\n\n In Content Update #2, the previously used \u201cgamePort\u201d was removed from Enshrouded. Now the only port used by the game is the \u201cqueryPort\u201d.<\/p>\n\n\n\n Do I have to change anything now with the content update #2? Update 2 of Enshrouded brought additional options for players to set up their servers. The structure of the enshrouded_server.json file, which is used to configure the dedicated server, has been updated for this purpose. Depending on the previous configuration of the server, some changes may be necessary on your side. The password for a server was previously defined in line 3 of the \u201censhrouded_server.json\u201d file. This line is no longer used to set the password for dedicated servers! However, from now on, if the game recognizes a password defined in line 3, it will create a new \u201cuserGroup\u201d called \u201cdefault\u201d that will use the password and automatically grant the same permission level that players were used to until Content Update 2. Creating new \u201cuserGroups\u201d Authorizations for players to play on servers are now managed via user groups (\u201cuserGroups\u201d). Each group can be configured in the \u201censhrouded_server.json\u201d file with a unique configuration of authorizations and an associated password that grants the logged-in player the authorizations. By default, the \u201censhrouded_server.json\u201d starts with 3 user groups, which can serve as the basis for hosts (i.e. you). The default settings are: By default, NO passwords are assigned for these groups. You always have to assign a password manually and then add it. You will see a corresponding button in the basic settings of your server. If you want to use different user groups, we strongly recommend that you assign appropriate passwords so that nobody can do anything nonsensical on your server. Can I also create new user groups (\u201cuserGroups\u201d)? New and unique user groups can also be set up in the \u201censhrouded_server.json\u201d file. To do this, simply add a new user group section with a new name and set a password and the desired authorizations. Another setting that can be configured for each user group is the number of reserved slots for this user group.The option for this is called: \u201creservedSlots\u201d: 1 If 1 or more reserved slots have been set up, the lobby will be marked as \u201cfull\u201d for players trying to join the server with another user group, which would result in all session slots being full. This allows for example admins or friends to join even if there is a high demand for slots by \u201cguests\u201d. Changes to used ports In Content Update #2, the previously used \u201cgamePort\u201d was removed from Enshrouded. Now the only port used by the game is the \u201cqueryPort\u201d. Example of an updated server configuration<\/p>\n","protected":false},"author":16,"featured_media":21250,"comment_status":"closed","ping_status":"open","sticky":false,"template":"post-blog-template.php","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[30,22],"tags":[],"acf":[],"yoast_head":"\nCreating new \u201cuserGroups\u201d<\/h2>\n\n\n\n
\n
\n
\n
\n
Can I also create new user groups (\u201cuserGroups\u201d)?<\/h2>\n\n\n\n
The option for this is called: \u201creservedSlots\u201d: 1<\/p>\n\n\n\nChanges to used ports<\/h2>\n\n\n\n
Example of an updated server configuration<\/h2>\n\n\n\n
{\n\"name\": \"Enshrouded Server\",\n\"password\": \"\",\n\"saveDirectory\": \".\/savegame\",\n\"logDirectory\": \".\/logs\",\n\"ip\": \"0.0.0.0\",\n\"queryPort\": 15637,\n\"slotCount\": 16,\n\"userGroups\": [\n{\n\"name\": \"Admin\",\n\"password\": \"Randomized password 01\",\n\"canKickBan\": true,\n\"canAccessInventories\": true,\n\"canEditBase\": true,\n\"canExtendBase\": true,\n\"reservedSlots\": 1\n},\n{\n\"name\": \"Friend\",\n\"password\": \"Randomized password 02\",\n\"canKickBan\": false,\n\"canAccessInventories\": true,\n\"canEditBase\": true,\n\"canExtendBase\": true,\n\"reservedSlots\": 3\n},\n{\n\"name\": \"Guest\",\n\"password\": \"Randomized password 03\",\n\"canKickBan\": false,\n\"canAccessInventories\": false,\n\"canEditBase\": false,\n\"canExtendBase\": false,\n\"reservedSlots\": 0\n}\n]\n}<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"