Add a way to refer back to a common deep ancestor 🦑 #5534
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
This allows querying for a potentially far-off ancestor in the bevy
hierarchy with the
Ancestor
component.Motivation
I found myself needing such components a lot in #5378,
I think it might also have a few other applications.
Solution
It's a very simple system that recursively traverse the children of an
entity marked with a
MarkDescendants
component, and adds aAncestor
component to entities that comply to a rule provided in the
MarkDescendants
component.drawbacks:
components once. No dynamically updating the
Ancestor
componentto account for runtime changes to the hierarchy.
providing a generic system and letting the user add the system with
their prefered query filter.
mark_descendants
system themselves.Changelog
MarkDescendants
andAncestor
components to make deep hierarchical relations easier to handle