Loading content...
Feb 11, 2026
Calculating...
Back to Knowledge Base
Blog
The Evolution of BloxdForge: Understanding the Versions
A comprehensive history of BloxdForge from the original PyInstaller app to the modern Next.js platform.
A comprehensive history of BloxdForge from the original PyInstaller app to the modern Next.js platform.
If you've stumbled upon videos or posts about BloxdForge (or at least look like it, we're sort of stuck with this colour scheme now) that look nothing like its current state or have a different name (I'll talk about that in a bit), you're not going crazy. And no, it's not an April Fool's joke, although it would be very funny if you're reading this on April 1st, you're seeing before your eyes the evolution of BloxdForge, the culmination of years of experimentation, building, and growth.
This is the story of how we got here.
BloxdForge started, surprisingly, as a desktop application – a Python program packaged with PyInstaller (or was it Electron? Even I don't remember…) that you had to download and install on your computer. It was janky, only worked on Windows, and extremely ambitious for what it was: a local, static tool that attempted to work with an online game. If you can't see where I'm going, it doesn't work that way. The app was never meant to be. However, no matter how rough it was around the edges, it was enough to prove the concept, and it showed us that people wanted tools like this.
That version hasn't been updated since December 2024. Nearly two years later (or whenever you're reading this), most of its features don't work anymore: the GitHub repos it relied on are long gone, there are countless bugs, and at some point you really can't just call every bug a feature, and the design (or the lack of it) was just… bad. The installer is still on GitHub if you're curious (here), but it's more of a time capsule now than anything else.
The desktop app couldn't keep up. Still, it was the foundation. It taught us what people needed and what was possible. And it was built together, by two people who believed it could be something more.
Let's be real, the desktop app was never going to reach everyone. You had to download it from GitHub (which, to normal people, just looks like a sketchy website), ignore your antivirus software, albeit rightfully, flagging the file due to it being generated by PyInstaller, and install it, and this was only for those who used Windows. So we moved to the web – version 2 was born on GitHub Pages, powered by jQuery and a lot of hope and optimism. It most certainly wasn't fancy, I'd even go as far as to say the desktop app had a better UI, but it worked. Anyone with a browser could use it.
We built out the essentials: a game launcher that ran in the browser with some QoL features – some of which lived on to the current version, texture pack downloading, an editor where you could edit textures, manage your files, and create skyboxes. We even wired up an AI chat that could answer questions about Bloxd.io, pulling from a knowledge base we'd assembled. And because we needed some way to support the project, we added optional features that could be unlocked by watching ads. Free for everyone, with a little something extra if you wanted it. (And no, if you're wondering, I'm not adding back any ads or other forms of distractions; I hate ads, period.)
Version 2 was scrappy, but it was a real platform. And we built it together, the way we'd built everything up to that point.
After v2 stabilised, version 3 emerged - still on the same tech stack, still GitHub Pages and jQuery, but with a refreshed interface and some nice quality-of-life improvements. The biggest addition was texture pack previews, something people had been asking for (and also to flex my aWeSoMe coding skills :) – no, you don't get to judge). You could finally see what a pack looked like before downloading it.
But v3 was different in another way. It was primarily developed by my co-creator, not as a joint effort like before. We were both busy with studies and work, pulled in different directions, and trying to survive the cruelty that is society. It wasn't a split, not in any dramatic sense, but it was the start of us realising we might have different ideas about where this project should go.
After v3, I knew I wanted to rebuild everything from scratch. Not because what we'd built was bad - thousands of people have used it just fine - but because I could see what it could become with modern tools. I wanted Next.js for the performance, Vercel for the infrastructure, TypeScript for the safety, and Tailwind for the design flexibility. I wanted server-side rendering, edge functions, and Progressive Web App capabilities. I wanted to build something that felt like a proper application, and most importantly something that I wanted to use.
And I wanted to call it v1.x.x. Not v4. Call me cringe, but to me, this was a new beginning, a fresh start with a clean slate and a clearer vision. It was my project now, the way I wanted to build it, and no matter how insignificant it may seem, I needed the version number to reflect that.
So I rewrote everything. New UI from the ground up. Schematic previews that you could explore. A proper script editor with syntax highlighting. Downloadable community scripts. Comprehensive guides (like this one). A texture studio that was actually pleasant to use. And underneath it all, a tech stack that could grow with the platform instead of holding it back.
This is the version you're using now. It's not perfect, and it never will be - there's always something to improve, always a better way to do things - but it's mine, and it's the best version of BloxdForge that's ever existed.
When I started building the current version, my co-creator continued developing v3 as a separate project. Eventually, they cloned the v3 repository and gave it a new identity, which is why some older promotional content might look confusing or refer to features that don't exist here.
This wasn't a falling out. We just wanted to build different things, and that's okay. Sometimes creative partnerships evolve, and people need space to explore their own ideas. The split didn't affect our personal relationship - we're still connected, still supportive of each other - but our projects took different paths.
If you're here at bloxdforge.com, you're on the current platform. This is the one I'm actively developing and maintaining. The rebranded v3 is its own thing now, with its own vision, and I wish them nothing but the best moving forward.
I'm constantly updating BloxdForge. New features, bug fixes, performance improvements, UI refinements - it's an ongoing process. The modern tech stack makes it easier to iterate quickly, to experiment with new ideas, to respond to what the community needs.
Some of what's coming: better mobile support, more advanced scripting tools, deeper workshop integration, improved AI assistance, and a lot of polish. There's a long list, and it grows every time someone suggests something I hadn't thought of. (and you can help by filling out this form)
If you're using BloxdForge, thank you. Seriously. This project started as a tool I wanted for myself, and it's grown into something much bigger because people like you found it useful. Every piece of feedback, every bug report, every feature request - it all helps shape what this becomes.
This is just the beginning.