Difference between revisions of "Talk:UpdateCurrentInstanceGlobal - Quest"
Jump to navigation
Jump to search
Talk:UpdateCurrentInstanceGlobal - Quest (edit)
Revision as of 10:49, 16 April 2013
, 10:49, 16 April 2013→Usage and context?
imported>HawkFest |
imported>HawkFest |
||
| Line 5: | Line 5: | ||
*2- As for quests, from what I understood in the Wiki, they hold a "copy" (like some cache) of any global declared in their quest text global list. Thus if a global is modified outside some quest script, UpdateCurrentInstanceGlobal would be put into action so as to update that "quest's Globals cache" (the Global in question). Is this a correct assertion? | *2- As for quests, from what I understood in the Wiki, they hold a "copy" (like some cache) of any global declared in their quest text global list. Thus if a global is modified outside some quest script, UpdateCurrentInstanceGlobal would be put into action so as to update that "quest's Globals cache" (the Global in question). Is this a correct assertion? | ||
*3- For all other instances where (one Global = one shared value for all), and from what I understand here, I don't see the value of putting a global variable into some quest global list, if not for the laziness of declaring global properties in whatever script depending on such quest (but one would have to declare it anyways in the quest's global list and refer to it from "outside scripts" via the quest's prefix and make reservations in the code design for the use of UpdateCurrentInstanceGlobal and...... Not a so "lazy" shortcut in the end...). | *3- For all other instances where (one Global = one shared value for all), and from what I understand here, I don't see the value of putting a global variable into some quest global list, if not for the laziness of declaring global properties in whatever script depending on such quest (but one would have to declare it anyways in the quest's global list and refer to it from "outside scripts" via the quest's prefix and make reservations in the code design for the use of UpdateCurrentInstanceGlobal and...... Not a so "lazy" shortcut in the end...). | ||
*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 | *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) | ||