I'm going to ignore all that and tell my developers working in complicated codebases that they have to use AI. I'm sure comprehending side effects in a world building text adventure is completely different that understanding spaghetti code
replyDesarcasmed version: "I think that problems with Zork make those models virtually useless in programming tasks." Correct?
replyHe said complicated code bases. LLMs are great at producing small snippets of code to address very targeted problems.
replyGreat on small snippets of code, passable on larger pieces of code, great at finding vulnerabilities in large pieces of code, terrible in Zork. All-in-all, a jagged frontier that defies a simple sarcastic characterization.
replyVery kiki, not very bouba, as Aphyr rightfully stated.
replyYou can code your prompts to read and write an external world model on the side. This is what most people do who are seriously doing games with LLMs.
replyWhat do you mean with this? What is this world model, what does it capture?
replyYou keep a document going called "state of the world", on every turn, you read this document in (as context), use it to help compute what happens, and based on what happens, create an updated "state of the world" document. You track important details so your LLM is consistent from turn to turn.
replyIf you doing an RPG, which I guess is where this is more obvious, you track the play and enemy positions, their health, their moods and perhaps top thoughts, the state of important inanimate objects. if you break down the door, you update the door's state in the document. This is in contrast to just giving the LLM the previous turns and hoping it realizes the door is broken down later (just by statistical completion).
I would love to see consistent-world-state-capturing more integrated into, for example, SillyTavern.
replywe should talk. i sent you an email.
reply