Backpack
Everyone wants extra storage, Backpack!
Do not use the 1.6.x builds of backpack with a 1.7.x. server....
Backpack
Core Features
- Configurable Drop on death
- Uses Vault for Economy handler.
- Allow your players to expand their Backpack from 9 slots to a max of 54.
- Multiworld support with different Backpacks or Sharing!
- Overflow abilities from players main inventory. (Must have at least 1 open slot to make overflow abilities work).
- Blacklist Abilities - deny certain items in the Backpack
- Fully functional API.
Spout Enabled Features
[Requires SpoutPlugin ]
- Custom GUI for Upgrading Backpacks.
- Custom Hotkey assignments for opening Backpack.
Multi-Server Enabled
- This plugin is written for both Bukkit and Spout Servers.
Developers:
- AlmuraDev Team
Configuration
File: config.yml
General:
- use-economy: Whether or not to enable economy system for backpack purchase & upgrades.
- use-spout: Whether or not to enable SpoutPlugin based features.
Admin:
- control-panel: Enable or disable Admin Panel.
- hotkey: KEY_V {default keybinding inside of Spoutcraft to display Admin Panel}
Backpack:
- no-perm-default-size: 9 {default backpack size if no permissions system found}
- hotkey: KEY_B {default keybinding inside of Spoutcraft to open Backpack}
File: blacklist.yml
- Contains list of items you dont want users to save in their backpack.Follow file format automatically created. Use only names of materials, not numbers.
File: share.yml
- Contains list of backpack shareable worlds.
share: world: - world_nether - world_end
In this above configuration, WORLD is the name of the Parent World. The child objects below it will be the name of shared worlds from the parent. Simply modify the name of your Parent Worlds to get the specific world sharing you desire.
- If you used any previous build of Backpack prior to build 81, I would advise you that if you decide to use the world sharing feature, delete any world directory in your /backpacks/ directory that is now being shared. The existence of these now un-used files give troubles for the upgrade procedure under very specific circumstances.
Permissions
Here's a list of specific permissions nodes for this plugin and what each does.
- backpack.use = Allows the users to use the Backpack itself.
- backpack.upgrade = Allows for users to upgrade their Backpack.
- backpack.keepitems = Allows users to keep items in Backpack upon player death.
- backpack.noblacklist = Allows users to bypass the backpack blacklist.
- backpack.noupgradecost = Allows users to upgrade backpack for free.
- backpack.overflow = Allows item pickups to automatically go into the backpack if users inventory is almost full.
- backpack.share = Allows backpack to be shared across specified worlds from share.yml
- backpack.admin = Allows user to use Admin Panel.
- backpack.size.18 = Allow 18 Slot Backpack.
- backpack.size.27 = Allow 27 Slot Backpack.
- backpack.size.36 = Allow for 36 Slot Backpack.
- backpack.size.45 = Allow for 45 Slot Backpack.
- backpack.size.54 = Allow for 54 Slot Backpack.
Commands
- /backpack = Opens Backpack
- /backpack upgrade = Upgrades backpack
Addons
Support
Support for this and all other AlmuraDev plugins can be found by joining our chat channel here:
Hard Dependencies
- Bukkit 1.5.1+
Soft Dependencies
- SpoutPlugin [Needed for Hotkeys and Custom Interface] << Not Required
- Vault 1.2.15+ [Needed for Economy Support] << Not Required
Spoutcraft & SpoutPlugin

