Difference between revisions of "Cross Script Variables"

53 bytes added ,  08:35, 24 December 2010
imported>Bruneauinfo
imported>Bruneauinfo
A scenario for creating and testing this type of functionality includes at least three features:
 
1 - A quest script that acts as the database for storing values. (One might want to read over the article [[Quest scripts]] to get familiar with the source of this idea.)
 
2 - A script that writes a value to one of the variables in the "database" Quest script when it is activated.
====Notes====
 
*YouIf should NOTyou assign starting values to your variables. Ifin youthe need"database" script use a doOnce variable to dokeep this,the dovariables itfrom usingbeing somereset otherto method.their Settinginitial values withinon thisevery scriptframe essentiallyrefresh. locksSetting thevalues valuewithin in.this script's ThereBegin-End mayblock bewithout a workarounddoOnce forwill doingessentially this,"lock butin" morethe testingvalues willto their beinitial requiredsetting.
 
*The variable names listed in the script can be named whatever you like - preferably something meaningful to their purpose.
</pre>
 
If you use this script exactly as written the message box will show the name of your reference rather than the reference. See [[MessageBoxEx]] for more. But the reference value is there and ready to use.
 
== Practical Applications ==
Anonymous user