tcod-rs VS roguelike-tutorial-cpp

tcod-rs

I might look into using Rust. Rust looks fast, has a package manager, and can compile to WebAssembly. There's an existing Rust port of libtcod without a maintainer. It might be able to do the things that I'm struggling to get working in C++.

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