Old error returns. :/

[Innomen]

Error
[ { "origin": "string", "code": "too_big", "maximum": 200, "inclusive": true, "path": [ "events", 15, "action" ], "message": "Too big: expected string to have <=200 characters" } ]

I did git pull, npm install, npm run build, and npm run start.

Garuda DGE (arch linux plasma kde etc)

Takes a couple turns to get to the error.

(Really hope to see the contemporary world setting open up soon, just sayin.)

[p-e-w]

The error message is telling you exactly where the problem occurs: at events[15].action. Open the state debugger (click the icon in the top right corner) and look at that value. What is it? Is it longer than 200 characters? Was it generated by the model, or typed by you?

[Innomen]

It's possible for me to type too much? That's probably what happened then. Input box needs some sanity checking then I guess, (also spell check access for the browser maybe?) If i can get it to happen again i'll let you know.

[p-e-w]

The input box has sanity checking, namely a limit of 200 characters, exactly as required. Are you sure you're running the latest version of Waidrin?

[Innomen]

Oh, well if it would have stopped me then i guess it wasnt me, i'll get more state data next time it happens. When it happens it erases a lot of progess backwards, my event log only goes ot 7 now, and the error was in 15, unless i'm misreading the state debugger. And as for latest version i did the stuff i said above to update it: git pull, npm install, npm run build, and npm run start, and i made a new "world" cleared the old one.

[p-e-w]

Please test if you can type arbitrarily long text in the action input. If you can, you're not running the latest version. It should prevent you from entering more than 200 characters.

[Innomen]

╭─innomen@innomen in repo: waidrin on  master via  v24.4.1
╰─λ npm run start

waidrin@0.1.0 start
next start

▲ Next.js 15.4.1

• Local: http://localhost:3000
• Network: http://192.168.1.170:3000

✓ Starting...
✓ Ready in 564ms

The text does indeed cut me off, and how could i possibly not be running the latest version after git pull, npm install, npm run build, and npm run start?

Where is the latest version indicated in the repo?

I'm used to releases.

[p-e-w]

Releases will happen once Waidrin is sufficiently stable. Currently, everything is WIP.

I don't quite understand how an action longer than 200 characters could appear in your setup. The next time it happens, please post more details, especially whether you typed the action yourself or chose it from the list, and what Waidrin was doing (status bar message) before the error appeared.

Also, what backend are you using? It might be that it doesn't respect the JSON schema length constraint.

[Innomen]

Will do, i'll test it tomorrow. llama.cpp.

[Innomen]

I can't reproduce the error, but i think it's because i'm picking prefab answers mostly and not typing my own. I really need the contemporary setting to inspire me XD I'll post back if i can make it stutter again. :)

[p-e-w]

I can't reproduce it either. It's difficult to understand what is going on here.

Regarding non-fantasy scenarios, I need to be completely frank: I don't see those coming for the next 2 months or so. Generalizing over scenario types will involve a substantial rewrite of much of the engine and state schemas, and that's only going to happen once the fantasy setup is rock-solid, because fixing the same problems three times is much more work than fixing them once.

[Innomen]

Well i'm not trying to be impatient, take your time, do it all right by your lights. But that surprises me. I don't see (from ignorance i'm sure) how the theme of the text would be so complicated mechanically. But then I'm not a coder. In my mind the whole thing amounts to prompt scaffolding where the content of the prompts is mostly code structure agnostic. Like you're not just telling it "generate fantasy X" and search and replace fantasy with contemporary I guess.

At any rate, i think if you do get contemporary going you'll see a surge of adoption once it gets around because man, scifi and elves are done to death. VTM bloodlines is cult classic for a reason. (You remind me of wesp hehe, a singular development heroic figure.)

Also, the contemporary thing allowed non-recreational use cases. Like how you can use silly tavern as an agent framework, the contemporary larp theme would allow like a company simulator in a similar way that could actually produce real outputs. Like simulating a software company and aiming it back at improving waidrin.

But yea good luck regardless, two months is still plenty fast for me /shrugs. Thanks again :)

[p-e-w]

I don't see (from ignorance i'm sure) how the theme of the text would be so complicated mechanically.

The whole point of Waidrin is that it uses structured information, not just plain text. It has specialized object schemas that contain fields like character races (currently "human/elf/dwarf"), location types ("tavern/market/road") etc. These are used to drive frontend features like flavor images, which are highly genre-specific. The UI itself is also currently designed to evoke a fantasy atmosphere, and I would want it to look very different for a sci-fi setup.

[Innomen]

Thanks for the explanation and the project :) Take all the time you need :)