What stays behind when you leave

You stopped logging in eight months ago. You didn't announce it, because almost nobody does: first you missed a couple of days, then a week, and at some point it became final without there being a decision.

And yet your house is still there. With the badly aligned door you never fixed. There's a trodden dirt path between that house and the mine, marked into the ground, because you walked it hundreds of times. Nobody decided to keep any of it. It simply stayed.

You leave traces without meaning to

The striking thing about the traces left in a place like this is that they're almost never the ones you'd have chosen to leave.

Nobody builds with posterity in mind. You build because a roof was needed, because it looked nice, because there was stone to spare. Paths aren't designed: they appear because the ground wears away where people walk. The odd staircase getting over a slope is there because it was what was to hand.

That's precisely why the trace is reliable. It isn't written up. It's what's left when someone lived in a place without thinking about how it would be told afterwards, and that makes it more honest than any monument.

The two comfortable ways of getting it wrong

The first easy way out is the eraser: wipe everything. A new world every season, a clean reset, everyone starting again from the same line. It's convenient and fixes real technical problems. The price is that the place stops having an age: nothing indicates that anyone lived there before you, and in a place with no visible past it's hard to believe that staying means anything.

The second is the museum: freeze everything. The old area is cordoned off as heritage. It sounds respectful and often is, but the good space is already taken by people who don't log in, and whoever arrives today can only build on the outskirts.

Both are the same mistake with opposite signs: treating the past as a block —all out or all intact— instead of as layers.

A place should show its time

In 1972 the urban planner Kevin Lynch wrote a whole book on this question applied to cities: what an environment should do with the traces of the time it carries.

His answer was the middle one, uncomfortable for both sides. Lynch argued that a place needs to show the passage of time for people to be able to live in it: the old next to the new, traces of several eras living side by side. He criticised with equal severity those who raze the past —ageless cities— and those who mummify it.

The idea underpinning it travels well: evidence of time is information. A place where you can see that someone was there before tells you something useful about what you've got yourself into. A place without marks isn't neutral; it has decided to tell you nothing.

What the trace does for whoever is still there

There's a consequence of this that's rarely mentioned, and it's the one that interests me most.

The marks of those who left don't work for them: they work for those who remain. Whoever arrived last month and finds a path already made is using the wear of someone they never knew. Whoever asks what that tower is receives a story, and with it the idea that the place has depth. A server full of traces of people who no longer log in communicates something no welcome message manages: here, people stay long enough to leave signs.

Put the other way round: when a place erases those who left, the punishment isn't borne by the one who left —they're not there any more— but by whoever arrives afterwards, who inherits a place with no evidence that it was worth staying.

The principle: what a place keeps says who it is

Step out of the server, because this applies to almost any inhabited place.

An office that reassigns your desk the same day you leave. A family home where the height marks are still on the door frame. A neighbourhood that knocks down its old local bar and another that keeps the sign. The same thing happens in all of them: what a place decides to keep of someone who is no longer there is the most sincere statement it makes about what it values, precisely because the one who left can no longer claim it or thank anyone for it.

It's a clean test because there's nothing to gain. Keeping the trace of someone who isn't coming back produces no measurable benefit. That's why it says so much.

What doing it well would look like

If there were a place where the builds of someone who stopped logging in weren't erased by default, where you could find out who made what and when, and where a new world didn't mean the previous one vanished without a record, I'd like it to be called KobiiCraft.

And now the obligatory part: keeping everything isn't possible. Disk space costs money. A world that's too big performs worse and ruins everyone's experience. A new version sometimes breaks the previous one beyond repair. Anyone promising that nothing will ever be lost is promising something they don't control.

What's sustainable is more modest: acknowledging that choosing what to keep is an editorial decision and not a neutral technical calculation. Warning beforehand and not afterwards. And, when something can't survive, leaving at least a sign that it existed. The difference between losing a house and the house never having been there is exactly that sign.

The badly aligned door

Your house is still there, with its crooked door. Nobody has fixed it or knocked it down, and someone who doesn't know you has probably walked past thinking that somebody used to live there.

That's all that's left, and it's more than it seems: proof that the place where you were was a place and not a service.

Frequently asked questions

What traces does a player leave when they stop logging in? More than they meant to leave. The builds remain, and they usually survive intact because nobody bothers to knock them down. The paths remain: the trodden ground between two points that someone walked hundreds of times becomes a route others use afterwards. Signs remain, names on chests, a staircase placed oddly to get over a slope. Almost none of it was made with leaving a mark in mind, and that's exactly what makes it reliable.

Why does a world reset hurt so much? Because it doesn't erase objects, it erases evidence. A reset removes at once the builds and the record that someone was there, and in doing so turns years of shared life into something that now exists only in the memory of those who lived it. It's usually announced as a technical decision —performance, world size, a new version— and that presentation hides the fact that it is, in reality, a decision about which part of people's past deserves to survive.

What did Kevin Lynch say about time in places? Lynch, an urban planner, argued in 1972 that an environment must show the passage of time to be habitable and to orient whoever moves through it. He criticised both easy ways out equally: razing the past, which produces ageless, disorienting places, and freezing it as a monument, which produces places with no room left for new life. His proposal was in between: that time should be visible and layered, with traces of several eras living side by side without any one of them taking over.

Can everything players build be kept? No, and saying otherwise would be lying. Disk space costs money, a huge world performs worse and a new version sometimes forces you to start from scratch. The limits are real. What can be done is to acknowledge that choosing what to keep is an editorial decision and not a neutral calculation, to warn beforehand rather than afterwards, and to offer some way for a trace to be kept even if the original doesn't survive.