Skip to content

Update to Bevy 0.10 #264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
Tracked by #266
rj00a opened this issue Mar 3, 2023 · 0 comments · Fixed by #265
Closed
1 task done
Tracked by #266

Update to Bevy 0.10 #264

rj00a opened this issue Mar 3, 2023 · 0 comments · Fixed by #265
Assignees
Labels
enhancement New feature or request

Comments

@rj00a
Copy link
Member

rj00a commented Mar 3, 2023

Is your feature request related to a problem? Please describe.

Bevy 0.10 (unfinished as of writing) includes some very large changes to the scheduling API. These changes should help make #199 and #257 more achievable.

Describe the solution you'd like

Use a recent commit on the main branch of bevy or 0.10 when that comes out.

Additional context

Allowing system sets to be nested helps when there are a large number of systems that need to be scheduled. Sets of systems (e.g. all the systems needed to update inventories) can be encapsulated together in a sane way without having to create an explicit label for it.

@rj00a rj00a added the enhancement New feature or request label Mar 3, 2023
@rj00a rj00a self-assigned this Mar 3, 2023
This was referenced Mar 3, 2023
@rj00a rj00a closed this as completed in #265 Mar 4, 2023
rj00a added a commit that referenced this issue Mar 4, 2023
## Description

Fix #264

Bevy version is pinned to a recent commit on the main branch until 0.10
is released.

## Test Plan

Run examples and tests. Behavior should be the same.

scheduling is a bit tricky so I may have made some subtle mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant