Pause between spells! Options

[Sikret]

There's no any reasonable need to ensure delay between spells - game engine is perfectly doing this job on it's own.

No, if you use "ForceSpell" instead of "SpellNoDec" the game's engine will not ensure the delay. If "ForceSpell" is used the timer is needed to ensure the delay, because without it the caster will cast in improved alacrity.

The point is that people used to think that when the spell is not memorized by the spellcaster, they needed to use "forceSpell" action and consequently, it is natural that they need the timer to ensure the delay.

However, my point was that you can use"SpellNoDec" even when the spell is not memorized and "SpellNoDec" doesn't need the timer to ensure the delay.

The error in the tutorial in question was not about the code itself, but about a false comment inside the code. I don't think that the comment is ambiguous or unclear. It's plainly false.

[Sikret]

You need the timer, because it is a cast n attack stuff. If i recall correctly SpellCastNoDec has time, if you don't have a delay, the forthcoming attack will break it, no?

No, it won't! The forthcoming action will not start till the spell is finished.

Furthermore, I didn't start this topic to discuss "cast and attack". It was about the delay between spells and I informed everyone that they can use "SpellNoDec" without any need to a timer if they want to ensure the delay between spells.

Since SimDing has recently linked to this post (from another forum), I need to clarify a point:

The timers he refers to exist in IA's scripts but not for the reason he said and had in mind (i.e. not because the action will be interrupted by the forthcoming atatck and not because ensuring the pause between spells as SpellNoDec does take care of it).

The timer does something quite different. Without the timer the creature running the script will pick his target for the next action prematurely. For example, he will cast his first spell and will immediately pick his target for his second spell even though he can't yet cast it (for the pause). Consequently, if this newly and prematurely picked taregt becomes invisible during the pause, the creature will lose his target for the spell. The timer is there to ensure that the creature will not try to pick his next spell's target before its due time.

[SimDing0]

i.e. not because the action will be interrupted by the forthcoming atatck

Actually, I said it prevents the creature immediately queuing the next action. Subtle difference. The timer's there for the reason I said.