![]() |
|
#181
|
||||
|
Quote:
Regular 16 hour window Dain you get the 2 trackers, you are kidding yourself if you think this happens on the ring war Dain. Where you'll have your 2 trackers already set up, and a whole slew of people taking off through the castle at the respawn message regardless that he spawns shortly thereafter. | |||
|
|
||||
|
#183
|
||||
|
[QUOTE=FatMice;2234580]
Quote:
so again, if you mean what you say, do a concession, and ask everybody back to the table. Then negotiate in good faith to make the server a better place for all (including yourselves) then you can call yourselves the saviors of the server, but if you don't nobody will believe a damn thing you say | |||
|
|
||||
|
#184
|
|||
|
Okay, you two idiots need to learn how to properly quote already.
| ||
|
|
|||
|
#186
|
||||
|
Quote:
There are people poopsocking Dain for Ring turn ins who are affiliated with various guilds but you will notice they are untagged as per the accepted server behavior for quest turn ins. These players should not be confused for players going for FTE - however I can tell these distinctions might be difficult for you. Show us the fraps that prove your stance, until then you are 100% wrong and obviously hilariously uninformed. Enjoy your beers with Gimp tho [You must be logged in to view images. Log in or Register.] | |||
|
|
||||
|
#187
|
|||
|
Guess people CotHing early because they were off a few seconds on the fail timers doesn't happen or raids moving to the Ice Bridge early before FTE occurs doesn't happen either?
You are fooling yourself if you don't think 'Letter of the Rule' violations occur on just about every failed ring war Dain repop. Or sitting there spam hailing Dain while you set the aggro/banish/summon table, seeing him run back into the castle then back to the raid followed by the 'stall' tells and ooc pissing contests. We see this stuff all the time. | ||
|
|
|||
|
#188
|
||||
|
Quote:
| |||
|
|
||||
|
#189
|
||||
|
Quote:
A simple rule adjustment of only being to engage FTE'd 1 mob at a time or setting a 20 minute kill timer after FTE would alleviate some of this stuff. There's basically 3 issues going on in this. 1) Aftermath getting FTE, bailing, then coming back while the timer was still running where no one else could engage the mob. Sirken still gave the mob to Aftermath and enforced the rules as stated. Simple rules tweaks mentioned above would fix. 2) How/when Gimpster got FTE. The outcome was Sirken enforcing the FTE and letting Aftermath have the mob. 3) Pint/Detoxx bringing up the raid rules about timers and how long guilds have to kill things before the raid summit, not having them addressed in any meaningful way, then going ahead and doing things how the rules are currently written. My point is you see people doing all sorts of infractions of raids that never seem to amount to anything. I'm sure those ripping on Aftermath have already got petitions going and their supporting evidence posted, but we won't find out for a while what punishment gets dolled out. | |||
|
|
||||
|
#190
|
|||||
|
Quote:
Quote:
| ||||
|
|
|||||
![]() |
|
|