Configuration

Configuration

This guide covers all configuration options available in Prodigy Chat. All settings are located in config.lua.

General Configuration

Basic Settings

Config.moneySymbol = "$"                    -- Currency symbol used throughout the chat system
Config.welcomeMessage = false               -- Enable welcome message on player connect
Config.serverName = "Server Name"           -- Server name displayed in welcome message
Config.maxCharactersPerMessage = 250        -- Maximum characters allowed per chat message

Job Advertisement Configuration

Config.jobAdWhitelistedJobs = {
    "police", "ambulance", "mechanic", "taxi", 
    "realestateagent", "cardealer", "banker", 
    "lawyer", "reporter"
}
Config.adCooldowns = 100                    -- Cooldown in seconds between /ad and /jobad messages
Config.adPrice = 100                        -- Set to 0 to disable charge

Permission Groups Configuration

Prodigy Chat uses ESX's group system for permissions. Groups are stored in the users table's group column.

Group Descriptions

  • management: Management, full access to all commands

  • developer: Developers, full access to all commands

  • leadadmin: Lead Admins, can use /la, /aooc, /announce, /changeplayername

  • gameadmin: Game Admins, can use /adminduty, /admins, /sc, /a, /setmodel, /clearmap

  • tester: Beta testers, can use /help, /report, /tickets, /testers

Feature Toggles

Misc Features

Admin Commands

Clothing System Configuration

The clothing system allows players to toggle clothing items on/off for roleplay scenarios.

Available Clothing Commands: /shirt, /bra, /pants, /panties, /shoes, /chain, /decals, /vest, /bag, /mask, /hat, /glasses, /earrings, /watch, /bracelet

Damage Tracking System

The damage tracking system monitors and displays damage taken by players.

Damage Configuration

Auto Grammar Configuration

Automatic grammar correction for common mistakes.

Configuration Best Practices

  1. Start with defaults: Begin with default settings and adjust as needed

  2. Test changes: Test configuration changes on a test server first

  3. Backup config: Always backup your config.lua before making changes

  4. Document customizations: Keep notes on why you changed specific settings

  5. Group permissions: Carefully configure permission groups to match your server structure

Common Configuration Scenarios

Disable Admin Commands

Enable Phone Commands

Customize Permission Groups

Disable Clothing System

Adjust Damage Tracking

Last updated