[=;296888]
That even gave me a bluescreen once . :rolleyes:
From my expierience, the BP system does not take too kindly on changing variable types etc.
If you are not following the exact ritual of:
-Unwiring all pins of that variable in use
-Change the type of the variable.
-Recompile the BP
-Refresh nodes where still neccessary
-Rewire again
If you follow that, it works, if not, you are playing Russian Roulette and each time another round gets added to the drum…
The same goes for:
-Create a struct
-Create a variable of that struct and fill it with values
-Change the type of one of the struct members
Sometimes the variable of the struct is just “blank” again, no values stored.
But again, it sometimes crashes the editor.
I havent made extensive tests, but this seems to happen only if the former type that was changed from was “pointer style” like a mesh or material reference.
If it was just a float or int, etc, its usually ok…
This makes iterations, especially for beginners who fiddle a lot, extremely “difficult” 
[/]
It also defeats the very thing blueprint was designed to do. It’s not practical at all to try to unwire everything in all of your blueprints if you need to change a struct. I’d be totally happy with a crash 3 times an hour as long as things don’t corrupt 