Difference between revisions of "Talk:UpdateCurrentInstanceGlobal - Quest"
Jump to navigation
Jump to search
Talk:UpdateCurrentInstanceGlobal - Quest (edit)
Revision as of 15:16, 21 September 2013
, 15:16, 21 September 2013→Usage and context?
imported>HawkFest |
imported>Egocarib |
||
| Line 7: | Line 7: | ||
*4- '''The only context that I can see, is when some global should "hold" two possible values at the same time: one set within the quest's context, and another one for the rest of the game. Consequently, when the quest stops, the original Global is still available and untempered by the mod's quest itself (which is a good thing in terms of mod management : removing a mod having a quest modifying some Global would leave the corresponding vanilla Global untouched). Am I right?''' | *4- '''The only context that I can see, is when some global should "hold" two possible values at the same time: one set within the quest's context, and another one for the rest of the game. Consequently, when the quest stops, the original Global is still available and untempered by the mod's quest itself (which is a good thing in terms of mod management : removing a mod having a quest modifying some Global would leave the corresponding vanilla Global untouched). Am I right?''' | ||
--[[User:HawkFest|HawkFest]] ([[User talk:HawkFest|talk]]) 2013-04-16T11:25:55 (EDT) | --[[User:HawkFest|HawkFest]] ([[User talk:HawkFest|talk]]) 2013-04-16T11:25:55 (EDT) | ||
:*The fact that globals set up in quests retain their original value could be useful if you are running a quest that needs to base itself off of conditions that exist when it first starts, and continue basing itself off those conditions throughout the quest. Maybe, for instance, if you start the quest on a rainy day, a whole different storyline unfolds, and in order to remain consistent throughout, that same storyline (which relies on the globalVariable at the quest's start) needs to reference that variable at different times as the quest progresses. | |||
:*RE: your number 4 - if the quest stops, the global will not be returned to an original value as you seem to suggest. They quest's snapshot of what the global was when the quest started will simply evaporate. (apologies if I'm misunderstanding you there). | |||
:*And just a clarification for anyone wondering about broader functionality - you don't ever need to use this function if you are retrieving a Global Variable's value via '''getValue()''' in a script or script fragment - that function will always return the true current value of the Global Variable property in question. --[[User:Egocarib|Egocarib]] ([[User talk:Egocarib|talk]]) 2013-09-21T16:16:20 (EDT) | |||