Skip to content
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

Update to bevy 0.10 #72

Merged
merged 2 commits into from
Mar 6, 2023
Merged

Update to bevy 0.10 #72

merged 2 commits into from
Mar 6, 2023

Conversation

NiseVoid
Copy link
Contributor

@NiseVoid NiseVoid commented Mar 2, 2023

Nothing too crazy in this update, except if someone does something weird in First, PreUpdate or Last they might need to specify .after/.before with the corresponding BigBrainSet

BigBrainSet::Thinkers
.in_base_set(CoreSet::First)
.after(BigBrainSet::Scorers),
BigBrainSet::Actions.in_base_set(CoreSet::PreUpdate),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been kinda wondering if PreUpdate is really the appropriate stage for this, to begin with...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's definitely a safe option, but I can't say if it's appropriate or not. Ideally users would just be able to specify which set it would be in, but I'm not sure if that's possible by default with sets.

@NiseVoid
Copy link
Contributor Author

NiseVoid commented Mar 6, 2023

Tested this PR in my application and it seems to work fine. Also updated it to use the tagged release. As for the First and PreUpdate, might be a good idea to ask some of the ECS experts about their opinion on what would and wouldn't be appropriate base sets for it

@NiseVoid NiseVoid marked this pull request as ready for review March 6, 2023 20:46
Copy link
Owner

@zkat zkat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this! I'll release this shortly!

@zkat zkat merged commit 66ece02 into zkat:main Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants