Going to tell the Preface story tomorrow at work, I guess if your reading this you now know my HN handle ;) Not sure I will do the 'game' but that into was worth clicking the link.
> I guess if your reading this you now know my HN handle
No worries. A great philosopher once wrote:
"There is a theory which states that if ever anyone discovers exactly what your HN handle is for and why it is here, it will instantly disappear and be replaced by an HN handle even more bizarre and inexplicable."
Just for curiosity I just asked chat deepseek to load and solve the game and it solved it in half a second.
It suggested adding some riddle, for example:
path(castle, up, tower) :-
at(blueprint, holding),
(solved_riddle -> true ;
write('Answer the riddle first: What walks on four legs in the morning...?'), nl,
read(Answer),
(Answer = 'human' -> assert(solved_riddle) ;
write('Wrong! Try again.'), nl, fail)).
That's only if you are using pure predicates.
From a quick glance, the code makes liberal use of assert, retract, and the cut operator, so you can't write a query that solves the problem automatically.
I have never heard of Prolog before so this was cool. I did think the "make sure the flashlight is turned on" point was kind of confusing. I have the battery and flashlight, but there's no way to turn it on. I couldn't run it with gprolog but swipl works fine.
This condition is checked when you try to reach "woods" and "woods_1". (And that's the only place you can test if the flashlight is on, because it's otherwise not checked and doesn't change any of the descriptions.) The flashlight doesn't save you from dying in the "deepforest_X".
Good catch! Although I do have some README.md templates where I use "yourusername" or whatever. I bet it would be said it was generated by an LLM. :/ Oh well, it still would take someone skilled to have it made by an LLM anyways. :D
I only learned Prolog as a hobby, so I may be mistaken, but the quality of the code seems really bad? Starting from keeping game state in a bunch of magic globals (assert/retract everywhere), to a lack of input parsing (even though DCGs would be a perfect match), to comments that disagree with the code[1], to the game logic coupled with game mechanics as side effects (the winning condition is checked inside `take`)... I may be too used to Prolog code from books and tutorials, but the number of cuts also seems much larger than expected.
...now that I look at this, it's 3 years old. I wonder how much better today's LLMs would fare?
When I was in school I had to do some stuff with prolog. I got my wife interested enough that she added some rooms and items to a game like this. Good times!
-▶ swipl -s treasure_hunt.pl
Welcome to SWI-Prolog (threaded, 64 bits, version 9.2.9)
SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software.
Please run ?- license. for legal details.
For online help and background, visit https://www.swi-prolog.org
For built-in help, use ?- help(Topic). or ?- apropos(Word).
?- start. % <- this
Enter commands using standard Prolog syntax.
Available commands are:
start. -- to start the game.
up. down. right. left. -- to go in that direction.
...etc...
https://github.com/Dialog-IF/dialog/
https://linusakesson.net/dialog/