Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Suggestion] Remove entities with no components
See original GitHub issueRight now it is possible to remove all components on an entity and have a blank component-less entity orphaned in the pool. What do you think of adding a check on component removed that removes the Entity if it has no remaining components?
I have a few place in my code handling manual cleanup, but it would be really nice to have this handled by Entitas. I could see this having an issue with the OnComponentRemoved callback, but there may be a way to work around that.
Issue Analytics
- State:
- Created 7 years ago
- Comments:23 (17 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I was reading through the discussion again, but I still have the points in my head that I made earlier. I think your solution with a custom cleanup system as a last system in your list could solve this.
And yes, there is a way for having one system for multiple pools (pretty new feature): See AnimateDestroyViewSystem.cs
PoolExtension.cs