The First Build Isn't Right. Here's What to Say Next
Fixing a mod is a conversation. Stay in the same project, report what happened like a tester, change one thing per message, and give the numbers.
A first build that's close but not right is normal. The part people get wrong is what they type next. "Fix it" and "make it better" give the AI nothing. A clear bug report gives it everything.
#Stay in the same project
Every project in Creator Hub is a thread. When you send a follow-up message, the AI already has your prompt, the code it wrote, and the notes from the last build. It changes what you asked for and leaves the rest alone.
Starting a new project throws all of that away. You'll pay for a full build and get a different mod, with different bugs.
Start over only when the foundation is wrong: the wrong platform, the wrong Minecraft version, or the wrong environment. Those can't be patched with a follow-up. Everything else can.
#Report it like a tester
Three lines cover almost every follow-up:
- What you did. "Ran /home after setting it with /sethome."
- What happened. "Nothing happened and no message appeared."
- What should have happened. "It should teleport me after a 3-second warmup and say 'Teleporting...' in the action bar."
If there was an error, paste it word for word from chat, the console, or the crash report. The exact text is worth more than a description of it.
#One change per message
If three things are wrong, send three messages, or one message with a numbered list. Don't fold a fix and a new feature into the same request. "Fix the cooldown, and also add a /warp system" is two jobs, and the second one is the one that gets half done.
#Give the numbers
"The cooldown is too long" can be fixed ten ways. "The cooldown is 5 minutes, make it 30 seconds" gets fixed once.
Balance
Bad Prompt
“The sword is way too strong, tone it down”
Good Prompt
“Frostbite does 12 damage, change it to 8. Keep the slowness effect the same”
Why it works: The current value, the new value, and what to leave alone.
Something missing
Bad Prompt
“The recipe doesn't work”
Good Prompt
“The lapis pickaxe has no crafting recipe. Add one: 3 lapis blocks across the top row, 2 sticks down the middle, like a normal pickaxe”
Why it works: What's missing and exactly what to add. The AI doesn't have to guess the shape.
Wrong behavior
Bad Prompt
“Zombies are still normal”
Good Prompt
“Zombies still have 20 health at night. They should have 30. I tested by hitting one with a diamond sword, it died in 3 hits instead of 5”
Why it works: How you tested tells the AI which code path to look at.
Visuals
Bad Prompt
“It looks wrong”
Good Prompt
“The Frostbite texture is a plain grey sword. It should be light blue with a white edge, like the diamond sword but blue”
Why it works: Describe the look by comparing to something in the game.
#When it isn't a prompt problem
If the mod never shows up at all (not in the Mods list, no line in the startup log), the build is probably fine and the install isn't. Loader mismatch, wrong version, wrong folder, missing Fabric API. Go through the troubleshooting checklist before you send a follow-up.
If the build failed with an error before you could download anything, the request was usually too big or two parts of it contradicted each other. Cut it down to one feature and generate again.
#Keep a changelog in your head
After each follow-up, test the specific thing you asked for, then re-test the thing that worked before. A fix that breaks something else is a normal bug, and the next message is "the cooldown is fixed, but /sethome now says 'unknown command'".
Follow-up message checklist
Build it yourself
Turn an idea into a working Minecraft mod
Describe it in plain English. Download the build. Drop it in your mods folder. No coding.
Start building