Your first game with AI

This walkthrough builds a small racing checkpoint script with an AI assistant. You do not need to write code yourself.

What works today

The assistant can write resources, check them and create your project page and marketplace entry. Playing and testing in the game needs the engine plugin and test servers, which are planned.

1. Connect

Connect your assistant as described in Connect your AI assistant. For this walkthrough you need the address with login (/mcp) and a token with the template Build with AI.

2. Describe your idea

Tell the assistant what you want, in your own words. Be concrete about the rules:

I want a racing game. Players drive through checkpoints in order. When a player reaches the last checkpoint, everyone sees their time. Keep the best time per player.

A good assistant asks follow-up questions: how many checkpoints, what happens after the finish, should times be saved. Answer them.

3. Let it plan

Ask: “Before writing code, show me the plan: which resources and files, and what each one does.” Check that the plan matches what you want.

4. Let it write and check

Ask it to write the resource. The assistant uses the GAMPEON tools to:

1. look up the right functions in the Lua API reference,
2. create the files from a template (scaffold_resource),
3. check them for mistakes (check_resource): missing files, forbidden functions, GTA natives that do not exist on GAMPEON.

Ask it to fix everything the check reports.

5. Create the project page

Create a project called “Checkpoint Rush”, genre racing, status development.

The assistant creates the page in your account. You can change the text anytime in the portal.

6. Prepare the release

Prepare this as a marketplace item.

The assistant creates the marketplace entry and gives you a link to the portal. You read the rights statement there, confirm it and upload the files. The assistant never confirms rights on your behalf. See Rights statement.

Tips

• Change one thing at a time and ask the assistant to check again after each change.
• Ask “Explain what this script does, line by line, in simple words” whenever you want to understand it.
• See Good prompts for more.