Mastering Your Clothing Script: `config.lua` Deep Dive

The Clothing Script offers a wealth of customization options via its config.lua file, typically found in resources/rs_clothing/config.lua. This guide will walk you through configuring every aspect to tailor the script perfectly to your server’s needs.

Core System Setup

These settings form the foundational link with your ESX framework and control the script’s basic operational behaviors.

ESX Framework Integration

Custom ESX Event Prefixes

If your server uses custom ESX event prefixes, adjust these settings to ensure compatibility:

-- ESX Event Configuration
Config.CustomESXPrefixEvents = "esx:"
Config.CustomESX_SKINPrefixEvents = "esx_skin:"
Config.CustomESX_ADDONACCOUNTPrefixEvents = "esx_addonaccount:"
Config.CustomESX_SKINCHANGEPrefixEvents = "skinchanger:"

ESX Shared Object

The script needs to access the ESX shared object, typically handled by:

-- ESX Shared Object
Config.ESXSharedObject = function()
    ESX = nil
    TriggerEvent('esx:getSharedObject', function(obj) ESX = obj end)
end

If you’re using a newer version of ESX that uses exports instead of events, you’ll need to modify this function accordingly.

General Settings

Core Functionality Options

Configure the basic operational settings for the script:

-- General Settings
Config.Debug = false -- Enable for verbose logging in console (useful for troubleshooting)
Config.OpenMenuKey = "E" -- Key to open the clothing store menu
Config.OpenTimeout = 500 -- Cooldown in milliseconds to prevent menu spam
Config.Dimension = true -- When true, players enter a separate dimension when using the clothing store
-- Note: Requires OneSync Infinity
Config.SaveFullOutfit = true -- When true, saves the entire current outfit when a player saves an outfit

Setting Config.Dimension = true creates a better user experience by isolating players while they change clothes, but requires OneSync Infinity to be enabled on your server.

Interface & Player Feedback

Customize how the script communicates with your players, from notifications to in-menu text.

Notification System & Localization

Custom Notifications

Customize how notifications are displayed to players and integrate with your existing notification system:

-- Standard ESX Notification
Config.Notification = function(text)
    TriggerEvent('esx:showNotification', text)
end

-- Help Text Notification (shown at the bottom of the screen)
Config.OpenNotification = function(text)
    SetTextComponentFormat("STRING")
    AddTextComponentString(text)
    DisplayHelpTextFromStringLabel(0, 0, 1, -1)
end

Localization

Customize the text messages displayed to players:

-- Localization Settings
Config.Locals = {
    clothesbought = "You've bought some new clothes!",
    outfitsaved = "Outfit has been saved!",
    outfitdeleted = "Outfit has been deleted!",
    notenoughmoney = "Not enough money!",
    editname = "Outfit name has been changed!",
}

To integrate with custom notification systems like pNotify, mythic_notify, or ox_lib, replace the Config.Notification function with the appropriate event trigger for your system.

Economy & Storefronts

Manage your in-game clothing economy, define store locations, and set up item availability and pricing.

Clothing Store Locations

Store Configuration

Define where clothing stores are located on the map. You can add multiple stores with different settings:

Config.Locations = {
    [1] = { -- Unique ID for the store location
        ShowMarker = true, -- Display a marker at the location
        ShowBlip = true,   -- Display a map blip for this store
        
        -- Outfit Sales Payout Configuration
        GiveOutfitOwnerMoney = "empty", -- Who receives money from shared outfit sales:
                                       -- 'society', 'owner', or 'empty' (no one)
        SocietyNameOutfit = "police",  -- Society account name if using 'society' option
        
        -- Clothing Purchase Payout Configuration
        GiveBuyClothingMoney = "empty", -- Who receives money from clothing sales:
                                       -- 'society' or 'empty'
        SocietyNameClothing = "police", -- Society account name if using 'society' option
        
        MoneyPercentage = 100, -- Percentage of sale price given to society/owner
        
        Location = vector4(72.3, -1399.1, 28.4, -90.0), -- Store coordinates (x, y, z, heading)
        
        -- Marker Configuration
        Marker = {
            DrawDistance = 25.0,
            Scale = vector3(1.5, 1.5, 1.0),
            InteractDist = 1.5, -- Distance from which menu can be opened
            Colour = {r = 245, g = 135, b = 46},
            Alpha = 100,
            Type = 1,
            MSG = "Press ~INPUT_CONTEXT~ to open the menu",
        },
        
        -- Blip Configuration
        Blip = {
            Sprite = 73,
            Display = 4,
            Scale = 1.0,
            Colour = 47,
            Name = "Clothing Store",
        },
    },
    -- Add more stores by adding [2], [3], etc.
}

For finding precise coordinates, use the /coords command in-game if you have an admin resource installed, or use an online FiveM coordinate finder tool.

Clothing Categories & Pricing

Item Configuration

Define clothing categories, set default prices, and create specific overrides for individual items:

Config.Categories = {
    ["arms"] = { -- Category ID (must match game component names)
        Label = "Arms",  -- Display name in the menu
        Price = 321,     -- Default price for items in this category
        Overrides = {    -- Specific overrides for individual items
            ["5"] = {    -- Item ID (drawable ID) within this category
                Gender = {"male", "female"}, -- Which gender(s) this applies to
                Label = "Custom Arm Model 5", -- Custom display name
                Price = 500,                 -- Custom price
                Blocked = false,             -- If true, item cannot be purchased
                AccesableFor = {             -- Job/gang restrictions (optional)
                    -- 'ambulance',
                    -- 'police',
                },
            },
            -- Add more item overrides as needed
        }
    },
    -- Add more categories as needed (tshirt_1, pants_1, shoes_1, etc.)
}

Valid category IDs include: arms, tshirt_1, torso_1, pants_1, shoes_1, bags_1, chain_1, helmet_1, glasses_1, watches_1, bracelets_1, mask_1, ears_1, etc.Each category corresponds to a specific clothing component in the game. The item IDs (drawable IDs) must be valid for that component.

🚀 Pro Tips for Deep Customization

Take your clothing script setup to the next level with these advanced strategies:

Optimize Performance: If you have numerous clothing stores, tweak DrawDistance in Config.Locations to balance visibility and resource load.
Boost Economy: Leverage society payment options (GiveOutfitOwnerMoney, GiveBuyClothingMoney) to create dynamic revenue streams for player-run businesses or server funds.
Create Exclusive Stores: Design job-specific or gang-affiliated boutiques by using AccesableFor in Config.Categories to restrict item purchases to certain groups.
Strategic Pricing Models: Implement varied pricing for items and categories to influence your server’s economy and player spending habits.
Theme Your Stores: Use distinct blip icons, names, and marker colors for different store brands or types (e.g., high-end fashion, workwear, tactical gear).

Getting Started

Scripts

Support

Configuration

Mastering Your Clothing Script: `config.lua` Deep Dive

Core System Setup

Custom ESX Event Prefixes

ESX Shared Object

Core Functionality Options

Interface & Player Feedback

Custom Notifications

Localization

Economy & Storefronts

Store Configuration

Item Configuration

🚀 Pro Tips for Deep Customization

Getting Started

Scripts

Support

​Mastering Your Clothing Script: config.lua Deep Dive

​Core System Setup

​Interface & Player Feedback

​Economy & Storefronts

​🚀 Pro Tips for Deep Customization

Mastering Your Clothing Script: `config.lua` Deep Dive

Core System Setup

Interface & Player Feedback

Economy & Storefronts

🚀 Pro Tips for Deep Customization