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.

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

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.

1

ox_lib

Releases · overextended/ox_libGitHub

2

oxmysql

Releases · overextended/oxmysqlGitHub

3

hospital_map (default hospital)

GitHub - qbcore-framework/hospital_map: Map Used With QB-AmbulancejobGitHub

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:

sv_enforceGameBuild 3095

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

Server.cfg Positioning

To ensure [hospital] works properly, always start your framework (e.g., ESX, QBCore) first, followed by your inventory system (e.g., qs-inventory, ox_inventory) and your shops system (e.g., qs-advancedshops, ox_inventory).

Finally, start [hospital], making sure all dependencies are already running beforehand.

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.

As there are multiple housing systems in the market, and frameworks like QBCore include systems like qb-houses with similar database columns to qs-housing, we will begin by cleaning the database before executing the SQL. Start by using the first dropdown labeled "First we clean the database", then select the dropdown for the framework you are using.

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

CREATE TABLE IF NOT EXISTS `hospitals` (
	`id` INT(11) NOT NULL AUTO_INCREMENT,
	`creator` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`zone` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`respawnPoint` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`blip` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`duty` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`stash` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`boss` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`checkIn` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`wardrobe` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`shop` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`garage` LONGTEXT NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	PRIMARY KEY (`id`) USING BTREE
)
COLLATE='utf8mb3_general_ci'
ENGINE=InnoDB
;

CREATE TABLE IF NOT EXISTS `hospitals` (
	`id` INT(11) NOT NULL AUTO_INCREMENT,
	`creator` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb3_general_ci',
	`zone` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`respawnPoint` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`blip` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`duty` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`stash` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`boss` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`checkIn` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`wardrobe` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`shop` LONGTEXT NOT NULL COLLATE 'utf8mb3_general_ci',
	`garage` LONGTEXT NULL DEFAULT NULL COLLATE 'utf8mb3_general_ci',
	PRIMARY KEY (`id`) USING BTREE
)
COLLATE='utf8mb3_general_ci'
ENGINE=InnoDB
;

Automatic System Detection

One of the strengths of Quasar Hospital Creator is that it automatically detects the systems your server is running, so you don’t need to manually configure most integrations. When the script starts, it scans your active resources and links itself with the correct dependencies.

For example:

• Frameworks → Detects if you use ESX, QBCore, or QBX, and configures itself accordingly.

• Inventories → Works with popular systems such as qs-inventory or others without requiring edits.

• Wardrobes → Compatible with qs-appearance, qb-clothing, codem-appearance, and many more.

• Vehicle Keys → Supports different car key systems automatically, from qs-vehiclekeys or others.

• Fuel Systems → Recognizes resources like qs-fuelstations, LegacyFuel, ox_fuel, etc.

• Society/Job Management → Adapts to esx_society or qb-management.

• Phones → Works seamlessly with qs-smartphone-pro or others for distress calls.

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.