shipyard VS revengate

With game matching the binary name used in Cargo.toml, above. The code we use is provided as an example of using the Shipyard Rust ECS. Paste the main.rs square_eater code from the repo into src/bin/main.rs in your project.

I also initially followed the amazing bracket-lib tutorial, but was not satisfied with specs. Tried legion, but it seems kind of abandonned too. I choose to use shipyard in my project and I am pretty satisfied with it until now. I feel like it's a great compromise between usability and effectiveness, plus there is relatively up-to-date documentation. Maybe can you give it a try ?Shipyard

Shipyard (Rust)

It's not that it's incompatible, it's that when the ECS is the primary tool for organization, a DOM tree (or scenegraph) is merely one way of iterating over the entities - not the way.

This provides tons of benefits, so for example you can also decide to iterate over the entites by shader program and gain significant speedups for graphics processing, or maintain components that roughly sort them by their position in world space for physics and culling or lighting, etc.

To add to the sibling comment, there's another wonderful Rust ECS called shipyard[0] and I helped write a scenegraph for it (which I really need to update, one of these days)[1]

[0] https://github.com/leudz/shipyard

Just as a final thing here, are, a, bunch, of, links for shipyard's tuple impls to show how its not an uncommon thing to need to do when writing an ECS :)

The old Python version of the game had a perfect separation between calculations and presentation, so it was really easy to make a simulator for it. With Godot, presentation is coupled more tightly, but I think that the work I did on perception and visibility should be enough to run combats faster than game-speed (monsters that you can't perceive move without animations).

OK, I went a bit wild with the summoning spell. If you squint, you can probably guess how it works. The key is picking good looking decals to start with, then it's just a bit of pixel shifting with some colorization.

Oh no! It's in open testing in a few countries and I guess that Google Play prefers to pretend that the app does not exist if you are from somewhere else rather than saying that its region restricted at the moment. The code is here and you can see what it looks like on my devlog.

I couldn't find a good sound effect for the explosion, so I ended up voice acting it.

You are in luck because I'm more than happy to share! https://gitlab.com/ygingras/revengate/-/blob/main/src/ui/water.gdshader

Revengate – a steampunk roguelike for Android – Website | Git repo | Downloads

Revengate 0.4.0 went out to Google Play (also available for manual side-loading). This release includes the monsters stat page, monsters who remember what happened to them, non-aggressive rats, dialogues, and a skills system that is not exposed to the players yet, but which already reduces the number of misses during the typical encounter.

I added victory conditions, so you can finally win the game rather than infinitely bashing monsters. I have a few things to tidy up, then I will probably push a v0.3 build to Google Play next week.

You read my mind! I was stuck with my previous overly complicated and brittle level generator and I would find all sorts of excuses to browse the news rather than writing code. So I tried writing monster descriptions instead and I sent a few commissions out. I really liked the results and it boosted my motivation, so I did it again a few times. It's kind of hard to stop once you have the ball rolling, but you obviously can't make a game with only a killer bestiary, so I took a break from sourcing arts.

I merged the Godot implementation back into the main git repo. There are still a few design docs that should be updated to clarify if they refer to the Python or to the Godot code.