Green Raid Rules/common raid rules

WARNING: Page is in draft form

Common Raid Rules

This is a currated list of common raid rules. Note that rules are sourced from the Raid FAQ page which is considered the authoritative source.

97% Rule

Must get target under 97% within 1 minute of engage. If you fail to reach 97% within the 1 minute mark you must drop your engage. You may re-attempt after waiting 3 minutes.

discussion

There are currently only 3 targets that this rule applies

1. Dozekar
2. Yelinak
3. Zlandicar

Encounter Stall

Taken from the FAQ Page

Your granted about the length of a DA to properly engage a target. That means you are given, about the length of a DA, to get the target sufficiently tanked. That means either having it tanked with heals rolling, or followwing it up with bumps to hold it until you do. Additional DA's are not allowed.

Discussion

There is a lot of discussion about what "about the length of a DA" means. This ambiguous rule has been the source of some recent raid concern discussion.

there is also a discussion on whether 1 or more DA's can be used legally for an engage. If so it could be strategically wise to help protect FTE's during failed bumps. For example if 1 DA is used to start the engage, additional DA's are used to help secure FTE but the target is adequately being bumped by the appropriate classes.

You are allowed to DA into a bump, as many bumps as needed. Bumping is the practice of using a discipline's like Weapopn Shield to parry all incoming attacks, typically used to buy time while stratigcally positioning other tanks and healers in place to stabilize an encounter.

Recently staff has asked the UN guilds to better define what they consider a stall. The discussions are ongoing and incomplete. This rule may change in the future.

A Train

text

Tracker FTE

When a guild obtains an FTE on a target without starting from a specified race-line, or by not following a vacate rule, they are considered to have committed a tracker FTE which should result in a concede

Discussion

From the faq page

Q15: Are either of my two trackers allowed to get FTE? A: Absolutely not. If one of your trackers gains FTE, you need to drop aggro immediately and concede/forfeit the mob. Furthermore, if a guild gets FTE, any other guilds that are tracking the mob and end up with tracker FTE as a result of the first guild are not DQd from the mob.

Q30: What can a tracker do? Trackers are for tracking. They cannot kite, pull, DPS, heal, or perform any actions that would populate on an encounter log.

For Example: A mage tracker can COTH + lay down rods, but can't nuke or utilize their pet.

Please Note: If utilizing a necromancer as a tracker, be aware their "twitch" spells will create an entry on an encounter log as well.

If utilizing a cleric tracker; they will no longer be able to rez dead bodies and or heal any players that are part of the encounter.

For Brevity: Guilds are only allowed a maximum of two trackers in a zone. It is permissible for a tracker to gate, camp out, or return to the zone line in order to clear their "tracker status" as long as the total number of trackers are two or less. Additionally; we do not want to discover guilds abusing the two tracker rule and create unfair advantages by sneaking in a third tracker. If there are more than three trackers logged in; it would result in a disqualification for their guild.

In the event of a raid target spawning; two trackers are allowed to check a target with their active raid force beyond the entrance; however, that raid force must return to the entrance before being COTHed or moving towards that newly spawned target. We do not want guilds abusing the definition of a raid force by having multiple players online, sitting at spawns claiming to be part of a raid force, when they aren't helping with the target of the primary raid force.

If it is brought to our attention a guild is abusing the two tracker rule and/or participating in actions that would be in violation of our guidelines; we will consider enforcing stricter rules and/or severely punishing the involved guild(s).

TOV Vacate Rule

If your raid force exists in the same wing, at the time a desired target spawns, your raid force must vacate the wing entirely before engaging the spawned target of interest. An FTE on the target prior to vacation is considered a Tracker FTE.

To vacate the wing successfully your guild must remain with no more than 2 trackers present in the wing, while all others are outside of the wing at the same time. As clarified in the UN. [1]

discussion

If guild is pulling in Aary pit, crawling to Vyemm, and Feshlak spawns that guild must vacate the wing if they chose to go to Feshlak instead. Alternatively that guild may continue on and persue other targets, like Vyemm, but if an FTE from them goes out on Feshlak prior to vacation then it is considered a tracker FTE

This rule comes from the following text on the FAQ page.

MUST LEAVE THE WING ENTIRELY WHEN A RAID TARGET SPAWNS. ALLOWED 2 CHARACTERS MAX TO NOT LEAVE WING.

Further clarified in the UN.