The Party is the Game: Why AI RPGs Need Friction, Not Just Infinite Stories

When constraints become narrative

You need to get into a manor. The obvious route is guarded. Your rogue could scale the wall, but your mage has exactly the wrong spell prepared. One companion knows the family inside, but bringing her along will definitely make things worse. Your best fighter is currently nursing a cracked rib because of a stupid thing you did twenty minutes ago.

None of these facts are interesting alone. Together, they're the game.

That is the enduring trick behind party RPGs. They give you a collection of competing priorities, capabilities, and relationships, and then let the world put pressure on them. The best ones—from the Infinity Engine classics to Baldur's Gate 3—aren't really about controlling four characters instead of one. They're about having more things that can go wrong in interesting ways.

The question isn't whether your party has a tank. It's whether swapping one member of the group fundamentally changes what you know, where you can go, and what plans seem plausible.

The limits of authored reactivity

Modern CRPGs have pushed authored reactivity to its absolute limits. You can talk, sneak, spell-cast, or explode your way through encounters in ways that feel entirely unique to your playthrough.

But every traditional RPG eventually reaches the edge of its possibility space. You'll inevitably find a door you can't climb through even though your character obviously could, or a companion who should have an opinion on your recent betrayal but just stands there waiting for their next programmed trigger.

This isn't bad design; it's just the basic economics of authored video games. Developers can anticipate an absurd number of player decisions, but they cannot anticipate all of them.

Tabletop RPGs don't have this problem because a human GM can adjudicate the stupid plan you invented five seconds ago. Computer RPGs have spent forty years trying to fake pieces of that flexibility.

The Calvinball problem with "AI Storytellers"

This is where text-based RPGs and language models are making things interesting again—but a lot of current projects are learning the wrong lessons.

Understanding natural language intent isn't the hard part anymore. Parsing a player typing, "Mara keeps the watchman occupied while Ellis looks for a second-floor window" is trivial.

The hard part is what the game actually does with it.

A pure AI storyteller can just make something up. That's fun for a few minutes, but it destroys the very thing that makes RPG systems satisfying: resistance.

If Ellis finds a window simply because it makes for a dramatic scene, why did I bother leveling Ellis's perception? If an NPC's disposition is whatever produces the most interesting next paragraph, why should I care how I treated them yesterday? An RPG needs the ability to say no, or yes, but, and have those answers grounded in something more durable than a language model's instinct to keep a story moving.

Without underlying game mechanics, you aren't playing an RPG. You're playing Calvinball with a very eloquent dungeon master.

Game state first. Prose second.

This distinction is the entire foundation of Otherlands. We aren't trying to build a chatbot that roleplays being a game. We're putting a language interface in front of a persistent, simulated game state.

We separate the two questions that AI games usually collapse into one:

• What is the player trying to do? (Where language models excel).
• What actually happens? (Where traditional game state and friction are required).

In Otherlands, characters are physically somewhere. Resources are finite. Injuries matter. Information has to come from someone. If there's a storm between your party and the next town, we don't need a quest designer to write a branching narrative about it. The game state already knows one of your characters is injured and another is carrying repair gear. The story emerges procedurally from the friction of those overlapping facts.

A modern, accessible engine

Because we are rendering a complex simulation through text rather than demanding a massive 3D rendering pipeline, we don't have to care what hardware you own.

Otherlands is designed as a browser RPG. You don't need to download a heavy client, which means it is natively a Mac RPG, a Linux RPG, and a PC RPG right out of the box. No Steam required. No installation. The processing happens under the hood; all you need is a browser and an internet connection to access the simulation.

The computer handles what it's good at: tracking thousands of state changes, maintaining inventories, and simulating a continuous world. You handle what humans are good at: looking at the mess you're in and saying, "Given the people and things I have with me, what could actually work?"