GrayRage
01-17-2004, 09:03 AM
Greetings mighty butt pirates of doom!
As many know, we have been working fevorishly on a Charter for DB in WoW. We determined that the guild should also have a UNIVERSAL CHarter which effected the guild in ALL games as well as a "code" or specific charter to each game. Much thought has already gone into both parts of this and now it's time for YOU all to also get a voice in! This is just a draft of the charter and will not be FINAL until we put it up on the website so here is your chance to help shape darkenbane!
We could have done this on one of the private forums, but not all members have access to all private boards so it must be done here.
Darkenbane Universal Charter
Summary:
Darkenbane is a Massively Multiplayer Online Gaming Guild which specializes in the area of PvP (player versus player). Membership to the guild is free, but has expectations of it's members in conduct and gameplay.
The guild is historically ruthless by nature to it's foes and has few friends. We offer no mercy to our enemies nor expect any in return. Those desiring to know and understand what a DB member is in a game should compare them to an carnivore that stalks sheep. The cold certainty of impending attack lurks as a companion to the Darkenbane member with fear riding along and lashing out at his intended victim. There is no mercy in his eyes, only blistering relentless death. Flee when they come for you...or die.
The Guild only will play as an organized unit in Online games that have a heavy involvment of PvP. For a game to be supported by Darkenbane, the game, it's guild leaders for that game and it's "Code" for that game must be approved by the Overlords (defined in a later section).
Changes to the Charter
This can only occur after all 5 sitting Overlords unanimously agree on a change.
Universal Guild Structure
As the Guild will be involved in more then one game, some with a large number of people, some not, it's important for a group of Leaders to oversee that any games supported by Darkenbane are being conducted properly by that division's officers. These individuals will be considered Overlords and have the following responsibilitites:
1) Approving a new game to be supported by DB. Approving the new game's initial leadership, officers and "Code" (a ruleset for the guild specific to that particular game). If this approval is reached, the game will be added to our forum list. The game will receive private forums and the guild in that game will be reognized as an authorized representative of Darkenbane.
2) Making additions or subtractions to the Universal Guild Charter which is a ruleset adhered to by Darkenbane across all games.
3) Removing Darkenbane Support from a game. This will take a unanamous vote.
4) Replacing a leadership structure of a supported game. This will take a unanmous vote and can only occur if the leadership of said game is violating the Charter and/or Code.
Overlord is a lifelong position, but has requirements as follows:
1) An Overlord cannot be inactive for more then a month. They MUST be active in the guild to maintain the position. If they become inactive as determined byt the other Elders, they can be voted out (with a unanamous vote of the remaining Elders.
2) Any Overlord found to have violated the guild Charter or a Game's Code, can be reviewed by the other Overlords for potential removal. This, again, will need a unanamous vote.
3) Overlords must be active in the guild for a period of at least 1 year before they can attain said position.
4) Overlords will be selected via a unanmous vote of the standing Overlords. 5 Overlords MUST be always sitting and active in the guild at all times. If one Overlord is removed and/or becomes inactive, then another MUST be chosen. If the remaining Overlords cannot decide upon (unanamously) a new person to fill the position, a Guild Vote will occur in whichever private board is the most active. The people who receive the most votes will have a "run off" election and the winner will be named as an Overlord.
5) One Overlord position will always be the website administrator (Meter presently).
Roster and Recruitment
There will be no universal roster or recruitment requirements across all games for Darkenbane. Instead, this will be specific to a particular game and must be addressed in that division's "Code" among other things.
Conduct
All Darkenbane members across all games will be required to follow our conduct requirments which involves the following:
1. Understanding anything you say or do on a public message board, chat room or game can and will be screen shotted and used against you.
2. If anything said by a member causes the guild embarassment, said member could fall under review for discipline. Such things include, but are not limited to the following:
a) Begging
b) Grovelling
c) Asking for mercy
d) Asking for a Truce
e) Making "deals" of non agression.
f) Generally acting stupid over time.
g) Hacking a supported game which actually alters the gameplay of said game.
h) Treason - Defined, but not limited to: Engaging in any act counter to the interests of the guild, posting private board information, giving out account information to non DBers, joining enemy guilds without being formally supported by the guild as a spy, attacking guild members in an agressive manner or giving any information deemed to be private in way shape or form to non guildmates.
i) Disloyalty - Threatening to quit the guild or actually quitting the guild. Attempting to join other guilds playing a supported game (without being supported as a spy).
j) Racism - Racist remarks more often then not (even when used as a goof) cause drama and annoy some people. As such, we are going to draw a line here and ask members NOT to utilize racist remarks or racism in any form of communication involving the guild. The level of discipline for a violation of this will range from DKP deductions, warnings and even removal if it warrants such action.
The division's "Code" should address conduct more specifically and subsequent disciplinary action. The Overlords may take action if the Division does not handle complaints against a member within a reasonble period of time. Decisions of the Elders will always overide that of any Division Leaders.
Special Operations
Darkenbane will always have a secret operations forum and group. This will be overseen by the Overlords and will admit only those necessary to study various vulnerabiltites of games, websites or other areas of interest to the guild. On this board, discussion and research will occur to determine how to utilize various tools to accomplish our goals and the necessity of using them. The Charter of the guild authorizes the Overlords to discuss and/or take whatever means necessary to ensure the success and power of the guild.
Darkenbane - WoW Code
Overview
This will be finalized after Blizzard annouces the type of servers it will offer. Things to consider are whether it will be team based and how we will deal with teamates that are not guildmates plus more that cannot be finalized until the server type is determined.
Changes to the Code
A change to The Code once it is finalized can only be done with a unanimous officer vote after an idea is presented. The vote must include at least 66% of all officers.
Guild Structure
The guild has several catagories of members which range from leadership to new recruit. Each catagory will be discussed in detail as well as their responsibilitites.
1. Leader (GM) - This person will be in charge of final decision for the guild. He should put controversial decisions to a guild or officer vote based on his discretion. He should uphold the Charter and Rules of the guild to the best of his abilities. He will make policy decisions, alliances and strategies for the guild. This person will be elected by the guild in an election once every 6 months on January 1 and June 1 of every year. A primary election will be held of all potential candidates (they must be nominated) and the top two people receiving votes will then be in a "run off" election. Each potential leader must name his officers BEFORE the election the primary. The number of officers will be based on the number of folks on the roster with 1 officer per 10 members not counting Meter who is an eternal officer in charge of the website. A GM can be removed by a 66% officer vote only with at least 75% of officers voting. The CURRENT GM in office must handle the election process and turn over power to a new GM if that comes to pass.
2. Officers - These folks will be named by the potential elected leader (prior to the election). He will pick 1 for every 10 people on the roster PRIOR to his election. An officer CANNOT be fired without a majority officer vote first (75% of officers must be involved in the vote). Only a CORE member (as defined below) can become a GM or Officer of the guild. Officers will have specific duties as follows:
a) Assistant GM - This person will take over GM position if the GM quits or get's booted. He will have similar duties as the GM and is in charge of the guild when the GM is not on. This person should be considered second in command of the guild.
b) Recruiting Officer - This person will be in charge of all things recruiting. He will abide the rules set forth for guild recruitment in this charter and will adminster the processing of all new folks as well as the board stuff involvoing them. This person willmake sure recruits meet all requirments of them and will be in charge of recruits until they achieve full membership status.
c) Adminstrative Officer - This person will be in charge of the DKP system, adjustments to it and monitoring. He or she will have to monitor the boards set up fro DKP and make adjustments as necessary and set forth in the DKP rules. Raid leaders and PvP leaders will also make additions to DKP and such, but the Admin officer will take care of disputes, adjustments and maintenance.
d) PvE Raid Leaders - These are in game leaders who will lead raids. A read leader will be responsible for taking roll call right when the event begins and keeping track of who won what loot. They will also give the loot out to the winners based on the DKP system. The number of raid leaders will be detemined by the remaining slots open for officers which is based on the roster.
e) PvP Raid Leaders - These will be the ONLY people who can issue DKP for a PvP raid. If they call a PvP raid, they have the authority to issue DKP based on guildlines set by the officers and GM to induce inflation in the DKP system and to encourage PvP.
f) Conduct Officer - This person will be in charge of dealing out discipline to those members who violate the DB code of conduct. Any incidents should mostly be referred to and handled by this person if at all possible. This refers to all sections which involve discplinary action versus a recruit, member or officer. Any complaints or issues involving conduct should be directed at this officer.
3. Members - These folks will make up the body of the guild. They have the protection of being a member and cannot be removed without a majority officer vote. They will be expected to follow the charter of the guild and the instructions of the officers. There are two types of members as follows:
a) Core - This person has been a member AND active in a given game for more then 6 months in Darkenbane. Additionally, he/she must be voted by a majority of the current officers into the "core" position after being nominated for the promotion by an officer. Only CORE members can ever become officers and/or the GM of the guild. A CORE member will be reduced to MEMBER status if he is inactive for more then a period of 3 months.
b) Member - This person has passed the requirements for moving up from recruit status. It's affords them the full benefits of membership in the guild and protection from arbitrarily being removed. A member can be placed on the "inactive" list if not active for then a period of 3 months. If they become "inactive" they can be reinstated at GM discretion upon request or might be required to go through the recruitment process again.
4. Recruits - These folks can be removed from recruitment at anytime by any officer. They will need to meet certain criteria set forth by the charter before becoming a recruit and then before moving up to member status.
Recruitment:
The guild should have 40 to 50 members online each primetime and/or 80 to 100 on the over all roster. If these criteria are not met and at the discretion of the leader, recruitment will open and new folks will be allowed to apply. A seperate public recruit board will be made for recruits to apply to the guild and where discussion of them will ensue. These are the requiremnts for new recruits:
1. Must meet level restriction requirment set forth by GM.
2. Must have 3 sponsers who are willing to put up their OWN membership on behalf of the recruit. These sponsers MUST be at the Member level or above. Members can sponser 1 recruit per month whilst CORE can sponser unlimited recruits.
3. Must maintain recruit status in good standing for 1 month.
4. Will begin as minus 10 DKP which will be distributed to the guild once their recruitment begins (10 divided by the number of current members). This number can change based on DKP conditions in game and will be GM discretion.
5. A recruit cannot receive ANY veto from a CORE member or above. If any CORE or above vetoes a recruit's status, the recruit will be required to have thos CORE member clear the veto before gaining admission to the guild.
Member conduct and discipline:
There are two types of discipline which willbe handed out to members as follows:
1. DKP penalty - This will be the penalty used by officers for minor infractions such as raid disruption, abuse to other members, failure to listen to instructions, failrue to PvP when it's called for ect. The penalties for infractions will be set by the GM and officers. These penalties can be appealed on the forums and pvertunred by the GM only. A 10 DKP penalty will be met out to anyone who quits the guild. The DKP will be distributed to the current members.
2. Removal - This will happen only after a member is brought on charges before the officers. A member can only be removed with a majority officer vote. Offenses for removal are:
a) Getting caught cheating - This allegation must be proved beyond a reasonble doubt. 1 single person witnessing a cheat is not sufficient as people are FALLABLE and so is the game. Additionally, a test for a bannable offense is if the member WOULD be banned from GAME if caught using the cheat. If a person would only be WARNED by a GM for using a cheat or exploit, it will then not be bannable in DB. Our standard will be the same as the GMs.
b) Treason: This will include the sharing of private board information, private channel information or anything that is considered "guild eyes only" with anyone NOT in the guild. This also will include any actions or conversations which are deemed to be hurtful or against the best interests of the guild.
c) Begging, grovelling, asking for mercy, making deals with non dbers to avoid PvP, saying stupid shit that get's screen capped and embarrases the guild. All of these are viable charges for a vote of removal. If not voted out, DKP penalty will be instituted.
d) Consistant disruption of the guild not limited to, but including: Abuse to other members, public flaming of the guild or it's members, constant whining or disruption. Any officer can bring charges against a person which willbe voted on to remove them.
Communication
Darkenbane will use the Teamspeak system. It is madatory for use of all members and will be our primary source of communication. In game guild chat will be used for frivolous general chat whilst TS will be more narrow. The following rules apply to Teamspeak useage:
1. In general, the channel should be limited to game related chat. When an event or PvP is NOT occurring, general chit chat is allowed, but it is recomended that folks do not over use it.
2. Do not ever talk over other people unless it is an emergency where a person will yell "CLEAR". Only push your button to talk if no one else is talking.
3. During events, everyone is to keep quiet unless they have vital information. No suggestions, no jabbering, no ideas, no thoughts, no opinions. TS during raids is used if you need a heal, need a mex broken or have some other VITAL information to convey to the event leader. The leader will call out target and instructions and everyone WILL follow those instructions without pause.
Loot Distribution:
We will utilize a DKP system to organize loot distrobution in the guild. The system will work as follows:
1. DKP is ONLY awarded if items from a raid are "bought" by someone. The price that person "pays" in DKP is split up among the people who helped the person get the item. Example: A Red Robe of Coolness drops off of the God of Underwear. It's price has been set at 10 DKP. Mindagmes buys it. He is deducted the 10 DKP which is split among the 20 DBers who attended the event giving them each .5 DKP.
2. Inflation: I believe inflation is necessary to reward long time members and keep newbs from getting gear over them. Newbs should have to earn DKP for a few eeks at least before they can get items over old timers. As such, folks should NOT be in the negative. To keep them OUT of the negative we will have DKP events for PvP that do NOT have outgoing DKP (no items paid for only DKP awarded to those who attend). This will basically reward anyone who attends and will be comparable reward to the same time spent on a mob.
3. Setting prices for items: I suspect that raid leaders will have to set the price on items as they drop. They can be adjusted later after discussion then set. We can do a monthly evalaualtion on prices of items. A message board will likely be set up for this purpose as I am sure it will have considerable debate.
This is how I envision it for a regular member:
- There is a link to see DKP after logging onto the website. They click on it and see the following:
1. Roster link - Show all members
2. Event Link - Show all events
- Roster Link: Shows All members with columns to the right. Each member's name will have a link. If u click on a member's name it will show their DKP history. All events attended, DKP earned and all dkp spent for which items. The colums next to each member's name should show:
1. Total CURRENT DKP
2. Total SPENT DKP
3. Total Earned DKP
Each Colum should be clickable to allow the list to be done by who has the most current DKP...who has spent the most or who has earned the most since day 1.
- Event Link: This link should show all events that have been entered with colums. Each event will be a link that will have detailed info about the event including the roster (who attended), what items dropped and who bought them. It should have how much DKP was awarded to each member (some members might earn more then others based on adjustments for rare classes, high levels ect). The colums should be as follows:
1. Date of the event
2. Amount of DKP awarded
Admins will obviously have more stuff. When an Admin logs on they will the links above, but also have the following links as well:
- Add a member: This will have blanks to fill out to add a person to the list. The blanks to fill out will be as follows:
1. Name (and other info like class ect)- Self Expanatory
2. Catagory - This will be complicated and involves DKP bonuses that we as leaders will set. Everyone in the beginning will be set as catagory 3 and will earn 100% DKP. Catagory 2 and 1 will be reserved for later use for perhaps recruits or lower level guys where they will earn 80 and 90% DKP respectively if they are placed in this catagory. Catagory 4 will be 110% DKP Catagory 5 120% and so on. This will allow us to reward folks who work on the website or do other funtions with higher DKP awards for their efforts. Also we can award rare classes...for example making clerics catagory 4 by default if we need clerics. This will basically be an easy way for us to have auto adjustments for better or more valuable members and reduced dkp for less valuable or folks who are lower level ect. This will allow level 55s to earn DKP...but not the same DKP as a level 65 who does alot more and it wille ncourage folks to make their characters powerful.
- Edit a member: Self expalnatory. Mostly will be used for changing category. But also for editing their DKP. Any entry for DKP will need to be logged by the system with who made the change and the date. If someone has their DKP changed it will show up in their DKP history as an addition or substration in DKP and should have the reason for this addition or subtraction.
- Add an event: This will allow an admin to add an event in the system. The following blanks will appear:
1. Name of event: Since the rewards for events are based off the loot, the event can be just typed in each time by an admin.
2. Date of event: There should be a drop down menu here so the date is not entered int he wrong format. Events will be stored by date so it's important this is entered correctly.
3. Date of Entry: Should be logged automatically by the system.
4. Roster for event: This should be a big blank area that will parse a /log showing all attendees. It will detect and enter all people who were presently from the log entered. At worst, a drop down menu with all members should be here and will allow an admin to select the names of each members who attended. Parsing would be nicer tho :) Course we are aussming they have logging and some kind of /who in WoW.
5. Gear awarded: This will be a drop down menu also listing all items already in the system. If the item is NOT in the system, an admin can then ENTER the item (and it's stats/info) with a cost for DKP.
6. Notes: This will be an area where an admin can enter misc info about the event.
- Edit an event: This link will bring up the full list of events. An event can then be clicked on and the following options are presented:
1. The ability to add or remove roster members. There will always be folks who were late that should be added or mistakes where people need to be removed.
2. The ability to edit the gear awarded.
3. The specific ability to adjust a members DKP for that event with a mandatory note advising the reason. This will often be fore disciplinary reasons or many other factors.
Anytime an admin edits an event, a log should be made advising the date of the edit...and who did it. This log will be seen if anyone clicks on the event.
- Add an Item: I expect we will have a pretty good database of items. This link will let admins add items, their stats and the DKP cost.
- Edit an Item: Self explanatory. Should have a history too...so anytime it is edited it should show when someone clicks on the item in the database.
As many know, we have been working fevorishly on a Charter for DB in WoW. We determined that the guild should also have a UNIVERSAL CHarter which effected the guild in ALL games as well as a "code" or specific charter to each game. Much thought has already gone into both parts of this and now it's time for YOU all to also get a voice in! This is just a draft of the charter and will not be FINAL until we put it up on the website so here is your chance to help shape darkenbane!
We could have done this on one of the private forums, but not all members have access to all private boards so it must be done here.
Darkenbane Universal Charter
Summary:
Darkenbane is a Massively Multiplayer Online Gaming Guild which specializes in the area of PvP (player versus player). Membership to the guild is free, but has expectations of it's members in conduct and gameplay.
The guild is historically ruthless by nature to it's foes and has few friends. We offer no mercy to our enemies nor expect any in return. Those desiring to know and understand what a DB member is in a game should compare them to an carnivore that stalks sheep. The cold certainty of impending attack lurks as a companion to the Darkenbane member with fear riding along and lashing out at his intended victim. There is no mercy in his eyes, only blistering relentless death. Flee when they come for you...or die.
The Guild only will play as an organized unit in Online games that have a heavy involvment of PvP. For a game to be supported by Darkenbane, the game, it's guild leaders for that game and it's "Code" for that game must be approved by the Overlords (defined in a later section).
Changes to the Charter
This can only occur after all 5 sitting Overlords unanimously agree on a change.
Universal Guild Structure
As the Guild will be involved in more then one game, some with a large number of people, some not, it's important for a group of Leaders to oversee that any games supported by Darkenbane are being conducted properly by that division's officers. These individuals will be considered Overlords and have the following responsibilitites:
1) Approving a new game to be supported by DB. Approving the new game's initial leadership, officers and "Code" (a ruleset for the guild specific to that particular game). If this approval is reached, the game will be added to our forum list. The game will receive private forums and the guild in that game will be reognized as an authorized representative of Darkenbane.
2) Making additions or subtractions to the Universal Guild Charter which is a ruleset adhered to by Darkenbane across all games.
3) Removing Darkenbane Support from a game. This will take a unanamous vote.
4) Replacing a leadership structure of a supported game. This will take a unanmous vote and can only occur if the leadership of said game is violating the Charter and/or Code.
Overlord is a lifelong position, but has requirements as follows:
1) An Overlord cannot be inactive for more then a month. They MUST be active in the guild to maintain the position. If they become inactive as determined byt the other Elders, they can be voted out (with a unanamous vote of the remaining Elders.
2) Any Overlord found to have violated the guild Charter or a Game's Code, can be reviewed by the other Overlords for potential removal. This, again, will need a unanamous vote.
3) Overlords must be active in the guild for a period of at least 1 year before they can attain said position.
4) Overlords will be selected via a unanmous vote of the standing Overlords. 5 Overlords MUST be always sitting and active in the guild at all times. If one Overlord is removed and/or becomes inactive, then another MUST be chosen. If the remaining Overlords cannot decide upon (unanamously) a new person to fill the position, a Guild Vote will occur in whichever private board is the most active. The people who receive the most votes will have a "run off" election and the winner will be named as an Overlord.
5) One Overlord position will always be the website administrator (Meter presently).
Roster and Recruitment
There will be no universal roster or recruitment requirements across all games for Darkenbane. Instead, this will be specific to a particular game and must be addressed in that division's "Code" among other things.
Conduct
All Darkenbane members across all games will be required to follow our conduct requirments which involves the following:
1. Understanding anything you say or do on a public message board, chat room or game can and will be screen shotted and used against you.
2. If anything said by a member causes the guild embarassment, said member could fall under review for discipline. Such things include, but are not limited to the following:
a) Begging
b) Grovelling
c) Asking for mercy
d) Asking for a Truce
e) Making "deals" of non agression.
f) Generally acting stupid over time.
g) Hacking a supported game which actually alters the gameplay of said game.
h) Treason - Defined, but not limited to: Engaging in any act counter to the interests of the guild, posting private board information, giving out account information to non DBers, joining enemy guilds without being formally supported by the guild as a spy, attacking guild members in an agressive manner or giving any information deemed to be private in way shape or form to non guildmates.
i) Disloyalty - Threatening to quit the guild or actually quitting the guild. Attempting to join other guilds playing a supported game (without being supported as a spy).
j) Racism - Racist remarks more often then not (even when used as a goof) cause drama and annoy some people. As such, we are going to draw a line here and ask members NOT to utilize racist remarks or racism in any form of communication involving the guild. The level of discipline for a violation of this will range from DKP deductions, warnings and even removal if it warrants such action.
The division's "Code" should address conduct more specifically and subsequent disciplinary action. The Overlords may take action if the Division does not handle complaints against a member within a reasonble period of time. Decisions of the Elders will always overide that of any Division Leaders.
Special Operations
Darkenbane will always have a secret operations forum and group. This will be overseen by the Overlords and will admit only those necessary to study various vulnerabiltites of games, websites or other areas of interest to the guild. On this board, discussion and research will occur to determine how to utilize various tools to accomplish our goals and the necessity of using them. The Charter of the guild authorizes the Overlords to discuss and/or take whatever means necessary to ensure the success and power of the guild.
Darkenbane - WoW Code
Overview
This will be finalized after Blizzard annouces the type of servers it will offer. Things to consider are whether it will be team based and how we will deal with teamates that are not guildmates plus more that cannot be finalized until the server type is determined.
Changes to the Code
A change to The Code once it is finalized can only be done with a unanimous officer vote after an idea is presented. The vote must include at least 66% of all officers.
Guild Structure
The guild has several catagories of members which range from leadership to new recruit. Each catagory will be discussed in detail as well as their responsibilitites.
1. Leader (GM) - This person will be in charge of final decision for the guild. He should put controversial decisions to a guild or officer vote based on his discretion. He should uphold the Charter and Rules of the guild to the best of his abilities. He will make policy decisions, alliances and strategies for the guild. This person will be elected by the guild in an election once every 6 months on January 1 and June 1 of every year. A primary election will be held of all potential candidates (they must be nominated) and the top two people receiving votes will then be in a "run off" election. Each potential leader must name his officers BEFORE the election the primary. The number of officers will be based on the number of folks on the roster with 1 officer per 10 members not counting Meter who is an eternal officer in charge of the website. A GM can be removed by a 66% officer vote only with at least 75% of officers voting. The CURRENT GM in office must handle the election process and turn over power to a new GM if that comes to pass.
2. Officers - These folks will be named by the potential elected leader (prior to the election). He will pick 1 for every 10 people on the roster PRIOR to his election. An officer CANNOT be fired without a majority officer vote first (75% of officers must be involved in the vote). Only a CORE member (as defined below) can become a GM or Officer of the guild. Officers will have specific duties as follows:
a) Assistant GM - This person will take over GM position if the GM quits or get's booted. He will have similar duties as the GM and is in charge of the guild when the GM is not on. This person should be considered second in command of the guild.
b) Recruiting Officer - This person will be in charge of all things recruiting. He will abide the rules set forth for guild recruitment in this charter and will adminster the processing of all new folks as well as the board stuff involvoing them. This person willmake sure recruits meet all requirments of them and will be in charge of recruits until they achieve full membership status.
c) Adminstrative Officer - This person will be in charge of the DKP system, adjustments to it and monitoring. He or she will have to monitor the boards set up fro DKP and make adjustments as necessary and set forth in the DKP rules. Raid leaders and PvP leaders will also make additions to DKP and such, but the Admin officer will take care of disputes, adjustments and maintenance.
d) PvE Raid Leaders - These are in game leaders who will lead raids. A read leader will be responsible for taking roll call right when the event begins and keeping track of who won what loot. They will also give the loot out to the winners based on the DKP system. The number of raid leaders will be detemined by the remaining slots open for officers which is based on the roster.
e) PvP Raid Leaders - These will be the ONLY people who can issue DKP for a PvP raid. If they call a PvP raid, they have the authority to issue DKP based on guildlines set by the officers and GM to induce inflation in the DKP system and to encourage PvP.
f) Conduct Officer - This person will be in charge of dealing out discipline to those members who violate the DB code of conduct. Any incidents should mostly be referred to and handled by this person if at all possible. This refers to all sections which involve discplinary action versus a recruit, member or officer. Any complaints or issues involving conduct should be directed at this officer.
3. Members - These folks will make up the body of the guild. They have the protection of being a member and cannot be removed without a majority officer vote. They will be expected to follow the charter of the guild and the instructions of the officers. There are two types of members as follows:
a) Core - This person has been a member AND active in a given game for more then 6 months in Darkenbane. Additionally, he/she must be voted by a majority of the current officers into the "core" position after being nominated for the promotion by an officer. Only CORE members can ever become officers and/or the GM of the guild. A CORE member will be reduced to MEMBER status if he is inactive for more then a period of 3 months.
b) Member - This person has passed the requirements for moving up from recruit status. It's affords them the full benefits of membership in the guild and protection from arbitrarily being removed. A member can be placed on the "inactive" list if not active for then a period of 3 months. If they become "inactive" they can be reinstated at GM discretion upon request or might be required to go through the recruitment process again.
4. Recruits - These folks can be removed from recruitment at anytime by any officer. They will need to meet certain criteria set forth by the charter before becoming a recruit and then before moving up to member status.
Recruitment:
The guild should have 40 to 50 members online each primetime and/or 80 to 100 on the over all roster. If these criteria are not met and at the discretion of the leader, recruitment will open and new folks will be allowed to apply. A seperate public recruit board will be made for recruits to apply to the guild and where discussion of them will ensue. These are the requiremnts for new recruits:
1. Must meet level restriction requirment set forth by GM.
2. Must have 3 sponsers who are willing to put up their OWN membership on behalf of the recruit. These sponsers MUST be at the Member level or above. Members can sponser 1 recruit per month whilst CORE can sponser unlimited recruits.
3. Must maintain recruit status in good standing for 1 month.
4. Will begin as minus 10 DKP which will be distributed to the guild once their recruitment begins (10 divided by the number of current members). This number can change based on DKP conditions in game and will be GM discretion.
5. A recruit cannot receive ANY veto from a CORE member or above. If any CORE or above vetoes a recruit's status, the recruit will be required to have thos CORE member clear the veto before gaining admission to the guild.
Member conduct and discipline:
There are two types of discipline which willbe handed out to members as follows:
1. DKP penalty - This will be the penalty used by officers for minor infractions such as raid disruption, abuse to other members, failure to listen to instructions, failrue to PvP when it's called for ect. The penalties for infractions will be set by the GM and officers. These penalties can be appealed on the forums and pvertunred by the GM only. A 10 DKP penalty will be met out to anyone who quits the guild. The DKP will be distributed to the current members.
2. Removal - This will happen only after a member is brought on charges before the officers. A member can only be removed with a majority officer vote. Offenses for removal are:
a) Getting caught cheating - This allegation must be proved beyond a reasonble doubt. 1 single person witnessing a cheat is not sufficient as people are FALLABLE and so is the game. Additionally, a test for a bannable offense is if the member WOULD be banned from GAME if caught using the cheat. If a person would only be WARNED by a GM for using a cheat or exploit, it will then not be bannable in DB. Our standard will be the same as the GMs.
b) Treason: This will include the sharing of private board information, private channel information or anything that is considered "guild eyes only" with anyone NOT in the guild. This also will include any actions or conversations which are deemed to be hurtful or against the best interests of the guild.
c) Begging, grovelling, asking for mercy, making deals with non dbers to avoid PvP, saying stupid shit that get's screen capped and embarrases the guild. All of these are viable charges for a vote of removal. If not voted out, DKP penalty will be instituted.
d) Consistant disruption of the guild not limited to, but including: Abuse to other members, public flaming of the guild or it's members, constant whining or disruption. Any officer can bring charges against a person which willbe voted on to remove them.
Communication
Darkenbane will use the Teamspeak system. It is madatory for use of all members and will be our primary source of communication. In game guild chat will be used for frivolous general chat whilst TS will be more narrow. The following rules apply to Teamspeak useage:
1. In general, the channel should be limited to game related chat. When an event or PvP is NOT occurring, general chit chat is allowed, but it is recomended that folks do not over use it.
2. Do not ever talk over other people unless it is an emergency where a person will yell "CLEAR". Only push your button to talk if no one else is talking.
3. During events, everyone is to keep quiet unless they have vital information. No suggestions, no jabbering, no ideas, no thoughts, no opinions. TS during raids is used if you need a heal, need a mex broken or have some other VITAL information to convey to the event leader. The leader will call out target and instructions and everyone WILL follow those instructions without pause.
Loot Distribution:
We will utilize a DKP system to organize loot distrobution in the guild. The system will work as follows:
1. DKP is ONLY awarded if items from a raid are "bought" by someone. The price that person "pays" in DKP is split up among the people who helped the person get the item. Example: A Red Robe of Coolness drops off of the God of Underwear. It's price has been set at 10 DKP. Mindagmes buys it. He is deducted the 10 DKP which is split among the 20 DBers who attended the event giving them each .5 DKP.
2. Inflation: I believe inflation is necessary to reward long time members and keep newbs from getting gear over them. Newbs should have to earn DKP for a few eeks at least before they can get items over old timers. As such, folks should NOT be in the negative. To keep them OUT of the negative we will have DKP events for PvP that do NOT have outgoing DKP (no items paid for only DKP awarded to those who attend). This will basically reward anyone who attends and will be comparable reward to the same time spent on a mob.
3. Setting prices for items: I suspect that raid leaders will have to set the price on items as they drop. They can be adjusted later after discussion then set. We can do a monthly evalaualtion on prices of items. A message board will likely be set up for this purpose as I am sure it will have considerable debate.
This is how I envision it for a regular member:
- There is a link to see DKP after logging onto the website. They click on it and see the following:
1. Roster link - Show all members
2. Event Link - Show all events
- Roster Link: Shows All members with columns to the right. Each member's name will have a link. If u click on a member's name it will show their DKP history. All events attended, DKP earned and all dkp spent for which items. The colums next to each member's name should show:
1. Total CURRENT DKP
2. Total SPENT DKP
3. Total Earned DKP
Each Colum should be clickable to allow the list to be done by who has the most current DKP...who has spent the most or who has earned the most since day 1.
- Event Link: This link should show all events that have been entered with colums. Each event will be a link that will have detailed info about the event including the roster (who attended), what items dropped and who bought them. It should have how much DKP was awarded to each member (some members might earn more then others based on adjustments for rare classes, high levels ect). The colums should be as follows:
1. Date of the event
2. Amount of DKP awarded
Admins will obviously have more stuff. When an Admin logs on they will the links above, but also have the following links as well:
- Add a member: This will have blanks to fill out to add a person to the list. The blanks to fill out will be as follows:
1. Name (and other info like class ect)- Self Expanatory
2. Catagory - This will be complicated and involves DKP bonuses that we as leaders will set. Everyone in the beginning will be set as catagory 3 and will earn 100% DKP. Catagory 2 and 1 will be reserved for later use for perhaps recruits or lower level guys where they will earn 80 and 90% DKP respectively if they are placed in this catagory. Catagory 4 will be 110% DKP Catagory 5 120% and so on. This will allow us to reward folks who work on the website or do other funtions with higher DKP awards for their efforts. Also we can award rare classes...for example making clerics catagory 4 by default if we need clerics. This will basically be an easy way for us to have auto adjustments for better or more valuable members and reduced dkp for less valuable or folks who are lower level ect. This will allow level 55s to earn DKP...but not the same DKP as a level 65 who does alot more and it wille ncourage folks to make their characters powerful.
- Edit a member: Self expalnatory. Mostly will be used for changing category. But also for editing their DKP. Any entry for DKP will need to be logged by the system with who made the change and the date. If someone has their DKP changed it will show up in their DKP history as an addition or substration in DKP and should have the reason for this addition or subtraction.
- Add an event: This will allow an admin to add an event in the system. The following blanks will appear:
1. Name of event: Since the rewards for events are based off the loot, the event can be just typed in each time by an admin.
2. Date of event: There should be a drop down menu here so the date is not entered int he wrong format. Events will be stored by date so it's important this is entered correctly.
3. Date of Entry: Should be logged automatically by the system.
4. Roster for event: This should be a big blank area that will parse a /log showing all attendees. It will detect and enter all people who were presently from the log entered. At worst, a drop down menu with all members should be here and will allow an admin to select the names of each members who attended. Parsing would be nicer tho :) Course we are aussming they have logging and some kind of /who in WoW.
5. Gear awarded: This will be a drop down menu also listing all items already in the system. If the item is NOT in the system, an admin can then ENTER the item (and it's stats/info) with a cost for DKP.
6. Notes: This will be an area where an admin can enter misc info about the event.
- Edit an event: This link will bring up the full list of events. An event can then be clicked on and the following options are presented:
1. The ability to add or remove roster members. There will always be folks who were late that should be added or mistakes where people need to be removed.
2. The ability to edit the gear awarded.
3. The specific ability to adjust a members DKP for that event with a mandatory note advising the reason. This will often be fore disciplinary reasons or many other factors.
Anytime an admin edits an event, a log should be made advising the date of the edit...and who did it. This log will be seen if anyone clicks on the event.
- Add an Item: I expect we will have a pretty good database of items. This link will let admins add items, their stats and the DKP cost.
- Edit an Item: Self explanatory. Should have a history too...so anytime it is edited it should show when someone clicks on the item in the database.