Bukkit

Changes in this update:

v0.192

• Better Spout checks on the Listeners
• Minor edits to the internal LogBlockQuestioner

v0.191

• Bows are now considered tools, so enchantments and durability will be appropriately saved.
  • Sorry for not catching this earlier in regards to durability. (Maybe it sorta was working...?)

v0.19

• Full right-click support for chest access
• Potions now stack appropriately when using the command to take them from the item pool
• Right clicking the link sign now goes to the previous page. Should make navigating the chest pages a bit nicer.
  • Forwarding the page is still left click either the sign or the chest. This should allow for some consistency in that left goes forward and right goes backward.
• Chest access re-population occurs on a 1-tick interval, instead of the 5-tick. Changes made to chests should now be ever so slightly faster.
  • IF this is an issue, please let me know.
• Adding ALL the permission nodes (or a lot at the very least)
  • KarmicShare.commands.list : Allows user to use the command, /ks list
  • KarmicShare.commands.value : Allows user to use the command to view multipliers, /ks value
  • KarmicShare.group.* : Allows users access to all group commands
    • KarmicShare.group.create : Allows user to create groups
    • KarmicShare.group.add : Allows user to add players to their groups
    • KarmicShare.group.remove : Allows user to remove players from their groups
    • KarmicShare.group.leave : Allows user to leave their groups
  • KarmicShare.admin.*: Allows admin to access to all admin commands
    • KarmicShare.admin.add : Allows admin to add generated items to item pool
    • KarmicShare.admin.reset : Allows admin to reset player's karma
    • KarmicShare.admin.set : Allows admin to set a player's karma
    • KarmicShare.admin.drain : Allows admin to drain the item pool
    • KarmicShare.admin.reload : Allows admin to reload plugin
    • KarmicShare.admin.group.* : Allows admin access to all group admin commands
      • KarmicShare.admin.group.create : Allows admin to create groups
      • KarmicShare.admin.group.delete : Allows admin to delete groups
      • KarmicShare.admin.group.add : Allows admin to force add players to groups
      • KarmicShare.admin.group.remove : Allows admin to force remove players from groups

These permissions were added to have more fine control over what players had access to. For instance, you would probably want mods the ability to force add players to a group, but not access to the drain command. Or, maybe you want to hide the command-based list function from users to persuade them to use the chests. Maybe you want players to add and create groups, but not to remove other players. Etc, etc.

Please adjust your permissions accordingly

KarmicShare.admin has been replace with the modular permission nodes. For a better list, as to how its supposed to work, look on the Commands and Permissions page.

v0.18

• Proper PEX support.
  • Sorry, apparently Vault was getting first dibs when checking permission. Now, Vault is second if PEX is detected. This should fix permission errors with PEX and Vault.
• Changed group commands to support multiple users:
  • /ks group add <groupname> <player> [player2]...
  • /ks group remove <groupname> <player> [player2]...
  • /ks group leave <group> [group2] ...
  • /ks admin group add <group> <player> [player2] ...
  • /ks admin group remove <group> <player> [player2] ...
• Added more defaults for items thanks to @holsamoht

v0.17

• Chests now display the stacks of the items rather than a singular item
  • Linked chests now behave a lot like regular Minecraft chests. Interactions should now be much faster and enjoyable.
• The /ks list command now only shows items for the global group rather than all the groups.
• New permission nodes specifically for the chat commands /ks give and /ks take. Please update your permissions accordingly.
  • Respective nodes are: KarmicShare.commands.give and KarmicShare.commands.take
  • Please note, these are ONLY for chat commands. Not needed for chest access. However, you still need the main command, KarmicShare.give / KarmicShare.take to either give/take. Much like how chests enable viewing, but you still need the respective permissions to do anything.

v0.16

• Cleanup task occurs every minute and is much more concise of a query.
• Now check against the impossible, rather than assume that the impossible is impossible.
  • Basically, rather than only removing entries if the amount equals 0, remove entries if they're zero or negative.
• Should have fixed dupe bugs on chest access.
  • Shift clicks may or may not still be an issue....
• The ignore permission nodes are now default to false, and thus must be explicitly added.

v0.15

• Critical update: fixed typos on queries.

v0.14

• Initial group support
  • Players can create and add people to groups.
    • When adding players to a group, if no group is specified, it will use your main group (if you are in a group), which is the first group listed when using /ks.
  • Admin commands to manage/force groups and membership.
  • Chest support for groups.
  • Due to sign line limitations, group names must be at or less than 15 characters, alphanumeric, no spaces.
