Knapsacks-v1.0.22a-mc_bukkit_1.7.10.x

Details

  • Filename
    Knapsacks-v1.0.22a-Bukkit_1_7_10.jar
  • Uploaded by
  • Uploaded
    Feb 7, 2015
  • Size
    414.14 KB
  • Downloads
    219
  • MD5
    77c8cbd714d24cb470fc74c0396b5136

Supported Bukkit Versions

  • CB 1.7.9-R0.2
  • CB 1.7.9-R0.1

Changelog

Quick bug fixes from recent release changes..Sorry!



Changes from 1.0.20/21 - 1.0.22 (these changes cover both Bukkit-1.7.10 and Spigot/Bukkit - 1.8.x)

MAKE SURE YOU GRAB THE RIGHT BUILD FOR YOUR SERVER


Upgrading? Just stop your server, delete old (.jar) version, drop this version in plugins folder and restart server


  • CRITICAL: Update provides support for Minecraft Player Name Changes. Knapsacks didn't need much as its foundation was build on UUID's, but needed a few tweaks!
    • Player Knapsack migrations are performed when the player logs in for the first time with a new name.
    • After a player has logged in and is migrated all should have went well. However, in the event there are any issues with the players stashed Knapsacks, issue command (op only) (/ks sconvert [player])

  • Added new (undocumented command) (/ks dropdays [days]).
    • This will allow an admin or op to edit the age of a players Knapsack Drop Days where a Knapsack is potentially being detected as unrecoverable. By simply add a day or number of days (defaults to the current date), a player should be able to initiate Knapsack Recovery without any further issues. This is a Fail-Safe and is to be used with EXTREME CAUTION.
      • Example: /ks dropsdays 3 tigerwoods -30 - sets the tigerwoods knapsack3 for thirty days prior to the current date.
      • Example: /ks dropsdays 3 tigerwoods 30 - sets the tigerwoods knapsack3 for thirty days into the future from the current date.
        • Setting a players knapsack back in time will have adverse effects, depending on the number of days back. Generally speaking, always go forward to allow the player ample time to do the recovery if you are not doing it for them while they are online.
  • Added new command (/ks recover). Recover can be used in the event a player loses a Knapsack or for whatever reason the Knapsack(spawn egg) disappears from a players inventory. There are only a few situations where this still might take place (not go to detail these to avoid players from doing it). Situations on losing and or spawning a monster egg are more restrictive now and they just don't happen!
    • 3 New permissions to accompany the recover command:
      • (knapsacks.recover.self) : Player must have this to use the recover command
      • (knapsacks.recover.other) : Allows a player to attempt recovery for another player. The other player must be on-line for recovery to regenerate the Knapsack!
      • (knapsacks.recover.age.exempt) : Allows a player to be exempt from the Min and Max Age of lost/dropped Knapsacks, if unlimited age is off(false).
    • Configuration section:
      • KnapsackRecovery:
        • Enabled: true
        • NotInWorlds: hub
        • UnlimitedAge: false
        • MinAge: 0
        • MaxAge: 18
          Recovery configuration
EnabledTurn recovery system on or off
NotInWorldsEnter world names, separated by commas here to limit a world from performing a Knapsack recovery while the player is in that world!
UnlimitedAgeSetting this "true" will allow player to recover a Knapsack regardless of when it was dropped or lost
MinAgeIn days and setting this to 0(zero) will allow a player to recover a Knapsack immediately after losing it.
MaxAgeIn days and will allow a player to recover a lost Knapsack up to and including this number of days since it was dropped or lost



  • Enhanced all Knapsack dropping and stash tracking to coincide support for recovery of Knapsacks. Especially for Non-Owner Knapsack dropping, players that don't have the (knapsacks.keepondeath) permission and drop their Knapsacks when they die and never go back for them or they burned up in lava when they died.
    • Never fear, that Knapsack is still alive!
    • The player can use the /ks recover [id] to retrieve that Knapsack should such an event like above takes place, or any other situation where the Knapsack just disappeared!
    • NOTE: There are limitations to this and the system will auto-detect weather the Knapsack is recoverable or not. Newly Crafted Knapsack (not owned) ARE NOT Recoverable!!
    • If a player attempts to recover a Knapsack that is excluded (NotInWorlds) from recovery they will not be able to recover it while in that world. Just because a player had the Knapsack while in that world does not mean they will be able to recover it should they die or lose it...
  • Fixed right clicking a Knapsack with a Knapsack open did not allow you to open it (it should). Issue was cause from a previous upgrade to stashing strategies.
  • Fixed when stashing a Knapsack in a container that is NOT DISALLOWED (was allowed) and then server DISALLOWS (restricting) the container
    • The player was not able to remove or de-stash the previously stashed Knapsack. All stashed Knapsacks should be able to be de-stashed, if the player has the respective permissions.
  • Fixed issue with materials not being as they previously were, during stashes and other item and material testing, specific to Knapsacks to avoid console error spamming when testing non-Knapsack materials and items (jacked up sword for example with mega lore, etc...)
  • Tweaked spawn egg events to trap up to 99.98% of egg events specific to Knapsack Materials (what you have configured in the Knapsack Section of the configuration.
  • Fixed issues when in inventory and you right clicked another Knapsack, players sometimes would receive the "You don not have permission to Stash Knapsacks" message
  • Changed Creative Restrictions: Creative is now 100% Restrictive. When a player goes into Creative Mode, all Knapsacks the player is carrying will be saved, fills turned off, and removed from the players inventory.
    • When the player exits creative mode all saved Knapsacks the player was carrying will be restored back to the player.
      • This is a temporary thing until full support for Creative vs Non-Creative Knapsacks is implemented, if requested. Don't really see a need for Knapsacks in creative mode though??
  • Fixed messaging when a player has a fill that is not allow in a "NotInWorlds" of a Sack or in global "WorldExclusions" settings. Players will be informed if they are about to pickup an items that is determined for a fill sack that is restricted from world use (including filling). The item will revert to the player if the player has room.

Please Submit a Ticket if you find something!