Referencing Level Blueprint Variables prevents saving?
I've run into a roadblock and would love your advice.
In conclusion, it feels like these save error messages are intended... but if the game compiles with no errors, and everything works at runtime, why would I not be allowed to save these changes? This is a strange exception to the rule.
For default game variables, save them in your Default Game Mode, particularly if you are using a asset in multiple levels. The problem is that the variables you are trying to reference do not exist in the current context because the map that houses those variables is not loaded. The Default Game Mode class, however, stays constant even between levels unless you explicitly change it. You would have this same problem with C++, because the problem is that they don't exist.
answered Jan 04 '15 at 08:19 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here