Taken - Sev

[arsenalpow]

TMO has draco FTE. IB kills it. IB suspended.
Taken has Nagafen FTE. Taken kills it with BDA assisting on the last 10%. BDA suspended.
AG has Sev FTE. Taken kills it. No punishments.

[zanderklocke]

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

TMO has draco FTE. IB kills it. IB suspended.
Taken has Nagafen FTE. Taken kills it with BDA assisting on the last 10%. BDA suspended.
AG has Sev FTE. Taken kills it. No punishments.

Well...AG's FTE wasn't legitimate, so that might have some affect on this. However, Taken did not let the mob reset. Shrug.

[arsenalpow]

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

Well...AG's FTE wasn't legitimate, so that might have some affect on this. However, Taken did not let the mob reset. Shrug.

The rule is if it isn't your FTE then you don't touch the mob. There's no caveats, there's no special circumstances governing illegal FTEs. The mob must reset. Period.

[Hitpoint]

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

The rule is if it isn't your FTE then you don't touch the mob. There's no caveats, there's no special circumstances governing illegal FTEs. The mob must reset. Period.

Yea, pretty much this.

They were warned the entire time they were pulling Sev too. There is three minutes of chat log where people are telling them that the pull had to be dropped so there could be a new FTE message. They chose to ignore people who are familiar with the rules, and take their chances with a GM decision. Which should never be the case.

You are supposed to ALWAYS respect the FTE shout. No exceptions. Even if you think the other guild is kiting, or cheating, or their pull is illegitimate in some way. You cannot pull it off them because the FTE is not credited to you, and players do not have the power to overrule an FTE message. You have to let them do whatever it is they are going to do with it (which should be to drop the pull if they are smart) and let the GMs handle it. The GMs have ruled on this very clearly in the past. Numerous examples include FE pulling fay off a blatant kite, pulling gore after an FTE snipe (which was wrong and bad), pulling tal off an alleged kite, and engaging CT off another alleged snipe (which turned out not to be the case). In each of these situations, it was made clear that it was wrong to disregard the FTE shout, no matter how illegitimate we thought the pull was.

The correct thing to do on this Sev, was for nobody to pull Sev in. Everyone who was on the agro list should die/FD/camp/gate/coth themselves, whatever they can do to lose agro immediately. And allow a new FTE to go off.

I don't care whether Taken is suspended or not. The rules are clear and I guess technically Taken should be suspended if we're trying to be consistent in rulings. But rulings have not been consistent here lately, and maybe that's just something we have to accept. I do hope this is the last time this lesson needs to be learned. If the FTE doesn't belong to someone in your guild, or someone who you're willing to forfeit all loot to (assuming both parties combined are under the two tracker limit), then you absolutely cannot kill the mob. No exceptions.

[arsenalpow]

That's my issue, consistency. I was on vacation when Sadad got dragged to the table by Derubael and TMO over an issue that was nearly 90 days old that Sirken personally told me was squashed. We engaged a FFA Naggy at 10% when Taken had FTE. Taken wasn't likely to wipe and one of our officers made the call to get some hits in. Unbrella demanded a Nagafen because Taken could have wiped thus preventing a TMO engage. Derubael decided an appropriate punishment was to leverage the class R rotation slot we have for Naggy into being skipped the next time up. I fully disagreed with the punishment on multiple levels.

Taken killing Sev was so much more blatant. I'm fucking shocked that the staff made this ruling with multiple incidences of precedence that have already been resolved. It's not consistent at all. Why should BDA lose a class R target over an FFA encounter and Taken gets a warning? What's the logical precedence to determine that? If the answer is "because the staff said so" then expect this type of fallout every fucking time because when the staff isn't consistent there will be questions and cries of favoritism.

[Arteker]

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

The rule is if it isn't your FTE then you don't touch the mob. There's no caveats, there's no special circumstances governing illegal FTEs. The mob must reset. Period.

what you waited to happen, catherin was found using a 3 party program even going so far to admit it. and she did not get any punishment . you realy think she must be afraid to break standard fte or raid rules when she or him scaped unscratched of using autofire?.

[Swish]

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

what you waited to happen, catherin was found using a 3 party program even going so far to admit it. and she did not get any punishment .

wasn't there a suspension involved? i do find it hard to believe that causing more heartache (pun intended) for clerics by using autofire isn't a bannable offence.

3rd party programs definitely on the ban list, seems strange.

[Frieza_Prexus]

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

Well...AG's FTE wasn't legitimate, so that might have some affect on this. However, Taken did not let the mob reset. Shrug.

The staff has been pretty adamant about telling players to not judge the worthiness of any particular FTE and to instead let them sort it out after the fact. Thus, AG's FTE, good or bad, shouldn't really play a part in the consideration of Taken's actions.