Is there a reason for using HandleSpawnSystems collection for handling both spawns and despawns? Code (CSharp): // CharacterModuleShared public void HandleSpawns() { m_HandleSpawnSystems.Update(); } public void HandleDepawns() { m_HandleSpawnSystems.Update(); } Mistake maybe? Also, in CharacterModuleServer constructor, same collection is used for spawn and despawn systems: Code (CSharp): // CharacterModuleServer // Handle spawn CharacterBehaviours.CreateHandleSpawnSystems(m_world, m_HandleSpawnSystems, resourceSystem); // Handle despawn CharacterBehaviours.CreateHandleDespawnSystems(m_world, m_HandleSpawnSystems); HandleDespawnSystems is just empty collection.
Good find - It is a bug. It is already fixed and will end up on github on next full release. As you can see we have been trying out different ways to make it easy to add new systems, but also make it easy to get and overview of ordering of systems. We are not particulary happy with any of the solutions so this is something we will put some more effort into (hopefully making it harder for me to make this kind of bug )