61e36d0abd
Due to an issue that stops the SSC config persister thing from working, I moved the config item that's new back to the config file. I tried applying the patches from https://github.com/Pryaxis/TShock/pull/2354/commits but these didn't actually resolve the issue. I'm keeping the commits here but I'm not sure they help. The core problem is this: if you add a new config file item to the ssc config, the ssc config is overwritten with the default config items instead of being merged automatically with the new items. This is a critical issue as it means that SSC is disabled on all servers that had it enabled and results in "data misplacement" which is alarming enough to cause users to think they had data loss, which is not ideal. Until the issue with the SSC config is resolved, I'm not willing or confident to change it.
1.1 KiB
1.1 KiB
Enabled
Enable server side characters, causing client data to be saved on the server instead of the client.
- Field type:
Boolean - Default:
False
LogonDiscardThreshold
Time, in milliseconds, to disallow discarding items after logging in when ServerSideCharacters is ON.
- Field type:
Int32 - Default:
250
ServerSideCharacterSave
How often SSC should save, in minutes.
- Field type:
Int32 - Default:
5
StartingHealth
The starting default health for new players when SSC is enabled.
- Field type:
Int32 - Default:
100
StartingInventory
The starting default inventory for new players when SSC is enabled.
- Field type:
List1` - Default:
System.Collections.Generic.List1[TShockAPI.NetItem]`
StartingMana
The starting default mana for new players when SSC is enabled.
- Field type:
Int32 - Default:
20
WarnPlayersAboutBypassPermission
Warns players and the console if a player has the tshock.ignore.ssc permission with data in the SSC table.
- Field type:
Boolean - Default:
True