Roblox isn't just a game, it's a platform built on user-generated content.
When someone asks When Was Roblox Created, the short answer is 2006, but the actual timeline is messier than a Wikipedia box makes it look. David Baszucki and Erik Cassel started work on the project under the working name "DynaPlay" back in 2003 while they were still running their educational software company, Knowledge Adventure. They spent roughly three years prototyping what would eventually become the platform, then rebranded it to Roblox and launched the beta in 2006. The beta launch happened in September 2006. The official public release came in December of that year. That's the two-date answer most people are looking for. But if you're actually trying to understand the platform, those dates barely scratch the surface of what matters. Here's the thing nobody tells you: Roblox's original programming language wasn't Lua. The early prototypes used a custom language called GPE (General Programming Environment), which was later replaced by Lua 5.1. The switch happened around 2008-2009, and it completely changed the development ecosystem. If you've ever tried to port old pre-2009 Roblox code, you'll find nearly nothing works without significant rewriting. The API surface was entirely different, and the engine architecture shifted alongside it.
I ran into this head-on a couple years ago when I was digging through archived game files from an old group I was part of. The source code was written against the GPE-to-Lua transition period, which means it was using a hybrid syntax that no longer compiles in modern Roblox Studio. The workaround was basically writing a converter script that mapped the old event names to their modern equivalents. It took about three days for a small project. A larger one would have been a slog. The other counter-intuitive fact is that Roblox was never designed as a traditional game first. It was designed as a creation tool that happened to ship with a few demo experiences. That design decision shaped everything about the platform's economics and technical constraints. The Developer Exchange program, which lets creators cash out Robux, wasn't introduced until 2013. Before that, Robux was effectively a dead-end currency with no real-world value. If you were creating serious content between 2006 and 2013, you were essentially volunteering your labor for the platform. There are also hard limits most people don't understand. The maximum player count per server was originally 20, then bumped to 50, and now certain experience types can support up to 10,000 players through meshing. But meshing introduces its own problems — latency spikes, desync issues, and a lot of headaches for anyone building large-scale experiences. I've seen experienced developers abandon meshing entirely and stick to smaller, instanced servers because the debugging overhead wasn't worth the player count upside.
The monetization side has its own traps. The platform takes a 30% cut on Robux purchases from players, but developers only receive about 24-26% of the face value when they cash out through DevEx. The rest gets eaten by payment processing fees, currency conversion, and the platform's take. It's not catastrophic, but it's nowhere near the 70/30 split that gets thrown around in casual discussions. If you're building a business case around Roblox development, use the real numbers. One more limitation worth mentioning: Roblox Studio runs exclusively on Windows. There is no native Mac or Linux version. I've had people try to set up headless build servers on Linux for CI/CD pipelines, and while it's technically possible through Wine or containerization, it's fragile and slow. The official path is Windows-only, period. If your team is all-Mac, plan accordingly. Visit Roblox
Get the Full Details
