Recruitment Advice for AM.

[diamondfist]

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

Better questions like why does one person logging in on top of a boss who's gone LD lock a guild in for 30 mins.

So you are admitting for your guild it was tracker FTE on a mob you killed?

Seems about right with Aftermath's history.

[Arkanjil]

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

So you are admitting for your guild it was tracker FTE on a mob you killed?

Seems about right with Aftermath's history.

That’s not tracker at all...the guy who got FTE went LD earlier in the day at that spot and logged in not knowing Aary was up. It shouldn’t have even been considered a valid FTE as the AM force was all the way at Vulak. Talk about misinformation with your pretty picture.

[Baylan295]

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

That’s not tracker at all...the guy who got FTE went LD earlier in the day at that spot and logged in not knowing Aary was up. It shouldn’t have even been considered a valid FTE as the AM force was all the way at Vulak. Talk about misinformation with your pretty picture.

That is, by definition, a tracker.

We have a lot of silly rules, though. And I don't anticipate anyone making a big deal about that one.

[Nexii]

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

So you are admitting for your guild it was tracker FTE on a mob you killed?

Seems about right with Aftermath's history.

Tracker FTE rules in TOV were thrown out the window. Well, kinda. Who knows anymore.

[Arkanjil]

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

That is, by definition, a tracker.

We have a lot of silly rules, though. And I don't anticipate anyone making a big deal about that one.

Note on Rule Lawyering – I think the spirit of everything we are trying to accomplish here is pretty clear. Anyone that tries to twist the words to support and/or justify nefarious actions will not be rewarded. There will be no “technically this could be that”, or “well it doesn’t exactly say this word for word”. From this point forward we will be actively enforcing the spirit of these rules more so than the exact letter of the law. Don't expect to skirt passed a raid suspension on a loop hole or technicality.

[diamondfist]

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

That’s not tracker at all...the guy who got FTE went LD earlier in the day at that spot and logged in not knowing Aary was up. It shouldn’t have even been considered a valid FTE as the AM force was all the way at Vulak. Talk about misinformation with your pretty picture.

You get your rules from Detoxx direct or have you actually read the rules posted on the forums?

DMX your an officer right??!? Explain to me why you guys didnt call accidental? You wanted to lock, because you wanted aary not knowing vulak was an option.

[planarity]

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

Note on Rule Lawyering – I think the spirit of everything we are trying to accomplish here is pretty clear. Anyone that tries to twist the words to support and/or justify nefarious actions will not be rewarded. There will be no “technically this could be that”, or “well it doesn’t exactly say this word for word”. From this point forward we will be actively enforcing the spirit of these rules more so than the exact letter of the law. Don't expect to skirt passed a raid suspension on a loop hole or technicality.

yeah great, so why (and I'm not being sarcastic or snarky here) did you not call accidental? It sounds like it was accidental.

[Arkanjil]

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

yeah great, so why (and I'm not being sarcastic or snarky here) did you not call accidental? It sounds like it was accidental.

Because there had been inconsistent rulings in the past on when it’s appropriate to call accidental. We said “call accidental and risk loot deletion if a GM doesn’t think it was appropriate for some reason, or just wait and see if they get it down in 30 minutes?” We chose to wait and not risk penalties, which is hilarious considering a member went full retard and trained you guys in retaliation for training us.

I don’t condone what Riptoes did at all and we are eating the punishment for the actions of one person. We conceded immediately, because Rip training was obviously stupid and cheap, your open raid still got Vulak, and we removed the offender, but that wasn’t enough.

See you in a week.

[Baylan295]

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

Because there had been inconsistent rulings in the past on when it’s appropriate to call accidental. We said “call accidental and risk loot deletion if a GM doesn’t think it was appropriate for some reason, or just wait and see if they get it down in 30 minutes?” We chose to wait and not risk penalties, which is hilarious considering a member went full retard and trained you guys in retaliation for training us.

I don’t condone what Riptoes did at all and we are eating the punishment for the actions of one person. We conceded immediately, because Rip training was obviously stupid and cheap, your open raid still got Vulak, and we removed the offender, but that wasn’t enough.

See you in a week.

No one has answered why AM moved from a safe spot to Vulak 4 way 10 minutes into their lock. Regardless of accidental or not - what was the reason for moving from a safe spot into a place with more risk?

The only answer I can come up with is to block a pull.

[Viscere]

Diamondfist, why so angry? Isn't it like 3am in your country? go to bed pal

You have to concede dragons, we took a 7 day bann for a meth head that lost his cool and got then guildkicked. All in all, it's all good.