Installation

Script Download

Before starting, you must log in to the CFX portal to download the asset. You will be able to download it as many times as you want on the official CFX page. Just as you download it the first time, you will also download it multiple times in the future to get updates.

Logging in to the CFX Portal

First, log in to the official CFX portal by clicking here.

Finding Your Assets

Once logged in, navigate to the Granted Assets section to access your purchased assets. You can download them by clicking the "Download" button.

Remember, if you encounter any issues or errors when starting the asset, you can check here to see if the problem is related.

Understanding CFX Auth

Downloading Dependencies

The dependencies for this asset are mandatory, so please follow the dependency guide completely and use all required files.

When downloading a dependency, ensure the file is properly unzipped and does not include "-main" at the end of its name. If it does, please remove it.

Update artifacts and gamebuild

Updating to the latest artifacts and gamebuild is essential to avoid common server issues. Here's how to do it properly:

Update Artifacts

Completely replace your current artifacts with the latest version. Download the appropriate artifacts for your operating system from the official links:

Windows: Windows Artifacts.
Linux: Linux Artifacts.

Update Gamebuild

Using the latest gamebuild is critical to take advantage of the newest features and avoid compatibility errors.

Edit the server.cfg file and add the following line:

sv_enforceGameBuild 3258

You can see the complete guide to update your server here:

How to update my server

Server.cfg Positioning

To ensure Quasar Crafting Creator works properly, it must always be started after your framework (e.g., qb-core, es_extended) and after your inventory system (e.g., qs-inventory, ox_inventory). This ensures all dependencies are properly loaded before the script is initialized.

Database Installation

For this step, we highly recommend using HeidiSQL to avoid issues, as it provides an updated version of MariaDB. We have a guide that explains step-by-step how to use HeidiSQL. If you choose to use phpMyAdmin, we will not be responsible for any errors that may occur in your database.

How to install HeidiSQL

Since this script supports both ESX and QBCore, the SQL file includes entries for both frameworks. Simply select the SQL section that matches your framework — either ESX or QBCore — and execute it accordingly.

Database for esx

CREATE TABLE IF NOT EXISTS `crafting_queue` (
	`id` INT(11) NOT NULL AUTO_INCREMENT,
	`owner` VARCHAR(80) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`tableId` VARCHAR(30) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	`item` VARCHAR(50) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	`amount` INT(11) NOT NULL DEFAULT '1',
	`startDate` TIMESTAMP NULL DEFAULT NULL,
	`duration` INT(11) NULL DEFAULT NULL,
	`earn` INT(11) NULL DEFAULT '0',
	PRIMARY KEY (`id`) USING BTREE,
	INDEX `owner_tableId` (`owner`, `tableId`) USING BTREE
)
COLLATE='utf8mb3_general_ci'
ENGINE=InnoDB
;



CREATE TABLE IF NOT EXISTS `crafting_tables` (
	`id` INT(11) NOT NULL AUTO_INCREMENT,
	`creator` VARCHAR(80) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`label` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`size` SMALLINT(6) NOT NULL DEFAULT '0',
	`job` VARCHAR(30) NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`grades` LONGTEXT NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	`object` VARCHAR(50) NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`coords` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`recipes` LONGTEXT NOT NULL COLLATE 'utf8mb4_bin',
	`blip` LONGTEXT NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	PRIMARY KEY (`id`) USING BTREE
)
COLLATE='utf8mb3_general_ci'
ENGINE=InnoDB
;

ALTER TABLE `users` ADD IF NOT EXISTS `crafting_skill` LONGTEXT NULL DEFAULT NULL;

Database for qbcore

CREATE TABLE IF NOT EXISTS `crafting_queue` (
	`id` INT(11) NOT NULL AUTO_INCREMENT,
	`owner` VARCHAR(80) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`tableId` VARCHAR(30) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	`item` VARCHAR(50) NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	`amount` INT(11) NOT NULL DEFAULT '1',
	`startDate` TIMESTAMP NULL DEFAULT NULL,
	`duration` INT(11) NULL DEFAULT NULL,
	`earn` INT(11) NULL DEFAULT '0',
	PRIMARY KEY (`id`) USING BTREE,
	INDEX `owner_tableId` (`owner`, `tableId`) USING BTREE
)
COLLATE='utf8mb3_general_ci'
ENGINE=InnoDB
;

CREATE TABLE IF NOT EXISTS `crafting_tables` (
	`id` INT(11) NOT NULL AUTO_INCREMENT,
	`creator` VARCHAR(80) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`label` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`size` SMALLINT(6) NOT NULL DEFAULT '0',
	`job` VARCHAR(30) NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`grades` LONGTEXT NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	`object` VARCHAR(50) NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`coords` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`recipes` LONGTEXT NOT NULL COLLATE 'utf8mb4_bin',
	`blip` LONGTEXT NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	PRIMARY KEY (`id`) USING BTREE
)
COLLATE='utf8mb3_general_ci'
ENGINE=InnoDB
;


ALTER TABLE `players` ADD IF NOT EXISTS `crafting_skill` LONGTEXT NULL DEFAULT NULL;

Key bind manipulation

All Quasar Store assets use the same process for modifying Key Binds to ensure consistency and optimized performance across all resources.

Below is a clear and detailed guide on how to adjust them to your preferences.

How to change key bindings

Last updated 1 hour ago