-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Closed
Labels
A-ECSEntities, components, systems, and eventsEntities, components, systems, and eventsC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to useS-BlockedThis cannot move forward until something else changesThis cannot move forward until something else changes
Milestone
Description
What problem does this solve or what need does it fill?
When attempting to resolve system order ambiguities, it can be very challenging to track down and eliminate ambiguities when multiple copies of the same system exist.
This is particularly common and brutal for apply_system_buffers, as we have many copies of this system in each schedule and they conflict with everything.
What solution would you like?
- Add this field (off by default).
- When this field is set to
true, report all system sets that the conflicting systems are part of.
e.g apply_system_buffers (CoreSet::PostUpdateFlush), my_system (no sets)
Additional context
Please don't do this until #7267 is merged for the sake of my sanity.
Metadata
Metadata
Assignees
Labels
A-ECSEntities, components, systems, and eventsEntities, components, systems, and eventsC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to useS-BlockedThis cannot move forward until something else changesThis cannot move forward until something else changes