.
On a dedicated server you cannot change a sandbox setting after the world is generated. The value is baked into the save at world-gen and there is no supported way to change it on a live world after it starts, The code is baked into the main.ttw on world generation.
Changing any sandbox Setting in the serverconfig gets overridden on every boot, and setting it live with a console command reverts on the next restart.
The only way to actually change a sandbox setting on dedicated is to wipe and regenerate the map.
That's the bug, and it's a real problem for anyone running a persistent server.
Concrete example from my seed: I had QuestsPerTier set at 15. That runs straight into the bug you confirmed a couple posts up, over 10 breaks traders. So, 15 was baked into the save.
There is no way on a dedicated server to change that value on the live world without resetting the map.
This has not been my experience. After shutting down the server, and changing the sandbox code in serverconfig.xml, and restarting the server, WITH NO OTHER CHANGES, the new sandbox code is respected and used as intended.
That is not to say you have not experienced it, but to say changing ANY sandbox setting gets overriden is inaccurate.
I did NOT confirm OVER 10 breaks traders, i confirmed that UNDER 10 requires an simple xml edit alogside it to make it work as I think it was intended. I personally set it to 7 via sandbox and xml without issue.
Why not try the simple xml edit alongside the sandbox setting that I suggested? Not saying that it's not a bug but it's a simple workaround. Maybe it will solve your biggest problem
I have no experience nor desire to gain experience with setting it over 10, due to my limited play time I prefer a much faster progression than vanilla not slower.
So that's two sandbox bugs compounding: a setting that breaks over 10 and no way to change a baked sandbox setting on a live dedicated world.
Both from my own experience, both 3.0.
Agreed, the first one is a bug and should be addressed by the devs.
However, I personally have not experienced being unable to change sandbox codes post RWG. I have changed mine at least 4 times without issue, and without needing to regenerate the world.
The second one is the bigger issue and it's the specific answer to your question: on dedicated, a wrong sandbox value can't be corrected without destroying everyone's progress.
Maybe there's a misunderstanding here...When you say "wrong", do you mean wrong in the sense that the code you made in the sandbox on a client, and then copied and pasted into the serverconfig.xml, did not actually take effect?
Or do you mean that somehow you came up with and actually invalid code outside of the client sandbox settings, that waqs not accepted when you pasted it into serverconfig.xml?
It's an important distinction.