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.
1
Logging in to the CFX Portal
First, log in to the official CFX portal by clicking here.
2
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.
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.
1
ox_lib
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:
1
Update Artifacts
Completely replace your current artifacts with the latest version. Download the appropriate artifacts for your operating system from the official links:
This asset must always be started below your framework and inventory. Failure to do so may result in functionality issues or critical errors. To ensure smooth operation and proper initialization, it is recommended to start the entire download folder using "ensure [minerjob]" in your server.cfg.
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.
Select the framework you are using and then execute the SQL in your HeidiSQL. If you encounter errors, ensure you are using the most current version of MariaDB. You can refer to our guide above or search online.
Database for esx
INSERT INTO `jobs` (name, label) VALUES
('miner','Miner')
;
INSERT INTO `job_grades` (job_name, grade, name, label, salary, skin_male, skin_female) VALUES
('miner',0,'novice','Novice',10,'{}','{}')
;
CREATE TABLE IF NOT EXISTS `qs_miner` (
`identifier` VARCHAR(46) NOT NULL COLLATE 'utf8mb4_general_ci',
`level` INT(10) UNSIGNED NOT NULL DEFAULT '1',
`experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`total_experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`total_earnings` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`season_experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`season_earnings` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`daily_experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`daily_earnings` INT(10) UNSIGNED NOT NULL DEFAULT '0',
PRIMARY KEY (`identifier`) USING BTREE
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
CREATE TABLE IF NOT EXISTS `qs_miner_resets` (
`identifier` VARCHAR(46) NOT NULL COLLATE 'utf8mb4_general_ci',
`last_daily_reset` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
`last_season_reset` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (`identifier`) USING BTREE
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
CREATE TABLE IF NOT EXISTS `qs_miner_rewards` (
id INT AUTO_INCREMENT PRIMARY KEY,
identifier VARCHAR(255) NOT NULL,
reward_type VARCHAR(50) NOT NULL,
reward_amount INT NOT NULL
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
CREATE TABLE IF NOT EXISTS `qs_miner_leaderboard_winners` (
id INT AUTO_INCREMENT PRIMARY KEY,
position INT NOT NULL,
identifier VARCHAR(255) NOT NULL,
reward_amount INT NOT NULL,
reward_type VARCHAR(10) NOT NULL,
UNIQUE KEY (position, reward_type)
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
Database for qbcore
CREATE TABLE IF NOT EXISTS `qs_miner` (
`identifier` VARCHAR(46) NOT NULL COLLATE 'utf8mb4_general_ci',
`level` INT(10) UNSIGNED NOT NULL DEFAULT '1',
`experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`total_experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`total_earnings` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`season_experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`season_earnings` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`daily_experience` INT(10) UNSIGNED NOT NULL DEFAULT '0',
`daily_earnings` INT(10) UNSIGNED NOT NULL DEFAULT '0',
PRIMARY KEY (`identifier`) USING BTREE
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
CREATE TABLE IF NOT EXISTS `qs_miner_resets` (
`identifier` VARCHAR(46) NOT NULL COLLATE 'utf8mb4_general_ci',
`last_daily_reset` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
`last_season_reset` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (`identifier`) USING BTREE
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
CREATE TABLE IF NOT EXISTS `qs_miner_rewards` (
id INT AUTO_INCREMENT PRIMARY KEY,
identifier VARCHAR(255) NOT NULL,
reward_type VARCHAR(50) NOT NULL,
reward_amount INT NOT NULL
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
CREATE TABLE IF NOT EXISTS `qs_miner_leaderboard_winners` (
id INT AUTO_INCREMENT PRIMARY KEY,
position INT NOT NULL,
identifier VARCHAR(255) NOT NULL,
reward_amount INT NOT NULL,
reward_type VARCHAR(10) NOT NULL,
UNIQUE KEY (position, reward_type)
)
ENGINE=InnoDB
COLLATE='utf8mb4_general_ci'
;
Replacing LegacyFuel with Quasar Fuel Stations
Quasar Fuel Stations is designed to completely replace the LegacyFuel system while maintaining compatibility with LegacyFuel's exports and events. This ensures a seamless transition without requiring significant changes to your existing codebase.
1
Remove LegacyFue
Before starting Quasar Fuel Stations, ensure that LegacyFuel is completely removed from your server. Keeping LegacyFuel alongside Quasar Fuel Stations may result in conflicts or duplicate functionality.
2
Automatic Compatibility
Quasar Fuel Stations automatically reads and handles LegacyFuel's exports and events. This allows existing scripts that rely on LegacyFuel functionality to continue working without modifications.
3
Verify Deletion
Double-check your server's resources to confirm that LegacyFuel has been deleted to prevent errors or unexpected behavior.
By following these steps, Quasar Fuel Stations can take over all fuel-related functions on your server, offering enhanced features while preserving backward compatibility with LegacyFuel systems.
