RPCrate AI: first project, checks and ZIP export

Start with one small feature in RPCrate AI, then review and test it before adding more. A successful generation means files were saved; it does not prove that the resource works with your server's dependencies or economy.

Write a prompt your server can useCopy Anchor Link

Select your actual framework. Include the inventory and target resources you run, how players open the feature, which settings belong in config and what the server must validate. Do not upload credentials, player data or someone else's protected resource.

For a first run, try this standalone feature:

Create a standalone FiveM /rules command. Show a small NUI panel with
three server rules from config.lua. Escape and a Close button dismiss it.
Release NUI focus on close and resource stop. No database, payments or
external HTTP requests. Include fxmanifest.lua and explain how to test it.

This keeps the first test bounded: run /rules, read the panel, close it with each control and confirm that movement and keyboard input work afterwards. Credit use depends on the generated output and revisions; a template is not a promise that a run fits the free balance. The free allowance is 3 credits per day, capped at 15 per calendar month.

Choose QBCore, ESX or Qbox deliberatelyCopy Anchor Link

Framework names are not interchangeable. Tell the generator the versions and resources installed on your development server, rather than asking it to guess.

For a delivery job, first ask for clock-in and clock-out only. Once that works, add one destination and a fixed payout. Ask for the server to verify the active shift, job, destination distance and completion state before awarding money. Test repeated completion requests and disconnects before expanding the route.

Review the files and checksCopy Anchor Link

Open the file tree and read fxmanifest.lua. Confirm the scripts, dependencies and NUI assets match the files in the ZIP. Manifest entries determine what FiveM loads; a file that merely exists in the folder may not run.

Review the Lua on both sides. Any event affecting money, inventory or permissions needs server-side validation. For NUI, check that callbacks answer, input is validated and focus is released. Generated explanations are useful context, but the source and your test results are the evidence.

RPCrate's checks can flag Lua syntax, manifest, framework API and NUI build problems. They do not run your full multiplayer server. If a check fails, use its file and line to request a focused correction. If you see a runtime error, provide the error and reproduction steps with secrets removed. Compare the changed files before retrying.

Export and test on a development serverCopy Anchor Link

1. Download the project's ZIP. If the editor reports problems, review them before choosing to download anyway.
2. Extract it into a new resource folder in your development server. Read the generated instructions and install the listed dependencies.
3. Start dependencies first, then add ensure your_resource_name to server.cfg. Keep the folder name consistent with your ensure command.
4. Check the server console and client F8 console. Run the normal flow, cancel midway, repeat an action and test with a player who lacks permission.
5. For UI, test open/close, Escape, resource restart and different resolutions. For payouts or items, test with two players and confirm the server decides the result.
6. Keep the working ZIP and configuration as a rollback copy before changing a live server.

Use the installation guide and the QBCore, ESX or Qbox instructions for framework setup. Larger systems such as phones or housing need broader testing; browse finished scripts when an existing product better fits your requirements.

References for checking generated codeCopy Anchor Link

• Cfx.re resource manifest reference
• Cfx.re guidance on securing events
• QBCore core object documentation
• Qbox server exports
• ESX shared functions

Return to the FiveM AI Script Generator with one clear feature and a test you can perform.