Difference between revisions of "Talk:Variables and Properties"
Jump to navigation
Jump to search
Talk:Variables and Properties (edit)
Revision as of 18:14, 12 February 2017
, 18:14, 12 February 2017→Adding Properties on Script in Current Game
imported>Lisselli |
imported>Marth |
||
| Line 220: | Line 220: | ||
:From my understanding, all properties are baked into the save the moment the game is loaded. ObjectReferences tend to be a bigger issue because the properties pointing at them, will make them persistent. So in practice, one should use ObjectReference properties when absolutely necessary, and never no more than what you need. There's a clearer info on this but the page is inaccessible at the moment. --[[User:Lisselli|Lisselli]] ([[User talk:Lisselli|talk]]) | :From my understanding, all properties are baked into the save the moment the game is loaded. ObjectReferences tend to be a bigger issue because the properties pointing at them, will make them persistent. So in practice, one should use ObjectReference properties when absolutely necessary, and never no more than what you need. There's a clearer info on this but the page is inaccessible at the moment. --[[User:Lisselli|Lisselli]] ([[User talk:Lisselli|talk]]) | ||
::I could be wrong here, but its not just ObjectReferences. Now, this could be because I wasn't adding Properties to an ObjectReference, but in fact adding Properties to the Base Item. Because there was hundreds of child ObjectReferences, and filling each one was too monumental. It appears to have cascaded down to the objectReferences in terms of filling these Properties though, however, if those ObjectReferences were already baked in to the game, adding Properties would always return a Null (None) value. Those Properties could be a Boolean array, MiscObject, Static, etc,etc. In terms of adding Properties to a child Object Reference in some cell that has a script attached to it, that I do not know if the same thing occurs. | |||