nests-and-insects VS wh40ksim

I wrote my PhD in LaTex with the simplest template I could find online (luckily someone hat put one up formatted for my university's engineering department and I didn't have to mess with it almost at all).

But once I was done, I wanted to blow off some steam and started writing a silly little tabletop RPG. I decided the rulebook would be text-only for portability with box drawing borders and ASCII tables and stuff, so I spent the first week or so writing a small ASCII typesetting engine in Prolog (because logic programmer).

And then I spent more time writing a vim syntax file so I could read the glorious ASCII with syntax highlighting.

Here:

https://github.com/stassa/nests-and-insects

I'm still looking for ANSI/ ASCII art contributions btw.

Sorry to plug my game but the way it works is that characters have a Base Attack and Special Attack, and which attack hits or misses depends on the Degree of Success (DoS) of the attack roll.

This is absolutely very interesting to me! My own game is inspired by roguelikes and it's got text-based art. I was going to go with pixel art for my next game but you ninja'd me :P

Probably not what you are looking for but my game, Nests & Insects, is designed to remove all arithmetic from action resolution it and it is very, very far from a rules-light game like Lasers & Feeling. It's a roll-under-and-over d100 game. Even increasing or reducing the value of "Features" is done without arithmetic.

Here's some stuff I've written in Prolog, some for my own enjoyment, one for my degree project.

Most of the benefits I found come down to two things:

a) Prolog, like the various kanrens, is a relational language so a program is effectively a database. There's no need to do anything special to glue together a data layer and a logic layer, because you have both written in Prolog.

b) Prolog's declarative style makes translating rules and directives to code a breeze. The three projects below are all games and benefit heavily from this feature. I

1. Warhammer 40K simulation:

https://github.com/stassa/wh40ksim

Runs simulations of combat between WH40k units.

2. Gleemin, a Magic: the Gathering expert system:

https://github.com/stassa/Gleemin

Doesn't work anymore! Because backwards compatibility. Includes a) a parser for the rules text on M:tG cards written in Prolog's Definite Clause Grammars notation, b) a rules engine and c) a (primitive) AI player. The parser translates rules text from cards into rules engine calls. The cards themselves are Prolog predicates. Your data and your program are one and now you can also do stuff with them.

3. Nests & Insects, a roguelike TTRPG:

https://github.com/stassa/nests-and-insects

WIP! Here I use Prolog to keep the data about my tabletop rpg organised, and also to automatically fill-in the character sheets typeset in the rulebook. The Prolog code runs a character creation process and generates completed character sheets. I plan to do the same for enemies' stat blocks, various procedural generation tables, etc. I also use Prolog to typeset the ASCII-styled rulebook, but that's probably not a good application of Prolog.

You asked about "logic programming" in general and not miniKanren in particular. I haven't actually used miniKanren, so I commented about the logic programming language I've used the most, Prolog. I hope that's not a thread hijack!

All three of the projects above are basically games. I have more "serious" stuff on my github but I feel a certain shortfall of gravitas, I suppose.