Taken - Sev

[Locust]

and taken wasn't at fault for deliberately killing the dragon

[arsenalpow]

Nemce didn't know where Sev spawned. Warning for AG for not knowing something and getting other people AE'd. After that anyone that was on the encounter list and didn't actively try to get off it should be dealt with. Theya dragged Sev to TT under a false FTE, that's blatantly wrong. Taken killed the dragon under false FTE, also blatantly wrong. Don't paint everyone with the same brush just because it was a clusterfuck, FFA mobs are always a clusterfuck but respecting an FTE usually happens.

[Argh]

The only reason there are so many people on the encounter log is because a bard chose to pull it from spawn to the zone line where there were 160 other people waiting. Nobody there expected the mob to be pulled considering everyone in the zone was shouting/ooc'ing that Nemce was a tracker and there had to be a new FTE before the pull. I don't think anyone else considered that an illegal FTE meant that the mob was just up for grabs, since that would mean there would be no FTE message to go off of.

Most if not all people outside of taken on the logs show up there doing 0 dmg/hate, and when it was clear Taken was killing the dragon why would you cap/camp/gate aggro to get off the hate list for a reset that you know isn't coming?

No other guild is at fault for what happened, and no other guild did anything wrong by simply showing up on the encounter log.

[kotton05]

Originally Posted by Argh [You must be logged in to view images. Log in or Register.]

The only reason there are so many people on the encounter log is because a bard chose to pull it from spawn to the zone line where there were 160 other people waiting. Nobody there expected the mob to be pulled considering everyone in the zone was shouting/ooc'ing that Nemce was a tracker and there had to be a new FTE before the pull. I don't think anyone else considered that an illegal FTE meant that the mob was just up for grabs, since that would mean there would be no FTE message to go off of.

Most if not all people outside of taken on the logs show up there doing 0 dmg/hate, and when it was clear Taken was killing the dragon why would you cap/camp/gate aggro to get off the hate list for a reset that you know isn't coming?

No other guild is at fault for what happened, and no other guild did anything wrong by simply showing up on the encounter log.

This, wtf happened deru ur ruling sucks and has no basis.

[sulpher01]

I think we can all agree taken is a bunch of asshats?

[Locust]

Originally Posted by -Erati- [You must be logged in to view images. Log in or Register.]

you do realize the yellow text was put in so players could police themselves and behave better upon a dragon being engaged in front of a zerg of guilds. just a graphical representation that is avail to avoid confusion....the GMs still have the power to look up encounter logs and point out who has legit FTE according to the rules.

what occurred last night was the very first instance of a dragon being killed without a 'legal' yellow text, something that has never happened since the autofire/tracker rule update

Your flowchart became null and void soon as new rules were implemented and changed the fact that sometimes a FTE shout is not actually legit FTE.

Originally Posted by -Catherin- [You must be logged in to view images. Log in or Register.]

you guys are very good at ignoring every other moving part in this situation that you are guilty of too. As well as this situation being completely different from anything else that has ever happened.

Taken sought to finally receive some direction on what would happen in this unique situation. Now we all have it. I hear all of this talk of negotiation, but there is nothing that can possibly be negotiated because of the facts of the situation that you keep ignoring. You just want punishment.

Enjoy your forumquesting.

unique situation:

a tracker engages a raid target (illegal), dies and loses FTE, but not before other guilds engage said raid target

not a raid rule:

raid targets are FFA if the FTE message was illegal

well defined raid rule:

don't kill a mob unless you have FTE

guilds who didn't break this rule:

TMO, IB, BDA, A-Team, etc

guilds who definitely broke this rule:

Taken

things that don't matter:

how many guilds were on the agro list
how long it would take everyone to clear agro
whether or not you were confused about the rules

Taken's actions cost the entire raid scene a Severilous and 16 hours of tracking

of course we want punishment

every other guild there could have killed Severilous yesterday, but they respected the rules of engagement

[Detoxx]

Originally Posted by Locust [You must be logged in to view images. Log in or Register.]

unique situation:

a tracker engages a raid target (illegal), dies and loses FTE, but not before other guilds engage said raid target

not a raid rule:

raid targets are FFA if the FTE message was illegal

well defined raid rule:

don't kill a mob unless you have FTE

guilds who didn't break this rule:

TMO, IB, BDA, A-Team, etc

guilds who definitely broke this rule:

Taken

things that don't matter:

how many guilds were on the agro list
how long it would take everyone to clear agro
whether or not you were confused about the rules

Taken's actions cost the entire raid scene a Severilous and 16 hours of tracking

of course we want punishment

every other guild there could have killed Severilous yesterday, but they respected the rules of engagement

This is RnF, please refrain from using logic

[Lisset]

As much as I have enjoyed your posts Swish, I'm just gonna go ahead and block you. You've turned into nothing more than a whore for red lately and that's just sad.

[Shinko]

learn to not be KOS to dragons

[Troubled]

Not sure why Deru still saying multiple guilds would be suspended. Being on the hate list isn't against any written rules.