**Carbon** Backpack Capacity IssueSolved

Im using carbon on my test server and Im using dynamic settings.

 

I was troubleshooting why player reguardless of permission would only get 48 slots (even when they have the permission for 96) so I thought that maybe there was an issue with the order of the config (sort of like kits where it reads from top to bottom for auto spawn kits) so I reversed my config so that 96 slots showed before 48. I have 5 dynamic groups (48, 96, 144, 192 and 240) and now players have 240 slots instead of the one they are supposed to have.... even after setting the config back the way it origionally was players still have 240 even tho they dont have permission for 240. I even unloaded the addon and deleted all the data files and reloaded the addon and players still have 240 even tho no group currently has permissions for 240 slots... Im at a loss

Can you share your config?

From your description, it sounds like you are using the dynamic capacity feature (which designates a min/max capaity range and requires integration with other plugins to increase capacity through various events). When using that mode, capacity data is stored in the data/BackpacksCapacity.json file. I know you said you deleted "all" data files, but I just wanted to call out that file specifically in case you missed it.

Yes I deleted the folder that stores the items in the backpack and both the capacity and the other backpack file as well... 

I was able to reproduce one issue, where if you grant none of the size profile permissions, the first one applies. This is consistent with your account, which means the order does matter in that case. Otherwise, order is not applicable. It wasn't intended that the first profile apply if you don't have the permission for it, so I will make an update to determine size differently in that case.



Merged post

I pushed a fix to the plugin's GitHub repo for testing, which fixes the issue where the first dynamic size profile applies even when you have no size profile permissions granted.

https://github.com/WheteThunger/Backpacks/blob/master/Backpacks.cs

For continued troubleshooting, please share your config.

https://imgur.com/a/ujI09Sp - Ive posted the permissions I have and that its still giving me 240 slots
{
  "Backpack size": {
    "Default size": 48,
    "Max size per page": 48,
    "Enable legacy backpacks.use.1-8 row permissions": false,
    "Permission sizes": [],
    "Dynamic Size (EXPERIMENTAL)": {
      "Enabled": true,
      "Reset dynamic size on wipe": {
        "Enabled": true
      },
      "Size profiles": [
        {
          "Permission suffix": "240-480",
          "Initial size": 48,
          "Max size": 480
        },
        {
          "Permission suffix": "192-480",
          "Initial size": 96,
          "Max size": 480
        },
        {
          "Permission suffix": "144-480",
          "Initial size": 144,
          "Max size": 480
        },
        {
          "Permission suffix": "96-480",
          "Initial size": 192,
          "Max size": 480
        },
        {
          "Permission suffix": "48-480",
          "Initial size": 240,
          "Max size": 480
        }
      ]
    }
  },
  "Drop on Death (true/false)": false,
  "Erase on Death (true/false)": false,
  "Minimum Despawn Time (Seconds)": 900.0,
  "GUI Button": {
    "Enabled": false,
    "Enabled by default (for players with permission)": true,
    "Skin Id": 3050418770,
    "Image": "",
    "Background Color": "0.969 0.922 0.882 0.035",
    "GUI Button Position": {
      "Anchors Min": "0.5 0.0",
      "Anchors Max": "0.5 0.0",
      "Offsets Min": "185 18",
      "Offsets Max": "245 78"
    }
  },
  "Container UI": {
    "Show page buttons on container bar": false,
    "Max page buttons to show": 8
  },
  "Softcore": {
    "Reclaim Fraction": 0.5
  },
  "Item restrictions": {
    "Enabled": false,
    "Enable legacy noblacklist permission": false,
    "Feedback effect": "assets/prefabs/locks/keypad/effects/lock.code.denied.prefab",
    "Default ruleset": {
      "Allowed item categories": [
        "All"
      ],
      "Disallowed item categories": [],
      "Allowed item short names": [],
      "Disallowed item short names": [],
      "Allowed skin IDs": [],
      "Disallowed skin IDs": []
    },
    "Rulesets by permission": [
      {
        "Name": "allowall",
        "Allowed item categories": [
          "All"
        ],
        "Disallowed item categories": [],
        "Allowed item short names": [],
        "Disallowed item short names": [],
        "Allowed skin IDs": [],
        "Disallowed skin IDs": []
      }
    ]
  },
  "Clear on wipe": {
    "Enabled": false,
    "Enable legacy keeponwipe permission": false,
    "Default ruleset": {
      "Max slots to keep": -1,
      "Allowed item categories": [],
      "Disallowed item categories": [],
      "Allowed item short names": [],
      "Disallowed item short names": [],
      "Allowed skin IDs": [],
      "Disallowed skin IDs": []
    },
    "Rulesets by permission": [
      {
        "Name": "testing",
        "Max slots to keep": -1,
        "Allowed item categories": [],
        "Disallowed item categories": [],
        "Allowed item short names": [],
        "Disallowed item short names": [],
        "Allowed skin IDs": [],
        "Disallowed skin IDs": []
      }
    ]
  }
}​

Thanks for providing both the config and permissions. I see you have granted two size-related permissions:

  • backpacks.size.profile.48-480
  • backpacks.size.profile.96-480

I'm assuming that you expect to have 96 capacity in that case (until you increase the capacity through other events). The reason that you are seeing 240 capacity is that the permission you titled "48-480" is actually configured with "Initial size" 240. It looks like this was a consequence of your attempt to reverse the order of the entries. It seems you reversed the names but not the actually capacity amounts. Or perhaps you had initially set the "Initial size" values in the reverse order before reversing the entries.

To resolve all inconsistencies, make the following changes:

  • Update "240-480" to have "Initial size" 240 (currently 48)
  • Update "192-480" to have "Initial size" 192 (currently 96)
  • Update "96-480" to have "Initial size" 96 (currently 192)
  • Update "48-480" to have "Initial size" 48 (currenlty 240)

For your convenience, here is that section of the config modified. Note that the order does not matter.

"Size profiles": [
  {
    "Permission suffix": "240-480",
    "Initial size": 240,
    "Max size": 480
  },
  {
    "Permission suffix": "192-480",
    "Initial size": 192,
    "Max size": 480
  },
  {
    "Permission suffix": "144-480",
    "Initial size": 144,
    "Max size": 480
  },
  {
    "Permission suffix": "96-480",
    "Initial size": 96,
    "Max size": 480
  },
  {
    "Permission suffix": "48-480",
    "Initial size": 48,
    "Max size": 480
  }
]

If you want to avoid the possible issue where the permission names do not match the actual capacity, simply rename the permissions to something that doesn't indicate the exact size (e.g., vip1, vip2, vip3, or big, bigger, biggest).

Locked automatically