Drape of Shadows

[Voragath]

I had to change my hotkey tonight. I noticed /pet back off was just a little too early and almost gave me aggro back. I barely squeezed in my invis before the mob was there because the mob was follwoing my pet and I was pretty close to the mob.

/pet stop
/alt activate 8341
/pause 12
/alt activate 3812
/pet back off

Having the pet come back after invis seemed safest since mob will sit there with mob beating on it. Once you hit fade, I noticed the mob just stands there and blinks at the pet since pets don't pull proximity aggro. A stopped pet is supposed to ignore aggro from things such as nukes so having the pet sit and wait for me to invis seems ok.

[Danille]

Found the perfect FADE hotkey:


/pet stop
/pet target
/pause 12,/alt activate 8341
/pet back off
/alt activate 3812

Drops hatelisted mobs
targets pet
casts drape
backs pet off
casts group invis

No need to worry about targeting pet, Very quick. Flawless every time.

[Voragath]

The pet doesn't need to be targeted at all, ever. The pet simply must be up. You actually don't have to target anything. If the pet is not up, you do get the message that you must select a target for the spell which is funny because so does Thauma if you don't have a target (Thauma doesn't need a target either to work).

[Merlaina]

So I had some problems with this AA recently and am wondering if anyone might know why. I was doing my rooftop of Beza thing and had a wizzy friend up there with me. I had cleared the central area and we were working on the catapult crews around the edges which are in packs of 3 or 4. I would pull with AA malo and then pretty immediately after hit drape (maybe 1 second later, so it goes off about two seconds after malo lands). I had no merc up and pet was on hold. The first time this worked fine. Mobs dropped aggro and walked back to their stations and I'd pet pull a straggler. The 2nd and 3rd times I tried this however all 3 mobs kept coming. I'm 99% sure I was still out of aggro range when drape finished casting, but there wasn't even a pause. It's as if I had never cast drape. On the 3rd pull I thought a few seconds after drape finished one of the three mobs momentarily dropped off my extended target window but then popped back on a second later. They were definitely in aggro range at this point so if drape had been delayed this would make sense.

Has anyone else had issues like this? Might it have just been lag and the server didn't get my drape request until a full second or two after I actually cast it? I've never really had lag issues before, but when you have 3 mobs running after you is not the best time to discover an AA isn't working as advertised. It had worked perfectly for me before those pulls (used it to pull maybe 6 times, though only twice in the fashion described above).

[Malleria]

Yep, had same issue. 9 times out of 10 it works exactly as described. Every now and then it acts as though it had never triggered. Pet on hold, no merc, 3 mobs inc, hit drape, nada. As you said, they don't drop from extended target, so it's unlikely to be re-agro. 100% chance my ass.

[Voragath]

I had this happen once out of 6 or 7 tries. And I was only using the spell malosenea rk. 3 to pull. I hit fade but nothing happened. So I kept pulling the same mob from the same camp the same way. Used fade at about the same distance every time and was pulling from max casting range. I did notice that one time after casting, it took another full second for fade to work after the initial casting was done. This is what might be the problem. Somehow, the tic is off. I also noticed something odd that happened the other night in convorteum: a mob will sometimes follow. In convorteum, a mob followed my pet for several minutes. Tonight, the mob came to my camp and stayed even when I moved; so this one came to me, parked itself, and decided NOT to be a stalker lol

Ok, just got it to happen again, this time the icon landed and everything but the mobs kept charging. There was some odd delay between cast and icon landing sound but the icon landed right away. Something is definitely wonky.

I wonder if there's some issue with how long it takes for mobs to show up on hatelist? Say, you cast malo, then immediately cast fade but the server thinks fade hit before the aggro? Maybe from lag or something.

[Merlaina]

Glad to know I'm not crazy or doing something wrong, sad to hear the AA might not be as reliable as advertised.

[Malleria]

I wonder if there's some issue with how long it takes for mobs to show up on hatelist? Say, you cast malo, then immediately cast fade but the server thinks fade hit before the aggro? Maybe from lag or something.

Eh, maybe, though in my instances of it failing they'd been agro'd atleast a full tick before I hit fade (I was pulling the mobs just outside of camp so enc could ae mez em).

[Voragath]

I wonder if there's some issue with how long it takes for mobs to show up on hatelist? Say, you cast malo, then immediately cast fade but the server thinks fade hit before the aggro? Maybe from lag or something.

Eh, maybe, though in my instances of it failing they'd been agro'd atleast a full tick before I hit fade (I was pulling the mobs just outside of camp so enc could ae mez em).

A full tic? So 6 seconds? That's a long time and the range for malo isn't that great. Where I was testing, if I waited more than 2 seconds after the spell landed, it was too late and they were in aggro radius. I'm guessing you were just in aggro radius if you were waiting a full tic. This is what seems to be messing people up. Aggro radius is a funny thing and seems to be the #1 cause for it failing. As for the failing right after casting at max range of a spell, then that's an actual issue. IIRC, doesn't the aggro radius of a mob increase when they are debuffed or attacked? Calling for help can be an issue too because they just might call for help from a mob that has a larger aggro radius, has bad pathing, or may end up warping on top of you.

[Malleria]

Er.. well, I didn't cast malo and stand there for 6 secs I was y'know, tagging and then running back to camp They were definitely out of agro range, and as I said, they never dropped from extended target anyway.