Skip to content
Getting started

How to write a good request

What to include in a Codexe request, with good and bad examples for plugins, mods, datapacks, bots and websites.

Updated

On this page
  1. What to include
  2. Bad vs better
  3. Big projects: build in steps
  4. Enhance
  5. Say what you don't want

The request is the biggest single factor in the quality of the result. The AI can only build what it can infer, so specific requests beat long ones.

#What to include

  • Platform and version. "Paper 1.21.4", "Fabric for 1.20.1", "datapack for 1.21.1", "discord.py".
  • Behaviour. What happens, step by step, including what happens when something goes wrong.
  • Commands and arguments. /home <name>, who can run them, and the messages shown.
  • Permissions. Node names and defaults.
  • Configuration. What server owners should be able to change.
  • Storage. In memory, a YAML file, SQLite or MySQL, and whether it survives restarts.
  • Integrations. Vault, PlaceholderAPI, LuckPerms, WorldGuard. Name them explicitly.
  • UI. Chat messages, GUIs (inventory menus), scoreboards, boss bars.
  • Edge cases. Offline players, full inventories, disabled worlds, reloads.

#Bad vs better

Bad: make a factions plugin

Better:

Text
A Paper 1.21.x factions plugin.
- /f create <name>, /f invite <player>, /f join <name>, /f leave, /f disband (owner only).
- Max 10 members per faction (configurable).
- Chunk claiming with /f claim and /f unclaim; claimed chunks block building by non-members.
- Faction power: +1 per online member, claims limited to power x 2.
- Data saved to SQLite, loaded on startup.
- Vault economy: creating a faction costs 1000 (configurable).
- Permissions: factions.use (default true), factions.admin (op) for /f admin bypass.

Bad: a mod with new swords

Better:

Text
A Fabric mod for Minecraft 1.20.1.
- Adds three swords: Ember Blade (sets targets on fire for 3s), Frost Edge (Slowness II for 2s), Void Cutter (5% chance to teleport the target 8 blocks).
- Crafting recipes using blaze rods, packed ice and ender pearls with a netherite sword.
- English lang file and item models (textures can be placeholders).
- No client-only code on the server side.

Bad: custom recipes

Better:

Text
A datapack for Minecraft 1.21.1.
- Shaped recipe: 8 rotten flesh around a leather = 1 leather.
- Shapeless recipe: 9 nether wart = 1 nether wart block, and the reverse.
- A function that runs every tick and gives Speed I to players standing on gold blocks.

Bad: moderation bot

Better:

Text
A discord.py bot with slash commands.
- /warn <user> <reason>: stores warnings in SQLite, DMs the user.
- /warnings <user>: lists warnings with dates.
- /timeout <user> <minutes> <reason>: applies a Discord timeout; only for members with Moderate Members.
- Logs every action to a channel set with /setlog.
- Token read from an environment variable.

#Big projects: build in steps

Don't paste a fifty-feature specification into one request. Start with the core (data model, main commands), let Codexe verify it, then add features in follow-up messages. Each step is smaller, cheaper, verified, and easier to correct.

#Enhance

On Create (Creating a project), the Enhance button rewrites a rough request into a more complete one. It costs a flat 5,000 tokens. Always read the enhanced text before generating: it may assume details you don't want.

#Say what you don't want

"No database, keep everything in config.yml", "don't use NMS", "no external dependencies". Constraints stop the AI from choosing something you can't use.

How to write a good request | Codexe Docs