Airshipper VS specs

Windows user will get it by the usual auto-update, AUR is already updated. Flathub will update soon. All downloads can be found here: https://veloren.net/download/

You can follow flathub installation : https://veloren.net/download/

Most probably you have out-of-date version. First, you should have Airshipper launcher installed. Then run game using the launcher and it will be up-to-date. If you get the message again, probably you should quit the game, press "Update" button in the launcher and launch updated version. Also see https://veloren.net/download/

According to the Veloren website, provided they’re using the net.veloren.airshipper flatpak, it is official. The unofficial Veloren/Airshipper packages are the Ubuntu PPA and Copr RPM packages

To join, you can download the game for free at veloren.net and create an account, then launch the game and hop on the default server. See you there!

Interestingly their launcher GitHub readme provides installation instruction for NixOS users but their website does not mention it.

Launcher GitHub page: https://github.com/veloren/Airshipper

such a cash grab that they're releasing it as free and open source

You don't have to be professional for a bug report, the developers will help you if needed, just use the issue section of the repo https://github.com/veloren/Airshipper

Source: https://veloren.net/download/

The question arises from seeing a plethora of projects using ECS: hecs , Bevy , specs, legion

Instead, I'm using now the specs Library. It's a pure ECS library and much less powerful, without any visualization capabilities, but its works for me :)

writing an ECS is defined a challenging project, no matter the language or if you're a beginner. although it is entirely possible to write one in Rust, check out specs and bevy_ecs for examples.

specs

The official 3d rendering client uses a custom engine called Voxygen. They use Specs for logic.

Rust has a delightful ECS library, specs, that I absolutely love. It has safe multi-threaded execution built right in, which is fantastic for the pretty parallelizable work I was doing. Concurrency in C++ is nasty business on the best of days, and I've run into so many nasty bugs with the custom system I've had to build out to fit the web's weird threading model.

Man, this Specs [0] library is so strange to me, coming from a Unity background. Is there some sort of comparison as to why one way is better than the other?

[0] https://specs.amethyst.rs/

Hi everyone - I just picked up one of my long-unfinished side project built with Rust and would like to show it to you here. It's a clone of the famous(?) Winterbells game. It's written entirely in Rust and uses OpenGL and an entity-component-system architecture ([the `specs` crate](https://crates.io/crates/specs)) (still learning), no game engine.

Wait did the person at your company write specs or something else because they weren't pleased with it? I don't know much about amethyst and vaguely know about entity component systems but I watched a talk on someone making a game with amethyst and was pretty impressed -- it looked thoroughly approachable and I do not doubt the performance is there (since the whole reason you do ECS is performance).