backroll-rs VS rfcs

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.

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 :)