Why this Minecraft world is built to last

Sunday Market is a public 18+ Minecraft survival SMP for Java and Bedrock players, and it runs one persistent world with no scheduled resets. The world, Omeyocan, began in June 2026 and has never been wiped. There is no season clock and no planned fresh map, so a house you build this week is meant to still stand in years. A promise like that is easy to write on a homepage and harder to keep on a server, so this piece covers what keeping it involves and why we think it is worth the work.

What "no scheduled resets" means

Many survival servers run in seasons. At the end of a season the operators archive the map, start a new one and everyone begins again with empty hands. Seasons solve real problems: the economy starts clean, new terrain arrives with each update, and old bases stop clogging the map.

We chose the other path. The policy on the server reads: "No scheduled resets. One persistent world since launch, snapshotted automatically while players are online." Each of the problems that seasons solve still exists on a persistent world, so each one needs its own answer.

The economy row has its own essay, why Sunday Market uses a time-weighted economy. The other rows are the subject of the sections below.

Keeping the world safe

The world is snapshotted automatically while players are online. While the server is empty, the snapshots pause, and they pick up again when the first player logs in.

Permanence has a cost, and we pay it in disk space. Every chunk a player explores stays in the save, and every snapshot has to hold it. In September 2026 the world took 17 GB. Every widening of the border adds to it, and the backups grow with it.

Day to day, protection sits closer to the player. A Ward is a block you place in your build, and the area around it becomes your claim: other players cannot break or build inside it. For land outside a Ward, the server keeps a rollback log of block changes with a timestamp, the player, the block type and the coordinates, so staff can trace griefing after the fact and reverse it. Region protection explains the layers, including the protected spawn zone.

Handling new Minecraft versions

A persistent world has to survive Minecraft updates without starting over. The server runs Minecraft 26.1.2, and a server-side version bridge accepts Java clients from 26.1.2 to 26.3 plus recent older releases. Bedrock players connect through a separate bridge that supports Bedrock 26.30 to 26.51 as of September 2026. The version compatibility page keeps those ranges current.

Bridges buy time. A player who updates their game the day a new release ships can still join, and the world does not have to move the same week. When the server itself moves to a new version, the save moves with it. The terrain you already explored stays as it is, and new chunks pick up whatever the new version adds.

Finding room to grow

Seasons hand out fresh land. A persistent world has to make room another way. On 23 September 2026 we widened the overworld border from 20,000 to 40,000 blocks across, centred on 0,0, so land past the old edge would generate the first time a player reached it. Two days later we set it back to 20,000 blocks across. Generating new terrain far from spawn needed more memory than the server has, and 20,000 blocks is where the terrain generated so far ends. That still leaves 10,000 blocks from spawn to the edge in every direction, in the same reworked terrain with roughly a hundred new and reworked biomes, and most of it no player has visited yet.

The live map shows the overworld from above, so you can look for quiet land before you set out. Plan a long walk: the wiki's first-day guide calls a 200 to 500 block trip from spawn normal and says aiming farther tends to pay off.

The story so far

The history is short, and we publish only what we can date.

The move in July is the one that tested the promise. The server changed machines, and the world went with it, every build in place. By September the save held 17 GB of terrain across 1,602 overworld region files, shaped by 60 datapacks. The world history page keeps the running record.

How permanence changes building

A season teaches you to build fast and cheap, because the map has an end date. A permanent world rewards the opposite. You can spend a month on a harbour, because the harbour will still be there next year. You can build a road to a friend's town and expect to walk it for as long as the world runs. On a world that lasts, an early build can turn into a landmark that later players steer by, and a first shelter can grow into a town over a year of evenings.

Permanence also makes claims and manners matter. On Sunday Market the community recognises a build as yours even without a Ward, and the farther from spawn you settle, the more the area counts as yours. A player who has not logged in for 30 days keeps respect for their build, though others may then build nearby, and locked chests stay locked indefinitely. Building and griefing lists the details. Those rules only make sense on a world that expects people to come back.

What it asks of you

Build as if you mean to stay. Put a Ward on your base, sign the builds you are proud of, and pick a spot a few hundred blocks out where the land is quiet. The world will keep what you put into it, and the history page will keep the dates.