#vintage story Serverconfig not being read

10 messages · Page 1 of 1 (latest)

bitter girder
#

So I'm changing values following wiki's and even BiSect support pages but i have found the world generation section in the serverconfig file are being completely ignored and continuously follows Default values. I have wiped the save files, renamed the worlds save file name in the config and that works but changing the value for month length has to be done in game and does not work and is ignored if this is set in the serverconfig. It also ignores landform scaling and ocean scaling values on top of many other world gen values plus time scaling.

Does Bisect hosting just not allow us to customize these values and force us to use vanilla values? Is the serverconfig file set to read only? Is there a second or hiddenn serverconfig file i am unaware of located elsewhere other than container/data/serverconfig.json?

#

vintage story Serverconfig not being read

merry marten
#

Bisect does not block any changes to the config file that are not network related - and they block network related changes by not allowing access to addresses/ports, not by altering the file itself.

#

I don't know VS at all, but I know most games will deal with a config file with formatting errors and sometimes even invalid values by wiping the file and reverting everything to defaults.

#

Is it possible the changes are missing a comma or quote somewhere?

If you save the file and re-open it before starting the server, are the changes there? (e.g. make sure the save button is getting hit.)

#

Are the settings you're trying to change also in the Startup tab? If so, those usually take precidence over the config file.

bitter girder
#

-I double checked the syntax and then triple checked it by havin someone else look at it they even said no errors.
-We are hitting the save button and only changing and saving it while the server is stopped.
-Unfortunately the Startup Tab does not allow me to override a serverconfig.json

cyan mason
#

If the config files don't seem to be applying I would suggest to have ticket staff take a look!

#

!ticket

simple pewterBOT