A lot of people share cool game demos with a "look what I built" caption. Well, I didn't build this. I paid Claude to build it.
For educational purposes, I had it reverse engineer The Elder Scrolls IV: Oblivion, decompiling the game with REA and taking detailed notes.
Then, working from those notes, it built a brand-new game engine that runs the game in a web browser.
It didn't copy the original code. It reimplemented everything from scratch in TypeScript and Three.js, and adapted the original assets to work with the new engine.
To play it, you need to own the original game, since the assets are streamed from your copy.
It's kind of wild. I now have something that looks like a complete game running in Three.js.
And yes, I did learn something along the way. I asked Claude to create educational material to teach me about reverse engineering as we went.
Still, I didn't make this game. I appreciate AI, and it's amazing. It lets us reach beyond what we could do on our own.
But if you're truly curious, learn the underlying skills.
That's why, a while back, I bought
@iced_coffee_dev's Three.js course.
AI can probably build every game I can imagine, but I think the real joy is understanding how it's done and having the skill to do it yourself, even if you're not typing as much code by hand.
Think of it like music. Sure, I can use Suno to generate a song. But because I also learned music theory and how to play guitar (albeit poorly), I can hear almost any song and play it by ear.
So even when I create a song with Suno, I can still play it on a real instrument.
Code is the same way. I can use AI, but I want to know that if I'm ever broke and can't pay for Claude, or I don't have internet, I can still create things.
Anyway, rant over. Have a nice day.