Working on the LSP VSCode extension for #suetum posed interesting questions, like "what is a variable definition in a logic programming language"?

Formally there's nothing like a declaration in that case, but the best way to put it is that the first time a variable is used, this is where it gets declared, and since Suetum integrates logic and imperative programming, it's been cool to notice that every reference in the imperative part must have a counterpart in the logic one to be correct!

In order to expand strings like
"Hello, [greeting.towards.Person]."
I must know context about Person (like: do I hate them? I love them? I'm neutral?), which means that intelligent expansions must be used (context free grammars with conditions from the current state of the game, in practice), which means that they are not just syntactic replacement but need the whole machinery of the runtime engine, which means moving lots of code... AAAAA xD

#Suetum #versu #praxis

Since I have a little lull in the development of Selanìa, I'm advancing with #Suetum.

The system is more and more getting structured in a way that allows for parts of the project to be used independently. One can just use the fact list as a knowledge base, or just the expansion mechanism, just the instructions, or multiple parts combined into something different from Suetum (e.g.: with this architecture, one could implement a Lume-like system based on exclusion logic: https://www.researchgate.net/publication/335590895_Lume_a_system_for_procedural_story_generation )

Ian Horswill is writing a book that is a very good introduction to formalisms around procedural generation.

I love how it is quite focused on text generation, but it shows how very similar techniques can be applied to e.g. generating environments.

Very well written, clear, to the point, without sacrificing precision.

I will definitely use lots of the elements laid out here to work on the expansion/interpolation mechanism in #Suetum .

https://ianhorswill.github.io/DPGD/index.html