Configuration

This page provides a comprehensive guide to configuring the d_roulette script. All settings are located in `config.lua`, which is unencrypted and fully customizable.

Framework Settings

Specifies which RedM framework your server uses. The script will automatically integrate with the selected framework's economy and player systems.

Type: string

Available Options:

• "vorp" - Old VORP-Core below Version 2.0.0

• "vorp2" - Current VORP-Core after Version 2.0.0

• "redemrp" - Old RedEM:RP below Version 2.0.0

• "redemrp2" - Current RedEM:RP after Version 2.0.0

• "rsg" - Old RSGCore

• "rsg2" - Current RSGCore

• "qbc" - QBR-Core

• "gum" - Gum Framework

• "custom" - For your own Framework

Example:

Config.Framework = "vorp2"

Notes:

• Must be set correctly or economy integration will fail

• Framework core must be started before d_roulette

• See Background Information for adding custom framework support

---

Language Settings

Sets the display language for all in-game text, notifications, and UI elements.

Type: string

Available Languages:

• "en" - English (default)

• "de" - German (Deutsch)

• "ru" - Russian (Русский)

Example:

Config.UsedLang = "en"

Adding New Languages:

1. Copy language/en.lua to language/yourlang.lua

2. Translate all string values

3. Set Config.UsedLang = "yourlang"

Language File Structure:

Language["yourlang"] = {
    ["Title"] = "Your Translation",
    ["Start"] = "Your Translation",
    -- ... all keys must be translated
}

---

Table Locations

Defines all roulette table locations, their spawn positions, and unique settings. Each location is a separate table instance with independent configuration.

Type: table (array of location configs)

Location Structure

Each location entry contains:

Config.Locations = {
    ["ExampleLocation"] = {
        Name = "Roulette Blackwater",        -- Display name for prompts and UI

        -- Blip settings
        showBlip = 75,                                          -- Blip visibility range (-1 = always, 0 = never, >0 = within range)
        blipSprite = 1243830185,                                -- Blip icon sprite ID
        blipLocation = {x = -724.79, y = -1238.45, z = 43.7},   -- Blip position

        -- Table spawning
        tblSpawn = true,                                                -- Spawn the table object? (false if spawned by mapping)
        tblModel = "p_roulettetable01x",                               -- Table model (added to match original structure)
        tblLod = 25.0,                                                  -- Table spawn LOD
        tblCoords = {x = -724.79, y = -1238.45, z = 43.7, h = -90.0},   -- Table spawn coordinates + heading

        -- Interaction / prompt settings
        promptLocation = {x = -724.79, y = -1238.45, z = 43.7, h = 358.42}, -- Position of the interaction prompt
        promptRadius = 1.9,                                                 -- Radius to trigger the prompt
        tblRange = 2.5,                                                     -- Max distance allowed while playing

        -- Gameplay configuration
        pricePerChip = 2.5,                     -- Cost per chip
        chipColors = {"blue", "green", "red"},  -- Chip color set
        odds = {                                
            ["straight-up"] = 35,
            ["split"] = 17,
            ["street"] = 11,
            ["corner"] = 8,
            ["five-line"] = 6,
            ["six-line"] = 5,
            ["dozen"] = 2,
            ["column"] = 2,
            ["low-numbers"] = 1,
            ["high-numbers"] = 1,
            ["red-numbers"] = 1,
            ["black-numbers"] = 1,
            ["odd-numbers"] = 1,
            ["even-numbers"] = 1,
        },-- Payout odds for each bet type

        -- Camera offsets
        tblCamBetFieldOffset = {x = 0.4,  y = -0.1,   z = 1.7},
        tblCamRouletteOffset = {x = -0.745, y = -0.170, z = 1.8},
        tblRouletteWheelOffset = {x = -0.738, y = -0.172, z = 1.061},

        -- Optional props to spawn (chips rake, etc.)
        props = {},

        -- Optional objects to delete (mapping cleanup)
        delete = {}
    },
    -- Add additional locations in the same format below...
}

---

Location Properties Explained

Basic Properties

Property	Type	Description	Default
Name	string	Display name shown in prompts and UI	Required

Example:

Name = "Roulette Blackwater",

---

Blip Configuration

Controls the map blip (marker) for this roulette table.

