Difference between revisions of "Talk:UpdateCurrentInstanceGlobal - Quest"

Talk:UpdateCurrentInstanceGlobal - Quest (edit)

1 byte added , 10:26, 16 April 2013

m

Anonymous user

@@ Line 1: / Line 1: @@
 == Usage and context? ==
-Although it looks quite simple, I wonder about the potential contexts which would make this function actually useful (if no mandatory for whatever reason). Although I don't really understand its usage scope yet in regards to its Wiki article (so please correct me if not to confirm what I'm writing), Here's how I see it :
+Although it looks quite simple, I wonder about the potential contexts which would make this function actually useful (if not mandatory for whatever reason). Although I don't really understand its usage scope yet in regards to its Wiki article (so please correct me if not to confirm what I'm writing), Here's how I see it :
 *1- I can get and set values on globals from within any script via global properties. No need of a quest to do so. Now, why would a quest require to "cache" some global variable, since we can use properties and work along these? I'm sure there's a legitimate reason, unfortunately I fail to see it at first glance, some explanation is required.
 *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 true?