Update v-risingconfig.json to fix LanMode flag

[Choque]

The LanMode flag should correctly be added to the ServerHostSettings.json with a value of true or false.

[Greelan]

What are you basing this on? There is no such setting in the default ServerHostSettings.json that ships with V Rising, so curious.

Anyway, just adding to to the AMP config won't set it in the file

[Greelan]

FWIW, this debate was had and resolved a year ago: #988

[Choque]

Yea it seems to be undocumented, but it does work. If you add "LanMode": true to your config, you won't be able to connect via the Server Browser. You have to specifically use Direct Connect and check the "Lan Server" checkbox in the direct connect popup.
The current way of adding "-lan" in the console doesn't seem to carry over between server restarts. And for a while the "LanMode": true add to the config was/is the only way to counter the error that's been bugging V-Rising for quite a while - the infamous

src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address {MY-IP-ADDRESS} SteamNetworking - SteamNetConnections.ConnectionUpdate: k_ESteamNetworkingConnectionState_Connecting, 4199381823, 131073 SteamServerTransport - Update 4199381823 - k_ESteamNetworkingConnectionState_Connecting src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address {MY-IP-ADDRESS} src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address {MY-IP-ADDRESS}

For some reason - and I don't know why - if you get this error no one can connect to your server anymore. You have to restart the server, then people can connect ONCE and after that this error appears again and you have to restart again and so on.

If you start the server in LanMode, via the edit of the config, people now have to use Direct Connect but the server can stay up and running and the error doesn't appear.

[Greelan]

Actually, it is documented in the instructions on GitHub - reminded myself with that issue I linked. The instructions are still the same for 1.1 and say the env var or command line arg overrides the json setting

As noted in that issue I linked, it would be preferable to use a command line arg or env var since the default json doesn't have the setting and amp can't write it in

It would really be helpful if you could try out one of the other methods and see whether any of them solve the issue. I don't play the game myself

[Greelan]

An alternative command line flag has been implemented