Bug 863: (Developer) When I use Shadow Step in a ma...

[BugTracker]

Bug ID       : 863 - When I use Shadow Step in a ma... 
Bug Date     : 2016/11/27 02:52:20
Assigned To  : Developer
Priority     : Low

Category     : VGClient
Sub-Category : Gameplay: Ability
Severity     : Standard
Reproducible : Every time

Details:
When I use Shadow Step in a macro, I warp behind the mob as I'm supposed to, however the ability that is macro'd with Shadow Step (Harrow, in this case) does not fire. I get a message "You do not have a valid target for Harrow I."

Since Harrow requires you to be behind the mob, there must be some timing problem with the firing of Harrow (i.e. it fires immediately after Shadow Step is invoked, but before I am actually moved into place to make Harrow a valid ability).

Originated From World: New Telon (1)
Chunk                : Tursh Village (144)
Location             : -7831 6401 40689

Entered on Nov 27, 2016 07:47 by theFoof
Not sure on the mechanics on this one.

[Jakkal]

They have it right. You should be able to shadowstep and harrow. It's listed on some websites as a common DK macro. Harrow is listed as inactive in the DBE though.

[Xinux]

The issue is right now using that macro Harrow fires as soon as you hit the macro. What should happen is you cast shadow step the server then wait's for the next ability to be cast like Harrow then the server fire's off shadow step then Harrow.

[Jakkal]

So really, right now, players should be testing single abilities and not try to stack them in macros? (Asking so I can add it to the "What you should be testing" list).

[Xinux]

Macro's should work fine as long as one ability doesn't require another like Shadow Step.

[Faux]

I added a lua function to check to see if a player's "warp" flag is set. We just need to add that to the precast for those spells that require you to be behind the mob. Or we can change the location of the warp check to be in the casting code, but then we don;t want it to trigger off of casting a group buff though.

So option a) Check for warp flag in precast check. If set, ignore range check.

option b) Move processing of warp check so you warp immediately upon activating the next ability, but we'll need to make a check to see if its a combat ability. Could probably use target_type == 1 for this.

[Faux]

I'll be around tonight to change those scripts to get the last bit of that system working so your positional attacks will work.

[Faux]

This should be fixed now