froggy VS bracket-lib

What I found in practice is that many people start using the ECS for speed, and then draw themselves into a corner of the design space. Now they have to weight every step on "how would it work in ECS?", and dedicate effort to fight the ECS paradigm.

For example, a mesh may contain multiple materials. Is each material chunk a separate entity? Or maybe each bone in a skeleton is a separate entity with its own "parent" and "transform" plus other component.

One of the different approaches is component graph systems [1]. It lacks the ability to mix and match components, but provides a more natural (and simpler) model to program for.

[1] https://github.com/kvark/froggy/wiki/Component-Graph-System

I had similar motivation back in the day for CGS in https://github.com/kvark/froggy, which was also powering https://github.com/three-rs/three. It's nice to see Rust ecosystem not locking itself on ECS, even if they are so cool :)

I think having to use a terminal is the scary part for many people. rltk/bracket-lib can be used to get a similar look and feel if that's what's important, but it is geared toward roguelikes.

Maybe bracket-lib from the amethyst authors? I‘m currently working through that book and find the library quite intuitive and simple to use. It started out as a toolkit for rouge-like games but has been getting more general. On that note, I recommend the hands-on-rust book which teaches rust concepts while building games with bracket-lib. As you have read the book, I‘m sure you would get through the first chapters quickly.

https://github.com/amethyst/bracket-lib has a great integration with Bevy, designed for exactly this sort of thing.

I've been doing some experiments with terminal based games and landed on https://github.com/amethyst/bracket-lib It's not exactly terminal based in the sense that it actually runs on OpenGL by default. But that's a plus imho because dealing with the bits of the terminal window that can change outside of your control (like fonts, window resize, etc) is a giant pita. It does let you swap the backend to run on crossterm if that's what you really want to do but if what you're after is the aesthetic like I am having bracket_lib handling all that makes life so much better.

Bracket-Lib for Bevy Github

Bracket-Terminal/RLTK for Bevy Github Branch | Twitter | Patreon

bracket-lib 👈🏻 (using this now)