Back

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

A simple doc test explaining how to swap states. Very handy, but has merge conflicts. Lemme see how bad they are... Oh nice, not bad at all.

Some ugly mocked / hidden `App` shenanigans (plz join me in my crusade to merge bevy_app and bevy_ecs), but otherwise I'm pleased.

Great, let's try and merge this.

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

A simple fix for a typo'd doc link. Francois appears to have already updated this to get the required new CI jobs: lovely.

Merging :)

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

Some simple documentation explaining how to initialize the values for an `OrthographicProjection` in a `Camera2dBundle` correctly.

I think this is net useful, even if I do worry about these little notes rotting over time. Merging.

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

One of my favorite dev tools: a debug overlay that shows you the outlines of all of your UI nodes. This sort of thing is incredibly useful on the web, and I've resorted to randomly coloring my nodes before.

An actual toggle is *way* better. This definitely goes in the release notes: lemme add a label for it. There's still some work figuring out how to configure / present these dev tools cohesively, but we need a couple examples first. Merging!

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

Just as all animals become crab, all programs become a relational database. Today, we take one step closer to our destiny by adding query joins.

These are a neat little feature that builds on our query lenses to get a new query from the intersection of data of two existing queries. In other words, an inner join. I want a proper example for this, but that can be done in a follow-up.

We'll see how useful this is in practice: maybe left/right/outer joins will follow.

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

The next step on my years-long master plan to ensure that users writing 2D games never ever have to think about "quaternions" advances: a dedicated `Rotation2D` math primitive. I wrote one of these for my own games and libs!

We still haven't swapped to a `Transform2D` that contains this: there's a whole RFC to write with the `#math-dev` folks about all of the different options and architecture there. Merging: this is a nice standard for the ecosystem even now.

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

A code quality PR for reflection: rather than messy, errorr-prone manual code, just use our existing macros to define `Reflect` implementations!

+18/-470 is the sort of line count I love to see. Merging once merge conflicts are fixed

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

Adds a `scale_around_center` method to our bounding volumes. The standard `grow` and `shrink` methods change things in absolute, rather than relative terms.

Some nice discussion by reviewers to ensure that the name is clear and the motivation is solid. Really cool to see the `bevy_math` primitives starting to get used in end-user games! Writing your own AABB gets old after the seventh time TBH.

Merging: I think this is useful and clear.

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

Adds different joint types (bevel, miter) to our gizmo lines. These will be a little more expensive, but markedly prettier. A nice little bit of polish that will come in handy for the editor, or for the 1 in 100 games that use gizmos in the actual final product.

I'm really pleased with the final API we came up with: it's good to see the review process meaningfully improving submissions. Merging :) More follow-up to do if this interests you!

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

The first bit of work from the refactoring students from Purdue: moving some code around to make the light files less massive. Nice!

Merge conflicts (of course) and the students are off this week, so this one will wait for now. Classic: git is by far the hardest thing for most new open source contributors.

11. https://github.com/bevyengine/bevy/pull/12382

Another little bevy_dev_tool: a simple FPS meter! While I think this is useful, I'm mostly keen on this as another example of a configurable and toggleable developer tool to use to refine https://github.com/bevyengine/bevy/issues/12368

Our vision here is to have a standard way to configure and toggle these, to make it really easy to hook these up to things like a Quake-style dev console, ensure they play nice and reduce maintenance burden. Merging, but I expect to refine it :)

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

Oh hey, one of the code quality changes I noticed while doing the bevy_color refactor. For some reason, we were using a `type PositionItem = [f32;3]` type alias when we have a perfectly nice `glam::Vec3` right there.

Great: it's such an awesome feeling to see the tiny issues you help generate get steadily and stochastically fixed up. Merging.

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

Ah, more variant methods for getting components from the world. This time, with lifetimes! Rather than returning a reference to a component with a lifetime matching the `EntityMut` etc that it was generated from, instead have it match that of the `World`. Okay sure. Good naming, good thoroughness, covers the untyped APIs.

Maybe the fabled effect system will save us from our endless code duplication here one day Merging: well-motivated and has no workaround.