Hiya everypony!  Here are the official rules and guidelines for our guild scheduled Operations.  All of our official guild Ops will be scheduled using the event page of our Enjin site, which can be found here.

• Operation Rules
  
• Operation Group Looting
  
• Operation Scheduling
  
• Progression Team Composition
  

Operation Hierarchy:
Guild Operation Events will be run with a single Mane as the leader of the group. They will be in charge of doing the following.

• Inviting players.
  
• Coordinating the group and devising the plan of attack.
  
• Punishing rulebreakers.
  
• Honestly and properly distributing loot.
  

Primary Operation leaders are Fluttershy and Pinkie Pie. Another Mane will substitute if both of the primary group leaders are not able to attend the event. In multi-group circumstances or in a case where all Manes are unavailable, a Royal Guard will take control of the group.

Royal Guards and other Manes will be responsible for the following.

• Setting an example for other players.
  
• Keeping other players in line.
  
• Helping the raid leader when necessary.
  

Operation Rules: Warnings and punishments will be delivered accordingly depending on the infringement.

• Operation groups formed before the designated Mane leader is present must pass leader to the Mane.
  
• No combat initiation unless ordered by the leader or designated main tank. Leroy Jenkins will not be tolerated. If a member does rush do not follow them.
  
• Do not argue or debate with the Operation leader over loot or strategy.
  
• Do not debate, argue, or insult the Operation leader over group composition or Operation details for that time slot. The leader reserves the right to form the group based on what is best for the group as a whole, not a single member. Members violating this rule will be dealt with promptly by the leader. If the member has concern about the Operation system or would like to report misconduct, please feel free to message Fluttershy or Pinkie Pie.
  

Ops Sign-up:
To sign up for a guild Operation, go to the event page of our Enjin site, click on the event on the calendar, and click "Sign up for this event!"  Please note that you must have an Enjin account to do so.  After signing up, please select the role which you are going to fill in the group (Tank, Healer, Melee DPS, Ranged DPS).  If the role you wish to perform has been filled, you are encouraged to sign up anyway in case a second group is formed or other members do not attend.

Operation difficulty for the timeslot will be specified in the event description unless noted to be determined at the time of the event.

Ops Scheduling: NOTE: This section is subject to change. Updates will be made in the future about scheduling as needed.
We are currently hosting top-tier Ops on Friday and Saturday at 9:00pm EST (GMT-5). Ops designated for gearing purposes are held on Monday, Tuesday, and Thursday at 9:00pm EST (GMT-5). Attendance permitting, we will attempt to get everyone into the run as possible. If you sit out one week, you'll have priority selection for you next Ops run.

Operation Looting: The following is a step-by-step process of how distributing loot will be handled. This looting system will apply for World Bosses when necessary and Hard/Nightmare difficulty Operations.

1. The raid leader will set the loot system to Master Looter.
   
2. After the boss is killed, the leader will announce the first dropped item in Ops chat (using Shift + Left Click).
   
3. The leader will then ask members to /roll 1-100 in Ops Chat. The member who rolls closest to 100 wins the item.
   

Operation Looting Rules: The following is a list of rules that players must follow while loot is being determined.

• Primarily, you may only roll on items that your class can benefit from. However, if no player of the said class desires the item up for grabs, then you may roll on it for other characters. For example, a pair of Jedi Knight boots drop and you're a Trooper. No Guardian or Sentinel in the group desires the boots but you'd like it for an alt. You may then roll for the boots in order to legacy them over to your alt as no current Guardian or Sentinel desires them.
  
• Players who need a gear token for the character they are in the Ops with currently get priority to the token. However, if a player is running a particular character for the benefit of the Ops group and needs gear for a character that is used in progression Ops, they may then roll for gear tokens (with the exceptions of Implants and Earpieces) with the same priority as other players. For example, if a player needs an item for their healer character that is called upon for progression but is asked to DPS for a current run with another character instead, they are then allowed to roll on tokens with the same priority as other Ops members. Alternate characters marked as progression will be determined by the current Ops leader.
  
