![]() |
|
#201
|
|||
|
If you don't know where Sev spawns after 4 years. Do everyone else a favor, and refrain from competing on FFA spawns until you've done your research. You can ask someone to leak you the spawn location. Or you can just watch where class C trackers are standing every single week, and watch for the mob to spawn one time. People asking for the GMs to give out the spawn location for every are ridiculous. In one spawn cycle, you can find out where a mob spawns, and your guild will have that info for ever. There is no excuse for anyone to be competing for an FFA mob, and not know it's spawn location.
And it's even more stupid for the guilds who DO know where Sev spawns, to put their kos mages there anyway. Taken and whoever else, BDA? I don't know who's mages were there. Just assume class C knows what they are doing, and don't just blindly follow what they do. What the hell did you guys think was going to happen if a dragon spawned on top of them? Also, why do those mages have pets up? Obviously he's going to aoe immediately. TMOs mage deliberately never made a pet for this. Rational thinking goes a long way when competing for spawns. | ||
|
|
|||
|
#204
|
||||
|
Also
Quote:
Telling guilds that they can't attempt mobs without knowing their exact spawn point is pretty condescending, especially with the raid rules like this that reward (KoS) mages for being as close as possible while staying outside of aggro range. That's not easy to pinpoint, and I'm surprised this hasn't come up sooner. | |||
|
|
||||
|
#205
|
||||
|
Quote:
I agree that the mage thing is stupid. If the point of the new rules was to encourage racing from zone lines, then this is just a loophole which completely defeats the purpose. TMO and IB have never done it on class C mobs, and I think we can safely assume that they don't want to do it on FFA mobs either. Catherin says she doesn't want it, but she's the one who started it on Sev and naggy, the very first week when nobody else wanted to do it. Chest seems to dislike the mag coth also, as well as some other class R guilds. Hopefully it will go away now. We'll see what guilds decide to continue, and force everyone else to do the same. | |||
|
|
||||
|
#206
|
||||
|
Quote:
| |||
|
|
||||
|
#207
|
||||
|
Quote:
We gave up a week of VP, and had the loot of 4 dragons deleted, over an EXTREMELY arguable, and non-malicious rules violation. In what was essentially a grey area of the rules which had not been ruled on, or explored before. Then compare that to this situation. Where Taken maliciously chooses to break the rules and absolutely nothing happens. I think they just want to give Taken a pass for some reason. That's fine I guess. But next time someone in my guild makes an honest mistake I hope they use the same consideration, rather than suspending us for a week. | |||
|
|
||||
|
#208
|
|||
|
And this precedent has been established and ruled on, like 10 times before. You always respect the FTE shout, no matter what. There's nothing new about it.
| ||
|
|
|||
|
#209
|
||||
|
Quote:
could you imagine the uproar if TMO had killed Severilous instead of Taken? do you think you guys would have gotten off as easily?
__________________
Grew | Stable | Doub | Bubb | Locust
| |||
|
|
||||
|
#210
|
||||
|
Quote:
| |||
|
|
||||
![]() |
|
|