The problem with repro for this specific issue is that it would take even more of my precious time. The issue is sporadic, and as far as I can tell there is no specific trigger for it. I’ll go two weeks at a time without any issue, then suddenly all of the child actors of a parent will have certain of its variables reset. I then have to spend hours debugging, because it’s not immediately obvious to me that that’s what caused the issue.
It seems to be some sort of architectural issue, and I’m sure an expert programmer could spot it eventually.
I won’t repro it, for the reasons stated above, but if you’d like to try a bit harder, below are some recommendations to generate the issue:
Create a blueprint actor with numerous variables (try all types… vectors, enums, booleans, etc.). Create numerous child actors from the parent and place them around a level, and set each of them to have different values from the parent. From here, experiment with then making code changes to the parent and saving them, or making changes to the level, or even creating a c++ class and having the parent inherit from that. I would also try forcing a crash of the editor, as that seems to have some relevance.
I should also add that the problem becomes more consistent when editable variables on a blueprint actor in a level reference another blueprint actor in the level. I’m thinking this might have something to do with the order of objects being instantiated on level load? If actor 1 references actor 2, and actor 2 references actor 1, it is usually a matter of time before one of those references changes back to None.