Description
Info
What is it?
PlantainDKP is an addon to manage in-game DKP, using a custom system named "Symphony". It was designed by the GM and Officers of the Behind My Camel Guild on EU-Kul Tiras and it has been in use since early Burning Crusade days.
It's one of the fairest DKP systems I have used (in my opinion, of course). It is designed with simplicity and speed in mind, and requires close to no maintenance to operate over hundreds of raids!
PlantainDKP is a fork of BananaDKP.
How does it work?
The Raid Leader must run the addon in server mode. The clients can (but it's not mandatory) to run the addon in client mode, syncing with the server (raid leader).
You gain DKP based on your time in raids, regardless of boss kills or not.
When you loot an item, a static 25% of your current DKP is subtracted from your total DKP, and is lost forever. So if you have 10 DKP and loot an item, you drop to 7.5 DKP. Obviously, since item prices are percentages, you can never go below 0 DKP.
Attendance is calculated by default over 45 hours. If your attendance drops below 60%, your DKP value will start to diminish. 1 DKP is worth 100% of its value at 60%, and 10% at 0% attendance. So if you've joined no raids for 3 weeks and have 10 DKP, it'll only be worth a total of 1 DKP. When your attendance increases, again, it will worth it's full value again.
If the raid is full, but you are still available for raiding, you can whisper the raid leader "sitout", and let him know that you are ready to step in at any time. If you do this, you will get 1 DKP per hour as if you were in the raid.
DKP is tracked per-character, so if you go to a raid with another toon, you will have a separate pool of DKP for that character, and will start out at 0.
The "sitout" list is pretty much static. There are no AFK or logon checks. You can stay logged off, on an ALT or whatever and you are still tracked as if you were in the raid.
It's up to the Guild Rules / Raid Leader / Officers to enforce penalties (or whatever) for people placing themselves on the sitout list and not being available for raid. The Raid Leader can remove people from the sitout list manually with the /pdkp sitout <player> command.
Why PDKP?
Since the author of BananaDKP stopped playing the game and I didn't want to "polute" the main code of it, I decided to fork and maintain my own copy, tailored to my current guild's needs.
All BananaDKP changes are integrated in PlantainDKP every time it gets updated.
Changes over BananaDKP.
- Food and Flask modifiers are turned off. In this day of guilds providing both feasts and flasks, the modifier doesn't really make sense 99% of the cases. Thus people on stand-by can gain the same amount of DKP as the ones active in raid.
- Added a few other commands
- Updated ignored loot list
- etc.
Why "Plantain"?
Quote from Wikipedia:Plantain (pronounced /ˈplæntɨn/; also UK: /ˈplɑːntɨn/ or US: /plænˈteɪn/) is the common name for herbaceous plants of the genus Musa.
The fruit they produce is generally used for cooking, in contrast to the soft, sweet banana (which is sometimes referred to as the dessert banana). There is no formal botanical distinction between bananas and plantains, and the use of either term is based purely on how the fruits are consumed.
Musa is one of three genera in the family Musaceae; it includes bananas and plantains.
Backward Compatibility
PDKP IS backwards compatible with BananaDKP.
PlantainDKP's command prefix is /pdkp, but /bdkp is also accepted.
If you are the raid leader (server) and you want to move from BananaDKP to PlantainDKP (while keeping attendance and dkp lists intact), rename (or copy) the BananaDKP.lua file to PlantainDKP.lua in the WTF\<account>\SavedVariables directory.
If you are currently running BananaDKP in client mode, you don't need to do anything special. You can still use BananaDKP to receive updates from the server without any modification. If you really want to change to PlantainDKP, you will only have to redo /bdkp role <raid leader> once you install PlantainDKP.
DO NOT ENABLE BOTH addons in the same time, as they use the same table name and it could blow up in your face!