Bevy

It’s a crate for server-authoritative networking.

Bevy has started drafting release candidates to let users test them before the actual release. And I think it's awesome!

This release adds support for Bevy 0.14.0-rc.2. There are no functional changes.

We haven't released bevy_replicon_renet because we need to wait for bevy_renet. However, other crates, including other messaging backends, won't be blocked.

📦bevy_replicon

You can find it on crates.io or on GitHub. Notice that as it's a release candidate, you have to specify the version for it to be selected, it's not automatic.

Please test it on all the strange use cases you have, update the plugins you maintain, and get ready for an exceptional release! The migration guide is still being worked on, but the draft can already prove useful.

For the next two weeks, we'll cherrypick back to the release branch merged PRs from the 0.14 milestone, so that they will be in the 0.14 release. While we will avoid breaking changes, it's still a possiblity one will be merged if there's a big enough issue.

Bought the device a few days ago and wanted to share the experience of running a Bevy game on it. I developing an open source life simulation game called Project Harmonia. The game is at the prototype stage: you can build walls, place objects and move around, but no no actual gameplay loop.

Bevy engine supports it natively since it's just a regular x86 with GNU/Linux. So nothing special was needed! I compiled the game via Cargo and it works.

The game runs great. I get stable 90 FPS (90Hz is the refresh rate of the device) consuming only 13.1 W. The UI is a little big and controls aren't adapted well for gamepads, but I will fix it later.

The console itself is also a nice machine for development. Next I will write about the setup I use.

As you may know, it runs SteamOS with KDE and based on ArchLinux.

Packages mostly mirror official ArchLinux repositories, but there are some additions and everything is compiled by Valve. So you can even install SuperTuxKart or GNOME 😃

Another difference from vanilla ArchLinux is immutable file system. You can make it writable via a single command in terminal, but each update wipes all changes made to the system. Home directory remains untouched.

Because of the immutable filesystem, I decided to try Flatpak. It installs packages into the user's home directory. Therefore, such apps won't be removed after an update.

But I faced some limitations due to containerization. For example, the Firefox extension for KeePassXC does not work because apps can't interact with each other. And it's not suited for installing stuff like compilers or libraries. So I decided to explore other options.

Next, I tried to create a script that I planned to run after each update. It installs all the packages I need through the system package manager.

But packages on SteamOS are older then in Archlinux. For example, Neovim on SteamOS is 0.9, but on ArchLinux it's 0.10, so I had to downgrade my configuration. And it causes incompatibilities with AUR. For example, I couldn't install Crow Translate because of it.

Another problem with such script is that Valve nuked /usr/include directory to free space. All packages are present, but the folder is missing. It makes sense for a gaming device, but I need it to compile packages from AUR.

It can be solved by reinstalling all packages that put files into /usr/include. But it causes another problem 😃 Allocated space for / is limited and you quickly run out of space after restoring headers and installing a couple of packages.

Then I decided to try Distrobox. It creates containers that tightly integrated with the host system. It even comes pre-installed on the Steam Deck.

And I like it a lot! It is very easy to use and combines the advantages of both approaches. All packages will persist across updates and I have access to all packages that I have on my regular PC. Graphical apps look native and can interact with each other.

The game on photos was compiled on the Steam Deck 🥰

cross-posted from: https://mastodon.social/users/Shatur/statuses/112508034539087653

It's a crate for server-authoritative networking.

In this release, we have completely reworked the events. We now use an optimization similar to what Bevy does for processing event updates.

The public API for events has not changed, except that custom systems have been replaced with simple serialization and deserialization functions. It’s faster and more convenient.

In addition, all network event registration functions can be used on regular events, automatically making them network events.

📜Full changelog 📦bevy_replicon 📦bevy_replicon_renet

cross-posted from: https://mastodon.social/users/Shatur/statuses/112464362803020971

Implemented a special component that allows the sides of objects to snap to others with the same component.

Bevy's gizmo was very helpful in visualizing the math.

It's a crate for server-authoritative networking.

We worked closely with the author of bevy_bundlication on this release to provide better abstractions for third party plugins on top of replicon. Here are some highlights:

Previously, users registered a component for replication and it was replicated if its entity was marked for replication. But this approach is quite limited. Now users can define replication rules similar to queries:

app.replicate_group::<(Transform, Player)>() // `Transform` and `Player` components will be replicated only if both present on an entity.

And it's possible to specialize ser/de for such groups. For example, replicate Transform in one way for players and in another way for static objects. Groups with more components take priority by default (but it's configurable). So it's also possible to have app.replicate::<Transform>(), but if Player component is present, (Transform, Player) will take precedence. In the next release we planning to support With and Without to let define something like this: app.replicate_group::<(A, B), Without<C>>().

Also check out 📦bevy_bundlication which is now an abstraction over replicon that provides a bundle-like API for defining replication groups.

Custom replication functions was also heavily reworked:

