⚙️Configuration

Overview

The Traffic Lights Hacking system is configured entirely through the config.lua file. This guide covers all available configuration options in detail.

Traffic Light Models

Define which traffic light models can be hacked:

Config.LightModels = {
    [1] = -655644382,  -- Standard traffic light model
    [2] = 862871082,   -- Alternative traffic light model
}

Configuration Tips:

• These are GTA V model hashes for traffic light props

• Add more model hashes if your server uses custom traffic light props

• Find model hashes using developer tools or object viewers

Police Requirements

Configure police requirements for hacking traffic lights:

Config.PoliceSettings = {
    enabled = false,  -- Enable/disable police requirement
    reqAmount = 1,  -- Minimum police needed online
    Notify = 'Not enough police on to do this',  -- Notification message
    PoliceJobs = {
        'police'  -- List of police job names
    }
}

Configuration Options:

• enabled - true to require police, false to allow hacking anytime

• reqAmount - Minimum number of online police officers required

• Notify - Message shown when not enough police are online

• PoliceJobs - Array of job names that count as police

Example with Multiple Police Jobs:

Config.PoliceSettings = {
    enabled = true,
    reqAmount = 2,  -- Require 2 police
    Notify = 'Not enough police on duty to hack traffic lights',
    PoliceJobs = {
        'police'
    }
}

Progress Bar Settings

Configure the initial preparation phase:

Config.ProgressBar = {
    timer = 4,  -- Duration in seconds
    title = "Preparing device",
    description = "Please wait...",
}

Configuration Options:

• timer - How long the preparation takes (in seconds)

• title - Text shown on progress bar

• description - Additional description text

Customization Examples:

-- Faster preparation
timer = 2

-- Slower, more realistic
timer = 10

-- Custom text
title = "Initializing Hacking Device"
description = "Connecting to traffic light system..."

Dispatch Settings

Configure police dispatch notifications:

Config.DispatchSettings = {
    title = "Traffic Report",
    description = "Traffic Control is reporting a disturbance",
    jobType = 'police',
    urgency = 2,
}

Configuration Options:

• title - Dispatch call title

• description - Dispatch call description

• jobType - Which job type receives the dispatch

• urgency - Urgency level

Customization Examples:

-- High urgency dispatch
title = "URGENT: Traffic System Breach"
description = "Traffic light system being tampered with - respond immediately!"
urgency = 4

-- Silent/low priority
title = "Minor Traffic Anomaly"
description = "Possible technical issue with traffic lights"
urgency = 1

Hacking Configuration

Configure the core hacking mechanics:

Config.Hacking = {
    requireditem = "jammer",  -- Item needed to hack
    requireditemamount = 1,  -- Amount needed
    takeitem = true,  -- Can the item be consumed?
    takeitemchance = 25,  -- Chance (%) to consume item
    timer = 25,  -- Time per minigame round (seconds)
    difficulty = 5,  -- Minigame difficulty (1-10)
    CompleteNotifyMsg = "Traffic Light hacked",
    CompleteNotifyDoneAlready = "This traffic light has already been hacked!",
    CompleteNotifyStatus = "success",
    CompleteNotifyTimer = 5000
}

Configuration Options:

Item Settings

• requireditem - Item name from your inventory system

• requireditemamount - How many items needed (usually 1)

• takeitem - true to enable consumption chance, false to never consume

• takeitemchance - Percentage chance (0-100) to consume the item on use

Item Configuration Examples:

-- Item is never consumed
takeitem = false

-- Item always consumed
takeitem = true
takeitemchance = 100

-- 50% chance to lose item
takeitem = true
takeitemchance = 50

-- Use different hacking device
requireditem = "advanced_laptop"

Minigame Settings

• timer - Time limit per minigame round (in seconds)

• difficulty - How hard the minigame is (1-10 scale)

  • 1-3: Easy (more time, fewer requirements)

  • 4-6: Medium (balanced)

  • 7-10: Hard (less time, more requirements)

Difficulty Examples:

-- Very easy (beginner friendly)
timer = 40
difficulty = 2

-- Hard (experienced players)
timer = 15
difficulty = 8

-- Extreme difficulty
timer = 10
difficulty = 10

Important: Players must complete 3-5 rounds (randomly chosen) of the minigame. Each round uses the same difficulty settings.

Notification Settings

• CompleteNotifyMsg - Success message

• CompleteNotifyDoneAlready - Message when traffic light already hacked

• CompleteNotifyStatus - Notification type ('success', 'info', 'error', 'warning')

• CompleteNotifyTimer - How long notification shows (milliseconds)

Reward System

The script supports three types of rewards: Items, Cryptocurrency, and Reputation.

Reward Notifications

Config.RewardNotify = true  -- Show notification when rewards are received

