Ah yes, it is. And is there a list of known issues, I can only Linux known issues, and it would help so that i do not repeat what you already know? There is also a loop where not all can be compiled, so I’ll have to keep that in mind. Didn’t notice this before, sorry about that. But would this also cause the one blueprint (mazepeice BP) somewhere in the chain is compiled to clear its variable refs on play? (The bp is never touched either) It also clears var refs after I hit compile on it directly while the others keep theirs. It’s the only blueprint that acts this way so far. Even when others are “dirty” they would still work fine.
And it doesn’t seem like a workaround as MazePeice bp is still being problematic on anything I try to do it.