roquest VS tcod-cpp-engine-2022

Repo: Still https://github.com/opadin/roquest Screen: https://github.com/opadin/roquest/blob/develop/screens/part7-ex3.png

FYI: The readme of the repo contains a screen. Still using all in one-in-all file (main.c).

Repo: roquest

I ended up following the C++ tutorial and creating a custom engine with the newer libtcod API. Writing the event API from scratch also let me compile with Emscripten to make a web build of my C++ libtcod projects. The resulting engine demo can be played online here. I lost steam near the end of the project since I was unsure how I should handle a database and because I tried too hard to keep saves compatible even though this was supposed to be a prototype. The main thing I learned is that serialization is difficult with C/C++ and it would've been easier to do had I used an ECS library.

The libtcod maintainer just finished a new C++ engine as part of this year's tutorial event. Or did you have to have videos? There are newer video series as well, but not C++.

I used and followed the instructions of this library. Nearly all of my serialization code ended up in one file.

I only develop on Windows right now, so I often miss feedback from the GCC and Clang compilers unless I check the workflow logs. All the platforms on Itch (win/mac/linix/html) are enabled by this GitHub Actions workflow which automatically deploys everything that's pushed to the main branch and just compiles and uploads test builds for any other branch. It's been modified from the libtcod template project to support Itch, but I can probably backport that feature. You can view the build logs from these workflows here.

GitHub | Playable

GitHub | Screenshot (Cave generation)

I'm working in C++17 and doing the ancient C++ tutorial on RogueBasin. I'm starting from the libtcod C++ template and plan on using the latest libtcod features rather than the older ones taught by that tutorial. My new repository is here.