Skip to main content

​
Configuration Structure

Each SixM script includes one or more configuration files that control its behavior.

​
Single Config

Simple scripts use a single config.lua: 
sixm_scriptname/
└── config.lua

​
Multi-File Config

Complex scripts use a config/ directory: 
sixm_scriptname/
└── config/
    ├── config.lua      # Main settings
    ├── client.lua      # Client-side settings
    ├── server.lua      # Server-side settings
    └── shared.lua      # Shared settings

​
Editing Config Files

Open the config file in any text editor. All config values are Lua tables: 
Config = {}

-- General settings
Config.Debug = false              -- Enable debug prints
Config.Framework = 'auto'         -- Framework detection
Config.Language = 'en'            -- Language code

-- Feature toggles
Config.EnableFeatureA = true      -- Toggle feature on/off
Config.EnableFeatureB = false

-- Numeric values
Config.CooldownTime = 5000       -- Time in milliseconds
Config.MaxDistance = 10.0         -- Distance in GTA units

-- Table values
Config.AllowedJobs = {
    'police',
    'ambulance',
    'mechanic'
}
Always save config files in UTF-8 encoding. Incorrect encoding can cause Lua parsing errors.

​
Config Tips

  • Don’t delete config options — if you don’t need a feature, set it to false or leave the default
  • Check data types — strings need quotes ('text'), numbers don’t (100), booleans are true/false
  • Restart after changes — config changes require a resource restart to take effect
  • Backup before editing — keep a copy of the original config in case something breaks