BlackLightning

Bag limits have always applied just to the bag's parent container. They never factored in bags inside of other bags. The only exceptions are: 1. Player inventory containers (main, belt, wear) which share a limit despite being technically three separate containers 2. Backpacks plugin on uMod which shares limits across pages despite each page technically being a separate container The main reason it has always worked this way is for simplicity, as some tricky situations can occur otherwise. For example, you might normally be able to pick up a Bag of Holding bag with contents in it, but because it has additional non-empty bags inside it, you are not allowed to pick it up as doing so would exceed your overall limit. The plugin would have to clearly communicate to players what the problem is so that the player can rearrange bags or contents to overcome it. For similar reasons, bag limits inside of bags are also not configurable according to permissions. I understand this isn't ideal because it means you either end up giving players excess capacity (they can have bags both inside and outside the Bag of Holding bag) or less choice (they can only have one bag in the inventory, and they finally break through the limitation when they get a Bag of Holding bag). One way you could try to ease players through the transition would be to have different tiers of Bag of Holding bags, which allows progressively more bags inside of them, allowing players to progress from 1 outer bag to 1 outer bag with 1 inner bag, then 2 inner bags, and so on. However, that is still an opinionated progression as you wouldn't allow multiple bags directly inside the main inventory ever. To mitigate the above concern of allowing too much capacity once a player acquires a Bag of Holding bag, I could potentially make an update that allows you to configure how many bags a specific bag profile counts as, so you could make a Bag of Holding bag count as 5 bags for example.

Setting a higher value will generally improve performance because it allows the server to do less work (fewer transfers). There isn't much reason to set it below your max stack size.

Let's say you set the config to 100k. For an item with 25 max stack size, one full stack can be transferred at once. For an item with 500k max stack size, a full stack will require 5 transfers, so it will take longer.

Thanks for reporting this. There's an open support request about a similar issue, though I haven't been able to reproduce it yet. I am currently away and will be able to look further into this in about 8 hours. To minimize impact, you can try adjusting the underwater drag in the config to a lower value like 0.3.

Thanks for reporting this. Unfortunately, I was not able to anticipate the Rust hot fix that caused this and I am not able to get home for probably 6-8 hours so you will have to wait. This means bags will revert to standard halloween loot bags, leading to the contents being lost when players attempts to open them. For now, warn your players to stash their bags somewhere safe and do not attempt to open them.