Add custom game settings preset

[naragonfr]

on persistant_data/Settings/ServerGameSettings.json:

"Level5": {
         "FloorLimit": 800,

in server log after launching docker compose up :

"Level5": {
        "FloorLimit": 550,

(same as server/VRisingServer_Data/StreamingAssets/Settings/ServerGameSettings.json and this file is restored every docker up)
So i cannot change Standard Settings with this image ?

[naragonfr]

I want to use custom settings that i create with VRising Game and copy the json to my docker server

[naragonfr]

the problem was the Custom game settings created by the game are not the same with ServerGameSettings.json, any way to maybe simplify ?
A way to add new preset called in ServerHostSettings.json ?

[TrueOsiris]

if I alter stuff in persistant_data/Settings/ServerGameSettings.json and restart the server, the settings are applied.
If this setting isn't applied, this smells like a bug with the dedicated server itself.
There have been multiple hotfixes. Isn't this fixed in those?

I was typing this "I'm not 100% sure that the server json and the local game json are formatted the same way, so you're doing this at your own risk." before I read your last comment.
I might add more optional environment variables to set different game settings (based on this)
Editing the files & restarting once is the way to go for now.

[damianjyates]

Summary of Troubleshooting Steps Regarding Bound Items and Teleportation in V Rising (Docker & Local Installs)

We encountered an issue where characters are unable to teleport with bound items, despite modifying the relevant server setting. To isolate the problem, we conducted the following steps:

Docker Environment Testing:

Deleted all save files under /srv/vrising/ImportedWorld-persistentdata/Saves/v4/world1/ on the host.

Confirmed removal, then restarted the container—but the same world and character state persisted.

Identified that the actual save being used was located under a separate folder: autosave_0, not world1.

Determined that the persistent save files are restored based on the Z:\mnt\vrising\persistentdata\Saves\v4\autosave_0\ path inside the container.

Confirmed bind mounts via docker inspect to validate persistent storage paths.

Local Install Testing (Non-Docker, Steam):

Copied the Docker container save files to the local save directory:
C:\Users<Username>\AppData\LocalLow\Stunlock Studios\VRising\Saves\v1\

Launched V Rising locally, confirmed the save loaded correctly.

Toggled the AllowTeleportBoundItems setting in ServerGameSettings.json to true.

Relaunched and tested teleportation—bound items still prevented teleportation.

Created a brand-new world and character, spawned level 30 gear including bound items, and repeated the teleport test—teleport still blocked.

Conclusion:
The teleport restriction persists regardless of environment (Docker vs. native Steam) or whether the setting is toggled on a migrated or freshly generated world. This suggests the setting either isn't being correctly applied or the game engine enforces bound item restrictions elsewhere.

We would appreciate insight into whether this setting should take effect immediately or if additional steps (e.g., full world regeneration, config re-parsing, or admin commands) are required.

[kwossi]

I got it to work now with these steps:
You have to add a custom preset json file in server/VRisingServer_Data/StreamingAssets/GameSettingPresets. Add a json file and call it Custom.json (for example). You have to add one because the other files get overwritten again.
You can paste all the ServerGameSettings in here that you want.
Then point your ServerHostSettings in persistentdata/Settings to that file by adding "GameSettingsPreset": "Custom",

Restart the server and this should do it.

[kwossi]

Toggled the AllowTeleportBoundItems setting in ServerGameSettings.json to true.

Also you wanna actually set TeleportBoundItems to false to be able to teleport stuff. The naming here is a bit misleading.