bevy_ggrs VS bevy-inspector-egui

As of today, I believe multiplayer support is not in the short term roadmap. There are community plugins like bevy_ggrs that could be used for that.

You could create a custom stage (by implementing the Stage trait) that stores its own schedule and then use schedule.run_once(world) to run all systems in the schedule exactly once. I did this in bevy_ggrs , a bevy plugin for ggrs, a rollback netcode library.

Regarding rollback networking, there is bevy_ggrs, which I think works really well.

With egui and some bevy related plugins you can get pretty close to a game engine editor, obviously missing a lot of things: https://github.com/jakobhellermann/bevy-inspector-egui

Like /u/tarkin25 already mentioned "egui" can be integrated into bevy. Bevy Inspector Egui is a plugin that not only provides a helpful way to inspect different entities in the world, but also re-exports "egui" for use.

Firstly, Bevy has an internal crate called bevy_reflect, and it can handle most of the things you would usually use reflection for. For example, https://github.com/jakobhellermann/bevy-inspector-egui exists which uses Bevy's internal reflect derive to make the values available via an egui-based UI. Changing simple values (like an f32, or a boolean) can be done at runtime, and if I remember correctly all you actually need to do is to add the plugin. Taking a look at the README https://github.com/bevyengine/bevy/tree/main/crates/bevy_reflect you can "patch" types with new values, iterate over struct fields, serialize + deserialize, and generally do stuff like that.

Yeah runtime editing is definitely a weakness at this point. An editor is definitely a part of our plans though! We'll likely break ground on it early this year. In the meantime https://github.com/jakobhellermann/bevy-inspector-egui provides some nice runtime editing / inspecting / editor-like tools.

Here is the example

Bevy-inspector-egui is a most have, I think this game would not have been possible without, abuse it,

What do you miss from scriptable objects that you don't get from a class that serializes to JSON? Global access (read only access shouldn't prevent this right)? The inspector (looks like egui can help there?

There are also some super interesting experiments with hot reloading, both with code and on the fly value modification.

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.