Difference between revisions of "SetStage"

Jump to navigation Jump to search
105 bytes added ,  18:07, 26 July 2007
Added - no nest depth limit
imported>Entim
(removed an unneccessary 'the')
imported>Haama
(Added - no nest depth limit)
Line 15: Line 15:
*Always remember that Setstage only accepts stages that are defined in the quest's "Quest Stages" tab. When you try to set a quest stage that isn't defined, the stage-index doesn't change at all.  
*Always remember that Setstage only accepts stages that are defined in the quest's "Quest Stages" tab. When you try to set a quest stage that isn't defined, the stage-index doesn't change at all.  


*The stage result script will be proccessed immediately after the SetStage call. The main script containing the SetStage call will be halted until the result script is finished. It is even possible to use the SetStage command inside a stage result script. In this case the new stage result script will run in place of the SetStage command and the old stage result script will continue after the new one has finished.
*The stage result script will be proccessed immediately after the SetStage call. The main script containing the SetStage call will be halted until the result script is finished. It is even possible to use the SetStage command inside a stage result script. In this case the new stage result script will run in place of the SetStage command and the old stage result script will continue after the new one has finished. Unlike [[Activate]], it seems that any number of recursive SetStages are allowed (at least 20 possible).


*It is NOT possible to define variables inside a stage result script! The script will compile, but the variables will always be 0.
*It is NOT possible to define variables inside a stage result script! The script will compile, but the variables will always be 0.
Anonymous user

Navigation menu