A persistent world is a game state that carries on existing after you log out: a city your hero is actually standing in, a clock that runs for everyone at the same time, a distance that takes hours to cross. A chat window does none of that, because a chat window is not a place; it is a conversation with as much past as its last few messages happen to remember. This page makes the difference concrete: the measurements of a continent, a calendar nobody can pause, NPCs who remember what you told them, journeys that take real hours and are itemised to the coin, events that stop the road, an economy in which players work for each other. And one thing the world deliberately does not do: an adventure at the table never moves your body.
What does a persistent world mean?
A persistent world is a game universe that every player shares, that keeps its state regardless of whether any one player is connected, and whose time runs on its own. The term comes from online roleplaying games, and there it is not so much a definition as a promise: close the game and the world does not vanish; open it again and you resume not where you left off, but where the world has got to. In AI roleplay the idea has only recently come to matter, because the thing an AI is best at (producing fluent prose) and the thing a world requires (a state that is shared, impartial and does not forget) are two completely different jobs.
Three questions will tell you whether something is really a persistent world. If the answer to any of them is no, what you have is not a world; it is a scene.
- Is the state kept in a record? Your hit points, your purse, your shop, your inventory and your location have to live in a database row, not inside a block of text. A number that gets summarised away when the conversation grows long was never persistent to begin with.
- Does time run for everyone at once? The world's clock must not depend on you. Morning has to arrive while you are asleep, and days have to pass for a player who never logs in at all.
- Is distance real? You should not be able to cross the gap between two cities with a sentence. A journey should cost hours, rations, money and risk. If it costs none of those, the map is scenery.
Those three conditions matter for play, not for engineering. A decision is only a decision if it costs something. If moving from one city to another is free, which city you are in stops meaning anything. If nobody's time is passing, being late for an appointment is impossible. If state is not kept in a record, nobody can promise that the shop you set up last month is still standing today. A persistent world is really just the infrastructure version of the sentence "let your choices have weight".
Why a chat window is not a persistent world
When you play a tabletop RPG with a chat bot, the world is the conversation. That sounds harmless enough, but the consequences are heavy. Close the conversation and the world stops. Let it run long and it is quietly summarised, and the details left out of the summary never come back. Most importantly, that world belongs to you alone. When your friend opens the same tavern in their own window, it is a different tavern; there is no single place that both of you can see. Without a shared place there is no gossip, no economy, no rivalry, and no running into anyone.
The difference shows up most clearly in distance. In a chat window, the sentence "I get on my horse and ride to the port city" puts you in the port city. It costs nothing, takes no time and carries no risk, and nothing happens on the way because there is no way. In a persistent world the same sentence turns into something else entirely: a route, a number of hours, a ration bill worked out per head, stops to pass through, and events that can genuinely befall you out there. One sentence, and on one side it is a scene transition, on the other a decision.
The second difference is the clock. In a chat, time stretches to fit the story: "three days later" when that is what the scene needs, and one endless evening when that is what it needs instead. It is wonderful flexibility for telling a story, and that is exactly why it cannot build a world. If there is no calendar everyone is looking at together, there is no way to say that two players mean the same moment when they both say "right now".
The map: the size of Velthara
Thavernia's world layer is a continent called Velthara, and its measurements are out in the open:
- 15 cities across 5 regions. Every city has an economy multiplier of its own; the same goods do not sell for the same price everywhere.
- 24 hand-authored roads. The roads were not generated. Each one has its own name, its own stops and its own danger rating.
- 330 buildings, 489 rooms. Cities are not labels pinned to a map. They are places you walk into and stand inside.
- 319 named NPCs. Every one of them has a name, a job, and a history you can build with them.
Hand-authored roads look like a small detail, but they are exactly what gives the world its character. In a generated road network every road is the same road, and none of them is memorable. A road with a name, a set of stops and a danger rating becomes something players can talk about: which route is long but safe, which inn is expensive but good, which pass nobody walks at night. That is the sort of knowledge that makes a world liveable.
The map itself is drawn like a sheet of parchment spread out on a desk, tilted a little by perspective. The pins and the city names, though, stay upright; they do not lean along with the surface underneath them. That is not an aesthetic whim but a matter of legibility, because slanted labels on a slanted map would look handsome and read badly.
The shared clock: a calendar nobody can pause
Velthara's clock runs for everyone at the same time. The scale is this: one real hour is four Thavernia hours. So a Velthara day, meaning 24 game hours, fills up in six real hours. Days pass in the world on the days you do not log in, and when you come back the next morning the calendar has not waited for you.
The calendar is the world's own, not ours in costume. The year is counted as KB 412, reckoned from the Kadeh Barışı onward. A year splits into twelve months of exactly thirty days each, and at the end of it stand five Kül days that belong to no month and no week. The week is six days long: Kadehgünü, Yolgünü, Ocakgünü, Ağgünü, Surgünü, Külgünü. The day is divided not into watches of six hours but into six watches of four hours each: Tan, Har, Bağ, Dem, Fener, Kor. A timestamp therefore reads something like "KB 412, Bağbozumu 14, Yolgünü, Fener vakti".
The technical side of the clock matters for what it produces. Time is not advanced by a background job; it is calculated at the moment it is asked for. In practice that means the clock cannot break, cannot skip a tick, cannot be wound back, and cannot be paused by anything a single player does. You can stop your own journey, pull into camp, leave the game shut for weeks. The world's clock cares about none of it.
Cities, NPCs and remembered conversations
Entering a city is not a matter of picking from a menu. You walk. There are districts, buildings inside the districts, rooms inside the buildings. You knock on a door, go in, and talk to the person there. An NPC is not a button: they have a name, a job, and a reason for being in that room. The 330 buildings and 489 rooms underneath the city layer exist precisely for this, because "I went into the city" and "I went into the back room of the salt store on the docks" are not the same game.
The real persistence here, though, is in the memory layer. NPCs remember what you told them across sessions. Tell someone your name, your trade and your intentions today, and when you come back a fortnight later the conversation does not start from zero. More than that, what was said does not stay shut in that room: what is spoken becomes city gossip, and gossip spreads. In a world, reputation is only possible on the condition that somebody remembers something.
Cities have an economic identity of their own as well. Each has its own economy multiplier, which is to say the same goods do not sit at the same price in every city. That lays the groundwork for the business and player-economy sections below: where you make a thing and where you sell it start to matter.
Your hero's first position in this world is set at character creation. When you build a character you choose a starting city from a list, and beside each city stands a short description of what sort of place it is. The city you pick is where your hero is physically standing in the world.
Travel: real hours, a real route, a real budget
When you want to go from one city to another, you choose the destination and the server works out the rest. The shortest route across the road network is found, which means that for two cities with no direct road the route is built in several legs, through the cities in between. What comes back to you is not a confirmation box. It is a travel plan.
- Route and stops. How many game hours the road takes, which stops it passes through (inns, caravanserais, villages, lighthouses) and at which hour you reach each one.
- Lodging and meals. At every stop you can choose separately whether to sleep or to eat. None of it is compulsory, and all of it is priced.
- An itemised budget. The total is laid out line by line before you set off, so nothing surprises you later.
- Rations. Provisions are counted per head: one share for every 8 game hours. A larger caravan eats more, and that is one of the journey's cost lines.
- Compulsory rest. A road longer than 12 game hours cannot be started without at least one stay booked. Nobody walks for three days without sleeping.
The moment you confirm, the journey starts running in real time. Your hero's portrait moves along the curving road on the map, and so do the portraits of the friends who are on that same road. Working out how long a journey takes is easy: four game hours to one real hour. This is the part of the world that draws the most objections and does the most work, because the only thing that turns distance into distance is waiting.
Your companions come with you. Your AI travelling companions are part of the caravan, which means they count towards the rations and they share in whatever happens on the road. Travelling in numbers is more expensive than travelling alone, and safer.
Making camp, and turning back
You can make camp anywhere on the road. Camp stops your journey clock: the road does not advance and your arrival slides back. What does not stop is the world's clock. While you sit in camp, days go on passing in Velthara. Camp is not a free waiting room either, because you still eat during those hours, and the rations for that time are added to the bill when you set out again. If the purse comes up short the journey still continues, so nobody is left locked in place halfway along a road.
You can also abandon a journey altogether, but the direction of abandoning is fixed: backwards. Cancel, and you return to the last town you passed; you are never carried forward. Without that rule, cancelling would turn into a free shortcut: walk three quarters of the way, quit, and land in the destination city. The direction rule closes that off from the start.
Road events and the one-session adventure
What keeps the road from being an empty progress bar is events. Events are set up the moment you depart, spread across the hours, and fire when their time comes. What happens to you happens because you have reached that hour of the road, not because you opened the screen. How many events there are depends on the length and the danger of the road, and how many companions you travel with lowers the chance of a bad one.
- Bad events: bandits blocking the road, a robbery in the night, a storm that closes the way. These stop the road.
- An opportunity: a caravan sighted. Set an ambush if you like, and carry on with the loot.
- Good events: a wanderer you meet on the road, a bard who keeps you company, a shortcut a shepherd points out.
When a bad event comes up, the road stops in earnest and two doors stand in front of you. The first is to pay it off: something leaves the purse, the matter closes, and the road resumes where it stopped. The second is to settle it by fighting: the event turns into a one-session adventure, you sit down at that table, play it and finish it. When the adventure ends the road opens again, and the journey continues from the hour it stopped at.
This bridge is the one point where the world layer and the table layer touch, and it is deliberately one-way. The world hands you an adventure, and the adventure hands the world one result: the road opens, or it does not. That is the whole of the adventure's job. It does not put you anywhere else on the map.
The caravan: friends on the same road
You can set out with friends, on two conditions. First, the person you invite has to be in the same city as you. Second, the invitation has to be accepted within the first two game hours of the road, which is roughly the first thirty real minutes. The reasoning explains more than the rule does: a caravan leaves by the same gate. You do not join a group that left half a day ago by appearing beside them from another city.
For the length of the road the caravan gets a chat of its own, and that chat lives exactly as long as the journey does. It is not only people talking in it: the AI companions join in on their own initiative and answer in their own manner. The best part of the travelling hours usually happens right here, because there is nothing else to do while walking and the table talk finally has somewhere in the world to land.
Travelling together is the most concrete form of the shared half of a persistent world. Being on the same road means being caught by the same event together and staying the same night at the same inn. In a chat window there is no way at all to say that two players are on the same road, because there is no one road there to be on.
Owning a shop in several cities at once
There are four trades in the world: fishmonger, baker, blacksmith and innkeeper. None of them is an extension of the town layer; they are the world's own economy. And the most important design decision is this: you can open the same trade in more than one city, and your shops do not blur into each other.
- Its own till. Each shop's income builds up in its own till. By default it holds 48 hours of income, and that window grows as the shop levels up.
- Its own orders. A customer's commission in one city drops into the workshop list in that city.
- Its own upgrades. An investment you make in one city does not grow your shop in another.
- Its own ledger. You see which shop is earning and which is sinking, separately.
- Its own shelf prices. The tag on the same goods in Kelmirin and the tag in Serazad are independent of each other.
Why the separation matters this much becomes clear the moment you imagine a world without it. With one shared till, a second shop would only be a multiplier: open it, forget it, watch the income double. Separate tills, separate orders and separate shelves make each shop a separate place instead. Neglect a distant shop and the customer in that city waits, the till fills and then overflows. Opening a shop in a second city is not an upgrade. It is a responsibility.
Each trade has a rhythm of its own as well. The inn keeps a board that posts one job a day, and that job is now different in every city, so running inns in two cities means two separate workflows. The pantry of a fishmonger or a baker sets aside one fresh good every 12 hours and holds at most three. The blacksmith's forge hammers out one piece every 14 days: rare, waited for, and valuable for exactly that reason.
The way this production ties back into the world is through the cities' own goods. There are 120 items written for the fifteen cities: a signature line for every city's smithy, one piece per rarity, and provisions of their own for every fishmonger and baker, drawn out of that city's own story. Kelmirin cures lake carp in willow smoke. Serazad dries canal carp and prepares spiced cistern eel. Drathar forges chain-gate armour. Morvael turns out an icebreaker axe. When the forge is lit, the piece that comes out is that city's own 60 per cent of the time, and the rest comes from the shared catalogue. The upshot: where a blacksmith works becomes readable from what they make.
The player economy: shopfronts, escrow, commissions
Each city lists the shopfronts of the businesses other players run there. The goods you see when you walk into a city are not a stock list the system generated; they are the shelves of real players keeping shop. You can do two things with them: buy what is sitting ready on the shelf, or commission a piece from a maker.
When you place a commission the money leaves your purse immediately, but it does not go to the seller. It waits in escrow. When the maker finishes the work and delivers it, the escrow resolves: the goods go to the buyer and the payment to the seller. Cancel an undelivered commission and what you paid comes back to you. Escrow does not exist because of trust; it exists so that trust is not needed. The seller starts work because the buyer has paid, and the seller cannot collect until the work is delivered. Neither side has to rely on the other's good intentions.
The owner sets the price, but that freedom has limits. The server clamps the shelf price at both ends: the floor is the production cost, the ceiling is three times the catalogue price for that city. The floor keeps loss-making prices, which distort the economy, off the shelves; the ceiling keeps the only producer of a scarce good from pushing the price to the roof. The space in between is still wide: an expensive, good shop and a cheap, fast one are both possible.
What the world deliberately does not do
The part most often skipped when persistent worlds are described is what the world chooses not to do. The most important boundary here is this: an adventure played at the table does not move your body. Even if the story told in that adventure crosses to the far side of a sea, when it ends your hero is still standing in the city they walked into on the map. Only two things change your location: walking in a city, and travelling. That separation is deliberate, because if position were left to a narrative decision, the entire cost of distance could be zeroed out with a single sentence.
The second boundary is about what an adventure may write into the world. Structural changes stay inside the adventure: an inn that burns down there does not burn down the continent's inn, and a bridge that collapses does not close a road on the map. What crosses into the shared world is social traces, meaning the NPCs you met and the gossip you left behind. The reason is simple: one table's decision should not rewrite the world of hundreds of players who never sat at it. In a shared world, persistence is only fair together with its limits.
The third boundary is about time, and it is the one people complain about most: the world does not stop for you. You cannot speed a journey up, wind the clock forward, or buy your way out of waiting. You can stop your own journey clock by making camp, and the calendar still runs. That is not a shortcoming, it is the price of persistence. The moment waiting is removed, distance goes with it, and the moment distance goes, the map turns into scenery.
Frequently asked questions
What does a persistent world mean?
A persistent world is a game universe shared by every player, one that keeps its state after you log out and whose time runs on its own. It has three conditions: state is kept in a record rather than inside a block of text, the clock runs in common for everyone, and distance is real. If one of them is missing, what you have is not a world but a scene. In Thavernia this layer is the continent of Velthara, and it is a place that keeps running separately from the adventures played at the table.
What is the difference between a chat window and a persistent world?
In a chat window the world is the conversation itself: close it and it stops, let it run long and it gets summarised, and what exists for you does not exist for anyone else. The difference is most visible in distance. In a chat, "I'm off to the other city" simply puts you there, at zero cost. In a persistent world the same sentence means a route, a duration, a ration bill and a risk. A chat window is not a bad tool, but it is not a place.
How does game time relate to real time?
One real hour is four Thavernia hours. So a Velthara day, meaning 24 game hours, takes six real hours. The calendar is the world's own: the year is KB 412, twelve months of thirty days each, and five Kül days at the end of the year that belong to no month and no week. The clock is not advanced by a background job; it is calculated the moment it is asked for. That is why it cannot break, cannot be wound back, and cannot be paused by anything a single player does.
Does travel really take time, or can I skip it?
It takes time and it cannot be skipped. Choose a destination and the server works out the route, shows the stops and an itemised budget, you confirm, and the road starts running in real time. You can make camp and stop your own journey clock, but the world's clock does not stop. You can abandon a journey, but abandoning takes you back to the last town behind you rather than forward, so cancelling is never a shortcut.
Can I invite a friend on a journey?
Yes, on two conditions: your friend has to be in the same city as you, and the invitation has to be accepted within the first two game hours of the road, which is roughly the first thirty real minutes. The reason is simple: a caravan leaves by the same gate, and you cannot catch up to travellers who are already halfway there. A caravan chat opens for the length of the road, and it is not only people who talk in it: the AI companions join in on their own.
If I die on the road, is my character gone?
No. On road tables death is not permanent: if the party goes down entirely the heroes do not die, they wake in the nearest city on the route, and the journey ends there. What you lose is progress and money, not a character. This is a separate rule from the risk of death at a campaign table. The world layer exists to make distance real, not to punish you.
Can I run the same trade in more than one city?
Yes, and your shops do not blur into each other. The same trade can be opened in several cities at once, and each shop has its own till, its own orders, its own upgrades, its own ledger and its own shelf prices. A till holds 48 hours of income by default, and that window grows as the shop levels up. A shop you neglect in one city is never fed by the earnings of your shop in another.
Does an adventure at the table move my character to another city?
No, it does not, and that is deliberate. Only walking and travelling move your body. Structural things that happen in an adventure stay inside it: an inn that burns down there does not burn down the continent's inn. What crosses into the shared world is social traces, meaning the NPCs you met and the gossip you left behind.