Difference between revisions of "Talk:ScriptEffectUpdate"

1 byte removed ,  22:03, 24 August 2007
m
clarifying answer
imported>ShadowDancer
m (formatting)
imported>ShadowDancer
m (clarifying answer)
Line 71: Line 71:
[[User:Haama|Haama]] 16:33, 24 August 2007 (EDT)
[[User:Haama|Haama]] 16:33, 24 August 2007 (EDT)


:No, if the '''ScriptEffectFinish''' block is placed before the '''ScriptEffectUpdate''' block (which does not cause any problems that I can see), it will find the '''ScriptEffectFinish''' block before it finds the '''ScriptEffectUpdate''' block and finish the spell without running the '''ScriptEffectUpdate''' block.  Once a block is no longer valid, it won't run so this can be used to get around the '''Return''' command firing in a '''ScriptEffectUpdate''' block (although in my experience, most of the time a constantly active '''Return''' command isn't necessary in a '''ScriptEffectUpdate''' block). For instance in the following spell script:
:No, if the '''ScriptEffectFinish''' block is placed before the '''ScriptEffectUpdate''' block (which does not cause any problems that I can see), it will find the '''ScriptEffectFinish''' block before it finds the '''ScriptEffectUpdate''' block and finish the spell without running the '''ScriptEffectUpdate''' block.  If a block is not longer valid, it won't run so this can be used to get around the '''Return''' command firing in a '''ScriptEffectUpdate''' block (although in my experience, most of the time a constantly active '''Return''' command isn't necessary in a '''ScriptEffectUpdate''' block). For instance in the following spell script:
<pre>ScriptName SCAlterWeather
<pre>ScriptName SCAlterWeather


Anonymous user