bevy_egui VS backroll-rs

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.

I'll share two other options, of course with numerous caveats on each: - https://github.com/HouraiTeahouse/backroll-rs Looks great for low-latency games - https://partner.steamgames.com/doc/features/multiplayer Steam can be used on non-Steam platforms too, and has official-ish rust bindings but haven't tried this route

I haven't actually got to the point of trying to implement it in my fighting game engine but Backroll rs is a rust implementation of GGPO https://github.com/HouraiTeahouse/backroll-rs

Backroll-rs is a brand new networking library based on GGPO dedicated to peer-to-peer Rollback Netcode, for use in fighting games, platform fighters, and other games with less than 8 players that require low latency. We are looking for programmers familiar with Rust to help finish this project. We are 80% of the way completed with this project, but we need more unit tests and debugging to fully finish it.