Bevy 0.7

• bevy

  574 32,210 9.9 Rust

  A refreshingly simple data-driven game engine built in Rust

  

I think making it easier for systems to observe the effects of Commands from other systems is a critical missing piece of the Bevy ECS puzzle. "Stageless" is a solid, holistic solution to the problem and we're seeing the community slowly establish consensus on that design. There is already a draft implementation in the works. And I think "stageless" is most likely the solution we will land on.

• rfcs

  16 106 1.2

  Suggest changes to Bevy and view accepted designs (by bevyengine)

  

I think making it easier for systems to observe the effects of Commands from other systems is a critical missing piece of the Bevy ECS puzzle. "Stageless" is a solid, holistic solution to the problem and we're seeing the community slowly establish consensus on that design. There is already a draft implementation in the works. And I think "stageless" is most likely the solution we will land on.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• bevy_editor_pls

  6 649 7.7 Rust

  In-App editor tools for bevy applications

For now though, bevy_editor_pls is a surprisingly useful third-party prototype.

• awesome-bevy

  30 931 8.6

  A collection of Bevy assets, plugins, learning resources, and apps made by the community

  

I've summarized a lot of my thoughts in this blog post, but in short: * "The Developer's Engine": most engines are built using multiple languages, with significant abstraction between "user code" and "engine code". Bevy is built with a consistent stack and data model (see the blog post I linked to for details). If you "go to definition" on a Bevy app symbol in your IDE, the underlying engine code will look the same as your app code. You can also swap out basically everything. We have a vibrant plugin ecosystem as a result. These blurred lines also make it way easier for "Bevy app developers" to make direct contributions to the engine. The new Bevy renderer (in 0.6) was also built with this principle in mind. It exposes low, mid, and high level renderer apis in a way that makes it easy to "insert yourself" into the engine. * Fully embraces ECS: No popular engines are currently all-in on ECS (either they have no official support ... or they are half-in half-out). I reflect on some of the benefits we've enjoyed thanks to Bevy ECS in the blog post I linked to. Note that there is a lot of pro and anti ECS hype. Don't just blindly follow dogma and hype trains. ECS isn't one thing and Bevy ECS intentionally blurs the lines between paradigms. * Fully Free and Open Source With No Contracts: Of the popular engines, only Godot is a competitor in this space.

• bevy_ecs_tilemap

  5 800 8.6 Rust

  A tilemap rendering crate for bevy which is more ECS friendly.

Yeah built in texture atlas requires that you manually manage the atlas and doesn't support swapping out textures on the fly (although I'm willing to consider adding support for that). I'm pretty sure the bevy_ecs_tilemap plugin uses the "texture array" approach to texture atlases. Its very possible that it will work for your usecase (or provide an example of how to do that in bevy).

• bevy-inspector-egui

  11 1,025 8.5 Rust

  Inspector plugin for the bevy game engine

The one in bevy is nowhere near the requirements of a desktop application-level editor. I don't plan to involve bevy there at all. egui looks quite usable for low-level debug UI, though, especially with this crate.

Suggest a related project