EDIT: improved descriptions, made the post prettier.
EDIT: still working on improved descriptions.
Hey thanks man. I'm sorry I missed you post on Edolas ,but there where many results when searching for 'server plugin'.
First question you have to answer for yourself is: how complex should the plug in get?
So I'm now going to point out what I wish in detail.
things I would like to see:
-plugin internal rank system: e.g. *admin *veteran *normal *guest
-group/party system, maybe with group intern rank system (to better handle the following things)
-area protection (destroy and place; if possible fire, explosions, liquids)
-locked chests and doors (no ender chests!)
-locked levers, buttons and pressure plates (if possible)
-locked devices like: crafting tables, anvils, cauldrons, ... (not necessarily)
So next I'm going to explain the different protection, lock functionality's and administration options in detail.
Ranks:
I suppose you know what I mean here. So I'll keep it short.
Think about how complex and edible you want to do it. basics would be:
*admin:
--use 'server' on signs
--promote guests to normal players those veterans and those to admins.
--downgrade other admins...
--protection types: place, destroy, fire, explosions, liquids
*guest:
--no permissions. no block breaking or placing. kind of an adventure mode
*normal:
--lock things with signs (I would limit this in some way, e.g. 20signs/player)
--protect areas with sings (I would limit this in some way, e.g. 3properties with up to 10.000blocks in total/player)
--protection types: place and destroy
--create and maintain one group
*veteran:
--premium player with higher limits (e.g. 50signs/veteran and 5properties with up to 50.000blocks/veteran)
Groups:
This one is to better handle things if many players get access to a chest or anything else protected.
Instead of putting every players name on a protective sign you just put a groups name and all players belonging to the group get access.
You could also add an group internal hierarchy:
*leader:
--the one who found the group
--everything
*member
--gets access to all properties the group has access to
*premium
--is allowed to use the groups name as owner on protective signs
--destroy chest etc.. belonging to the group / remove properties belonging to the group
Locking:
I would use a sign based system. So attach a sign to the thing you want to lock, write the 'activation code' and it's done.
To lock buttons and other devices you can't attach a sigh to place the sign next to it, write the 'code' and then click on the device you want to lock.
Every locked thing has an owner, that can either be a player, a group or the server. Only the owner is able to destroy what ever is locked. Guests are allowed to use the locked device.
All of these will then display the 'owner' and have reserved the last line for 'guests'. Is should be possible to add more then one guest, this can be done with chat commands or by placing an additional sign next to the 'protective sign' as shown below; removing guests would work the same way. to display all guests right click on the sign and the last line will scroll through the list of guests or display the list via chat.
-Chests:
-Doors:
-Buttons, pressure plates and levers:
For all of them: once you successfully locked something there is a chat message telling you so.
Protected areas:
this one is more complex, as your not locking a single block but an large area that needs to be defined.
So I would like to see btw
stakes involved in this. I suggest to surround an area with stakes and strings then putting a sign next to one of the stakes and write the 'activation code' (similar to the one we already know) on it to complete the process.
To keep things easy I would allow only squares. Next problem is the height. To declare the height of the protected are you use the second line telling how deep and how tall the are shell go (remember the layer the stakes are placed in is the 0 layer).
Next you can define the type of protection ; at the moment I think of 5 different protection types although only the first to are realy important:
-block destruction
-block placement
-fire
-explosions
-liquids (water and lava destroying things)
The bricks show the frame of the protected area, they all belong to the protected area
the left sign is the sign to create the protected area. the right one is to give more players or groups permission to 'use' the protected area; I suggest to destroy this sign when changes are applied.
this is how the creator sign looks after creating.
So that's it for now. Tell me if that's what you wanted to know, and ask if there are questions left.