Amethyst VS specs

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.

Rust also has seemingly better libraries for the purpose. Both Bevy and Amethyst are available, and plenty more.

Amethyst

I recently stumbled upon a short YouTube video of somebody building a roguelike game in Rust. From there, jumping from resource to resource, I ended up going through (part) of this massive (and awesome) tutorial by Herbert Wolverson about his Rust library bracket_lib. In this tutorial, Wolverson builds a roguelike game with colored text characters. After reading through, I felt like writing another type of game in Rust, so I looked at the available Rust game engines. The most popular, seems to be Amethyst, but it looks like they halted their development efforts. Second in line was Bevy. People are using it, support for Android and iOS is on the way, uses an ECS and have some usage examples: looks good.

Depends on my goals. I year ago I wanted to learn rust, so I used piston for a gamejam. (There are several rust engines including bevy, piston, amethyst. They probably vary in quality, features, and constraints.) Piston was a terrible experience because compilation is slow even on that tiny project.

And there's already a couple of surprisingly full-featured 3D engines already out there. Most notably Amethyst.

View on GitHub

Is anyone having this problem? I can't connect to rocket.rs, actix.rs and amethyst.rs servers. I would play at https://tera.netlify.app/, but people out there is really toxic. I heard that Rust is getting an update while playing in a Rust server, just then rust server freezes and goes down.

Or should I jump directly in one of the bigger engines like Amethyst, Bevy or other?

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

You could also look at Entity Component Systems. Something like specs.

If you are making a game, instead of a game engine, you can have your cake and eat it too -

https://godot-rust.github.io/

Allows you to pair Rust with Godot comfortably via gdnative.

Then use one of the good ECS systems in Rust like -

https://github.com/amethyst/specs

or (archetype style ECS)

https://github.com/amethyst/legion

To get spun up on ECS in Rust I suggest -

http://bfnightly.bracketproductions.com/rustbook/chapter_0.h...

This won't get you a godot project but will get you a basic concepted game you can then port into godot-rust.

Fair enough on leaving parts up to other code instead of the library. I started my ECS with the idea of optimized storage (eg hash maps for sparse components) and indexing (which is why formal Not helps a lot, but indeed Maybe is only sugar for less code). I really liked this Rust ECS which also does parallelization, which makes it important for the ECS to also know which order the systems execute in, and their dependencies on each other (something I started doing but never finished): https://github.com/amethyst/specs