If you set the Clear on Wipe to enabled = false, does that mean that the size set with dynamic sizing will not be erased at wipe?

I want to give my players extra slots through VIP and other methods via the backpack.addsize command, but when we wipe I don't want them to lose those slots. This is because the tool that sends the command will not know we wiped and will not re-send the command to re-add the slots. 

It will know to send the negative qty when the player loses VIP, for example, so I want their adjusted size to persist through wipes. It this possible?

"Clear on Wipe" applies only to the backpack contents, not capacity.

Dynamic capacity is always reset on wipe. There has been a suggestion to make this configurable and more complex. I agree with the suggestion, but I haven't gotten around to implementing any changes for this yet.

WhiteThunder

"Clear on Wipe" applies only to the backpack contents, not capacity.

Dynamic capacity is always reset on wipe. There has been a suggestion to make this configurable and more complex. I agree with the suggestion, but I haven't gotten around to implementing any changes for this yet.

Either you could just not use dynamic capacity (i.e., just use permission based capacity), or you could restore dynamic capacity after wipe by overwriting the data file (i.e., after data/BackpacksCapacity.json is cleared when the server starts, unload the plugin, restore the file, then load the plugin).

The idea of stacking permissions to stack capacity, I think is out of scope for this plugin to do directly. The idea behind the dynamic capacity system/API is that it enables you to create/use an addon plugin to achieve that specific behavior, as there may be too many (or too nuanced) use cases, making it difficult for one plugin to account for them all.

I pushed some changes to GitHub to help with your use case. I haven't tested them so not sure if it all works.

https://github.com/WheteThunger/Backpacks

• New config option to determine whether to reset dynamic size
• Initial and max size will be determined by taking the highest of all size profiles assigned to the player (e.g., with 32-36 and 30-40, actual will be 32-40)
• Data file will store the bonus size rather than the exact size, allowing players to retain extra capacity when upgrading/downgrading the range (e.g., with 32-36, if at 34, upgrading to 36-40 will give the player 38)

You are amazing! I will give this a try today and see how it works!

Merged post

This seems to work exactly as desired from my testing! Thanks so much!

What would cause the bacpackscapacity file to clear if you have it set to wipe false? My dev server file cleared on me and I can't tell how, but I lost my extra slots and want to prevent the same thing from happening on the live server. 

The plugin will only clear the capacity file if the config option to clear it ("Reset dynamic size on wipe" > "Enabled") is enabled (logic which checks this is here). You might have another plugin which cleans data files on wipe; some people do that.

WhiteThunder

The plugin will only clear the capacity file if the config option to clear it ("Reset dynamic size on wipe" > "Enabled") is enabled (logic which checks this is here). You might have another plugin which cleans data files on wipe; some people do that.

Ok, thanks! Maybe I tested lowering the capacity and don't remember then. We did a lot of testing that day. Thanks again for the quick reply.

 "Size profiles": [
        {
          "Permission suffix": "0-8",
          "Initial size": 0,
          "Max size": 8
        },

Did you get a chance to see this yet? I would really like to get rid of the 1 slot backpacks...

Hmm, I've never considered 0-slot backpacks. The plugin forces the capacity to be at least 1 since there would be no point in opening a backpack otherwise. It might be a significant change to support 0 size.

Maybe I could take away the 0-8 slot perm from everyone and only give it to those that buy the perks. That might work.

I get around this "problem" by using PlayerRankings (with playtimetracker) so that default players dont get a backpack until they achieve the first rank (one hour) then they get the minimal slot(s)  and those slots progress with each rank achieved.