Difference between revisions of "Bendu and S M Nodes"
m
no edit summary
imported>Lmstearn |
imported>Lmstearn m |
||
Line 1: | Line 1: | ||
'''''Or, a Brief Walkthrough Hooking the Bendu Quest onto the Story Manager.''''' | '''''Or, a Brief Walkthrough Hooking the Bendu Quest onto the Story Manager.''''' | ||
[[Image:DialogueInGame.png|900px]] | |||
==Introduction== | ==Introduction== | ||
Line 16: | Line 21: | ||
{{ProTip|<nowiki>Seasoned stagers can bypass the above and transpose just the methods to their own works.</nowiki>}} | {{ProTip|<nowiki>Seasoned stagers can bypass the above and transpose just the methods to their own works.</nowiki>}} | ||
==The Nodes== | ==The Nodes== | ||
Line 34: | Line 40: | ||
*This will bring up the quest tab, which is quite a useful shortcut, actually. Select the '''Quest Data''' tab and from the event drop-down list choose '''Script Event'''. Notice that the '''Start Game Enabled''' box is now greyed out. Now Ok out of all windows back to the main CK window and save. | *This will bring up the quest tab, which is quite a useful shortcut, actually. Select the '''Quest Data''' tab and from the event drop-down list choose '''Script Event'''. Notice that the '''Start Game Enabled''' box is now greyed out. Now Ok out of all windows back to the main CK window and save. | ||
==The Quest Script== | ==The Quest Script== | ||
Line 48: | Line 55: | ||
endFunction | endFunction | ||
*Save it and exit: let's review we have done so far. See [[Bendu_and_S_M_Nodes# | {{InDepth|<nowiki>All of the parameters excepting akLoc are unused here and can be removed, | ||
so GSQ01KeywordLocal.SendStoryEvent(akLoc = MixWaterMill) would work fine. | |||
Leaving them in shows how this function can work in relatively complex scenarios.</nowiki>}} | |||
*Save it and exit: let's review we have done so far. See [[Bendu_and_S_M_Nodes#Notes]] regarding the extra entry in the conditions. | |||
[[Image:S_M_Node.jpg|900px]] | [[Image:S_M_Node.jpg|900px]] | ||
Line 63: | Line 75: | ||
{{ | {{InDepth|One drawback of opting for "well used" objects like doors as activators, is that Papyrus will log those events more often. | ||
Also, the quest is being started unnecessarily every time we use the door during the quest. To limit Papyrus logging, conditions like GetStageDone can be employed. See Notes Below. | Also, the quest is being started unnecessarily every time we use the door during the quest. | ||
To limit Papyrus logging, conditions like GetStageDone can be employed. See Notes Below.}} | |||