Quote:
Originally Posted by Sirken
[You must be logged in to view images. Log in or Register.]
Q: What classifies a mob as "Engaged"?
A: A mob is classified as engaged as long as it has aggro on at least one player.
Q: Both raids got here simultaneously. What do we do?
A: First to Engage.
|
Not a question about the rules per se, but a question about if we could be provided with the tools needed to determine who had FTE to reduce potential for conflict and so that the playerbase can better police/manage themselves.
As it has been historically impossible to determine who had FTE with near-simultaneous engagements, prox aggro vs. damage aggro, having a mob charm the initial puller and having no one on the aggro list at the time it is re-tagged, etc., the FTE raid rules have largely depended on after-the-fact GM intervention/re-distribution of items after looking at engagement logs.
This is burdensome for the GMs, and forces guilds into a position where they can't disengage from the mob and let the other guild attempt on their own without risking losing loot rights if they did in fact have FTE.
Any updates/thoughts into programming in a FTE shout for raid target mobs? I.e.:
Talendor shouts, "Yendor from Bregan D'Aerth is the first to challenge me... may his death be swift!"
Upon clearing the hate list and returning to seek mode:
Talendor shouts, "I have defeated my enemy... who is next to feel my wrath?!"
Then, all raid forces present know exactly where FTE stands, can back off and let the guild who got FTE attempt the encounter on their own, sink or swim, and no need for after-the-fact GM intervention because it would be clear who had FTE and anyone looting from a force that did not have FTE would be dealt with severe punishment.
Yes, it's not classic, but it would simply tell us all at the time of engagement what the staff has to tell us after-the-fact in the current state in order to resolve FTE disputes.