Get Spoutcraft & Spoutplugin Now! >> Get Spout!
Donations for this project can be directed here: PayPal: Click Here
Many thanks for your consideration.
-
View User Profile
-
Send Message
Posted Jul 30, 2012Build 93 should have the fix for inventories not opening unless you have backpack.use. Major goof on my behalf.
Grab it via the link to Jenkins above!
-
View User Profile
-
Send Message
Posted Jul 30, 2012Is there no size 9 permission?
EDIT: Nevermind :)
-
View User Profile
-
Send Message
Posted Jul 30, 2012Hmm, having the same issues some below were having, anyone without backpack.use permission can't open any chests. Using build 92.
-
View User Profile
-
Send Message
Posted Jul 30, 2012@Krallnyx
You cannot use zero.
-
View User Profile
-
Send Message
Posted Jul 29, 2012Thanks :)
default-size=0 doesn't work
If i don't give users backpack.use perm, they can't open chest/furnace/workbench.
Upgrade works fine.
-
View User Profile
-
Send Message
Posted Jul 29, 2012Everyone fighting permissions issue use build 92.
Everyone also pay attention to the permissions nodes above, they changed.
-
View User Profile
-
Send Message
Posted Jul 29, 2012@iKrzysiek
Oh, you had to have the users upgrade their backpacks in game? That's definitely why it didn't work for me. I was hoping the permission nodes would set the slots each group had by default!
If iKrzysiek's question cannot be fulfilled, I double that the release of this option should be implemented. If it is, simply making an added node in the config file as follows:
use-perm-defaults: true/false (or something else, but same function) should be used!
I hope you consider :)
-
View User Profile
-
Send Message
Posted Jul 29, 2012I like this plugin and I hope I can use it. But the permissions don't work for me I'm using PermissionsEX, when I give some one backpack.upgrade they can upgrade until 54 slots. While I also give that group backpack.slot.18 (trusted rank) than I gave VIP+ backpack.slot.27 and also they can rank upto 54 slots using /backpack upgrade but If I don't give them backpack.upgrade they only have 9 slots.
There were no errors in the console. 29.07 20:39:14 [Server] INFO [Backpack] Successfully hooked into Vault for permissions 29.07 20:39:14 [Server] INFO [Backpack] Successfully hooked into Vault for economy transactions 29.07 20:39:14 [Server] INFO [Backpack] Enabling Backpack vUnknown
That's what It said. But other than that amazing and very unique plugin :D
-
View User Profile
-
Send Message
Posted Jul 29, 2012How to set That:
Rank A always have 9 slot backpack.
Rank B always have 18 slot backpack.
Rank C always have 27 slot backpack.
Rank D always have 54 slot backpack.
and they dont have to use /backpack upgrade?
-
View User Profile
-
Send Message
Posted Jul 29, 2012I use PermissionsBukkit
-
View User Profile
-
Send Message
Posted Jul 29, 2012@Krallnyx
Do you use bPermissions? I had the same exact problem. I don't know if bPerms is the problem.
-
View User Profile
-
Send Message
Posted Jul 28, 2012@predawnia
The thing is, I do not have a multi-world plugin, and I currently only have Essentials, Vault, PEX, and WorldEdit/Guard installed. o_o After a while I couldn't open chests either... strange...
-
View User Profile
-
Send Message
Posted Jul 28, 2012@finamenon
Apparently BackPack b81 doesn't support Multiverse or My Worlds at this moment. I already posted a ticket for it :)
-
View User Profile
-
Send Message
Posted Jul 28, 2012@predawnia
Currently I have no multi-world plugin, but plan to!
-
View User Profile
-
Send Message
Posted Jul 28, 2012Hello,
I want simple users to don't have access on any size. •no-perm-default-size: 0 and no permissions of any kind, they could not open anything (chest, furnace, crafting table...). Even if y give them backpack.use (but no size).
Any way to have players whithout any backpack ?
-
View User Profile
-
Send Message
Posted Jul 27, 2012@predawnia
I have the same issue as TerraVale, and I use Multiverse. D:
-
View User Profile
-
Send Message
Posted Jul 27, 2012@TerraVale
Are you using multi worlds? :)
-
View User Profile
-
Send Message
Posted Jul 27, 2012I am using PEX, and currently trying to use Backpack as a perk for donators. I have three donation rankings, and wish for each rank to have 9 more slots than the other, starting at 9. Example being the 'tier 1' donator having 9 backpack slots, 'tier 2' having 18 slots, and 'tier 3' having 27.
Each donator tier has backpack.use, backpack.keepitems, backpack.share, and a backpack.slot.# permission, corresponding to how many slots they need.
Unfortunately, I can't seem to get the different slot amounts working - they all default to 9!
Thankfully, though, standard users cannot use /backpack, however it returns this: "/backpack [command] [arguements]" instead of telling them they "do not have access to this command", which much more preferable for the sake of preventing induced confusion with commands of the like.
-
View User Profile
-
Send Message
Posted Jul 27, 2012@dockter
I spoke with the bPermissions team. They would like to know where you documented this bug so they can address it.
-
View User Profile
-
Send Message
Posted Jul 27, 2012<<reply 833996="">>
bPermissions does not work well with Backpack. We've told them about an issue that exists with THEIR plugin but they have so far refused to address it.