• You may only win one gear token per Operation with the exception of belt and bracer tokens. If everyone in the Ops has already won once or doesn't need the token, rolling for a second one is then permitted. Gear token lockouts reset when Ops lockouts reset (Tuesday morning).
  
• If you do not need the item then don't roll. Rolling with the intent to sell the item will hurt your fellow guild members.
  
• For progression runs, gear tokens will be given out based on need if the Ops leader deems it necessary for the benefit of the group. After the player accepts the token out of need, that player is then locked out of winning any more gear tokens unless all other players have won a token already. If the player in most need of the item refuses priority on it, then it will go to a roll. For example, if a player has two Underworld relics and another player has two Arkanian relics, then the player with two Arkanian relics is given the Kell Dragon relic. This player decides they want to roll on future tokens instead and allows the item to go to a roll among the other players in the group.
  
• For progression runs, if DPS appears tight on several progression encounters, the Ops leader may give progression DPS members priority on mainhand drops. For example, if Thrasher was defeated on Nightmare but she enraged at the end, the four progression DPS could be given priority on the mainhand drop by the Ops leader later on in the instance.
  

Voice Chat:
The use of voice chat on our guild Mumble server is required during Operations. If you do not have a microphone or do not wish to speak, that is acceptable. However, it is of utmost importance that you are able to hear the instructions of the Ops leader. More details on Mumble and our guild server can be found here.

Progression Team Composition Guidelines:
The progression team is comprised of guild members who are attempting to clear content that the guild has yet to complete. The progression team is in effect when there is new, PvE end-game 8-man content to be cleared. Group composition is at the discretion of the guild officers running the team in order to improve chances of developing strong strategies and completing content in a timely manner. Member selection is based on the following guidelines:

• Player gear is appropriate for content level.
  
• Player skill at their role is above average performance.*
  
• Player raid awareness is above average performance.
  
• The player has cleared lower difficulty content (e.g. has completed Hard Mode before attempting Nightmare).
  

*DPS may be asked to submit a dummy parse to an officer in order to assure that the player has the capability to perform up to, or above, what is expected by the encounters.

If there are multiple players of similar skill and gear interested in the same role for the progression group, then the group composition may be rotated day-to-day to accommodate other players (e.g. four tanks want to run in the progression group who are all similarly geared and skilled, so two tanks are assigned to day 1 and day 3 progression Ops while the other tanks get to run day 2 and day 4). This allows for more players to get in practice and prevent total exclusion. However, this rule may be suspended in times of major progression leaps (e.g. tanks were rotating but the day 1 group cleared two bosses, so the day 1 tanks get to continue until progression halts due to difficulty).

In the event a player is asked to sit out by an officer due to the officer deeming them unqualified, the officer will explain to the player why they were chosen not to attend progression run. Once the progression run is over for the night, or when both the potential progression raider and an officer have time, the player asked to sit out will be assisted by an officer to help them improve what the player is missing for progression run qualifications. If the issue is experience with lower-difficulty content (i.e. the player wants to run Nightmare but hasn't completed Hard Mode), they will get priority placement in the next lower-difficulty guild Operation.

Changes or additions will be made to the list as the Manes see fit.

Thank you for reading, and see you in the Ops party!

Look, updates!

Updates have been made to the scheduling section.

Updated: Revised looting and looting rules, and updated Ops scheduling.

Updated: Aug. 5, 2013

• Ops Loot Rules has been revised to fit the current gearing situation.
  
• Ops Scheduling is now accurate again.

Revisions are underlined in the spoiler.

Spoiler:

Updated: Aug 6, 2013

• Added progression loot rules.
  
• Revised the lockout loot rule to better reflect the guild's loot policy.
  

Revisions listed below:

Spoiler:

Updated: Aug 19, 2013

• Added progression team composition to the rules and guidelines.
  

Spoiler:

Update August 27th, 2013:

• Changed the loot rule from one token per week to one token per Operation. This was to help motivate more members to attend more Ops.

Spoiler: