GenghisKen CoarWell, there we go. I just uploaded the current state of my experimental and woefully incomplete TAGF (Text Adventure Game Framework #ruby #gem to #github. https://github.com/RoUS/rubygem-tagf
Basically 10K lines of undesigned brain vomit. Be kind.
The parts Im dreading include
1. Command line parsing a player input command; even approximate natural-language processing, or even a unicellur attempt is terrifying.
2, Working around `readline`s old-nonreentrant libc mechanisms when it comes to saving & restoring history; multi-layer reading from the message buffer and restoring them properly; and handling special cases (ADVENT's bird & snake, bird and dragon, ADVENT's bird & rod)l ...
1. Command line parsing a player input command; even approximate natural-language processing, or even a unicellur attempt is terrifying.
2, Working around `readline`s old-nonreentrant libc mechanisms when it comes to saving & restoring history; multi-layer reading from the message buffer and restoring them properly; and handling special cases (ADVENT's bird & snake, bird and dragon, ADVENT's bird & rod)l ...
In order to check things like location adjacency and shortest-path routing, I've cheated by embedding the #RGL #Ruby #graph package into the base code. Among other things, this makes it simple during game development to detect things like unreachable locations. It has the delightful side-effect of making it simplicity itself to generate a graphical map of the game!
#tagf #gaming #gamedev #digraphs #textadventure
#tagf #gaming #gamedev #digraphs #textadventure
I wanted to find some stuff I'd done with the #cri #Ruby #gem. When I found it, I was gobsmacked: in my sleep-deprived state, it looked bloody brilliant! And, of course, totally undocumented. So I'm going to document the original code and then adapt it into #TAGF for things like
ππππ ππππππ --ππππππ=ππππ.π’πππ --ππππππ=πΏπ½πΆ
and
ππππ ππππππππ --ππππππ=ππππ.π’πππ
and maybe even
ππππ πππ --ππππππ=ππππ.π’πππ