Bevy 0.16 is around the corner with many exciting features!

I'm currently working on adding support for some of them in my networking crate, bevy_replicon.

I just finished implementing immutable component support.

Next up: relations! I outlined the idea in this comment. Hope I can get it implemented before the 0.16 release 🙂

As for my game, I'm considering making an interesting announcement about it soon.

It's an input manager for Bevy, inspired by Unreal Engine Enhanced Input. We use it for Project Harmonia, but it's general-purpose.

This release contains many changes, most notably the component-based API for contexts. We've also reworked the documentation, now including a quick-start guide that walks you through the API. We would appreciate your feedback 🙂

📜Full changelog 📦bevy_enhanced_input

It's an input manager for Bevy, inspired by Unreal Engine Enhanced Input. We use it for Project Harmonia, but it's general-purpose.

This release contains many changes, most notably the component-based API for contexts. We've also reworked the documentation, now including a quick-start guide that walks you through the API. We would appreciate your feedback 🙂

📜Full changelog 📦bevy_enhanced_input

It's an input manager crate for Bevy, inspired by Unreal Engine Enhanced Input. We use it for Project Harmonia, but it’s general-purpose.

I love our trigger-based API, but the push-style API needed improvement. Previously, users had to read values from a resource - unergonomic and a bit confusing.

Now, contexts are components! This makes our push-style API similar to LWIM while keeping all the trigger-based ergonomics 🙂

See more details in the PR.

I recently received blessing from Alice (author of LWIM) to upstream this crate as a future Bevy input abstraction. But first, we need to polish the API - it's much easier to iterate on while in a separate crate.

It’s a crate for server-authoritative networking. We use it for Project Harmonia, but it's general-purpose.

A small release with improvements to the messaging backends API and ergonomics. I wanted to draft these changes before Bevy 0.16 to simplify the migration.

I also drafted a new RC release that supports Bevy 0.16 with no_std support! Nothing is feature-gated, the crate now completely no_std. Aeronet's author is working on bringing no_std support to aeronet, so you should be able to use it together with Replicon for some unusual platforms soon 🙂

📜Full changelog 📦bevy_replicon

It's a crate for dynamic and contextual input mappings for Bevy, inspired by Unreal Engine Enhanced Input. We use it for Project Harmonia, but it's general-purpose.

After some brainstorming with Alice (the author of LWIM), I replaced trait-based context creation with triggers. It was quite a significant refactor, but defining reloadable bindings in observers is so convenient.

There are also other minor ergonomic improvements and bugfixes. See the changelog for more details.

📜Full changelog 📦bevy_enhanced_input

Fascinating work done by a community member, which strongly suggests that the Retroid Pocket Mini may in fact just be a 3.92" 1080x1240 AMOLED panel (same as in upcoming RP Classic) but with part of the panel hidden to achieve a 4:3 aspect ratio.

Fascinating work done by a community member, which strongly suggests that the Retroid Pocket Mini may in fact just be a 3.92" 1080x1240 AMOLED panel (same as in upcoming RP Classic) but with part of the panel hidden to achieve a 4:3 aspect ratio.

It’s a crate for server-authoritative networking. We use it for Project Harmonia, but it's general-purpose.

Notable changes

• Connected clients are now represented as entities.
  • All related APIs are now component-based.
  • Entity is used to refer to a client everywhere, but ClientId is still present as a persistent identifier across reconnects.
  • Fast iteration and O(1) lookups.
  • Users can insert their own components or even replicate these entities.
  • Simplifies messaging backend integration.
• Switch from bincode to postcard.
  • Better varint serialization to save bandwidth.
  • Opens the door for no_std support after the 0.16 release.

I also rewrote the quick start guide. My recent talk at Bevy Meetup #9 helped me with this. It now contains much more information, including details on how to write a messaging backend or implement client-side prediction. I also tried to make it as user-friendly as p

For the past few days, I've been working on the ultimate quick-start guide for bevy_replicon.

It now contains much more information, including details on how to write a messaging backend or implement client-side prediction. My talk at the last Bevy meetup helped me with this. Any feedback is appreciated 🙂

Some people steal games from itch.io, add some AI crap to them, and put them on console stores.

Previously, I used a special ClientId type to refer to connected clients and stored their data in several resources.

I wasn't satisfied with this API and decided to try turning them into entities. Now, Entity is the identifier, and components store related data. I'm quite happy with the results, but waiting for a review from the second maintainer: https://github.com/projectharmonia/bevy_replicon/pull/423

If you have any suggestions or ideas, feel free to comment 🙂

Just preparing the crate to the upcoming talk at Bevy Meetup #9. Still in a break from actual game development.

It's a virtual meetup about Bevy, and I will be one of the speakers!

My topic will be Networking in Bevy with ECS replication, where I'll talk about bevy_replicon and networking in general.

I'm currently focused on crates that I use in the game, just to take a small break from the project. But I hope to get back to it soon :)

Just curious 🙂

It’s a crate for server-authoritative networking. We use it for Project Harmonia, but it's general-purpose.

Kinda our 30th anniversary 😅 This release introduces remote triggers. The API is similar to our networked events. Here’s a quick showcase for client triggers:

 rust

    
app.add_client_trigger::<DummyEvent>(ChannelKind::Ordered)
    .add_observer(receive_events)
    .add_systems(Update, send_events.run_if(client_connected));

fn send_events(mut commands: Commands) {
    commands.client_trigger(DummyEvent);
}

fn receive_events(trigger: Trigger<FromClient<DummyEvent>>) {
    info!("received event {:?} from {:?}", trigger.event, trigger.client_id);
}


  

Server triggers have a similar API. Targeting entities is also supported.

We now also provide an example backend and examples that directly from the bevy_replicon repo. The examples have also been re-written to take advantage of the latest Bevy and Replicon features.

📜[Full changelog](https://github.com/projectharmonia/bevy_rep

Refined the bindings menu for my game and ported it into a standalone example for bevy_enhanced_input.

Alice (the author of LWIM) and I quite like the main concepts of the crate, and we’re planning to refine it further to create the ultimate input manager 🙂