Quasar Store Logo

Installation

Installation guide — please follow each step carefully and exactly as described to ensure the script works correctly on your server. Skipping or modifying steps may cause the system to not function properly, so follow it step by step.

Download Script

To download the assets needed for this script, you must access the official Cfx.re portal, where all assets purchased through Tebex are managed.

1

Access the Granted Assets Page

Open the Cfx.re granted assets page: https://portal.cfx.re/assets/granted-assets.

This page contains all assets linked to your Cfx.re purchases.

2

Log In with Your Cfx.re Account

Sign in using the same Cfx.re account you used when purchasing the asset.

If you use a different account, the assets will not appear.

3

Download the Housing Assets

In the granted assets list, locate and download:

Diamond Casino [asset]
Diamond Casino [map]

These two packages are required to install the full housing system.

These files include the models, materials, and visual resources required for the proper operation of the housing system.





Download Dependencies

This script requires some mandatory dependencies to function correctly. Make sure to download and extract them inside your server’s main directory, keeping their original folder structure intact.





Remove Other Scripts

This script may cause conflicts or errors if you use other casino systems on your server. Common examples include qb-casino or other similar casino scripts. It’s strongly recommended to remove them completely before installation to prevent compatibility or functionality issues.





Database Setup

Avoid using tools like XAMPP or other non-optimized local servers, as they may cause connection errors.

This script includes an essential database required for its operation.You must import it before starting your server, preferably using HeidiSQL or any other manager compatible with MariaDB/MySQL.

ESX

INSERT INTO `addon_inventory` (name, label, shared) VALUES ('casino', 'Casino', 0); INSERT INTO `datastore` (name, label, shared) VALUES ('casino', 'Casino', 0); DROP TABLE IF EXISTS `casino_memberships`; CREATE TABLE `casino_memberships` ( `id` INT(11) NOT NULL AUTO_INCREMENT, `identifier` VARCHAR(90) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci', `chips` INT(11) NOT NULL DEFAULT '0', `vip` TINYINT(1) NULL DEFAULT '0', `luckywheel_date` TIMESTAMP NULL DEFAULT current_timestamp(), `chip_buy_date` TIMESTAMP NULL DEFAULT current_timestamp(), PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `identifier` (`identifier`) USING BTREE ) COLLATE='utf8mb3_general_ci' ENGINE=InnoDB AUTO_INCREMENT=1 ; DROP TABLE IF EXISTS `casino_blocked_players`; CREATE TABLE `casino_blocked_players` ( `id` INT(11) NOT NULL AUTO_INCREMENT, `identifier` VARCHAR(90) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci', `reason` TEXT NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci', PRIMARY KEY (`id`) USING BTREE ) COLLATE='utf8mb3_general_ci' ENGINE=InnoDB ;
QB





Casino Chips As Item

This configuration allows casino chips to be handled as an inventory item instead of a virtual balance. When enabled, players must physically own the chip item in their inventory to gamble, making the casino system more immersive and compatible with inventory-based economies. You can also limit the number of chips a player can purchase per day.

-- config/main.lua --────────────────────────────────────────────────────────────────────────────── -- Casino NPCs & Chips [INFO] -- [INFO] You can extend NPC configurations (chips, teleporters, memberships, market). -- Ensure correct models/coords/anims per NPC role. --────────────────────────────────────────────────────────────────────────────── Config.ChipBuyLimit = 5000 -- [EDIT] Max chips purchasable per day (false to disable limit). Config.ChipsAsItem = true -- [EDIT] Store chips as an inventory item? Config.ChipItemName = 'casinochips' -- [EDIT] Item name used for chips.