Bevy system scheduling
Organizes the order in which game systems read and change entity data. It expresses real dependencies so spawning, movement and combat stay correct when unrelated systems are rearranged.
bevy-ecs-scheduling
See how it helpsWhen is it useful?
Use when Bevy systems depend on data created by other systems during the same update.
What does it help you do?
- Maps component ownership and conflicting access before separating processing systems.
- Defines explicit ordering, including when deferred commands become visible to consumers.
- Separates global configuration from entity state using narrow queries and stable identifiers.
Try asking this
In our arena, spawn an enemy through deferred commands and let the targeting system find it in the intended update. Map the spawn, movement and damage dependencies, then reorder an unrelated animation system. Combat behavior should remain correct without relying on registration order.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Bevy — ecs scheduling
Use when designing Bevy components, resources, queries, plugins or system ordering.
Version and project gate
Inspect Cargo.toml, Cargo.lock, Rust toolchain, exact Bevy release, plugin compatibility, feature selection, schedules, state definitions, asset roots and target backend. Read the matching migration guide before using newer examples. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Model data ownership and access conflicts before splitting systems. Express required ordering explicitly, including deferred command visibility. Keep global configuration distinct from per-entity state and inspect the pinned release’s resource semantics. Use narrow queries and stable domain IDs.
Deliver
A component/system dependency map and a focused plugin that expresses its ordering requirements. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Registration order is not a substitute for an explicit dependency; resource/component behavior changes between releases.
Acceptance scenario
Spawn through deferred commands, consume the result in a dependent system and verify behavior after reordering unrelated systems. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Talon. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md