Need Clarification Please!

[Detoxx]

Seeking clarification on the new rules. If guild A has FTE on a mob in ToV, it is pretty well known that you cannt FTE anything in ToV ot Kael, but outside of that, are we locked out of FTEs from every mob outside Kael and ToV as well?

Being as the Title of the thread is: Tov and King Tormax / Statue Specific Rules my interpretation is that this only applies to ToV and Kael. In the post ot states you cannot FTE any mobs though, causing confusion and room for lawyer questing.

Would also like to know how other guilds interpret this.

Any clarification would be much appreciated!

Thanks!

[Daldaen]

I read "any other raid mobs" as any other raid mobs. Though I do understand there is some LawyerQuest grey area due to those rules being specifically for ToV and Kael.

But I think the intent behind them was to encourage a focus on the target. Those 60 minutes are supposed to allow you time to cleanly pull and kill your target mob. Not hang out with it on lockdown while you snipe Faydedar before you return to kill your target.

I would also appreciate Sirken's clarification on this.

[arsenalpow]

My interpretation is that the rule only applies to Kael/ToV where the one hour grace period is in effect.

[Sirken]

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

I read "any other raid mobs" as any other raid mobs.

this ^

[Daldaen]

Thus the hammer comes down and it is so.

The rule is intended to be once you're locked into a ToV or Kael target, that is to be your focus. No breaking off for Kunark or other Velious targets until your locked target is dead.

I also have a few other clarifications Sirken if you could. The first is more of a Nilbog question.

Vulak's Shout Change - I have no idea what this change entails, but it sounds like it is the dragon will override aggro, similar to Cazic Thule or Tunare's summon calls. This is a disastrous change when coupled with 16 hour variance.

Guilds classicly would clear NToV and then engage Vulak last, knowing no other dragons will be up. But with 16 hour variance this is not a possibility and it is very possible another dragon may spawn, and get called to Vulak while he is being fought. This is problematic. Guilds have no way of preventing this really. If the change removed the ability to kite these dragons away from your camp, either you need to be able to offtank Vulak and kill the second dragon (which is banned by the 1 dragon FTE at a time rule) or you must kill Vulak before the other dragon gets to your camp (definitely not possible many times). It would be nice to know exactly what this patch note means before a guild pulls Vulak and trains the hell out of everyone because of a new mechanic applied to his event.

I suppose the question for you would be, if you've already got Vulak engaged and another dragon spawns, and this change prevents you from kiting and therefore conceding the target... A guilds only option would be to offtank Vulak and attempt to slay the other dragon (which would be an impressive feat for any guild to even pull off)... Would such an attempt atleast be allowed? Or what would you want guilds to do if they have Vulak FTE and a second dragon spawns who is linked to him.

Lev Ring Jumping - This exploit has been banned in several player made agreements in the past and I would like some official ruling on the matter. Because I'm sure not everyone (including GMs) is aware of the meta-game of EQRacing. When you jump and use instant levitate clickies while jumping, it pushes you forward. Basically it allows you to gain an advantage in a footrace where levitate is allowed (Kael). Is this practice allowable? In the past there has been banning of using other levitate based exploits like the levitate tunnel in Vox's Lair among other areas. I can't imagine why this would be allowable but i figured it's worth asking so everyone is on the same page.

Repops - When the server shakes I believe the understanding is the second the shake happens you can leave the starting line because mobs are known to be spawning even though it may not happen instantly these days.

However when the server comes down for a patch or reset, the rule hasn't been clearly said. In these cases players are still expected to be camped at the starting line, not parking them underneath raid targets they expect will be spawned when they log in? Is this correct?

[Breaken]

Thank you for the clarification. Could you also clarify this situation:

Guild A gets fte in another zone, say VP. A mob in ToV spawns. The vp mob is coming into camp. Can Guild A run for FTE? My interpretation is yes, as long as you don't get new fte on VP mob after fte on tov mob goes out.

[Daldaen]

I suppose that's an interesting point too...

If ToV/Kael lock you out of the rest... The rest doesn't lock you out of ToV and Kael? So you can get Faydedar FTE and during his 10min pull get Dozekar FTE. Kill Fay then port over and kill Dozekar during your 60min.

[bktroost]

Isn't the intent of the rule to push guilds to not locking content while they are killing other mobs?

[Detoxx]

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

Isn't the intent of the rule to push guilds to not locking content while they are killing other mobs?

It was my understanding that the intent of the rule was to give all guilds equal footing to attempt and kill any mob.

[Culkasi]

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

It was my understanding that the intent of the rule was to give all guilds equal footing to attempt and kill any mob.

Hopefully that wasn't the case because as we discussed earlier today that is a pipe dream that will never come true.

The rule in place on the back of guilds getting trained in ToV, and the rule was in place so that you no longer had to pull dragons all over the place and had an hour to go and kill them. For some reason Aftermath and Awakened still aren't doing that, but that was the intention of the rule when it was discussed.