cosmetics+ idea

[Plugin category]
mechanics

[suggested name]
Cosmetics+ (since it is pretty straight forward)

[why do i request this?]
well, my main reason to request this, is that the minecraft donation rules are getting changed, also so known as the EULA. this makes selling game-play affecting privileges/permissions for real money illegal. and a lot of owners of small servers are struggling now since they can't afford an expensive custom plugin or sponsors. and this will most likely mean the end of small servers. giving big servers the possibilty use custom plugins. making bukkit become less usefull. so i figured we need a simple and easy-to-use alternative. that small servers can use, too stay alive. the only real way is cosmetics (besides donator goal events which i will request in another post) since the other options, pay-to-join or sponsors are a bit odd.

[the idea]
well the idea is to make a easy-to-use all in one plugin that has the all the features possible with bukkit and the new EULA rules, features like.
- pets
- particle effects
- custom names
- hats
- other ideas maybe?
these features should be highly configurable so that servers can take an identity where they can offer unique cosmetics.
the features should be easily accessible by one command /cosmetics or short /cms, this should open a GUI menu that can be configured

[GUI]
in the config there should be an option to add a category with these settings
GUI categories:
         name: {name of the category shown in the GUI}
         menu icon: {item used for this category in the GUI}
         category: {should be pets, particle, names, hats}
also the categories should be sorted like they are sorted in the config
the GUI is the menu where players can activate there cosmetics an cosmetic can be in 3 states, not bought, on and off. also some cosmetics can only be activated if there is other cosmetic in use in that category, when this happens it will tell you in chat that you already a cosmetic of this type on.
[pets]
so for the pets part i think it must be highly configurable. but straight forward
there should be a config where they owner can add pets easily by simple settings for example
pets:
       name: {name of the pets in the GUI and other places}
       item: {item used in the GUI}
       category: {in which category this pet shows up in the GUI}
       type: {which mob it is}
       mount: {which mob it is mounting, optional}
       mount baby: {true or false, if the mount is a baby or not}
       mount attribute: {look at attribute}
       renameable: {should have these options false, true, permissions (only if the player has the                                      permissions), once (once the player has bought a rename he can only rename it                                once)}
       item: {optional if possible, which item the pet is holding}
       attribute: {for different types villagers, sheeps, zombies, wolf color, horses, slime size and cats,                           optional if possible}
       baby: {true or false, defines if the mob is a baby mob}
       *awaketime: {how long the pet can be awake, optional}
       *commands: {let your pet do funny tricks on command}
                command name: {the thing you have to say in chat inorder to trigger (no slash (/)                                                         required), this can have the variable {petname}m in order to let the pet                                               only reacting to his name}
                command reaction:
                            1: That tickles! {what a pet says in return, for example.}
                            2: Hihihi!
                            3: Stop it!
       *hunger: {although i am not really sure if this is allowed since it only takes an item away from                         a player instead of giving some one, the lower the hunger, the better.}
                 satisfaction: 40 {how much the hunger drops after eating food, max hunger 100}
                 food: {which items the pet eats}
                 appetite: 1 {how fast the hunger increases per minute}

* options marked with these are not required but are kinda cool ideas i had and maybe could be          added later

[particle effects]
so for the particle effects it is a bit more difficult to make configurable, but this is what i had in mind

particle effects:
             name: {name in the GUI or other spaces}
             item: {item used in the GUI}
             particle: {which type it is, there are a lot of types, for example                                                                              http://minecraft.gamepedia.com/Particles}
             color: {which color if firework}
             appearance: {always, or a variable (the variable should indicate how long it takes for the                                        animations to reset)}'
             type: {trial, above head, teleport and death should be an option}

*note that only one particle of every type can be active (not 2 death particles for example)

[custom names]
i know some of these features are included in other plugins, but as i said i think this plugin should be all in one, this is how i had the config in mind.

custom names:
          name: {name of the name-effect in the GUI}
          item: {item used in the GUI}
          patern: {these should be made using color codes and ^ signs, for which letter should be                                   colored, for example if your name is jake or semistro, and the partern &b^&a^ is                               used, it should look this, jake or semistro, if the patern is not long enough it will start                         at the beginning}
          animation: {no, sliding, patern (if patern is used you must configure the other paterns it                                       animates to)}
                            patern1:
                                        &b^^&a^^ {jake or semistro}
                            patern2:
                                        &b^ {jake or semistro}
                            patern3:
                                         &a^ {jake or semistro}
[hats]
so the hats are pretty straight forward

hats:
         name: {name of the hat in the GUI}
         item: {the item used in GUI}
         hat: {block used as hat}

[commands]
for players:
  /cosmetics or /cms (opens the GUI menu)
for admins:
 /cosmetics+ reload {reloads the plugins}
 /cosmetics+ off {unloads all the cosmetics of all players}

[permissions]
for players:
-cosmetics+.gui {allows to open the GUI with /cosmetics or /cms}
-cosmetics+.pet.name {allows the use of a certain pet}
-cosmetics+.particles.name {allows the use of a certain particle effect}
-cosmetics+.customname.name {allows the use of a certain name}
-cosmetics+.hat.name {allow the use of a certain hat}
-cosmetics+.pet.rename {the ability to reset your pet his name (permission get directly removed                                                after usage if renameable is set to "once")}
for admins:
-cosmetics+.reload {gives permission to the /cosmetics+ reload command}
-cosmetics+.off {gives permission to the /cosmetics+ off command}
-cosmetics+.* {gives all the cosmetics+ permissions}

[final words]
now i can understand that maybe you think this is all crazy and not a realistic plugin request, but i had the ideas in my head for a while and i thought, why not try it, since i am not a good programmer myself. it would be awesome if someone actually wants to work on this project. if so , i don't mind your taking the credits. as last, i want to know what you guys think. feel free to fill in the poll below