This is a port of the Python code from the "Complete Roguelike Tutorial, using python+libtcod" into Common Lisp using cl-tcod (the official version needs to be updated though, see below). It uses libtcod (a.k.a. "The Doryen Library") through the Common Foreign Function Interface, CFFI. Commentary on writing this tutorial in lisp will be found on my blog in the near future, and linked here.
The code is basically a straight "translation" from Python to Common Lisp, and is not necessarily "lispy" in it's current form. This was done on purpose to make it easy to refer to the original tutorial, and to reduce the chance of bugs in making sure this works as a proof of concept of a roguelike in lisp.
Everything works exactly the same in terms of gameplay and presentation, as near as I can tell. The only exception is that currently cannot restore savegames where a monster was confused (via a "scroll of confusion"). This is due to the use of a recursive anonymous function (lambda). There are probably several ways around this, but for the purposes of this tutorial translation this is a minor issue and will be left as is for now.
cl-tcod is in the process of being updated to fix some bugs with the latest version of libtcod. For now there is a working fork available on Github as cl-tcod.
This code has only been tested with the current versions of libtcod (1.6.2), SBCL (1.3.12), and SDL (2.0.5) on x86-64 Arch Linux.
If current versions are prepackaged for your OS (downloaded binaries, apt-get, pacman, etc.) that is preferred, otherwise build from source.
- Common Lisp (e.g. SBCL)
- quicklisp
- libtcod (and its requirements, namely SDL2)
- cl-tcod (to quickload it, clone it to
local-projects; see the FAQ) - GNU Emacs with SLIME (not required, but highly recommended)
Then all one needs to do is open one of the tutorial-part##.lisp files in Emacs and load it (M-x slime-load-file or C-c C-l) with SLIME running.
All of the code works (other than the saving caveat mentioned above), but is missing some of the original Python comments and lisp specific comments. The code is not necessarily pretty, well organized, or in a final state. Updates will be made as the blog posts go up for each part. It is possible in the future to produce a "lisp first" approach to the tutorial, but that is not planned yet.