I had 2 guard spawners setup the same apart from their teams. I couldn’t figure it out why one was spawning and the other wasn’t. Maybe it’s not me, maybe it’s the engine somehow? So I wondered what would happened if I cut-and-pasted back the non-functional spawner? Turns out this fixed my problem.
I remember working on a different project using the Unreal Engine. Somehow copied instances of blueprints seemed to have messed up default objects or something like this and kept causing issues. I don’t remember the exactly what was going on, but it appeared as thought some config data was being saved under the hood by the engine in my project. I had to do a rework of the object using the exact same setup rather than doing a copy-paste from another. And the redo did something.
Thinking back on it now, I did duplicate the guard spawner through a copy and paste from the working spawner. This is very similar to what I did in the other project with Unreal Engine where I duplicated a Blueprint and things didn’t work as expected. In both cases it appeared as though something under the hood got messed up and reworking or cutting and pasting fixed them with the exact same parameter value settings afterwards too.
I wonder if this is related to file corruption or some type of corrupted data.
Anyways, hopefully this helps other people going forward. Sometimes just cut-and-paste as a last resort if it seems like things should be working.