bevyengine / bevyengine/bevy

System sets do not share their configuration across schedules

Open
#9,792 14 comments 1 reaction 0 assignees View on GitHub
A-ECS C-Bug D-Complex S-Ready-For-Implementation
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 22h
Merged PRs (30d)
161

Description

## Bevy version

0.11

## What you did

1. Create a system set `MySystemSet`.
2. Give it some configuration using `configure_set(Update, MySystemSet)`.
3. Add some systems in both the `Update` schedule and another schedule to this set.

## What went wrong

The configuration is silently missing for systems in other schedules.

If a system set defines a set of behaviors (like running in a certain state), then I would expect that behavior to be true across schedules (where possible).

## Additional information

The fact that this will happen is thankfully much clearer now that we require explicit schedules everywhere, but it's still a nuisance and a footgun.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.