I spent 18 years making music. Over 100 released songs across a lot of different genres and projects, built in home studios, on laptops, in sessions that ran too late and produced something worth keeping. Music production is a deeply solitary craft in a lot of ways: you have an idea, you build a structure, you refine it, you share it, and you learn from the response. It trains a particular kind of patience with iterative work and a particular comfort with building something that only exists in your head until you make it real. That background is why building IdleWorlds felt familiar from the first week, even though writing code is nothing like writing a bassline.
The honest version of how IdleWorlds started is that I wanted to play this game and it did not exist. Not exactly. There were idle games, and there were browser MMOs, and there were incremental games with economy layers, but nothing that felt like the specific combination I kept imagining: a persistent server-hosted world with real player economics, idle progression that kept working while you lived your life, and the kind of long-term character arc that makes a game worth returning to for months. I decided to build it myself, and I gave myself two months to get to a real playable state.
I used AI throughout the development process and I want to be straightforward about that. I am not a trained software engineer. I understand systems, I understand design, I understand what I want a player to feel, but I cannot hold the entire codebase in my head the way a professional developer can. AI let me move at a pace that would have been impossible otherwise and implement systems that I could design clearly but would have struggled to build entirely alone. That is not a secret or a compromise. It is a tool, the same way a DAW is a tool for music production. The judgment calls, the design decisions, the things that make the game feel like itself rather than a generic template, those are still mine.
Two months is not a long time to build an MMO. It is an embarrassingly short time if you measure it against industry standards. But I did not build IdleWorlds by industry standards. I built it by moving fast, fixing bugs in hours rather than weeks, listening to every piece of player feedback, and treating the early community like collaborators rather than customers. The players who were in the game in the first few weeks saw things break and get fixed the same day. They saw features arrive that they had asked for the previous night. That responsiveness is only possible at a certain scale and a certain pace, and I wanted to maintain it as long as possible.
The vision was always something like a passive Runescape or a low-intensity EVE Online. Games where the world felt real because other people were in it making real economic decisions, where your character was genuinely yours after months of investment, and where you could put the game down for a week and come back to a world that had continued without you rather than one that punished you for the absence. Those games have communities with real texture, real inside jokes, real shared history. IdleWorlds at two months old does not have that yet, but the architecture is built to support it.
The community that has formed so far is one of the things I am most proud of. It is helpful, cheerful, and honest in the way small early communities sometimes are before a game gets large enough to develop factions and grudges. Players help new arrivals learn the systems. They notice bugs and report them clearly. They have opinions about the economy and share them. Building something that people are willing to spend that kind of genuine attention on is the part of this that felt most like music production: you make something, someone else hears it and tells you what it did to them, and that exchange makes the whole effort feel real.