How to brief a Minecraft developer (checklist)
A checklist of what to send a Minecraft developer before ordering a plugin, model or resource pack, so you get an accurate quote and the result you imagined.
Most delays and surprise costs in Minecraft commissions come from a vague first message. Ten minutes on a good brief saves days of back and forth. Here's what to include.
The checklist
- Server software and version: Paper, Spigot, Purpur, Fabric, Bedrock… and the exact Minecraft version.
- What it should do, from the player's point of view: what they see, click and get.
- References: screenshots, videos or other servers that do something similar.
- Other plugins it must work with: economy, ranks, holograms, ModelEngine, ItemsAdder and so on.
- What your staff should be able to change in the config.
- Visual identity: logo, colors, theme, existing resource pack.
- Budget and deadline, even if they're rough.
Why the budget helps you
Sharing a budget isn't giving away leverage. It lets the developer suggest the best version of your idea that fits it, or tell you early which part to leave for later, instead of quoting something you can't pay for.
Before you pay
- Get a fixed price and a deadline in writing.
- Ask what's included: revisions, bug fixes, source code.
- Check real reviews and past projects.
- Pay through a method with buyer protection when you can.
On this site the request form asks for the essentials, and the quote comes back as a fixed price on Discord before anything starts.
Have an idea for your server? Send it with your budget and get a fixed price on Discord.