Guides
Prompting best practices
Describe what players should be able to do, agree on the rules, and make changes you can review and test.
Define the behavior
Section titled “Define the behavior”Start with the project type and Minecraft version: Paper for plugins, Fabric for mods, or Vanilla for datapacks. Then describe:
| Detail | Example |
|---|---|
| Trigger and result | A player runs /daily to receive a reward. |
| Permissions | Ordinary players can claim; only administrators can reload settings. |
| Rules | Each player can claim once every 24 hours. |
| Configuration | Reward item, quantity, cooldown, and messages. |
| Saved data | Claim times must survive a server restart. |
| Edge cases | A full inventory must not consume the claim. |
Use exact command names, Minecraft item identifiers, and messages when they matter. You can describe the behavior without designing each source class.
Plan a Paper plugin for Minecraft <version> called DailyGift./daily gives a player three cooked beef once every 24 hours.Use dailygift.claim, enabled for ordinary players.Save each player's claim time across restarts.If inventory is full, show a message and let them try again without a cooldown.Make the reward and cooldown configurable.Ask about any unclear rules before implementing.Resolve questions before building
Section titled “Resolve questions before building”Use Plan to discuss uncertain behavior. Check the assumptions before asking for implementation: What happens when the inventory is full? Who can use the command? What survives a restart? Does the feature need another plugin?
Ask for a revised plan when a rule is wrong or missing. See chat controls for switching modes and implementing a plan.
Make focused changes
Section titled “Make focused changes”Break a large feature into milestones, such as command behavior, saved data, configuration, and integrations. Review and test each milestone before continuing.
Keep edits together when they must agree. A new command may need its handler, registration, permissions, help, and messages updated together.
For a follow-up, state the problem and what must stay working:
The reward works, but a full inventory still consumes the cooldown.Fix that failure path so players can retry after freeing space.Keep successful claims, command names, and stored timestamps unchanged.Give relevant context
Section titled “Give relevant context”Reference the current project files that matter to the request. Save manual edits first. Use file mentions to point to the implementation you want inspected.
For an image, explain whether it shows a desired result or a bug. Identify the relevant area and describe the expected interaction. For example: “Use three category buttons in the top row and close the menu after a successful selection.” See reference images for uploading and managing attachments.
Report bugs with evidence
Section titled “Report bugs with evidence”Include the Minecraft version, build number, player role, reproduction steps, expected result, observed result, and a relevant log excerpt.
In build #8, an ordinary player with dailygift.claim cannot use /daily.The same command works when the player is an operator.Expected: a permitted player receives the reward without operator access.Observed: the player sees "No permission".Inspect the permission check and keep the existing cooldown behavior.A compilation failure and an in-game problem need different evidence. Share the build error for the first, or reproduction steps and deployment logs for the second.
Review and test the result
Section titled “Review and test the result”Inspect the changed files before keeping the result. Build the updated source, deploy the new artifact, and test the behavior as an ordinary player as well as an administrator. Check failure cases and saved data after a restart when relevant.
If a test fails, describe the specific failure in your next request. Read reviewing changes for the review controls.