Difference between revisions of "SetStage"

From the Oblivion ConstructionSet Wiki
Jump to navigation Jump to search
imported>JustTim
imported>JOG
(Layout, see also, minor editing)
Line 4: Line 4:
  SetStage MS27 30  
  SetStage MS27 30  


Sets the specified quest stage to "Done", and resolves any of the attached stage items that pass their conditions (runs results, adds to quest log, completes the quest if it should).  
Sets the specified quest stage to "Completed", and resolves any of the attached stage items that pass their conditions (runs results, adds to quest log, completes the quest if it should).  


If this is the first stage of the quest to be added to the journal, the player will receive a "Quest Added" message on screen.


Also, if the quest is not currently running, SetStage will automatically start it.
'''Notes:'''


*If this is the first stage of the quest to be added to the journal, the player will receive a "Quest Added" message on screen.


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 the Stageindex doesn't change at all.  
*If the quest is not currently running, SetStage will automatically start it.  


*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 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.


*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! It will compile, but they'll always be 0.
 
==See Also==
[[GetStage]]
 
[[GetStageDone]]
   
   


[[Category: Functions]]
[[Category: Functions]]
[[Category: Quest Functions]]
[[Category: Quest Functions]]

Revision as of 09:35, 31 July 2006

Syntax:

SetStage QuestID StageIndex 

Example:

SetStage MS27 30 

Sets the specified quest stage to "Completed", and resolves any of the attached stage items that pass their conditions (runs results, adds to quest log, completes the quest if it should).


Notes:

  • If this is the first stage of the quest to be added to the journal, the player will receive a "Quest Added" message on screen.
  • If the quest is not currently running, SetStage will automatically start it.
  • 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 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.
  • It is NOT possible to define variables inside a stage result script! The script will compile, but the variables will always be 0.


See Also

GetStage

GetStageDone