Property	Type	Description	Options
showBlip	number	Blip visibility behavior	-1 = always visible, 0 = never show, >0 = visible within distance
blipSprite	number	Blip icon sprite ID	RedM blip sprite hash
blipLocation	table	Blip position on map	{x = float, y = float, z = float}

Example (Always Visible Blip):

showBlip = -1,                                          -- Always visible on map
blipSprite = 1243830185,                                -- Roulette table icon
blipLocation = {x = -724.79, y = -1238.45, z = 43.7},   -- Map marker position

Example (Proximity Blip):

showBlip = 75,                                          -- Visible within 75 meters
blipSprite = 1243830185,
blipLocation = {x = -724.79, y = -1238.45, z = 43.7},

Example (No Blip):

showBlip = 0,                                           -- Hidden blip
blipSprite = 1243830185,                                -- Still required
blipLocation = {x = -724.79, y = -1238.45, z = 43.7},   -- Still required

Common Blip Sprites:

• 1243830185 - Poker/Roulette table icon

• Find more sprites in RedM native documentation

---

Table Spawning Configuration

Property	Type	Description	Recommended Value
tblSpawn	boolean	Should the table object spawn? Set to false if table exists in map	true
tblModel	string	Prop model name for the table	"p_roulettetable01x"
tblLod	number	Distance at which table spawns (meters)	25.0 - 50.0
tblCoords	table	Table spawn position and rotation	{x = float, y = float, z = float, h = float}

Example (Standard Setup):

tblSpawn = true,
tblModel = "p_roulettetable01x",                                -- Standard roulette table
tblLod = 25.0,                                                  -- Spawn within 25 meters
tblCoords = {x = -724.79, y = -1238.45, z = 43.7, h = -90.0},   -- Position + heading

Example (Custom Table Model):

tblSpawn = true,
tblModel = "c_roulettetable01x",                               -- Custom model
tblLod = 40.0,
tblCoords = {x = -724.79, y = -1238.45, z = 43.7, h = -90.0},

Example (Map-Placed Table):

tblSpawn = false,                                               -- Don't spawn, exists in YMap
tblLod = 25.0,
tblCoords = {x = -724.79, y = -1238.45, z = 43.7, h = -90.0},   -- Match YMap position

Note: Heading (h) is in degrees (0-360), where 0 = North, 90 = East, 180 = South, 270 = West.

---

Interaction & Prompt Settings

Controls how players interact with the table and at what distance.

Property	Type	Description	Recommended
promptLocation	table	Position where interaction prompt appears, should be the middle point of the table	{x = float, y = float, z = float, h = float}
promptRadius	number	Radius around prompt position to trigger interaction (meters)	1.5 - 2.0
tblRange	number	Maximum distance player can be from table while playing (meters)	2.0 - 3.0

Example (Standard Setup):

promptLocation = {x = -724.79, y = -1238.45, z = 43.7, h = 358.42}, -- Prompt position + rotation
promptRadius = 1.9,                                                 -- 1.9 meter interaction radius
tblRange = 2.5,                                                     -- Can play within 2.5 meters

Behavior:

• promptRadius: Player must be within this distance to see/trigger the interaction prompt

• tblRange: Player is kicked from game if they move beyond this distance during gameplay

---

Economy Properties

Property	Type	Description	Example
pricePerChip	number	How much in-game currency each chip costs	2.5 = $2.50 per chip

Example (Low Stakes Table):

pricePerChip = 2.5,       -- $2.50 per chip

Example (Standard Table):

pricePerChip = 10,        -- $10 per chip

Example (High Stakes Table):

pricePerChip = 100,       -- $100 per chip

Balance Considerations:

• Set based on your server's average player income

• Consider maximum bet sizes (e.g., straight-up bets pay 35:1)

• Test economy impact with your player base

---

Chip Colors

Property	Type	Description	Available Colors
chipColors	table (array)	Chip colors available for this table (max 3 players)	"blue", "green", "red", "pink", "white", "black"

Example:

chipColors = {"blue", "green", "red"},

Important Notes:

• Chip prop models must exist: prop_chip_[color]_x1 through prop_chip_[color]_x10

• Custom colors require creating new chip models and language entries

---

Odds Configuration

Standard American Roulette Odds:

