bracket-lib VS roguelike-tutorial-cpp

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)

Looking back, a lot of work not directly related to the game. E.g. a month-long attempt to make a tutorial (aka: make a constrained mini roguelike) which didn't get finalised as a tutorial, but got finalised as a product (look up last project). Here's the code](https://github.com/byte-arcane/roguelike-tutorial-cpp).

It's in a bit of a cryostasis. I released the final project, and I started making changes backwards and cutting features as per plan, but roundabout part 2 or 3 I was not happy with the leap required, and I'm overall I was unhappy about some abstractions (or the lack of some others). So to prevent the extra stress and time pressure from seeping into the main game dev, I paused it. It's still online and available, but text is written only for the last project, and the code works as expected from project 4 (or 3?) onwards.

C++ tutorial. So the final project code is now complete, and available on github. What's missing is installation instructions (if you know how to use vcpkg and cmake from command line, that's all you need though) and the actual week-by-week write-ups. I've thought of a 14-part structure, which will funnel in during the next month, and slightly deviates from the structure of the existing libtcod tutorial. If you're curious, have a look, any questions, give a shout. When it's done, I'll make a top-level post.

Hey, since you asked, here's the repository. I'm done due to time constraints, certainly not ideal (it never is), but I need to get a move on with my game... I have a clumsy batch file to build on windows, but I'm pretty sure you can manage. Have a look at the notes.txt to get an understanding of the scope/complexity