Lag and You (Mod related) - Page 4

Stein · 12/04/06, 7:32 PM

is there any state or action that could prevent /stopcasting from executing? if so, you could protect the current cast in that way....

/script checkCastBufferAndEnterUnStoppableModeIfNotReady
/stopcasting (which would fail if current cast was protected)
/cast ____
/script ifInUnStoppableModeLeaveUnstoppableMode

Cluey · 12/04/06, 9:21 PM

Originally Posted by Stein

is there any state or action that could prevent /stopcasting from executing? if so, you could protect the current cast in that way....

/script checkCastBufferAndEnterUnStoppableModeIfNotReady
/stopcasting (which would fail if current cast was protected)
/cast ____
/script ifInUnStoppableModeLeaveUnstoppableMode

You can't use /script in macros.
That is why /stopcasting and other similar things, which used to require a script command, were added.

• Shalas · 12/04/06, 10:13 PM

Originally Posted by Cluey

You can't use /script in macros.
That is why /stopcasting and other similar things, which used to require a script command, were added.

Yes, you can. They just added a few things to the list of stuff non-blizzard code is blocked from doing.

Kalman · 12/04/06, 10:14 PM

Originally Posted by Shalas

Originally Posted by Cluey

You can't use /script in macros.
That is why /stopcasting and other similar things, which used to require a script command, were added.

Yes, you can. They just added a few things to the list of stuff non-blizzard code is blocked from doing.

Like targeting and casting.

Calantus · 12/04/06, 10:26 PM

My favourite part of fastcast is actually the channeling protection. If I only hit my button once it doesn't always fire (at the end of a previous cast, end of a cooldown, etc). That's plenty fun when I really need the spell to go off fast. If I hit my button more than once I'd often cancel it just after it fired if the first click worked, wasting mana and a cooldown. When I put 2 seconds of channel protection up I can spam the button in that 2 second window until it fires and not risk cancelling it early. Does anyone know if that functionality would be possible in the xp?

• Chicken · 12/05/06, 5:29 AM

Originally Posted by Calantus

My favourite part of fastcast is actually the channeling protection. If I only hit my button once it doesn't always fire (at the end of a previous cast, end of a cooldown, etc). That's plenty fun when I really need the spell to go off fast. If I hit my button more than once I'd often cancel it just after it fired if the first click worked, wasting mana and a cooldown. When I put 2 seconds of channel protection up I can spam the button in that 2 second window until it fires and not risk cancelling it early. Does anyone know if that functionality would be possible in the xp?

There's a modifier for macros called [channeling], you could probably protect the spells that way. It'd make channeled spells suffer from an extra delay before you could recast them if you have a noticable latency though.

For instance you could do, say:

/cast [nochanneling] Mind Flay

And it'd only cast Mind Flay if you're not channeling any other spells at the time. But as I said above, it'd probably make channeled spells suffer from the same issues normal spells do.