Conflagrate post 2.1

VioL8oR · 05/24/07, 9:45 PM

With the change to conflagrate-button (it beeing grayed out as long as immo isnt up on target), ive found it to give a realy annoying delay when you immo->conflag combo.
Is this just me, is it stated by blizzard, and if so was it intended?

Cryect · 05/24/07, 9:57 PM

Prolly was intended change that effects if I had to guess other spells like swiftmend as well. Doesn't seem to be effecting dispells though. Makes sense to move it client side but yeah now you have the extra latency of seeing the event message.

BTW who else thought this was going to be about General Drakkisath.

VioL8oR · 05/24/07, 10:09 PM

Nice work by blizzard to "fix" something that wasnt even broken to begin with...

Theras · 05/24/07, 10:12 PM

Another irritating side effect of this change is that it screws up macros that have target-based conditionals. For example, I have a Righteous Defense macro that will cast it on my target if it's friendly, or my target's target if they aren't friendly (but the ToT is friendly). If I don't have a target, first of all the ? icon for the macro doesn't properly change to the Righteous Defense macro, and secondly I don't get a tooltip unless I have a target.

These are some greatly frustrating side-effects from what appears to be a wholly unnecessary cosmetic change.

Kyne · 05/24/07, 10:42 PM

Concerning Theras' post, I have an updated Righteous Defense macro that works the way the old macro tended to. There's been a lot of posts up on the Paladin forums about the same problem and the following macro should work similarly to your previous one:

/cast [help] Righteous Defense; [target=targettarget,help] Righteous Defense

I hope this helps.

About the delay in Conflagration, I'm certain you could construct a macro to allow for Immolate to cast before causing a delay in activating the spell. Have you tried basic stop spell-casting macros?

• frmorrison · 05/25/07, 12:09 AM

Try
/cast Immolate
/stopcasting (Use Quartz so you know when to hit the macro again)
/cast Conflagrate

I tested Conflag on the PTR, and had no problems using Immo + Conflag.

Calantus · 05/25/07, 1:23 AM

The most irritating part of it is how it affects shields. You can't cast PW:S on someone until after the client says you can, whereas before you could hit it when you knew the cast would hit the server right after the weakened soul debuff went off. Basically weakened soul now prevents a new shield for 16 seconds instead of 15, depending on your latency.

Darkmantle · 05/25/07, 2:55 AM

Why they disabled casting the spell instead of just having a visual effect is beyond me.

frmorrison what is your general latency?

The issue as say an australian is that before I could send the message to conflag as soon as immolate had finished without having to wait for conformantion. Now i have to wait for immolate to be applied and then the message sent back before I can start sending the conflag message.

Theras · 05/25/07, 3:05 AM

Originally Posted by Kyne

Concerning Theras' post, I have an updated Righteous Defense macro that works the way the old macro tended to. There's been a lot of posts up on the Paladin forums about the same problem and the following macro should work similarly to your previous one:

/cast [help] Righteous Defense; [target=targettarget,help] Righteous Defense

I hope this helps.

I don't think you quite understood what I was saying. The actual macro works fine. The tooltip and spell icon don't show up, though, unless I have either a friendly target, or a hostile target that has a friendly targeted.

PsiVen · 05/25/07, 3:34 AM

My macro is actually set to Hammer of Wrath if it's an enemy target, and taunt ToT if I alt-cast. I added this line and it doesn't have any strange icon/tooltip changes anymore:
#showtooltip Righteous Defense

Theras · 05/25/07, 3:44 AM

Originally Posted by PsiVen

My macro is actually set to Hammer of Wrath if it's an enemy target, and taunt ToT if I alt-cast. I added this line and it doesn't have any strange icon/tooltip changes anymore:
#showtooltip Righteous Defense

That fixed it. You're my hero! ♥♥♥♥♥

Kyth · 05/25/07, 5:09 AM

I'm very used to immolate followed by a fast conflag when doing burst on various things, and I now have to pause for a split second before casting the immolate -- basically makes it unusuable for how I often use it. Very annoying.

zirky · 05/25/07, 8:57 AM

PsiVen - I assume you can put the line #showtooltip XXXXXX on any macro, does it have to be in any specific location in the macro?

• Chicken · 05/25/07, 8:58 AM

Originally Posted by zirky

PsiVen - I assume you can put the line #showtooltip XXXXXX on any macro, does it have to be in any specific location in the macro?

I'm pretty certain it always has to be on top.

Cel · 05/25/07, 9:11 AM

There was something about dynamically updating tooltips in 2.1. How exactly is that done? I believe this was in regard to /castsequence macros.

Kiralyn · 05/25/07, 9:24 AM

There is a post on the WoW bug forums about this, but no reply as of yet. I've done a fair bit of testing and it seems that client/server latency is the issue, as the conflag checks at the client side for immolate and not the sever side, so we see a delay as the client reports to the sever that immolate was cast, and then has to get confirmation back before allowing conflag to be cast. From what I can tell there is no way to force the cast if the initial check fails. However, I havn't tried /stopcating before the conflag. Can anyone test this? I'm stuck at work.

WoW Bug report
http://forums.worldofwarcraft.com/th...05892655&sid=1

Warlock's Den Discussion thread
http://wowmb.net/forums/showthread.php?t=15331

Ichal · 05/25/07, 9:28 AM

Misunderstood and OT. Disregard.

talzar · 05/25/07, 9:31 AM

Well now that the person above me edited their reply out, mine wouldn't make any sense.

Brissa · 05/25/07, 9:42 AM

While we are roughly on the subject Im wondering if anyone has a solution to my problem.

I have a macro for all my stance switches that are coupled with stance specific skills so for example switching to battle stance is coupled with overpower.

/cast [stance:1] Overpower; Battle Stance;

This casts overpower in battle stance and if not it switches to battle stance. The problem is that previously this macro only lit up when it was possible to use overpower (since its the first skill in the conditionals list) but now it is always lit up since it is always possible to switch to battle stance.

Is there any way to have this revert to the original functionality?

• Chicken · 05/25/07, 9:47 AM

Originally Posted by Brissa

While we are roughly on the subject Im wondering if anyone has a solution to my problem.

I have a macro for all my stance switches that are coupled with stance specific skills so for example switching to battle stance is coupled with overpower.

/cast [stance:1] Overpower; Battle Stance;

This casts overpower in battle stance and if not it switches to battle stance. The problem is that previously this macro only lit up when it was possible to use overpower (since its the first skill in the conditionals list) but now it is always lit up since it is always possible to switch to battle stance.

Is there any way to have this revert to the original functionality?

Put this at the top of your macro:
# show Overpower

# show, and # showtooltip are basically overrides for the standard behavior of the macro's buttons, the conditional changing of what the button does just means they're more useful now than before.

Vodrin · 05/25/07, 11:33 AM

fyi;

/cast [help] [target=targettarget,help] Righteous Defense

will now work if you want to save space in a long macro. If any of the conditionals, from left to right, evaluates to true it skips the rest and casts the spell using that conditional for targetting etc.

Brissa · 05/25/07, 11:46 AM

Originally Posted by Chicken

Put this at the top of your macro:
# show Overpower

# show, and # showtooltip are basically overrides for the standard behavior of the macro's buttons, the conditional changing of what the button does just means they're more useful now than before.

Great, thanks.