Back

1. https://github.com/bevyengine/bevy/pull/13991

The culmination of a few weeks of work by Nth: re-implement hierarchical event bubbling for picking (mouse interactions!) using our observers.

Code quality and docs are great at this point, it has sign-off from all of the stakeholders. There are some outstanding vague questions about "how do all of our different event-like tools interact" and it's slower than the custom solution before, but IMO it's worth merging now. Unification and steady progress are invaluable.

2. https://github.com/bevyengine/bevy/pull/11460

So, plugin groups are a tool used to group commonly associated plugins together. This is better (for crate authors) than just sticking plugins inside of a single plugin, since then you can nicely disable them.

However, listing what's in them is a real maintenance burden: we've screwed this up repeatedly. With a simple macro, we can generate the type and automatically updated docs in a single blow. Not very user-facing, so I'm fine with a macro here. Merging :)

3. https://github.com/bevyengine/bevy/pull/13240

If a draw command (used to prepare work for the GPU I think?) has an error, apparently they currently get silently swallowed. We should be a good citizen and return those in a Result.

Very sensible! I've been griping about rendering reliability, docs and code quality for a while now; very pleased to see these sorts of efforts <3 Merging! Well, once merge conflicts are resolved.

4. https://github.com/bevyengine/bevy/pull/13695

Post-processing! Chromatic aberration! Another PR by the feature-machine: pcwalton. Good to see this made it through review <3

The second approval is relatively weak (focused on docs and testing), but the first approval is strong (rendering SME). I'm comfortable with that, especially from a contributor with a history of producing high-quality code. My own review pass didn't turn up any problems either. Merging.

5. https://github.com/bevyengine/bevy/pull/13820

A simple logging improvement: capturing the base path that the asset server is using. Very helpful: I've been frustrated by this both as a beginner and when using more complex project structures.

Nice QoL: merging :)

6. https://github.com/bevyengine/bevy/pull/13855

A redo of a previously merged PR: the logic was subtly wrong, and it broke our scene loading. I still like the API change :)

Let's do one final check on the previously regressed example.`gh pr checkout 13855` and we're off to the races. Yay, things are working still! Merging :)

7. https://github.com/bevyengine/bevy/pull/13859

Our first internal use of observers: porting over the existing `SceneInstanceReady` event to use them. This is a natural fit, as it already targets a single entity, and is relatively rare: we should get one to one hundred of these at the start of the app, and then very rarely afterwards.

Good migration guide, good idea. It's nice to start dogfooding this. However, some non-trivial merge conflicts. Pinging the author to resolve them.

8. https://github.com/bevyengine/bevy/pull/13903

More documentation for reflection always makes me happy. In this case, it's an example about `TypeData`: a powerful tool for extending reflection to work with your own traits.

Really solid improvement over the previous example: it focuses more on motivation, which IME is critical here. Neat to see the "literate programming" style; I'm a big fan of mixing code and prose like this. Merging!

9. https://github.com/bevyengine/bevy/pull/13963

Include the `AutoExposurePlugin` into `DefaultPlugins`, to match the API of everything else. This has repeatedly failed on web builds (sus...). Going to update the branch, and try again, but I'm pretty sure that there's something else going on here. Thanks CI!

IMO we're going to need to make an issue for this problem, and then mark this as blocked on getting this fixed.

10. https://github.com/bevyengine/bevy/pull/14099

A second pcwalton PR: this time localizing our volumetric fog. Love it! I saw this effect in the new FFXIV expansion, and I was pleased that we could replicated it in Bevy. Pretty simple, very useful, nicely made.

There was a simple merge conflict, but with that fixed up let's get this merged.

11. https://github.com/bevyengine/bevy/pull/14159/files

Allow observer systems to be piped, by providing them with an optional output type. Neat! Really cool to see features naturally composing like this.

This should be backwards-compatible due to the default type parameter of `()`. I'm personally pretty neutral on including it in the point release, but eh, why not.

Simple (as far as trait magic goes) and tested. Merging!

12. https://github.com/bevyengine/bevy/pull/14161

Ooh, an input PR I don't think I saw this one. This exposes key repeats to Bevy users. Apparently this is OS-level information analogous to our own just_pressed information. I wonder if we should use that internally. Probably not since it's OS-specific.

Anyways, very simple addition with docs. Useful enough to expose; merging.

13. https://github.com/bevyengine/bevy/pull/14168

Computers hate transcendental functions (like sin and cos): very slow to evaluate compared to simple multiplications and additions. So when writing performance-sensitive code, do some algebra and use those trig identities to avoid them :)

The math has been triple-checked; merging.

14. https://github.com/bevyengine/bevy/pull/14185

A simple cleanup in our input examples to match the migration guide. Great, merging :)

15. https://github.com/bevyengine/bevy/pull/14193

Ooh, virtual geometry PR. Some crunchy stuff here: a custom deserializer using `Pod` (plain old data) types to give us a 8x speed-up on deserializing.

Fun to see, and the measure-then-optimize strategy pays off well. Thoroughly reviewed and well-motivated: merging.

16. https://github.com/bevyengine/bevy/pull/14208

One of the more painful breaking changes in how states work in Bevy 0.14 is that they're now applied *before* startup systems. This is important to make sure that when you're in a state, all of the initialization for that state has been done! To support that, there's a state transition schedule being run in the startup meta-schedule(?).

Right now though it's just running in `Startup`, but it should run before everything else. Good fix, merging and backporting :)

17. https://github.com/bevyengine/bevy/pull/14211

Renames the very useful but somewhat mysterious `DebugName` system parameter to something more useful. This is now `NameOrEntity`, which more accurately captures what it does. Fundamentally, this is intended for use in dev-tooling: reporting the most user-friendly name it can find.

PR title and migration guide are out of date after some bikeshedding; let me edit that... Great, with that done, let's merge :)

18. https://github.com/bevyengine/bevy/pull/14212

A bit beefier now: an extension to out built-in hooks and observers triggers. When adding a component, there was both on_add and on_insert. The former runs whenever a component is first added to an entity, but the latter also works when the component is replaced via commands. On the removal side though, only the on_add equivalent exists.

This PR adds on_replace, resolving the inconsistency. Some nice debugging of UB via Miri in the comments: thanks CI! Merging :)

19. https://github.com/bevyengine/bevy/pull/14228

When writing Bevy applications, I typically just use `.chain` and the lazy system-type-name ordering. But for libraries, having public system sets is invaluable.

We added a UI system that wasn't part of our existing sets, which makes it much harder to order against. This PR fixes that! Merging :)

20. https://github.com/bevyengine/bevy/pull/14234

A simple documentation fix discovered by the Jam working group as they work on a game template :) `Commands::spawn_empty` is actually somewhat weird, in that it *doesn't* generate a command. Instead, it mutates the atomic counter that controls entity spawning, and allocates a new ID: giving the caller a stable entity ID despite the bulk of the work being done later.

Anyways, good little doc fix. Merging :)