Skip to content

Commit

Permalink
Revise introduction
Browse files Browse the repository at this point in the history
  • Loading branch information
alice-i-cecile authored Oct 18, 2023
1 parent e6efcbb commit a9a70dc
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion content/news/2023-10-21-bevy-0.12/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,10 @@ Since our last release a few months ago we've added a _ton_ of new features, bug

<div class="release-feature-authors">authors: @alice-i-cecile @pascualex, @Trashtalk217, @Zeenobit</div>

Previously, in order to run a system you'd have to add it to a schedule. But while schedules are very useful, not every system needs that sort of overhead. Hence the introduction of one-shot systems.
Ordinarily, systems run once per frame, as part of a schedule.
But what if you don't want to poll for them regularly?
Maybe you're responding to a very rare event like in a complex turn-based game, or simply don't want to clutter your schedule with a new system for every single button.
One-shot systems flip that logic on its head, and provide you the ability to run arbitrary logic on demand, using the powerful and familiar system syntax.

```rust
#[derive(Resource, Default, Debug)]
Expand Down

0 comments on commit a9a70dc

Please sign in to comment.