• Public API no longer requires any unsafe.
• Deserialization and writing now defined separately. This allows rollback crates to define their logic without touching user-defined ser/de functions.
• Writing now based on markers for more flexibility.
• Users can customize deserialization in-place.

The author of bevy_bundlication also developing input queue and rollback plugins, but they require an API for disabling entities from Bevy. If you are interested in this or have other suggestions how to achieve it, feel free to comment on this issue.

📜Full changelog 📦bevy_replicon 📦bevy_replicon_renet

Working on a life simulator game with a working title Project Harmonia. Just added vintage counter that my wife made to the game. I think it looks quite nice in Bevy.

The same model in Blender: https://toot.garden/@YaraGardaria/112322312099954470

Introducing renet2, a fork of the networking library renet that implements the game-oriented netcode standard.

Highlights:
- Allow netcode servers to manage multiple data sources at once (e.g. UDP sockets and a WebTransport server).
- Add built-in in-memory sockets and WebTransport sockets. You can now run a netcode server with native AND browser clients, with the same exact authentication workflow for all clients (using ConnectTokens).

@bevy

https://github.com/UkoeHB/renet2

#bevy #networking

Our very first game at Snowy Road Studios!

Scavenger: Jump around and scavenge for good items! https://snowy-road-studios.itch.io/scavenger

Scavenger came from a small in-house game jam with me (SRS founder koe) and my kid brother. Check the devlog to see how it went: https://snowy-road-studios.itch.io/scavenger/devlog/711861/developing-scavenger.

@bevy

#bevy #gamejam #family

We've long wanted a Bevy playground, just like the official Rust one, where you can type in code in the browser and quickly mess around with Bevy. Now, thanks to Liam, you can experience this for yourself!

The author is looking for feedback here.

List of changes: https://github.com/bevyengine/bevy/compare/v0.13.1...v0.13.2

Bevy can run on Android phones. But what about GNU/Linux phones?
I decided to find out using my PinePhone Pro with RK3399.

Managed to run my game using WGPU_SETTINGS_PRIO=webgl2.
But couldn't get past the main menu due to limited features of the GPU. 😢

But simple 2D games like breakout example runs!

Right now I working on networking for the game, but this evening I decided to tinker with my device a little.

List of changes: https://github.com/bevyengine/bevy/compare/v0.13.0...v0.13.1

In my initial implementation, doors opened when a character approached them (using a sensor collider). But it looked creepy 😅 Imagine simply walking past the doors and having them open unexpectedly.

In the current implementation, I analyze navigation paths to determine if characters pass through the door, and open it when they approach.

Additionally, I added small visual feedback for wall placement, fine-tuned navigation, adjusted controls, made a few QoL improvements, and fixed a bunch of bugs.

This is for my WIP open source life simulation game under the working title Project Harmonia.

This release is big! We abstracted out all I/O and renet dependency. We will continue to provide first-party integration with renet via bevy_replion_renet.

But now users can write their own integration with other messaging libraries. Refer to the documentation for instructions on how to do it, the process is very simple. See bevy_replicon_renet as an example.

This also opens up the possibility of simultaneously using multiple messaging libraries on the server, as long as the client identifiers they provide are unique.

See the changelog for a full list of changes.

📦bevy_replicon 📦bevy_replicon_renet

Glad to see that you can import the model from Blender and the transparency just works. Also the index of refraction table in the Bevy docs was very helpful! All models made by my wife 😅

It's a high level networking crate for the Bevy game engine.

Now we support Bevy 0.13. With this release we now use the improved Bevy's MapEntities trait instead of our custom one. This way users no longer need to define both to make mapping work for scenes and networking.

See the changelog for a full list of changes.

The crate is based on renet, but for the next release we planning to abstract out all I/O. We will continue to provide renet integration via separate bevy_replicon_renet crate. This way other messaging crates can be used by writing a thin integration crate.

📦bevy_replicon

It's a high level networking crate for the Bevy game engine.

Now mapped client events will not be drained and will behave exactly like other events. But it's a small breaking change since such events now require a Clone impl.

See the changelog for a full list of changes.

📦bevy_replicon

Improved logic and added visual feedback.

Also switched from bevy_rapier to bevy_xpbd. My game only needs collision detection and with bevy_xpbd I can disable unnecessary logic by toggling plugins. So convenient! It was an easy transition since the API is very similar. The author is also very active and helpful.

Boolean operations in 3D are quite heavy. But fortunately, each wall can be represented as two 2D planes.

To determine which 2D shape I need to cut from the mentioned planes, I add a special plane in Blender with "Cutout" name. This is what The Sims series do.

And for all doors located on a wall I triangulate combined vertices using earcutr. The library API doesn't fit well with Bevy, but it does the trick.

The project is open source, so if you are interested in the implementation, you can take a look at the wall module. I organize my modules as plugins, so you can copy the module and its submodules into your game with some minor edits and enable WallPlugin.

Now walls are separate meshes and take full advantage of ECS, including change detection to rebuild only changed parts.

The new approach also automatically fixed some bugs and enabled instant update of other walls that were affected by currently spawning wall.