67
edits
Difference between revisions of "Talk:EffectWasDualCast"
m
no edit summary
m |
|||
| Line 1: | Line 1: | ||
Most likely this function checks for the 'IsCastingDual' animation variable, and returns true, if 'IsCastingDual' is also true. The problem is, it looks like 'IsCastingDual' is true only while dual casting animation is playing - thus, if the ranged spell has a slow moving projectile, or if spell's target is far enough, a situation is possible when animation stops playing before the projectile hits the target; if this happens, 'IsCastingDual' '''often''' returns false, and, as a result, 'EffectWasDualCast' also returns false. | Most likely this function checks for the 'IsCastingDual' animation variable, and returns true, if 'IsCastingDual' is also true. The problem is, it looks like 'IsCastingDual' is true only while dual casting animation is playing - thus, if the ranged spell has a slow moving projectile, or if spell's target is far enough, a situation is possible when animation stops playing before the projectile hits the target; if this happens, 'IsCastingDual' '''often''' returns false, and, as a result, 'EffectWasDualCast' also returns false. | ||
Correct work of this function depends on projectile speed - | Correct work of this function depends on projectile speed - a spell’s '''projectile guaranteed to be considered as dual casted for ~0,9 seconds after being casted''', because this is the approximate duration of dual casting animation's 'fade-out' after the spell was casted; for instance, for ‘Calm’ spell which projectile has (default) speed of 2200 units/sec, max fail-safe distance is ~2000 units / ~95 feet / ~29 meters, and for 'Thunderbolt' this function always correctly checks the casting state, because although having aimed delivery, this spell's projectile has very high speed. --[[User:Ingvion|Ingvion]] ([[User talk:Ingvion|talk]]) 11:55, 12 July 2023 (EDT) | ||