-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Open
Labels
A-StatesApp-level states machinesApp-level states machinesC-BugAn unexpected or incorrect behaviorAn unexpected or incorrect behaviorD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!
Description
What problem does this solve or what need does it fill?
When you use DespawnOnExit, you need to ensure it is only used on the top level parents and is the only thing despawning the items.
Failing to do this will fill your logs with warnings while not a huge issue, it can bury other actual problems.
I would like a TryDespawnOnExit that will ignore despawned entities, as semantically I am saying "you should ensure it is despawned" rather then "You must be the one to despawn the entities".
Saves having to filter out logs that may contain more valuable information.
What solution would you like?
Either modifying DespawnOnExit or adding TryDespawnOnExit
What alternative(s) have you considered?
Using Tracing to filter out logs.
Making my own despawn component and activating on state transition.
I am currently marking components to not despawn.
Additional context
Metadata
Metadata
Assignees
Labels
A-StatesApp-level states machinesApp-level states machinesC-BugAn unexpected or incorrect behaviorAn unexpected or incorrect behaviorD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!