Writing a good prompt

What to say, what to leave out, and how to ask for changes.

Cyrus builds what you describe. The more concrete the description, the closer the result.

Say what it does, not how to code it

Good: "A /heal command that fully heals the player. 60 second cooldown per player. Operators can heal others with /heal <name>."
Weak: "Healing plugin."

Include these when they matter

Commands and who may use them (everyone, operators).
Numbers: cooldowns, chances, prices, amounts. Say which should be editable in config.yml.
What is saved between restarts (balances, homes, streaks).
What players see: titles, action bar messages, menus, boss bars.
Limits: "only in the overworld", "not in protected zones".

Keep it to one idea per mod

One clear mod builds better than ten loosely related ones. For a large project, build the core first and add to it. If the mod grows large, see Mod Packs and modules.

Check before you send

Cyrus checks your prompt first. If it is too vague or asks for something it cannot build, it says why and what to change, before any tokens are held.

Asking for changes

Be specific about the change and leave the rest alone: "Make the cooldown 30 seconds and show it in the action bar." Do not re-describe the whole mod.

What Cyrus cannot build

Cyrus targets Paper servers on the Minecraft versions it lists. It cannot make client-side mods, and it cannot change the game itself. See games and versions.

Need ideas? Browse the templates.