bevy_egui VS rfcs

I've heard that bevy_egui is good.

fwiw, I've had a blast using https://github.com/mvlabat/bevy_egui - you might find it easier as well.

Hi! Can't help but post a link to my plugin here: https://github.com/mvlabat/bevy_egui

Afaik, there are no plans to upstream Egui integration to Bevy, but if anyone needs an immediate mode UI, this plugin does the job (and it already supports Bevy 0.9).

It's much more mature than our UI solution (which is bevy_egui exists and is wildly popular). And for things like calculators and todo lists, there's no complex internal logic where you really want the tools that Bevy provides.

Oh, forgot to mention, egui is used for most of the gui features via bevy_egui, it's pretty nice, very easy to use (I've been using other immediate gui before).

For a GUI, you might consider egui which has an integration for bevy.

Bevy engine has also an editor UI plan like godot,but it's just the beginning. There is a Egui integration(bevy_egui) for the Bevy game engine which you can try.

For some good real-world use cases, check out this thread: https://github.com/bevyengine/rfcs/pull/39

I'm the author of the draft Many Worlds RFC. Current plan is to get scheduling sorted out, then pick that work up again.

Yep, we do this, it works great! We stole it from hecs and Amethyst before us. There's a nice write-up of the theory in the scheduler rework the team has been working on for the past few months.

I can tell you right now that there’s an entire channel in the Bevy discord server dedicated to making an out of the box api for multiplayer. If you want the current state of it, check out this RFC. https://github.com/bevyengine/rfcs/pull/19 I’m really excited for it when it eventually comes out.

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.

Cool! Looks like a nice complement to the RFC about keyboard navigation!

This should be fairly feasible: although you'll probably want to wait on (or implement) the dynamic components RFC. The comments above are more to the effect of "writing Rust is easier and more convenient than you might expect".

You will be happy to know that better/updated documentation is planned. It was briefly mentioned as "the new Bevy Book effort" in this paragraph of the blog post and there are a ton more details in this RFC. Your participation would be more than welcome!

So, several of us have been working on a relations feature for Bevy: first-class support for those sort of "target another entity with a component" patterns that keep cropping up. There's a lot to be done, and it's at a point where it can be chunked out, so if you're interested in helping out come say hi on Discord :)