hexdecimal / tcod-cpp-engine-2022

A modern roguelike engine made while following the older libtcod tutorials.

Libtcod C++ engine 2022

A modern roguelike engine loosely following the Complete roguelike tutorial using C++ and libtcod. As part of the RoguelikeDev Does The Complete Roguelike Tutorial (2022) series.

How to setup

• Make sure you have the correct tools ready.
  • For example on Windows: Make sure you install the C++ compiler tools from Visual Studio Community, install the latest CMake, and install Visual Studio Code.
• Clone the repository.
• Make sure to initialize the vcpkg and libtcod submodules. If either folder is empty then the build process will fail.
  • The command to do this is: git submodule update --init --recursive
• Load this project in VS Code and install any recommended plugins. Most importantly: C/C++, C++ Intellisense, and CMake Tools.
• Using the CMake Tools plugin you can now build and run this project. Dependencies will automatically be installed via Vcpkg.
  • On Windows, when CMake Tools asks for a toolkit you should select Visual Studio Community ... - amd64.
• The project will now build and run with F5.

tcod-cpp-engine-2022's Issues

More detailed map memory.

The current map memory only tracks terrain tiles. I want to update this to track everything. Tracking seen tiles by their graphic is probably the easiest way to do this.

Add equipment.

This engine is missing the equipment items from the Python tutorial (this was not part of the C++ tutorial.)

http://rogueliketutorials.com/tutorials/tcod/v2/part-13/

Make items more generic.

Right now items are setup as an abstract class and use polymorphic subclasses to define behavior. I want to change this so that items are a generic mostly-static type which can point to the behaviors they use. This should make it easier to add and remove item behaviors since right now serialization is a real pain.

Data associated with items should be moved to a dictionary like type. Something like std::unordered_map<std::string, std::any> or something more strict.

Make a database for monsters.

Monster stats are hard coded to the map generator. I'd like to move these to some kind of database-like system.

Continuous actions / autoexplore.

I want to implement a system for long running actions such as autoexpore.

Mouse support.

The mouse is supported in some menus but not others. In theory it shouldn't be too hard to have full mouse support like in Brogue.

• Inventory mouse support.
• Right click to dismiss menus.
• Click away to dismiss menus.
• In-game mouse menu for actions. As an always visible or right-click menu.
• In-game mouse movement. Like in Brogue.

Add animations.

I'd like to add animations for the spells. This will involve some refactors to the state handling, but it should be too difficult to actually design the animations.

Throwable potions/items.

Things like the scroll of confusion might make more sense as a confusion potion which you can throw at enemies.