target_practice 162 Posted February 28, 2020 I have been developing a number of scripts which involve storing UI elements as variables. I realised a while into their development that I've been forgetting to make use of disableSerialization, but despite this the scripts run without any issue, or even any errors. Simply put, how is this the case? Is there some kind of hidden consequence of not using the command? Share this post Link to post Share on other sites
opusfmspol 273 Posted February 29, 2020 Not using disableSerialization, my experience is, if you're storing UI elements in variables contained in a loop they work until you save, exit out and reload the saved game. You load the saved game and the UI variables come back nil. Causes errors. If defined within a script being called, spawned, etc. (not part of a loop), they may work. But sometimes not. Using disableSerialization prevents the script from saving, and therefore it won't run when the loaded save is played (prevents errors). It's something about, you can define (store) a UI element in a variable, but you cannot save a UI element in a variable. They're not persistent in a reloaded saved game. But I don't fully understand disableSerialization myself and look forward to hearing from others with knowledge. I'm just starting to delve into UI namespace. Some UI's I'd like to keep up after reloading a save, and I find disableSerialization in their scripts. 1 Share this post Link to post Share on other sites
target_practice 162 Posted February 29, 2020 If that's the only consequence, then it doesn't cause me any problems specifically as aforementioned scripts are part of a multiplayer gamemode I'm developing, but I'll still try to ensure I use it from now on to be safe. On a bit of a tangent though, is it really true that save games contain both active scripts and their state at the time the game is saved? Because I didn't know that. Share this post Link to post Share on other sites
