Backpacks not wipingNot An Issue
Good morning.

Today, we wiped our PvE server. Users still have their backpack and items in it. I did even a full clean installation, deleting lang files, config and everything related to it. Booted the server, asked 2 players of mine to come online and check, gave them some stuff in their backpacks and wiped it again to see if it can be reproduced and it does. 

No error log nothing.
I've moved your reply to a seperate thread, because it does not seem to be related to that topic.
Please make sure you have the config option for removing backpacks on map wipe enabled.

For manually wiping backpacks, you'd have to delete the data/Backpacks directory while the plugin is unloaded.

I have this set as true to clear on wipe. I delete my map saves, bp saves and etc but it still saved all my stuff in the backpack. Any idea as to why it didnt work? For now ill just clear the data files for the plugin.

This plugin, like all others that attempt to perform some specific function on wipe, relies on Oxide calling a particular hook the first time the server makes a new save after a wipe. If this didn't work, that probably means the plugin was not loaded at that particular moment. A common reason that a plugin wouldn't be loaded after a game update is because it was broken immediately following that update, but that seems unlikely in this case since nobody has reported issues with the plugin since the game update this week.

The only other reason I could think of is that Oxide itself was not even loaded immediately post wipe. If that was the case, then other plugins that perform a function on wipe would also have been affected, although you may not have noticed because the effect may have been more subtle or the stale data may have had no effect, depending on the plugin. This is a pretty interesting theory, as it could be pretty easy to encounter by restarting the server automatically without applying an Oxide update first, so it could lead to issues with potentially lots of plugins, so I wonder if there is any way Oxide could handle that better.

For the immediate concern, I am planning to add a requested feature soon to allow wiping specific players' backpacks, so I'll probably throw in a server/admin command to wipe all backpacks as well, which could be useful to server owners if and when this kind of thing happens in the future.

GGaq95K9icjqkF3.jpg WhiteThunder

This plugin, like all others that attempt to perform some specific function on wipe, relies on Oxide calling a particular hook the first time the server makes a new save after a wipe. If this didn't work, that probably means the plugin was not loaded at that particular moment. A common reason that a plugin wouldn't be loaded after a game update is because it was broken immediately following that update, but that seems unlikely in this case since nobody has reported issues with the plugin since the game update this week.

The only other reason I could think of is that Oxide itself was not even loaded immediately post wipe. If that was the case, then other plugins that perform a function on wipe would also have been affected, although you may not have noticed because the effect may have been more subtle or the stale data may have had no effect, depending on the plugin. This is a pretty interesting theory, as it could be pretty easy to encounter by restarting the server automatically without applying an Oxide update first, so it could lead to issues with potentially lots of plugins, so I wonder if there is any way Oxide could handle that better.

For the immediate concern, I am planning to add a requested feature soon to allow wiping specific players' backpacks, so I'll probably throw in a server/admin command to wipe all backpacks as well, which could be useful to server owners if and when this kind of thing happens in the future.

I was just thinking about this because i noticed all other plugins with a clear on wipe setting didnt work either. I think it was due to the fact i wiped the server while oxide was turned off and when i restarted the server a second time to update oxide the server had already created a map save so it probably didnt recognize it as a wipe. 

Yeah, exactly. So lesson learned is if you created a map without Oxide, wipe again once Oxide is installed.

I imagine there could be better education on this, but ideally some kind of tooling can help. Not sure what the options would be. I suppose Oxide could be "smarter" and detect that this is the first save since the previous version of Oxide, but that could lead to backwards incompatible behavior such as being called when you switch to another pre-generated map for instance.

VkN9NFab7QeSXKB.jpg WhiteThunder

Yeah, exactly. So lesson learned is if you created a map without Oxide, wipe again once Oxide is installed.

I imagine there could be better education on this, but ideally some kind of tooling can help. Not sure what the options would be. I suppose Oxide could be "smarter" and detect that this is the first save since the previous version of Oxide, but that could lead to backwards incompatible behavior such as being called when you switch to another pre-generated map for instance.

Usually i do that but i was in a situation where i wasnt home and had to use my phone which messed me all up. Not a hard process but something to make it easier would always be helpful. Thanks for the help nonetheless :D

Locked automatically