Issue 47 · Fireside

The Long Story

Deluvia began in notebooks when I was twelve.

That sentence can make the world sound more continuous than it has been. A thirty-nine-year project does not receive thirty-nine years of steady labor. It survives school, jobs, moves, changing media, family life, long dormant stretches, and periods when the maker is more interested in the container than the contents. Some years add a system. Some add a drawing. Some add only the knowledge that the world is still there.

Duration is not proof of quality. An old idea can remain old because nobody has tested it. Longevity can be love, habit, avoidance, private language, or all four in changing proportions.

What thirty-nine years proves is narrower: I have not exhausted the question.

The World Before Its Vessel

The early notebooks did not have a settled destination. Deluvia was a place to imagine in before it was a product, publication, game, or public identity. That freedom allowed the world to accumulate without having to explain who would buy it or how another person would enter.

It also postponed those questions.

A private world can grow by addition almost indefinitely. Another place, species, history, conflict, map, or system makes it feel richer. Public work requires subtraction. A reader or player needs an entrance, and the entrance cannot be all thirty-nine years wide.

For a long time, the problem looked like completion. Finish the world. Make the definitive map. Settle the canon. Build enough that another person can see what already exists in the maker’s mind.

That scale has no natural stopping point.

The Server

Stormroot became the Minecraft chamber of Deluvia. Over thirteen years, the server acquired builds, custom Denizen scripting, game mechanics, and a magic system based on attunement rather than collecting external power. A working MVP exists. The server can be entered.

That is a substantial change from a notebook. A drawing can imply a city. A Minecraft city must occupy coordinates. A written magic system can remain suggestive. A playable one needs rules for mana, timing, feedback, failure, and what happens when a person presses the wrong key.

The vessel forced decisions.

It also created obligations that were not identical to worldbuilding. Servers need maintenance. Players need orientation. Interfaces need to reveal enough without flattening discovery. A family-run world competes for attention with commercial games built by teams. Visitors often leave within ten or fifteen minutes, long before the accumulated depth can become visible.

That does not mean the world failed. It means the entrance and the world are different pieces of work.

For years, I treated the server as if finishing Deluvia meant solving both at once: complete the world and build the public mechanism that would keep other people inside it. The mechanism became a second endless project attached to the first.

A Change of Container

The current framing separates Deluvia from Stormroot more clearly. Deluvia is the deep world. Stormroot is one narrative and potentially public chamber within it. A possible illustrated tabletop sourcebook has been considered as another vessel, but it is not a commitment or release plan.

This distinction matters because changing containers can look like abandonment from the outside. The server is not becoming a large audience, so perhaps the work should become a book. The book is illustration-heavy, so perhaps it should become small zines. The zines take years, so perhaps the world should remain private.

Each move can be another way to avoid choosing. It can also be a useful test: which part of the work is the relationship, and which part is the current equipment?

Minecraft supplied scale, inhabitable geography, and systems behavior. A book could supply sequence, editing, illustration, and a finished object that does not require a live service. A tabletop game could let other people act inside the world without requiring me to script every action in advance. None is a neutral container. Each produces a different Deluvia by forcing different decisions.

The long story survives not by remaining unchanged but by retaining enough identity to recognize itself after those decisions.

What Finishing Can Mean

There is no useful task called finish Deluvia.

There can be a finished map. A finished bestiary entry. A playable mechanic. A town another person can navigate. A short campaign. A printed volume. A scene told well enough that it no longer asks for revision. These are real endings at a smaller scale.

This is not permission to call every fragment complete. A sketch abandoned midway is still a sketch. A server that cannot hold a new player has a design problem. A proposed sourcebook is not a book.

The smaller unit makes the problem testable. Does this chamber work? Can this artifact travel? Does this map reveal the place or merely record that many places exist? Can a stranger enter without thirty-nine years of explanation?

Long projects need such units because duration can hide the absence of finished form. There is always more context to add. The maker can remain busy without ever accepting the judgment produced by an ending.

The opposite error is to demand that the whole relationship justify itself through one definitive product. If the book fails, were the notebooks wasted? If the server remains lightly visited, did the scripted mechanics count? If no commercial audience arrives, was the world only rehearsal?

Those questions assign the last vessel authority over every earlier year.

The Maker Also Changes

At twelve, a private world needed no public byline. Later, the name SirBandersnatch or Bander could carry the game identity. That name now belongs inside Stormroot as a character. New public work uses Don Krumpos.

This sounds like metadata. It changes the relationship between maker and world. A handle can act as a costume, useful for entering a community and keeping ordinary identity elsewhere. A byline accepts that the person who has continued the work is part of its public history.

The aesthetic has changed too. A harder fantasy register has made room for warmer, stranger, more playful influences. That is not a correction made by a single art-direction meeting. It is what happens when the person who began the world at twelve reaches fifty-one and no longer needs the work to prove the same things.

A thirty-nine-year story contains several makers who share a name and do not share all their tastes.

The archive can preserve their disagreements without requiring the newest one to obey the oldest.

The Next Question

Deluvia is now described as a slow practice with no deadline and no commercial pressure. That framing removes a false emergency. It also removes the excuse that someday a market will decide what the work should become.

The next problem is not how to finish the world. It is which finite chamber is worth completing under my own name.

That could be a map, a mechanic, an illustrated booklet, or something not yet named. The answer does not need to contain thirty-nine years. It needs to be shaped well enough that another person can enter, encounter a piece of the world, and leave knowing what happened there.

The world can remain open behind it.

Workshop Sources