I’ve been through the forums & answer hub. I’ve tried the guesses as to how to stop this. I wasn’t even editing the variable it decided it didn’t like. It’s hidden in the blueprint. I tried creating it again. Now there are 2 hidden variables with the same name. I made a new variable, but the mere existence of the hidden, invalidated variables prevents compilation. How do I re-expose the variable or delete it altogether?
Made a copy, got no message to delete bad variables when entering the editor…
Tried a reload, ha ha, wiped out work & changed nothing.
We’re discouraged from converting blueprints to C++, where I could trivially edit out the offending variables and get on with my work. Here, I’m trapped in a never-ending “can’t touch that.” How do I get past this, and how do I prevent the engine from doing this ever again??