Pro Tips

These are the habits experienced users lean on. None of them are required, but they make a real difference once you're past your first mod.

Start a new chat when you start a new feature or fix

The longer a chat gets, the slower and less capable the AI becomes (this is a fundamental limitation of today's AI models). Start a new chat whenever you start working on a new feature or bug. New chats won't be able to see your previous chat history, but they will have access to your mod's description and codebase, so they already know what you're working on.

Switch to a more powerful model for the hardest bugs and planning sessions

You can switch to a different AI model when you start a new chat, or even mid-conversation. If Modmixer is struggling to fix an issue, try starting a new chat with Opus or GPT-5.5. These models are much more expensive, so it's best to save them for problems other models can't handle.

Most people use Kimi K2.6 most of the time, and switch to Opus for challenging bugs.

Start with a clear plan

The plan Modmixer shows you before it builds is the most important moment in the whole process. A few extra minutes describing exactly what you want saves far more time than fixing a half-right mod afterwards. Be specific about the behavior you imagine, the edge cases you care about, and anything that should stay out of scope.

Keep an eye on performance

Mods can quietly slow the game down, especially ones that run logic every tick. If the game feels sluggish after a change, say so. You can also ask Modmixer to review your mod for performance.

Don't break people's saves

Once players are using your mod, changes that rename or remove the things your mod defines (the data files behind its content) can corrupt their existing saves. When you update a published mod, ask Modmixer whether a change is save-safe, and note anything risky in your change notes. See Publishing Your Mod for more.

Useful prompts

A few prompts worth keeping in your back pocket:

• "Give me three small mod ideas that suit a beginner."
• "Review this mod for performance problems."
• "Explain what this mod does in plain English."
• "What could break this, and how do we test for it?"