After everything with News Beacon, I stepped back for a bit. Not in a dramatic way, and not all at once, just enough to actually see what I was doing. I had been putting time into something that made sense on paper. It looked like progress. It fit where everything else seemed to be going. But it didn't feel like mine, and that started to matter more than anything else.
Because I already had something that did feel like mine. Pip-Boy.com wasn't perfect, but it was real. People were using it. People were building on it. It had grown naturally without forcing it or trying to chase anything. And at some point, I realized I had drifted away from that. Not completely, but enough that it didn't feel like the center of what I was doing anymore. And I had left part of it unfinished.
The simulators had always been part of the original idea. Even before the tools, before the site really became what it is now, that was the direction. Not just something that connects to the device, but something that is the interface itself. Something you can open, interact with, and use on its own. That was actually how the site started.
In the beginning, Pip-Boy.com was the interface. It was a Pip-Boy on the screen that could also talk to the real device. The idea was to blend both worlds together. You could navigate it like the game, but it also acted as a companion to the hardware at the same time. It worked, but it didn't scale well.
Trying to make one thing do both jobs ended up making everything heavier than it needed to be. The interface, the simulators, the companion tools, they were all pulling in different directions. It wasn't clear what the site was supposed to be anymore, and that made it harder to improve any one part of it properly. So over time, I separated it.
The simulators became their own thing. The companion tools became their own thing. Different entry points, different landing pages, different purposes. That separation made everything clearer. It gave each piece room to actually be what it was supposed to be. But even after that, the simulators still weren't fully there.
They existed, they worked, but they were still tied too closely to everything else. They felt like a feature instead of something complete. So I went back to them.
Not to rebuild everything, just to finish them properly. And the biggest shift was how I thought about them. The companion app was always about the device. That part made sense. It needed the hardware, the connection, the interaction layer. But the simulators didn't. They were never really about the device. They were about the experience around it.
Once that clicked, everything got simpler. I stopped treating them like part of the site and started treating them like their own thing. Something that should stand on its own without needing anything else to make sense. That changed how I built them, how I structured them, and what I expected them to be.
They became standalone. Fully usable without the hardware. You can run them directly on the site, or you can run them independently without ever touching a Pip-Boy. And more importantly, nothing is locked down. There are no game assets, no hardcoded content, nothing that ties it to something it shouldn't be. Everything is customizable. Text, stats, health, XP, all of it can be changed to fit whatever someone wants to use it for.
If someone wants a Pip-Boy simulator, it works. If someone wants to use it for a tabletop game, it works. If someone wants to build something completely different with the same structure, that works too. That was the goal this time. Not to recreate something exactly, but to build something flexible enough that people can actually use and adapt. And a big part of getting here wasn't just me.
Along the way, people showed up. Developers who took the time to help others in Discord, answer questions, troubleshoot issues, and keep things running when I wasn't around. People who stepped in as moderators, who helped keep the space healthy and welcoming. And others who went even further, building their own apps, games, and tools and sharing them back into the ecosystem.
That changed things. It stopped being just something I was building and started becoming something people were contributing to. Not in a forced way, not because they had to, but because they wanted to be part of it. And that made it stronger than anything I could have built on my own.
Once I got the simulators where they needed to be, the next step felt obvious. I didn't want them locked to my site. So I packaged them as an Angular component and published them. Now it's not just something people can use, it's something they can build with. They can install it, drop it into their own project, customize it, extend it, and make it part of whatever they're working on.
And I kept it consistent with everything else I've done. It's free.
No restrictions, no locked features, no different versions. Just something I built and decided to put out there for anyone who wants it. That part mattered more than anything else, because it aligned with why I started building in the first place.
Looking back, this didn't feel like starting something new. It felt like returning to something that already worked and finishing it the way it should have been finished the first time. Not tied to anything else, not half complete, not waiting on something external to make sense.
Just complete. I didn't build something new. I went back and finished what I started. And this time, it actually feels done. The Pip-Boy 3000 and Pip-Boy 3000a inspired simulators are actually completed!