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.
Any chance we could customize the message when upgrading the backpack? Possibly add color codes or remove the [Backpack] tag?
Or have an option to automatically upgrade the backpack slots based on the player's backpack slot permission.
@GladimusMaximus
Same thing happens for my users.
Iv'e been using the plugin, and it works great, but for some reason, when the server restarts, the backpack wasn't saved for the past like 3 hours, and it goes back to a previous state.
Is it a known bug that it's not writing back to the file?
If not, could you maybe add an option to save the backpack when they log off?
@dockter
Are you planning to fix my issues with upgrades? I'm not asking for a ETA, but I would like to know if my issue is going to be addressed. Thanks and sorry to put more work on your back. I know you're busy with a lot of other things as well and don't get much in return. Keep up the great work on Spout! :)
@mblanchet75
You can do it from your ftp.
@tiagoomendess
Next time, read the description: "Soft Dependencies - SpoutPlugin - Vault"
Requires spout? It isn´t work withot spout?
@dockter
Exactly! I want to be able to view and modify inventory.
@mblanchet75
Are you asking to be able to just look or modify their inventory?
Chaznuts:
Thanks for the answer, but my problem, my modos does not have access to files. This is why I suggest a command like "/backpack PLAYERNAME:". It will be great if i player cheat with x-ray for example.
@mblanchet75 In game, I don't think there is, but in the folder plugins>Backpack>backpacks>[world]>[user] you can see everything that is there, which is updated as things are added/removed. I wouldn't mess with anything if you don't know what you're doing in there, but you can easily see what they have.
@dockter Any comment to my comment? Want me to create another ticket?
It is a very nice plugin.
I have a question. I want to know if there is a way for an admin to look inside a backpack of an other user?
If not, I suggest to add this feature.
@3ptO
Our current system is faster than mysql.
MySQL support?
@dockter
Alright I found out a few things. First of all, when "use-spoutplugin:" is on true, users who aren't using Spout cannot upgrade, which is a problem because a lot of servers who use SpoutPlugin don't use spout.plugin.focespoutcraft.
Second of all, the upgrading backpack sizes is completely different when you upgrade with a command or with the Spout GUI (which the command upgrade is better and if both ways were like that, the ticket I created would be completely unnecessary). When you use "/backpack upgrade," it forces the user to upgrade one size at a time and only costs the amount specified in the config (so if each size was 1000, it would only cost 1000 for each upgrade). When you upgrade with the Spout GUI, the user can skip sizes and also the config upgrading prices is cumulative (buying size 18 would be 1000, 27 would be 2000 on top of that, etc.).
Hope you guys can look into this soon! I really like this plugin, but it needs a couple fixes. Have yet to test out the dupe thing, but I appreciate the effort to try and resolve it. I will report any findings when discovered. Thanks!
@dockter
Yeah it's on. Players are reporting duplication if they went to another world, such as the nether, and the server restarted afterwards.
For those having the dupe bug issue, are you using the :
use-saveonlogin: true
Option? This should have resolve that issue.
@dockter
Is there a simple way to check if they're duping things with this plugin?
@mig4ng
Why don't you ban people that cheat, its easy to detect...
For some reason, the /backpack upgrade command isn't working.. The Spout GUI upgrading works fine, and it doesn't say anything about invalid command or no permission (which users have the correct perms). Would like it looked at for my users with no Spoutcraft. Thanks!