This is terrible, I had set purge time to 30 days and had enabled test mode, but without me realising, the plugin had reset the config after I reloaded it.
Now multiple users on my server complain about their buildings getting wiped!

Ok, seems that it cannot deal with an inactive time of 30 days (2592000‬s). This is very disappointing, I think for a more peaceful/creative server, 30 days is a completely reasonable amount of time and I would like to be able to configure AutoPurge to work with that amount of time before wipe. Also resetting the config when inputting an invalid value is very bad, as that caused test mode to get disabled :(

Merged post

Now it suddenly works, even with 30 days, but before I got this error: "

AutoPurge v1.6.1: Failed to load config file (is the config file corrupt?) (Unexpected character encountered while parsing number: ‬. Path 'Timing.inactiveAfter', line 30, position 28.)"

The error means that the configuration file was not edited correctly, or is invalid JSON due to an invalid change.

Yeah, it must have been a problem because i pasted from windows calculator (deleted the quotation marks though), but now I sit here with some of my regular's stuff purged and I don't think there's any way of undoing a purge, is there?

Sadly, there is no way to undo the purge.

Alright, I found an old save so it's only half as bad, and now everything is configured correctly, but now I wanted to give some users the exclude permission. But oxide tells me that the permission doesn't exist and so I looked at the C# file and I see that the exlude permission only gets added in the callback "OnServerInitialized". If I guess correctly, this means that loading the plugin while the server is running, doesn't register the exclude permission.

Onserverinitialized is called on server initialized and somewhen on plugin load. I am rewriting the plugin, please wait patiently

OnServerInitialized is always called when the server is initialized and always when the plugin is hotloaded unless you utilize the bool to be selective.

Yep, I know, I didn't say it's not called :p

But then why does oxide tell me that the permission doesn't exist?