• Chest link signs have been modified. You must put the [KarmicShare] tag on the second line, or it will NOT be detected.
  • To link a chest to a group, put the group name in the first line. You may colorize it / or use caps.
  • Due to the new group system, current signs will need to be remade.
• Fixed a critical bug regarding enchanted items and chest access.
• Added a cleaner thread, in the event that an item's amount hits 0 or a negative number. This does not ordinarily happen, and it probably only occurred during testing. However, just in case, this cleanup task occurs every hour only for erroneous item entries. So, all in all, it probably isn't necessary unless the SQLite database gets mucked up from an external source.
• Drain, reset, and other admin commands now ask for confirmation (if you're in-game. Console bypasses it.), thanks to DiddiZ's LogBlockQuestioner.
• Added new permission nodes, all of which default to op:
  • KarmicShare.ignore.karma - Completely ignores the karma system for the player. Player's karma does not change.
  • KarmicShare.ignore.group - Player is treated as if they are in the group, even if they're not. Thus, they're in "all" groups essentially.
  • KarmicShare.ignore.* - has the above nodes enabled.

Please note, the item table needs to be rebuilt due to database schema changes. While I have repeatedly tested the updater for tables of v0.13 (and thus supports any other previous versions), if for whatever reason it isn't able to smoothly transfer your item database, then I can only suggest removing the database file and starting anew. Once again though, I have tested it and it ought to work just fine. It may take an extra second when enabling on update to move stuff over into the new table, but it ought to be rather quick.

v0.13

CRITICAL : Fixed bug on wall sign breaking saying no permission. When moving stuff around, I forgot the vital check to see if it was even one of the plugin signs and not a generic sign that I shouldn't care about. VERY SORRY ABOUT THIS. D:

v0.12

• Fixed shift-click from linked chest to player inventory.
• Made the item re-population occur twice as fast.
  • If item re-population does not occur, and you know the item still exists in the pool, please let me know. It takes 5 ticks now before it adds the item back to the chest, so long as it exists, versus the 10 ticks in previous versions. I don't believe this should be an issue, especially considering the shift-click task on the player side is set to only a 1 tick delay. I'll keep testing and see if 1 tick for the chest is alright or not.
• Updated version to 0.12

v0.11

• Shift-click from chest to inventory seems to be bugged. Currently disabled until ghost item issue is fixed.
• When using /ks version to show current config, chests state is given now.
• Updated version to 0.11

v0.1

• Physical chest support :D
  • To make a chest linked to the item pool, just create a wall sign above the chest with "[KarmicShare]" (no quotations).
  • Or place a chest under a sign that has been detected and it will activate.
  • To cycle through the item pool using chests, either left click the chest or left/right click the sign. The page number will change appropriately.
  • Using chests require the KarmicShare.chest permission node.
  • Creation/Destruction of [KarmicShare] signs require the KarmicShare.sign permission node.
  • Signs/chests that are destroyed do NOT drop items from the item pool. So, they're safe to destroy.
  • Items in chests only have a stack size of 1. Thus, each item is a representation of a unique item in the item pool. When an item is taken out, it is automatically repopulated if there is still more in the pool.
  • Right click has been disabled for KarmicShare chests due to a ghost item bug. To ensure that users don't encounter such issues, right click events are cancelled/denied.
  • Chests are enabled by default. To disable them, make sure that you set chests to false in the config.yml before the plugin is enabled.
  • Due to a weird dupe bug, that shouldn't happen, signs cannot be placed next to existing, verified [KarmicShare] signs.
  • Item edits are reflected in the item cache for the command-based version of item-lists. So, everything should be in sync.
• Per-item karma has potion support.
• Vault support for permissions.
• Generic cleanup and edits on minor sections of code.
• Changed version number to 0.1

Important notes: If you want to use chests, you NEED to have the SpoutPlugin on the server side. If you don't, then you cannot use chests at all. This is vital as there is no base Bukkit for me to get the individual clicks and interactions in an inventory at the moment.

Delayed update due to working on a custom jail plugin solution for my server.

If you encounter any issues, please don't hesitate to create a ticket.

• Using admin command /ks admin add <item> ... does not allow for item name like the user's version of take /ks take <item name>. May or may not bother with this... Perhaps in the future.It can parse the name if given it as defined in Bukkit's Material class, but not in KarmicShare's normalized way.
• Initial per-item karma defaults are still quite limited...