#versu — Public Fediverse posts

The expansions generating that code look something like this. #suetum #versu #praxis

The expansions generating that code look something like this. #suetum #versu #praxis

Well, even though I was working on Selanía too these days, I've been able to get to the end of the expansion mechanism too! Now I can write stuff like

```
Have you heard of what [Gossippee.subj] said yesterday?
No! What did [Gossippee.subj] do?
Well, you know, someone gave [Gossippee.obj] the excuse to...
```

And have it expand to

```
Have you heard of what Mary said yesterday?
No! What did she do?
Well, you know, someone gave her the excuse to...
```

#suetum #versu #praxis

Well, even though I was working on Selanía too these days, I've been able to get to the end of the expansion mechanism too! Now I can write stuff like

```
Have you heard of what [Gossippee.subj] said yesterday?
No! What did [Gossippee.subj] do?
Well, you know, someone gave [Gossippee.obj] the excuse to...
```

And have it expand to

```
Have you heard of what Mary said yesterday?
No! What did she do?
Well, you know, someone gave her the excuse to...
```

#suetum #versu #praxis

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

Every time I work with #Avalonia and #ReactiveUI I'm equal parts delighted and enraged. Anyway! The foundations of the debugging tool are on.

Right now I've built an (optional) server that provides the debugging tool for the data necessary to see the internal state of the game as it runs. Simple JSON/RPC over TCP connection, nothing fancy. The idea is to build two main parts: one for querying the fact list, another for the practices and actions.

#suetum #versu #praxis

I finally have a #Suetum program actually running to its end!!!

As the #Versu papers suggested, the actual program is insanely long for such a simple interaction (it's about 120 lines), but after all, the interesting part is that this puts the basis for multiple, interacting practices.

So, during the holidays I'll probably put up a basic support for the editor (would love that to be #JetbrainsRider, but I've only created #vscode extensions!) and debugging tools!

#praxis

The fact that I could express the whole search algorithm over desired world states in my #versu re-engineering in a single, concise #LINQ query is both fantastic and terrifying.