Knapsack (backpack)
( backpack ) Knapsacks
Knapsacks are backpacks on steroids for MineCraft. Injected with a ton of options for both players and server owners, Knapsacks should prove to be a valuable asset to any MineCraft server.
Description
Knapsacks allow players to craft & give themselves and other players additional inventory slots. Knapsacks is packed with options for the player as well as for server owners and operators. Among those are the infamous Auto-Filling. Auto filling allows player to control what items get stored in their Knapsacks and when. Depending on how Knapsacks is configured, players will be able to keep items organized in Knapsacks Auto-Fills. Players have,for the most part, complete control on when items are filled to a Knapsack both before and after their inventory is full!
Another under-rated feature is the Knapsack expiry system. This system was built with the server owners in mind to stop the abuse of Knapsacks (crafting excessive packs, giving, dropping, etc..). Optionally, server owners can set limits on how many of a specific size Knapsack each player can have at any given point as well as an overall setting of all Knapsack sizes a player has.
Knapsacks is exactly what the name states, a Backpack on steroids! Jammed with many, many more options and more still coming
NEWS FLASH:
Always update to the latest for all bug fixes and latest Auto-Fill and other enhancements!
If your using plugin managers like plugman, etc.. DO NOT UNLOAD and LOAD Knapsacks using these plugins. You will have nothing but errors and exceptions due to database connections and event compiling priorities. You MUST restart your server when updating!
If you are running less than 1.0.28 Update now. Enhancements, Bugs and New Features Added!
Knapsack Releases/Builds:
Spigot/Bukkit 1.8.x: Bukkit/Spigot - Knapsacks-v1.0.28-Bukkit_Spigot_1_8_x
Bukkit/Spigot 1.7.10: Bukkit/Spigot - Knapsacks-v1.0.28-Bukkit_Spigot_1_7_10
Features
Completely Configurable
6 Different Steroids (9-54 slots - more coming) | Inventory Auto-Filling (1.0.12+) | |
Right-Click Sack while in Inv. GUI to Open another Sack!! | Right Click Normally to Open! | |
Give Sacks a default name | Control volume and pitch levels | |
Claim a found Knapsack | Craft any size | |
Keep Knapsacks when you Die | Custom Messaging | |
Global Black Listing | Sack Level Black Listing | |
Rename Using Anvils | Rename using commands | |
Clear a Knapsack with simple command | Clear and drop whats in a Knapsack at your feet | |
Share Knapsacks | Knapsack Thieving (not 100%) | |
Enable each Size Knapsack | Use Knapsacks stored any where!! | |
Global World Exclusions | Sack Level World Exclusions | |
Stash Knapsacks inside each other | Limits for each Sack | |
Upgrade Knapsacks | Place Limits on How Many at each Sack Level | |
Recipes for each Sack | Menu is Permission Based - keeps it short | |
Sizing for each Sack | Knapsack Expiry System, player and system to control abuse and lack of use | |
Weight for each Sack | Built-in filtering system for naming | |
Restricted Hot-Bar Swapping | Restricted Creative Use | |
Forbidden Monster Egg Spawning | Configurable Stashing Containers | |
Knapsack Recovery | Supports Minecraft Name Changes | |
SQL controlled databases | Configurable "command" for performing player cleanup of expired sacks | |
There is more..... | Interface Knapsacks with Signs, Blocks etc.. to Buy, Sell, or just to use a chest directly; known as "Knapsack Interface" (1.0.20+) |
Installation & Configuration
Installation & Configuration
Download the Knapsacks jar file.
Drop it in your plugins folder on your server.
Re-start your server.
Download your config that is automatically created at start up and Edit with your specific server settings for Knapsacks -or- just use the defaults and give it a go!!
Upload the editted config.yml back to your server and restart your server or use " /ks reload " from the console
Frequently Asked Questions:
I have compiled a bunch of questions with answers into it's own page rather than clutter this page. So if you have questions, please direct yourself to: Frequentl Asked Questions Page. If your question is not answered then please post a comment in the FAQ page and it will be answered as well as updated into the FAQ page!
Configuration Components:
The configuration for Knapsacks is pretty straight forwards. However due to the size of the config, I am only listing the components of the config on this page. Please see Installation & Configuration for complete configuration, broken down into the components.
The configuration is broken down into 6 Sections(click link above/below for config)
Plugin:
Config: (many things to config in here)
Sounds: (you make the choice!)
Notification Services (1.0.12+)
PlayerFeeds:
Knapsacks (sacks):
Installation & Configuration
Commands
Please see the Knapsacks Commands for a complete listing of all that Knapsack offers. In addition, the command page details the prerequisite or general permission node required for that command. However, each command Knapsack has may have additional functionality outside of the basic command which requires more permissions nodes.
All Permission Nodes & Easy Groups
For a complete listing of all permissions nodes and Pre-built Knapsack Permission Groups, visit the Permissions Page
Auto Filling 101
Auto Filling 101 details all the functionality behind Knapsack Auto-Filling as well as a complete list of commands and permissions for Auto Filling.
Knapsack Expiry System 101
Expiry System 101 details all the functionality behind Knapsack the Knapsack Expiry System for both Players and the Server. Also on this page is the complete list of commands and permissions for Knapsack Expiry System.
Knapsack Interface 101 (commonly called Knapsack Int)
Knapsack Interface 101 details all the functionality behind Linking Knapsacks for server and player shops, player private uses with chest, signs, etc... as well as a complete list of commands and permissions for Knapsack Interface.
Knapsack Stashing 101
Knapsack Stashing 101 details all the functionality behind Knapsack Stashing as well as a complete list of commands and permissions for Knapsack Stashing.
Monster Egg / Knapsack Id Reference
Here is a complete reference chart with each respective Knapsack for the Monster Eggs durability/typeId.
Monser Egg to Knapsack Cross Reference Chart
Default Crafting Recipes
These are completely configurable but by request, I've added this section as a quick reference! Images shown are are all the defaults that come configured when you first install Knapsacks. All default crafting recipes are located in 'images' tab of the site.
- The default crafting recipes:
Screen Shots:
The screen shots show most of the features in Knapsacks for this release. Will continue to add more and update as the features change...
Take a look at some screen shots!
Suggestions?
If you come across any bugs or issues or if you have any suggestions? Submit Issues and/or Suggestions Here
Resource Packs
Want to add the realism of the Plug-in to your GUI. Download one or all of the resource packs available now.
| Knapsack Resource Packs
To-Do
- Convert all in-line messages to language file
- Convert English language file to other languages (help wanted)
- Add Sheathing Options - Show that Sack on your back!
Add ability to interface Knapsacks with Shops, Chests...(completed-2-1-15:1.0.20+)Add ability to sell directly from Knapsacks(completed-1-24-15:1.0.20+)Add Creative Restrictions on Knapsacks(completed-1-24-15:1.0.20+)Add Support to stop Hot-bar Swapping(completed-1-24-15:1.0.20+)Add ability to exclude a preferred item(filling first and/or over-flow)Fix when players are allowed to drop Knapsacks(partial:1.0.16a)- Add option to Auto-Fill Stashed Knapsacks (logical?)
Add separate Knapsack Inventories for Creative and Survival(restrictive:1.0.20+)Add option to restrict use of Knapsack in Creative(more restrictive:1.0.16-1.0.20)World Exclusions, Global and Per Sack(completed-10-20-14:1.0.12+)Player Sack Expiry and Global Auto Clean(completed-10-19-14:1.0.12+)Death Control(completed-10-10-14:1.0.11+)Knapsack stashing enhancements(completed-12-24-14:1.0.18+)Right-Click Knapsack to Open it, same Inv. GUI(completed-10-21-14:1.0.12+)Knapsack Auto-Fill (100%)(completed-11-15-14:1.0.12+)Update with general console cmds(completed-11-15-14:1.0.12+)Migration Manager for Upgrades(completed-11-15-14:1.0.12+)- Complete Thieving Features (stalled)
- Knapsack Upgrades (stalled)
- Complete Realism Features (in-progress)
Sharing Features(completed-10-12-14:1.0.11+)Add Knapsack Recovery System(completed: 2-5-15:10.020)
Supports when "deathsacks" is disabled and players do not return
for their Knapsacksor some other freakish event occurred where player might lose Knapsack
- Add Share Items and Items Manager for Shares
- Add Knapsack Eco System
- allow buying and selling of Knapsacks
- Add Knapsack Transformation Option for each Sack.
- Player finds it, they can transform the item into a Knapsack of said [size]
Resource Pack for Knapsack Icons(completed-10-18-14:1.0.12+)
Release Notes
- 7-21-13: First "private" release for my son and his cousins on private server
- 9-15-13: Added support for more commands
- 9-16-14: Took a long business trip and no work was done...
- 9-28-14: Revamped most methods and functionality; added SQL support and UUID support
- 10-18-14: Added Player Expiry/System Expiry see change log for 1.0.12)
- 10-20-14: Added World & Sack Exclusions see change log for 1.0.12)
- 11-10-14: Added Auto-Fill Functionality see change log for 1.0.12)
- 11-16-14: Release of 1.0.12 - Steroid Injected - see change log for 1.0.12)
- 11-18-14: Release of 1.0.14 - Steroid Patch - see change log for 1.0.14)
- 11-19-14: Release of 1.0.15a/16 - Steroid Injection- see change log for 1.0.16)
- 12-11-14: Release of 1.0.16d - Auto-Fill Injection - see change log for 1.0.16d)
- 12-12-14: Release of 1.0.17 - MC1.7.x & MC 1.8.x Injection - See change log for 1.0.17)
- 12-26-14: Release of 1.0.18 - MC1.7.x & MC 1.8.x Injection - See change log for 1.0.18)
- 12-29-14: Release of 1.0.19 - MC1.7.x & MC 1.8.x Injection - See change log for 1.0.19)
- 02-01-15: Release of 1.0.20 - Knapsack Int - Bukkit(1.7.10-) See change log for 1.0.20)
- 02-01-15: Release of 1.0.20 - Knapsack Int - Bukkit/Spigot(1.8.x) See change log for 1.0.20)
- 02-03-15: 1.0.21 - 2 Qik Bug Fixes - Bukkit(1.7.10-) See change log for 1.0.21)
- 02-03-15: 1.0.21 - 2 Qik Bug Fixes - Bukkit/Spigot(1.8.x) See change log for 1.0.21)
- 02-07-15: 1.0.22a - Bug Fixes - Bukkit(1.7.10-) See change log for 1.0.22a)
- 02-07-15: 1.0.22a - Bug Fixes - Bukkit/Spigot(1.8.x) See change log for 1.0.22a)
- 02-09-15: 1.0.23 - SQL Fix & Minor fixes - Bukkit(1.7.10-) See change log for 1.0.23)
- 02-09-15: 1.0.23 - SQL Fix & Minor fixes - Bukkit/Spigot(1.8.x) See change log for 1.0.23)
- 02-11-15: 1.0.24 - Misc Fixes / Adjs. - Bukkit(1.7.10-) See change log for 1.0.24)
- 02-11-15: 1.0.24 - Misc Fixes / Adjs. - Bukkit/Spigot(1.8.x) See change log for 1.0.24)
- 03-05-15: 1.0.25 - Misc Fixes / Adjs. - Bukkit(1.7.10-) See change log for 1.0.25)
- 03-05-15: 1.0.25 - Misc Fixes / Adjs. - Bukkit/Spigot(1.8.x) See change log for 1.0.25)
- 03-08-15: 1.0.26 - Misc Fixes / Adjs. - Bukkit(1.7.10-) See change log for 1.0.26)
- 03-08-15: 1.0.26 - Misc Fixes / Adjs. - Bukkit/Spigot(1.8.x) See change log for 1.0.26)
- 03-10-15: 1.0.27 - HOT INJECTION. - Bukkit(1.7.10-) See change log for 1.0.27)
- 03-10-15: 1.0.27 - HOT INJECTION - Bukkit/Spigot(1.8.x) See change log for 1.0.27)
- 05-06-15: 1.0.28 - Fixes/Recompilations - Bukkit/Spigot(1.7.10-) See change log for 1.0.28)
- 05-06-15: 1.0.28 - Fixes/Recompilations - Bukkit/Spigot(1.8.x) See change log for 1.0.28)
Dependencies
Versions 1.0.16d and below require Vault (1.4.x)
Versions 1.0.17 and above require either Vault 1.4.x or Vault 1.5.x depending on the MC API (bukkit or spigot/bukkit) you are using.
Need Help?
If you come across any bugs or issues or if you have any suggestions? Submit Issues and/or Suggestions Here
Wanna Donate?
Care to help keep Knapsacks alive! I could use a new coffee maker!!
@zrocweb
Thanks for your very detailed reply. However, I have added these permissions to the sharee:
knapsacks.touch knapsacks.share knapsacks.size.54 knapsacks.open.other knapsacks.see.other knapsacks.list.other knapsacks.see.other.anywhere
... then I shared a knapsack #2 with the sharee. But when the sharee tries to list id with:
/knapsack see OtherChris 2, he gets this message:
"You don't have permission to see stashed knapsacks".
He gets the message regardless of whether the knapsack is actually stashed or not. The only way that I can fix this is by adding the permission "knapsacks.see.*" which then allows him to see all of my knapsacks regardless of whether or not they are shared (clearly I don't want this!).
@chrisotherwise
Sure no worries!
Permissions you need to give, some are optional:
where
is size of the knapsack(s)That's pretty much all you need to assign, permission wise (most of these are in the different Knapsack Permissions Groups, but some are not as they may vary.
In terms of using the Knapsack Share Functionality, it's quite easy. Once a player has permission to share Knapsacks (primary node), they can add players using the command /ks share [id] add [player, player, ....] For all the share commands use /ks share
Then any player that was added to another players Knapsack can simply use the command /ks see [player] [id]. Note: ID is the Knapsackid or Knapsack Number the player is sharing.
Depending on the permissions the player who was granted share rights to the Knapsack, they will be able to view the shared Knapsack, but maybe not modify it. The see.other.anywhere node controls distance in how a shared player can view another players Knapsack. If the shared player does not have this node and the knapsack owner is not in the proximity of the player they shared player will not be able to open the shared knapsack. Most of the other nodes are pretty self explanatory as well as the functions married to them. There are a few other features with shares that you'll probably stumble across, like stashing and porting and knapsack linking/interface modes. Other than this, that's pretty much it. Of course it does go deeper than what I've explained above but this is the basics and generally what people use. I'll leave the cool stuff (deeper things) for you to find while using the shares!
Sorry, another question... Can you explain how sharing works? I've shared a knapsack with a friend but can't work out how he can access it. Please could you explain? I've had a look through the docs but can't find anything related to this at all.
Also, in one of our worlds (named "spawn") all players are getting the message "Not allowed to use Knapsacks in this world!" when they try to take *any* inventory-related action - even moving stuff around in their inv. Any ideas how I could stop this? All worlds other than this one are fine.
Thanks again.
@zachrywilsn
Hey! Yes is a good idea and is in the works now. Still finishing up some things and testing. Maybe in the next release, not sure when yet, though. I can tell you that there will be a GUI involved that will help in the aid of config rather than having to use the yml by itself as the config (of course you can do either). Additionally, the eoc command (/ks buy, /ks sell) will be included. Sorting through some things on the auction piece to make it not only cool, but optimum as well logical!! Stay posted!
"Add Knapsack Eco System allow buying and selling of Knapsacks"
would like to see this similar to Auction plugin. Add the sack for sale with a price then people can maybe do /KS playershops This would let them hover over the sacks for sale showing the price. If you click on the sack it would show what is inside of that sack. :) good idea?
Also would like to see a way for players to buy the sacks via command. /ks buy <packsize>
a config would be used for pricing.
@zrocweb
wow, thanks for your amazingly quick reply!
Allocating to rank by size will do me just fine, thanks!
@chrisotherwise
Hey Chris! Thanks and your welcome! glad you like it!
answer to your first question regarding the ability to limit a players number of Knapsacks allowed to Craft based on rank. Short and sweet. No there is nothing of specific to rankings, yet. However you can limit the number of Knapsacks per Knapsack that are allowed to be crafted as well as limit based on size (permissions). This is not exactly what I think you were asking but might serve a small part in your cure. There are permissions for each size Knapsack as well!
Regarding your second question. The max: setting, per each Knapsack (sack) is the total number of Knapsacks any given player may craft or hold of that Knapsack, period.
Let me know if you have any more questions.
Hi,
Thanks for this great plugin, which will soon completely replace Virtualpack on our server. I do have one question about the config:
- I would like to be able to allow different ranks of player to create different numbers of knapsacks - so a beginning user can craft only 1, but a long-time player can craft (say) 20. Is this possible? I can't find any permission node related to this type of setting?
Also, please could you tell me what the "max:" parameter is in the Knapsack definition section of the config? - I couldn't see any definition of it in the docs.
Many thanks for your help,
Chris.
Getting a warning: (code removed from post)
.... and an error: (code removed from post)
Spigot is updated to the latest. using the latest permissionEx
Hey. Sorry about the delay in response here. I only check the curse sites know and then as I use the main project sites for all issues, etc.
Can you tell me anything about what you or the player was doing prior to the error and/or warning. I know what the issue is and it's corrected in 1.0.28 (not yet released).
@kirby456
Kiryby, Sounds good man!
In terms of the interface link with a chest and accessing it from far away. Hmm. interesting concept.. Will give it some thought, I like it. Would make chest shops easier to manage as well without having to actually go back to that chest/shop to re-fill if that is the style of that chest/shop..
As for the interface functionality.. It's actually pretty easy once you test and use it a few times. I tried to make it as easy as possible. As for the video. Yeah I am working on a mini-series of all the functions of the complete plugin as videos so people can get a better feel for it rather than all the reading.
However, until those are completed allow me to briefly describe to you the interface (have you read the interface project page?)
The purpose of the Interface is to allow players to use their Knapsacks like it was part of the player (as it actually is and should be). However there is no direct way to do that in Minecraft because of the inventory limitations. So this is how the Knapsack Interface and Link was born.
Let's say you have one Knapsack (size 54) and you have a few chests in your house as well as your inventory (player) is completely full. Rather than having to move stuff from your inventory to a chest or to a Knapsack, you can interface your Knapsack directly with any of the chests. There are several ways to do so. One is the most easiest and requires issuing command /ks sackmode with the Knapsack in-hand. Once you do this you will turn you Knapsack into your Player Inventory and it's accessible as if it was your inventory to anything other storage container you open, chest, furnace, etc...
The second method is to actually create a Knapsack Link to either one-side of a double chest or to a single chest. Using the blaze rod (configurable), issue command /ks link. Doing so will put your blaze rod into Link mode and then all you do is punch all the chests and other blocks that serve as storage containers and Knapsack Links are automatically created for you to those blocks/chest, etc... Then whenever you want to access that chest with your Knapsack, put the Knapsack of choice in-hand and use the Knapsack on the block/chests,etc... and your Knapsack is now in sackmode, again it becomes your player inventory and you can manage it's inventory directly with the chest, furnace, workbench, etc...
Note: There are permissions required for using links, creating links as well as using the manual /ks sackmode command. The manual command was created to allow players the options of interfacing their Knapsacks with their own chests, etc... when they didn't have access to create and/or use Knapsack Links.
Read the Interface Page a little more and I think you'll understand it based on what I explained here as well as the page itself. If not, let me know and I'll try to help you (can hop on your server, etc..)
Later.
@zrocweb
Sweet :) Thanks for a replay! That would be awesome if it works out great. Would you mind if I suggest another thing? Can you make it so the Knapack can access a linked chest if the owner locks the chest with Lockette (or any other lock plugins) so that other peps can't access the owners chest with the Knapsack but they can use the knapsack interface still. That would be very useful if you're very far away from your chest and you can just access it with a knapsack. Like I said before, the knapsack can access the chest if the knapsack is empty - there's nothing inside the knapsack - and you must be the owner of the chest. You can add a command that enables this option that allows you to do so. If this option is disable, you can't access the chest but you can still use the interface. I'm sorry if I suggested the feature that it's already made. I still don't understand the interface feature all the way. It's kinda confusing. You could make a video (or someone else could if they want to) that explains the interface feature if you want to. That would be helpful.
Thanks and your welcome :)
@kirby456
Hey Kirby. Yeah, I know these types of plugins are unique in themselves. The principal behind the auto-fill is to be able to automatically collect the items on the ground in an orderly fashion. However, because of these plugins, the items never actually hit the ground and are added to the players inventory immediately upon breaking and/or a percentage of the broken block spread out. With out direct interfacing with said plugins API (most don't have one), I will have to re-write the auto-fills to intercept player inventory additions as well. It could get a little hairy but I am working on it. Not sure on the release date of this though as it will require extensive testing to avoid major bugs and a ton up release updates.
We, knightsoftheblock.com, run the same plugin on our prison server and are probably going to be taking it off-line due to the popularity of the Knapsacks and the auto-fill AI. With the Auto-Fill, players actually pick-up the items faster than than they would naturally and if your using such plugins (Auto-Pickup, etc..) to avoid players from stealing other players drops, you may want to test it without these plugins, using Knapsacks auto-fill. It's quite robust in itself.
Other than that, I can't tell you anything else until I make some major changes and test and release. I can keep ya posted on targeted releases of such if you want.
Thanks..
Can you please support the plugins that is made to make the blocks go directly to your inventory when you destroy it? There's one that is called The Auto-Pickup plugin. When I destroy the blocks with that kind of plugin installed, it doesn't go directly to the knapsack even though there's a -first flag on the knapsack and I also set a preferred item that will only go to my knapsack, but the blocks will go into my knapsack when my inventory is full. I tested it without the plugin installed and it works fine - the preferred blocks goes directly to my inventory. That would be great if it's possible to do so :) Only thing I can say is good luck!
HOT INJECTION UPDATE: 1.0.27. Please see injection change log for fixes from 1.0.26.
@zrocweb
THANK you for the quick reply!
I'll have to try it out!
@omgGrim
Hey! Upgrades are in the works and what basically will happen is the server/player will have option to upgrade the current Knapsack into a completely new/next size or upgrade as in fix the current Knapsack if it's damaged which is another option being married with upgrades to increase usage as well as longevity of them;- more life like...
And currently there is nothing for that now.
As for the command to open a Knapsack, yes there is. You don't have to craft them at all. could just use a "give" command and they would get them. Command-wise, /ks [id] is the command to open said Knapsack. Each Knapsack gets an "ID", in the lore of the Knapsack in inventory you will see a tilde () next to the word Knapsack. This is the id, so if the player has 2 Knapsacks and wants to open Knapsack 2, command would be "/ks 2". Permission is needed for this and it's knapsacks.see.self (which basically allows the player to see/use a Knapsack regardless of it being "stashed" in a chest in the player home or where ever (if stashing is allowed).
Knapsacks in general are NOT ALLOWED to be dropped unless a player happened to pickup another players Knapsack when that other player died. If you are the player and you have 2 Knapsacks, you WILL NOT BE ABLE TO DROP any of them outside of "stashing" them in a chest, or another Knapsack.
I hope this answered your questions? If not or it lead to more questions just shout !!!
I want to make it so that each rank higher has a bigger backpack. Is this possible with a few config changes etc.
Also, is there a command way to open the backpack so instead of players crafting the backpack? And if say the player has a lower rank if they try to craft the next rank backpack will it work or just deny them? Or is there are command that will give the player a backpack but not let them be able to drop it or give it away?
[Sorry I haven't really read through the description carefully!]
@Astemus
Astemus. Hey man 1.0.25 is released (pending approval, so use the link in the upper/middle of this page to download 1.0.25).
Is it saying the the Knapsacks already exist or aren't lost....
To help you and your players, you may have to issue /ks dropdays [id] [player] [10] to all affected player knapsacks. Depending on how many players your having issues with it may be easier to use sqllite browser to perform a mass sql update to the db. If your not familiar with it, pm and I will shoot you my email address and you can send me your DB and I'll to it for you and send back.
Let me know man. Happy to come on your server or beta server if you want and help you troubleshoot. Multiinv should not affect this, I believe as I think I execute everything before and after it does so it doesn't grab them if it shouldn't...
@zrocweb
Yeah, for some reason the recover and getsacks commands don't seem to work in those situations. It always says that the bags already exist. It may have something to do with multiinv, because it's managing the inventory outside the world/userdata folder. Unrelated example, I've had issues with ender chests opening different instances of the ender chest with various plugins depending on how they hook into the inventory.
I haven't tried without multiinv, since it's not really something I can remove on the live server :) But I still haven't had the issue come up with any users, so it hasn't been very high on my list of things to investigate... so don't put it too high on yours.
I'll be waiting for the update!