Build

Changing your script in chat

Every change after the first generation happens in the chat. Say what should be different and watch the files change.

Asking for a change

Every change to an AI Script Generator project goes through the chat box at the bottom. Say what should be different, press Enter and watch the files change. Shift+Enter adds a new line.

Good change requests are specific and one step at a time:

"Add a /speedcams command for police that lists the last 10 fines."
"Use ox_target instead of the E key at the ATMs."
"Move all prices and coordinates into config.lua."

Sped up four times. After the request, each iteration shows what the assistant reads, searches and edits. The run ends with a summary, the changed files and the credits it cost.

While the AI Script Generator works, each step shows as a numbered ITER block: what it reads, what it searches in the FiveM docs and which files it writes. The chat box says Working… until the run ends.

A change running in the Script Generator chat: numbered iterations with the files it reads and edits, and Working in the chat box.

At the end you get a summary of what changed and one line with the details of the run.

The end of a Script Generator run: the last step, the summary and the line with model, tokens, credits and changed files.

Applied changes lists the files of a step, marked EDIT or new.
The last line shows the model, the tokens, the credits (cr) and how many files are new or edited.

When you come back later, each run is folded into a card with its changed files, its steps and its credits.

A past run in the Script Generator chat: the summary and a card with the changed files, the number of iterations and the credits it cost.

Pointing at files

Type @ and the start of a file name in the AI Script Generator chat. A list of matching files opens; pick one and it is inserted. The change then stays in that file.

Typing @ser in the Script Generator chat box opens a list of matching files, here server/main.lua.

Suggested next steps

After a generation the AI Script Generator shows Try one of these next above the chat: for example Add database persistence, Extract everything into config, Add admin commands or Make it translatable. Templates add one suggestion of their own.

The Try one of these next suggestions above the chat; a click on a suggestion filled the chat box with its prompt.

A click only fills the chat box with a detailed prompt. Change it if you like, then press Enter. The × hides the suggestions.

Fixing errors

When a generated script throws an error, give the AI Script Generator the exact text. The assistant fixes errors reliably once it sees the file and the line.

Client errors show in the F8 console in game. Server errors show in the server console or txAdmin.
Copy the whole line, for example SCRIPT ERROR: @speed-cameras/server/main.lua:42: attempt to index a nil value.
Add what you did when it happened: "when I drive past a camera as a police officer".

Good to know

Fix one error per message. A message with ten problems at once often leads to a large change that is hard to check.

Previewing a UI

When an AI Script Generator project has an HTML file, the chat box gets a Preview UI button. It shows your menu or HUD in the browser, without a game or a server, and follows every saved change.

How to use it, what it shows and where it stops is on Previewing HTML and NUI.

Screenshots in the chat

With a plan, the image button in the chat box attaches screenshots or reference images to a message, for example a menu that looks wrong or a design to copy. On free accounts the button shows a lock and opens the plans.