Permission Config Generator

Permission Config Generator generates FiveM-compatible GTA 6 / GTA RP code: server.cfg entries, item definitions, job configs, loot tables, polyzones, vehicle shop entries - any resource type the tool supports. The generated code adheres to the conventions of QBCore, ESX, QBox, ox_inventory, or standalone resources depending on what you select, so you can copy it directly into your server directory. Internally the output format is plain-text Lua, JSON, SQL or CFG depending on the tool used to generate it. All formats are git-friendly and have clean diffs when you re-run generation.

Fields map directly 1:1 to values written to the output file. You do not need to memorize syntax - defaults give you a working config file, and each input change only updates that line in the generated code. The live preview allows you to see what each field does before trying it on a live server. Framework choice: pick the one your server is currently running. If you are in the middle of migrating, run both and diff the outputs - they are structured nearly identically, so it'll be simple to identify what differs between QBCore and ESX.

Copy the generated code and paste it directly into your server config, resource Lua file or JSON/SQL config. Restart your server or resource and your config is now live! Should you be utilizing a framework (ESX Legacy, QBCore, QBox, VORP), the output will abide by framework standards and should not interfere with other resources. For ox_inventory specifically, the items table format is identical to the latest ox_inventory schema, allowing stack sizes, weights, and metadata blocks by default.

Minor adjustments can be made in your editor. The tool shines when you are scaffolding the structure; after it's in your repo, you use your normal workflow. Speaking of version control, commit your generated file with a clear message referencing the tool you used ("Generated server.cfg via gtatools.net"). Then, when you regenerate it later with modified settings, git diff will show you exactly what changed. Plus, reviewers will know at a glance it came from a tool and wasn't hand-edited.