-
Notifications
You must be signed in to change notification settings - Fork 351
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
ECS chapter for new book #182
Conversation
Book structure
No need for example on main page
The omission of States and system ordering is deliberate to keep the example simple. It would be nice to provide feedback about the key pressed, but no clean mapping to string exists due to different keybindings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed the chapter introduction. Mostly suggestions and a couple of change request for typos and other additions/corrections. Great work, anyway 🚀
EDIT: More reviews incoming...
@MinerSebas I think this PR involves more files than it should, probably because @alice-i-cecile included the commit "Book structure" (252325d) |
I think the problem is more that this targets the |
Enabled the anchor links for the ECS section in alice-i-cecile#4. |
Enable anchor links in ECS section
I intend to close and split #182 to improve both development and review workflows. This is a tiny PR to make reviewing that work less painful by reducing weird branch issues.
I intend to close and split #182 to improve both development and review workflows. This is a tiny PR to make reviewing that work less painful by reducing weird branch issues.
Closing this out in favor of the small, split PRs linked above. Working with all of the changes in a single PR is incredibly unwieldy as both an author and reviewer. |
Any plans to localize Bevy Book? |
@C-BJ personally yes, but once it's significantly more stable. I don't think it makes sense until 1.0. |
Maybe #265 description can be updated to list the PRs?
|
As an alternative, I'd advocate for setting up a project board instead of trying to use a tracking issue that needs to be manually kept in sync |
fn end_combat_system(query: Query<Entity, (With<Combatant>, With<InCombat>>, mut commands: Commands){ | ||
for entity in query.iter(){ | ||
// The component will be removed at the end of the current stage | ||
commands.entity(entity).remove(InCombat); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be remove::<InCombat>()
?
Extracted from #182. # Status - [x] Simplify example - [x] Avoid database analogy - [x] Edit and revise for clarity and quality - [x] Fix dead links - [x] Refactor Breakout example on Bevy repo - [x] Update text to sync closely with Breakout example
Ported from #182. # Status - [x] revisit and revise - [x] remove all use of direct world APIs - [x] distinguish between `Entity` type and entity concept
Ported from #182. # Status - [x] revisit and revise - [x] remove all use of direct world APIs - [x] distinguish between `Entity` type and entity concept
If you'd like to read (or review) this PR, you'll need to:
zola serve --open
from that directory.To do:
WorldCell
from this chapter.