Testing How AI Remasters Games by Remastering Eets (2006) A writer using Claude Opus through Claude Code remastered the 2006 Klei puzzle game Eets in about 25 minutes and roughly 150,000 tokens, producing a C file that raised the game from its 30FPS cap to interpolated 60FPS, added a native-resolution option and a toggle for stretched widescreen, and upscaled 2D assets and animations with Real-ESRGAN's cartoon model. The author reported that Claude downloaded the upscaling model and tested the game by opening and closing it without further input, and that results were imperfect, with some images degraded. The experiment was framed as a test of how hard it is to get an AI agent to fix a commercial game, what the process requires from the user, and how the agent makes the changes work. Testing How AI Remasters Games By Remastering Eets 2006 Introduction Last month, I wrote an article https://popcar.bearblog.dev/ai-is-mass-decompiling-games-thats-both-awesome-and-scary/ talking about how AI is mass decompiling/recompiling/modding all sorts of games. Since then, I decided the best way to truly understand what's going on... is to try it myself I'll be talking about my experience using Claude Opus to remaster a childhood favorite of mine, Eets https://store.steampowered.com/app/6100/Eets/ . If you just want the end result, skip to the conclusion Conclusion . Eets is a neat puzzle game where you try to lead this weird creature to the finish by adding obstacles and food that changes its behavior. It's also the very first game made by Klei, who went on to make some bangers like Don't Starve, Mark of the Ninja, and Oxygen Not Included. Anyway, the game recently got re-listed and made to work on modern PCs, which is great However, it still leaves a lot to be desired... the game runs at 30FPS, has a maximum resolution of 1024x768, and for some odd reason is stretched to fit the screen with no setting to change it back to its original 4:3 aspect ratio. Let's fix all that. My goal for this experiment is figuring out three things: - How hard is it to make Claude fix the game? - What's the process like? How many times do I have to intervene or manually fix something? - How does Claude make it work? First Impressions I got a free week of Claude Pro from a friend thanks again to test as much as I'd like. I'm going to try and put as little effort as I can and see what Claude dcan figure out on its own. From what I can tell, most people are doing the same thing. I opened the game files and put in my first prompt in Claude Code: This is a game called Eets. It's hardcoded to work at a low resolution and is capped at 30FPS. Make the game work at 60FPS and at a native resolution. Claude kept automatically churning out code and "testing" by opening and closing the game. It's honestly stressful to me that I'm just leaving an AI agent to play around on my system and take screenshots. The only saving grace is that it asks for my input before running dangerous commands such as removing a file. Still, the whole process leaves a massive question mark on how private/secure this actually is. I already had a weird moment where it accidentally screenshot my whole desktop while researching AI for something else.