forestia/bevy
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: SpecificProtagonist <vincentjunge@posteo.net>
This commit is contained in:
Tim 2025-07-12 16:32:56 +02:00 committed by GitHub
parent e91d6e41d7
commit 1d853754d6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
release-content/release-notes/event_split.md
View File

@ -29,7 +29,7 @@ or an observer event with `EventReader`, leaving the user wondering why the even
**Bevy 0.17** aims to solve this ambiguity by splitting the event traits into `Event`, `EntityEvent`, and `BufferedEvent`.
- `Event`: A shared trait for observer events.
- `EntityEvent`: An observer `Event` that additionally supports targeting specific entities and propagating the event from one entity to another.
- `EntityEvent`: An `Event` that additionally supports targeting specific entities and propagating the event from one entity to another.
- `BufferedEvent`: An event that supports usage with `EventReader` and `EventWriter` for pull-based event handling.
## Using Events
@ -92,7 +92,7 @@ let armor_piece = commands
commands.trigger_targets(Damage { amount: 10.0 }, armor_piece);
```
To allow an event to be used with the buffered API, you can derive `BufferedEvent`:
To allow an event to be used with the buffered API, you can instead derive `BufferedEvent`:
```rust
#[derive(BufferedEvent)]