I’m soooo glad I found this thread. Not because it’s helpful for me in the moment, but this BUG caused me days worth of grief and SOOO much wasted time when adding a game mode to a large project recently. Worked fine in the editor until reopening the level. All of the BP’s in the level were various children of a parent with a bunch of config vars that would change their behavior. Packaging the game and opening the level… all the bps would be reverted to parent’s default! I’d spend two hours customizing each one in the level to function how it should… and bam all undone. After two or three times I got wiser and just edited one or two for testing… never got a resolution (but i did make a workaround)
I reported the issue in answerhub and cited previous chains of people having the issue. But of course I ended up with the standard (maybe understandable but extremely frustrating) response of “if you can’t reproduce it in a fresh project we can’t help you”. Well my last comment on the thread was “well I can’t repro it in a fresh project… but its 100% a bug and its in the editor not in my code.” Then its just been lodged in my as one of those annoying things that eat at you.
So I’m glad something is getting done about it finally. The repro steps I’ve seen above don’t match my issue… I didn’t have a get all actors node and wasn’t using a template of any kind… but the issue is probably still the same. I’ve added ridiculous macros and pipe them into “begin play” that essentially just have every variable SET node i need to customize at runtime and then it sets them all on begin play.(setting in the editor panel doesnt resolve, i tried) Silly work around, and if you want to use const script to do this customization in the editor and see the updates real-time you’re SOL.
Reference to my thread from a couple months back just as an FYI: