Good prompts

Assistants work best with clear goals and small steps. These prompts work well with the GAMPEON tools.

Start

• “Read the GAMPEON docs on resources and events, then explain how a GAMPEON game is structured, in five sentences.”
• “I want to build [your idea]. Ask me the questions you need before you start.”
• “Show me the plan first: which resources, which files, which events. Don’t write code yet.”

Build

• “Create a resource called checkpoints from the gamemode template.”
• “Add an event that resets the race. Only the server decides the result.”
• “Check the resource with GAMPEON and fix everything it reports.”

Understand

• “Explain this file line by line in simple words.”
• “Which parts run on the server and which on the client, and why?”
• “What could a cheater do with this event, and how do we stop it?”

Port from FiveM

• “Here is a FiveM resource. Check it with GAMPEON and list what has to change.”
• “Replace the GTA natives where GAMPEON has an equivalent, and mark the rest with TODO comments.”

Things to avoid

• Asking for content from other games. Maps, cars, characters or music from other games are not allowed. See Allowed content.
• Pasting secrets. Never paste tokens, passwords or server keys into a chat.
• Huge requests in one go. “Build a full roleplay server” fails; “build a bank resource with deposit and withdraw” works.