Set to false to disable reward notifications.

Reward Tiers

Each reward type has three tiers based on random chance:

• lowtier - Common rewards, easier to get

• mediumtier - Uncommon rewards, moderate chance

• hightier - Rare rewards, low chance

Item Rewards

Config.Rewards = {
    Item = {
        enabled = true,  -- Enable/disable item rewards
        Rewards = {
            lowtier = {
                [1] = {
                    item = 'copper',  -- Item name
                    amount = 1,  -- Quantity
                    chance = 15,  -- % chance to receive
                }
            },
            mediumtier = {
                [1] = {
                    item = 'inverter',
                    amount = 1,
                    chance = 10,
                },
                [2] = {
                    item = 'electronicwiring',
                    amount = 1,
                    chance = 10,
                }
            },
            hightier = {
                [1] = {
                    item = 'jammer',
                    amount = 1,
                    chance = 5,
                },
                [2] = {
                    item = 'hacking_pcb',
                    amount = 1,
                    chance = 10,
                }
            }
        }
    }
}

Configuration Options:

• enabled - Enable/disable this reward type

• item - Item name from your inventory system

• amount - How many of the item to give

• chance - Percentage chance (0-100) to receive this item

Adding More Rewards:

lowtier = {
    [1] = {
        item = 'copper',
        amount = 1,
        chance = 15,
    },
    [2] = {  -- Add another item
        item = 'plastic',
        amount = 2,
        chance = 20,
    }
}

Cryptocurrency Rewards

Config.Rewards = {
    Crypto = {
        Enabled = true,
        Rewards = {
            lowtier = {
                [1] = {
                    type = 'primetoken',  -- Crypto type
                    amount = 1,  -- Quantity
                    chance = 15,  -- % chance
                }
            },
            mediumtier = {
                [1] = {
                    type = 'primetoken',
                    amount = 2,
                    chance = 20,
                }
            },
            hightier = {
                [1] = {
                    type = 'primetoken',
                    amount = 3,
                    chance = 25,
                }
            }
        },     
    }
}

Configuration Options:

• Enabled - Enable/disable crypto rewards

• type - Cryptocurrency type name from your framework

• amount - Amount of crypto to give

• chance - Percentage chance to receive

Using Different Crypto:

lowtier = {
    [1] = {
        type = 'bitcoin',
        amount = 0.001,
        chance = 10,
    }
}

Reputation Rewards

Config.Rewards = {
    Rep = {
        Enabled = true,
        Rewards = {
            lowtier = {
                [1] = {
                    Reptype = 'crime',  -- Reputation category
                    amount = 3,  -- Amount to add
                    chance = 25,  -- % chance
                }
            },
            mediumtier = {
                [1] = {
                    Reptype = 'crime',
                    amount = 4,
                    chance = 35,
                }
            },
            hightier = {
                [1] = {
                    Reptype = 'crime',
                    amount = 5,
                    chance = 50,
                }
            }
        },     
    }
}

Configuration Options:

• Enabled - Enable/disable reputation rewards

• Reptype - Reputation category from your framework

• amount - Amount of reputation to add

• chance - Percentage chance to receive

Multiple Reputation Types:

hightier = {
    [1] = {
        Reptype = 'crime',
        amount = 5,
        chance = 50,
    },
    [2] = {
        Reptype = 'hacking',
        amount = 10,
        chance = 30,
    }
}

Reward Chances System

Configure the probability of receiving each reward tier.

Basic Chance System (No Luck)

Config.RewardChances = {
    Item = {
        NoLuck = {
            lowtier = 80,  -- 80% or less = lowtier
            mediumtier = 50,  -- 50% or less = mediumtier
            hightier = 35  -- 35% or less = hightier
        }
    }
}

How It Works:

1. System rolls a random number 1-100

2. If roll ≤ hightier value (35) → Player gets hightier rewards

3. Else if roll ≤ mediumtier value (50) → Player gets mediumtier rewards

4. Else if roll ≤ lowtier value (80) → Player gets lowtier rewards

5. Otherwise → No rewards from this tier system

Tuning Examples:

-- Very generous (high chance of rare rewards)
NoLuck = {
    lowtier = 90,
    mediumtier = 70,
    hightier = 50
}

-- Balanced
NoLuck = {
    lowtier = 80,
    mediumtier = 50,
    hightier = 25
}

-- Very rare (low chance of good rewards)
NoLuck = {
    lowtier = 60,
    mediumtier = 30,
    hightier = 10
}

Luck-Based Rewards (Optional)

Enable luck-based reward scaling for players with luck status effects:

