Difference between revisions of "Local variable"

From Dragon Age Toolset Wiki
Jump to: navigation, search
(category)
(SetLocalLocation is in the "avoid" category)
Line 15: Line 15:
 
*[[SetLocalCommand]]
 
*[[SetLocalCommand]]
 
*[[SetLocalItemProperty]]
 
*[[SetLocalItemProperty]]
 +
*[[SetLocalLocation]]
  
 
These functions do *NOT* work the way that the first five do.  The major issue with this second set of functions is that they are not saved/loaded via the save system.  So, if a community member or designer wants to save information like this for use later, and someone saves/loads the game, that information is lost forever.  Thus, using them outside of situations where you can guarantee no save/load occurs (i.e. during combat) is pretty much guaranteed to fail for some enduser.  Furthermore, if you use these variable types in the var_ 2DAs, it will fail gloriously.
 
These functions do *NOT* work the way that the first five do.  The major issue with this second set of functions is that they are not saved/loaded via the save system.  So, if a community member or designer wants to save information like this for use later, and someone saves/loads the game, that information is lost forever.  Thus, using them outside of situations where you can guarantee no save/load occurs (i.e. during combat) is pretty much guaranteed to fail for some enduser.  Furthermore, if you use these variable types in the var_ 2DAs, it will fail gloriously.

Revision as of 16:21, 1 September 2009

There are a number of SetLocal* functions in the game engine. The five that are of use to you (that Programming fully supports) are:

These functions work and have been through the fire of QA for many months. They are solid and work well.

There are a number of other functions that happen to exist such as:

These functions do *NOT* work the way that the first five do. The major issue with this second set of functions is that they are not saved/loaded via the save system. So, if a community member or designer wants to save information like this for use later, and someone saves/loads the game, that information is lost forever. Thus, using them outside of situations where you can guarantee no save/load occurs (i.e. during combat) is pretty much guaranteed to fail for some enduser. Furthermore, if you use these variable types in the var_ 2DAs, it will fail gloriously.

Don’t use these functions. They will in all likelihood be removed in a future patch.