Build 26002890

build

SLOP FIGHTER · public · first seen

PICS live
1
Branches
2
Depots changed
1.38 GB
Download delta
02:56 UTC
Time · UTC
Patch notes · published by the developer

Make-a-point update

On Steam

Hello. First off, thanks for sticking with the project. It's immensely difficult to both predict language forms and then even harder to decipher the code that facilitates them. I've basically left it in Claude's hands to handle that, and today, we've had a breakthrough.

What I've done, for my part, was trim even more unhelpful words from narration. Words like "electromagnetic", which don't apply in almost any situation, should be worked out. I've also directed changes to force nouns (e.g. "patience", for WATER types) and gone through each type with a fine-toothed comb to make sure that the language they use is suitable for the situation. WATER types won't use "soak" or "drench" as an attack mechanism, for example.

On top of that, voicework has been improved so the different personalities are more accurately expressive. SHAD types were difficult to conceptualise, but now they more acceptably embody the idea of striking from and with shadows. It was a bit hit and miss, but now it's pretty good.

CUSTOM COMMANDS have been improved immensely, and with it so have regular commands. RANGED attacks are so much more fluid and expressive now, due to code changes with how all attacks are interpreted. Claude says:
- Before, only RANGED changed the Narrate line, and PHYSICAL vs SPECIAL had no effect. Now the four combinations
each get their own instruction:
- Physical melee: a body part makes direct contact.
- Special melee: the same strike, charged with the type's energy.
- Physical ranged: matter from the body is flung across the gap.
- Special ranged: energy leaves the body and crosses the gap, with no contact.
- Named moves and custom commands use the same table.
- For custom commands, the physical-vs-special call now comes from the player's text. A bite is physical, a beam is
energy, and "rain spines" is physical ranged.
- Combat rules are unchanged: custom attacks are still SPECIAL there, which matters for SHAD's damage rules.

What this means is that description is better. My wording remains the same, it's the underlying mechanics that have been improved. I let Sonnet 5.5 have a go at it. Previously I've just been running it with Sonnet 4.6.

So what's the point? I'll tell you. Video game NPC narration can work one of two ways. I've been seeing recently people crafting their own LLM-assisted NPCs for video games. What they do is give a base LLM a rulebook on how to operate, so the LLM can mould itself to the character. It's common practice in roleplaying circles at the moment. The issue is that the potential for out-of-character behaviour is strong, and the LLM-driven character is... malleable, to say the least. If you insert an LLM into Halo you can have a Spartan buddy speak with a German accent if you want it to, for example. This is, in my opinion, an incorrect way of handling character. Spartans shouldn't do that sort of thing. It's an alignment problem.

The other way is my way, doing it the hard way, by working from the ground up and building a LoRA adapter that is trained solely on the words it can use and the ways it can use them. There is no flexibility for the NPC to behave out-of-character. It simply must try to narrate the way it is trained. This means that your NPC will always behave like your NPC.

Do I think this is the best way of handling NPC dialogue with an LLM? No. There must be a middleground between the two options where you don't have to teach the LLM a whole new grammar, which is bound to be fraught with missteps like bad interpretation and awkward phrasing. I'd go as far as saying this whole SLOP FIGHTER project would have been simpler without the mutations. If they were just animals fighting each other, it would be MUCH easier to account for things like fighting styles etc. But! You can't tell my NPCs to recite a recipe for beef bourguignon in the middle of a battle. It's a trade-off I'm happy to make.

LoRA adapters work for simple NPC interactions. Imagine a detective game where you interview suspects, for example. Would it take you out of the story if a suspect said "You're absolutely right! The clue is x, not y." It would. Instead, if that character was trained to speak a certain way, and the words it used could ONLY relate to the case (and maybe a few other colourful conversational fractals) then you would have a complete, bound NPC.

If you have ever worked hospitality or retail, you should understand what I mean.

That's what I'm trying to actually do here. I want this game to be an example of what LLMs can actually do for NPC dialogue. If I can find that midpoint between tied-down LoRA adapters and tight system prompting, that would be immense for the video games of the future. I think I'm close with what I can do linguistically, but something isn't quite right.

Anyway, enjoy the update. It's really good!

Per-depot manifest changes

Depot changes

All depots
DepotNew manifestPrevious manifest
44300514884169928181994750150682495660978644
443005288704597724021336047803139347547055691