Config.RewardChances = {
    Item = {
        WithLuck = {
            LuckEnabled = true,  -- Enable luck system
            [25] = {  -- For players with 1-25% luck
                lowtier = 75,
                mediumtier = 20,
                hightier = 25
            },
            [50] = {  -- For players with 26-50% luck
                lowtier = 70,
                mediumtier = 25,
                hightier = 35
            },
            [75] = {  -- For players with 51-75% luck
                lowtier = 65,
                mediumtier = 30,
                hightier = 40
            },
            [100] = {  -- For players with 76-100% luck
                lowtier = 60,
                mediumtier = 35,
                hightier = 45
            }
        }
    }
}

Configuration Options:

• LuckEnabled - true to use luck-based scaling, false to always use NoLuck values

• [25], [50], [75], [100] - Luck level breakpoints

How Luck Works:

• Requires the statuseffects resource to be running

• Players gain luck from consumables or other game mechanics

• Higher luck = better chance at higher tier rewards

• System checks player's luck value and uses appropriate tier chances

Disabling Luck for Specific Rewards:

Config.RewardChances = {
    Item = {
        WithLuck = {
            LuckEnabled = true  -- Items use luck
        }
    },
    Crypto = {
        WithLuck = {
            LuckEnabled = false  -- Crypto ignores luck
        }
    }
}

Electrocution System

Configure the electrocution mechanic that can occur when hacking:

Config.ElectrocuteChance = {
    amount = 4,  -- Every X traffic lights
    chance = 50,  -- % chance when threshold reached
}

How It Works:

• Tracks how many traffic lights each player has hacked

• When player reaches the amount threshold, rolls for electrocution

• If electrocution occurs, player is stunned briefly

Configuration Examples:

-- Always electrocute after 3 hacks
amount = 3
chance = 100

-- Never electrocute
amount = 999
chance = 0

-- Rare electrocution
amount = 10
chance = 25

-- Frequent risk
amount = 2
chance = 75

Note: The amount field appears to track in memory but actual implementation uses a different trigger (on minigame failure). The electrocution primarily triggers when a player fails the hacking minigame.

Complete Configuration Example

Here's a fully configured example balancing difficulty and rewards:

Config = {}

-- Traffic light models
Config.LightModels = {
    [1] = -655644382,
    [2] = 862871082,
}

-- Require 2 police online
Config.PoliceSettings = {
    enabled = true,
    reqAmount = 2,
    Notify = 'Not enough police on duty to hack traffic systems',
    PoliceJobs = {'police', 'sheriff', 'trooper'}
}

-- 6 second preparation
Config.ProgressBar = {
    timer = 6,
    title = "Initializing Device",
    description = "Connecting to traffic light controller...",
}

-- High urgency dispatch
Config.DispatchSettings = {
    title = "Traffic System Breach",
    description = "Traffic light system being tampered with!",
    jobType = 'police',
    urgency = 4,
}

-- Moderate difficulty
Config.Hacking = {
    requireditem = "jammer",
    requireditemamount = 1,
    takeitem = true,
    takeitemchance = 33,  -- 1/3 chance to lose device
    timer = 20,
    difficulty = 6,
    CompleteNotifyMsg = "Traffic system successfully breached!",
    CompleteNotifyDoneAlready = "This light has already been hacked recently.",
    CompleteNotifyStatus = "success",
    CompleteNotifyTimer = 5000
}

Config.RewardNotify = true

-- Balanced rewards with luck
Config.RewardChances = {
    Item = {
        NoLuck = {lowtier = 75, mediumtier = 45, hightier = 25},
        WithLuck = {
            LuckEnabled = true,
            [25] = {lowtier = 75, mediumtier = 45, hightier = 30},
            [50] = {lowtier = 70, mediumtier = 50, hightier = 35},
            [75] = {lowtier = 65, mediumtier = 55, hightier = 40},
            [100] = {lowtier = 60, mediumtier = 60, hightier = 45}
        }
    },
    -- Similar for Crypto and Rep...
}

-- Generous item rewards
Config.Rewards = {
    Item = {
        enabled = true,
        Rewards = {
            lowtier = {
                [1] = {item = 'copper', amount = 2, chance = 50}
            },
            mediumtier = {
                [1] = {item = 'inverter', amount = 1, chance = 30},
                [2] = {item = 'electronicwiring', amount = 1, chance = 30}
            },
            hightier = {
                [1] = {item = 'jammer', amount = 1, chance = 20},
                [2] = {item = 'hacking_pcb', amount = 1, chance = 25}
            }
        }
    }
    -- Similar for Crypto and Rep...
}

-- Frequent electrocution risk
Config.ElectrocuteChance = {
    amount = 3,
    chance = 60
}

Next Steps

After configuring your traffic lights hacking system, check out the FAQ for common questions and troubleshooting tips, or return to Installation for setup instructions.