FiveM development. Step by step.
Understand configuration. Change values precisely.
Config Editor exposes supported resource settings in a visual interface. Keep the source in view and change values without searching through every line of a long configuration file.
What you can do
The editor supports Lua, JSON, YAML, TOML and INI. Which values can be edited visually depends on your file structure.
Open a config in chatConfig.Garage = {
label = "Central Garage"
}Work with the resource you already have
Open resource files through the chat and project workflow. First check which configuration file is actually loaded. Some scripts separate vehicles, locations and text into multiple files. The file tree and source view help you keep their relationship clear.
Check both the value and its meaning
Change labels, numbers or supported switches. A technically valid number is not necessarily a sensible game setting: prices, coordinates and job names must match the resource. Source view is important for dynamic Lua or complex expressions; not all logic can be represented as form fields.
Apply changes under your control
Compare your revision with the original file and download changes as ZIP. Back up the existing resource before replacing server files. Run it on a test server and check that the new values are actually loaded. This keeps editing separate from deployment.
For your next task
A focused configuration change
Open the garage configuration. Change the display name and parking fee while preserving event names and database fields. Review coordinates in source view, then export after comparing with the original version.
Check before moving on
- Check the loaded file and resource mapping
- Preserve data types and their meaning
- Review dynamic expressions in source view
- Back up and test the exported version
Scope and limitations
Visual editing covers supported configuration structures. It is neither a full Lua runtime nor a substitute for testing your server. Complex logic may still require editing source code.
Current plans and conditions →Common questions
Is the editor only for Lua?
No. Supported configurations may also use JSON, YAML, TOML or INI. Available editing depends on the format and structure.
Does it write directly to my server?
The workflow described here provides files for download. You decide when and where to deploy the reviewed version.
Your project. Your next step.
Describe your idea or upload an existing resource. Continue working on the source code and test the result on your server.
Open AI chat →