Pull request to add group support and singleton chest

[basicmark]

Hey Mtihc,

Don't worry if this is to late, I should have sent this request a while back.

I think other uses of treasurechest might find these enchantments useful, the main drive behind them is to allow tchest to be used in events and reduce the setup time by being able to create groups of chests all of which can be controlled via a single command.

Singleton chest support was added for events as well to keep the incentive for players to find a treasure 1st and be able to restrict the number of treasure items in a map globally rather then per-player.

Cheers,

basicmark

[Mtihc]

I'm going to merge soon. I had a good look at every commit. I am impressed that you managed to implement this so nicely. I also like to think that my code is very readable :smile:

[Mtihc]

I made some notes that I would like to share with you. Mostly small, stupid things. Except for the last note.

• Singleton is a confusing name, because it has nothing to do with the Singleton design pattern. I don't have an alternative yet.
• I get a compile error for some reason. I must typecast integers using (Integer) instead of (int). Easy fix.
• Group commands will be nested under /tchest group ... Still need a thorough look over the group commands.
• set-single command needs extra message, when singleton value changed. Instead of just "Treasure contents updated"
• Why no forget and rewards for singleton treasures? (see TreasureManager 358) I guess because the rewards would be activated every time a player opens the inventory. If we use the forget-time somehow, then we know who opened it first... and we can give rewards. Not sure how yet, exactly.