SetStage

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 stage-index doesn't change at all.

• The stage result script will be processed 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 250, tested from the same quest, are possible).

• 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