odds = {
    ["straight-up"] = 35,      -- Single number (35:1)
    ["split"] = 17,            -- Two adjacent numbers (17:1)
    ["street"] = 11,           -- Three numbers in a row (11:1)
    ["corner"] = 8,            -- Four numbers at intersection (8:1)
    ["five-line"] = 6,         -- 0-00-1-2-3 (6:1)
    ["six-line"] = 5,          -- Six numbers (two streets) (5:1)
    ["dozen"] = 2,             -- 1st/2nd/3rd dozen (2:1)
    ["column"] = 2,            -- Column bet (2:1)
    ["low-numbers"] = 1,       -- Low numbers 1-18 (1:1 / even money)
    ["high-numbers"] = 1,      -- High numbers 19-36 (1:1 / even money)
    ["red-numbers"] = 1,       -- Red numbers (1:1 / even money)
    ["black-numbers"] = 1,     -- Black numbers (1:1 / even money)
    ["odd-numbers"] = 1,       -- Odd numbers (1:1 / even money)
    ["even-numbers"] = 1       -- Even numbers (1:1 / even money)
}

House Edge Impact:

• Higher odds = Lower house edge (better for players)

• Lower odds = Higher house edge (better for casino)

• See [Game Rules](3_Game Rules.md#house-edge-explained) for calculations

---

Camera Offsets

Camera offsets control the player's viewpoint during betting and wheel spin phases. These are relative to the table position and rotation.

Property	Type	Description	Format
tblCamBetFieldOffset	table	Camera position for betting field view	{x = float, y = float, z = float}
tblCamRouletteOffset	table	Camera position for wheel spin view	{x = float, y = float, z = float}
tblRouletteWheelOffset	table	Wheel object spawn position relative to table	{x = float, y = float, z = float}

Standard Table Example:

tblCamBetFieldOffset = {x = 0.4,  y = -0.1,   z = 1.7},
tblCamRouletteOffset = {x = -0.745, y = -0.170, z = 1.8},
tblRouletteWheelOffset = {x = -0.738, y = -0.172, z = 1.061},

Calibration Tips:

1. Start with standard values

2. If using custom table model, adjust Z values for height

3. Test in-game with debug mode to see camera positions

4. Adjust X/Y for horizontal positioning

5. Higher Z = higher camera angle

Common Issues:

• Camera too high/low: Adjust Z value

• Camera clipping through objects: Adjust X/Y away from walls

• Wheel not visible: Adjust tblCamRouletteOffset position

• Bet field off-center: Adjust tblCamBetFieldOffset X/Y values

---

Props Configuration

Allows spawning additional decorative props around the table (rakes, chips, drinks, etc.).

Property	Type	Description	Format
props	table	Dictionary of additional props to spawn	["propName"] = {model = string, x = float, y = float, z = float, h = float}

Example (With Rake):

props = {
    ["rake"]  = {model = "p_rouletterake01x", x = 2868.948, y = -1402.569, z = 43.36999, h = -51.7686},
    -- Additional props...
},

Example (No Extra Props):

props = {},

Common Prop Models:

• p_rouletterake01x - Chip rake

• prop_chips_pile - Chip stack

Note: Coordinates are absolute world positions (not relative to table).

---

Object Deletion

Allows removing unwanted objects from the map at this location (useful for custom mapping).

Property	Type	Description	Format
delete	table	Dictionary of objects to delete by model name and coordinates	["propName"] = {model = string, x = float, y = float, z = float, h = float}

Example (No Deletions):

delete = {}

Example (Delete Specific Objects):

delete = {
    ["chair1"] = {model = "p_rouletterake01x", x = 2878.94, y = -1402.0, z = 43.7, h = -51.7686},
    -- Additional Objects
}

Use Cases:

• Removing conflicting map objects

• Cleaning up area for custom table placement

---

Economy Settings

Maximum time (in seconds) a player can remain inactive during their turn before receiving a warning.

Type: number

Default: 120 (2 minutes)

Example:

Config.ActionTimer = 120

Behavior:

• Timer starts when player joins or after previous round ends

• At 50% of time: No warning

• At 100% of time: First warning notification

• At 200% of time (double): Player kicked from table

Recommended Values:

• Fast-paced servers: 60 seconds

• Casual servers: 120 seconds

• Roleplay-heavy servers: 180 seconds

---

Control Keys

Defines which keyboard/controller buttons are used for various actions during gameplay. Uses RedM native control hashes.

Key Configuration Settings

Config.StartKey = 0xE3BF959B              -- R key (start/interact with table)
Config.InfoKey = 0x1ECA87D4               -- Q key (show information)
Config.CamKey = 0x07B8BEAF                -- ENTER key (camera toggle)
Config.RdyToPlayKey = 0xC7B5340A          -- ENTER key (ready to play)
Config.ChooseChipsLKey = 0x6319DB71       -- ARROW UP (increase chip value)
Config.ChooseChipsRKey = 0x05CA7C52       -- ARROW DOWN (decrease chip value)
Config.SetChipsKey = 0xC7B5340A           -- ENTER key (confirm chip selection)
Config.ChooseBetKey = 0x6DB8C62F          -- SPACE key (select bet position)
Config.ReplaceBetsKey = 0x17BEC168        -- E key (replace/modify bets)
Config.SpinRouletteKey = 0xC7B5340A       -- ENTER key (spin the wheel)
Config.SurrenderKey = 0x156F7119          -- BACKSPACE key (leave table)
Config.MoveUpDownLKey = 0x6319DB71        -- ARROW UP (navigate up)
Config.MoveUpDownRKey = 0x05CA7C52        -- ARROW DOWN (navigate down)
Config.MoveLeftRightLKey = 0xA65EBAB4     -- ARROW LEFT (navigate left)
Config.MoveLeftRightRKey = 0xDEB34313     -- ARROW RIGHT (navigate right)
Config.ColorOneKey = 0xE6F612E4           -- 1 key (select chip color 1)
Config.ColorTwoKey = 0x1CE6D9EB           -- 2 key (select chip color 2)
Config.ColorThreeKey = 0x4F49CC4C         -- 3 key (select chip color 3)

Key Configuration Reference

Setting	Default Key	Hash	Description
StartKey	R	0xE3BF959B	Interact with roulette table
InfoKey	Q	0x1ECA87D4	Display game information
CamKey	ENTER	0x07B8BEAF	Toggle camera view
RdyToPlayKey	ENTER	0xC7B5340A	Confirm ready to start round
ChooseChipsLKey	ARROW UP	0x6319DB71	Increase chip denomination
ChooseChipsRKey	ARROW DOWN	0x05CA7C52	Decrease chip denomination
SetChipsKey	ENTER	0xC7B5340A	Confirm chip selection
ChooseBetKey	SPACE	0x6DB8C62F	Place bet on selected position
ReplaceBetsKey	E	0x17BEC168	Modify or replace existing bets
SpinRouletteKey	ENTER	0xC7B5340A	Spin the roulette wheel
SurrenderKey	BACKSPACE	0x156F7119	Leave the table
MoveUpDownLKey	ARROW UP	0x6319DB71	Move cursor up on betting grid
MoveUpDownRKey	ARROW DOWN	0x05CA7C52	Move cursor down on betting grid
MoveLeftRightLKey	ARROW LEFT	0xA65EBAB4	Move cursor left on betting grid
MoveLeftRightRKey	ARROW RIGHT	0xDEB34313	Move cursor right on betting grid
ColorOneKey	1	0xE6F612E4	Quick select first chip color
ColorTwoKey	2	0x1CE6D9EB	Quick select second chip color
ColorThreeKey	3	0x4F49CC4C	Quick select third chip color

Finding Control Hashes:

• Use RedM native documentation to find control hashes

• Common hashes can be found in the RedM natives reference

---

Discord Webhooks

Discord webhooks allow you to log roulette game events to a Discord channel for monitoring, analytics, and moderation purposes.

Setting Up Discord Webhooks

Step 1: Add your Discord Webhook

Config.WebhookUrl = "YOUR_WEBHOOK_URL_HERE"

Step 2: Enable or disable the needed events

Config.WebhookLogs = {
    ...
}

Webhook Events Logged

The script logs the following events automatically:

Event	Description
TableStarted	First player joined a table
TableEnded	All players leaved a table
TableWinLooseHandling	Round completes
PlayerJoined	Player sits at table
PlayerLeft	Player left at table
PlayerEveryBets	logs sended everytime a player makes a move (adding/removing chips)
PlayerPlacedBets	only logs once for each player after all placed their bets