If you’ve been building your game with Rosie, our AI game maker, you might eventually run into the message saying that your project is too large.
If that sounds familiar, don’t worry—you’re not alone.
One of our awesome community members, Kastchey, recently found a solution for this situation.
Here’s a step-by-step breakdown of how to move your project over to the multi-file template so you can keep building without hitting the character limit wall.
Why This Happens
Rosie needs to keep track of your game’s code to help you write and debug.
But if your project grows too big, she starts to lose context (especially when everything’s crammed into one file)—and that’s when errors and “we’re working on it” messages start popping up.
The solution? Break your project into multiple files so Rosie can handle each part separately. That’s what the multi-file template is for.
Step 1: Back It Up
Before touching anything, back up your code.
Remix your project and keep that version untouched, or save the full code locally on your device. If anything goes wrong during migration, you’ll want that safety net.
Step 2: Slim Down Your Project Temporarily
If you’re already over the character limit, try this trick to free up some space:
• Manually delete all the comments in your code (those green lines starting with //).
It’s a quick way to reduce the total character count and buy yourself some room to prompt Rosie.
Step 3: Start Breaking Things (In a Good Way)
Ask Rosie to help you identify parts of your main class that can be turned into separate classes or modules.
For example:
• Reusable functions
• Logic blocks that can stand on their own
• Duplicated code that can be abstracted
Once she helps generate a new class, copy that code, save it to a local text file, and repeat. Slowly but surely, you’ll end up with several self-contained modules.
Step 4: Move to the Multi-File Template
Once you’ve got a few modules ready:
- Remix the multi-file project template (it’s available in the template library).
- Ask Rosie to create empty files for each class or module you saved earlier.
- Copy each module into its own file inside the new project.
- Don’t forget to move your main class too!
You might get some errors when running it for the first time—references might be missing or paths might need updating.
But you can work through these with Rosie, prompt by prompt.
If your current game is still relatively small, it might actually be easier to start fresh using the multi-file template and rebuild it piece by piece.
But if your game is already developed and you’re hitting limits, the step-by-step migration process is totally doable (and way better than losing your progress).
Quick Recap:
• Backup your project before making changes.
• Clean up comments to reduce file size.
• Use Rosie to identify reusable modules and extract them.
• Switch to the multi-file template and rebuild your project piece by piece.
By adjusting your workflow and using the multi-file template, you’ll avoid the project size limit and make it easier for Rosie to help you out—no more “Oops” messages!
Need help with the migration?
Pop into our Discord and ask the community. Chances are, someone like Kastchey has already figured it out.