Documentation
Follow the installation steps to get the script running quickly and correctly on your server, with everything you need to get started.
Before installing Quasar Motels Creator, make sure your server meets the minimum requirements. The resource requires FXServer build 5181+, OneSync (legacy or infinity), a working MySQL database, and ox_lib, oxmysql and bob74_ipl installed and running.
If you're using a modern ESX, QBCore, or Qbox server, most of these dependencies are usually already installed.
Requirement | Status | Download |
|---|---|---|
FXServer 5181+ | Required |
OneSync | Required | Enabled in your server settings |
| Required |
| Required |
| Required |
| Required | Included in the download |
| Optional |
| Optional |
| Optional |
| Optional | Only for the raid minigame |
Quasar Motels Creator automatically detects your framework, inventory (qs-inventory, ox_inventory, qb-inventory, origen_inventory, codem-inventory or standalone), clothing system (10 supported) and 3D sound provider (xsound, mx-surround, qs-3dsound).
bob74_ipl is required for IPL motels, and K4MB1-StarterShells provides the room shells.
After purchasing Quasar Motels Creator, the resource is automatically linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, then open Granted Assets and locate Motels Creator in your asset library. Download the latest version and extract the archive.
After extracting the download, you should have the following folders:
qs-motels-creator
K4MB1-StarterShellsFolder | Description |
|---|---|
| Main resource (required). |
| Room shells (required). Provides the interiors used by shell-type motels. |
Never rename the resource folders. They must remain qs-motels-creator and K4MB1-StarterShells, otherwise the resource and its user interface will fail to load correctly.
Move both folders into your server's resources directory. Although the resources can be placed anywhere inside the folder, keeping them organized inside their own directory is recommended.
A typical installation looks like this:
resources/
└── [motels]/
├── K4MB1-StarterShells/
└── qs-motels-creator/Once the resources have been copied, open your server.cfg and ensure every required dependency starts before Quasar Motels Creator.
ensure oxmysql
ensure ox_lib
# Framework
ensure es_extended
# ensure qb-core
# ensure qbx_core
ensure bob74_ipl
ensure K4MB1-StarterShells
ensure qs-motels-creatorThe loading order matters. Always start your framework, oxmysql, ox_lib, bob74_ipl and K4MB1-StarterShells before starting qs-motels-creator.
Quasar Motels Creator stores motels, rentals, employees, shared keys, stashes, bills, transactions, requests and notifications inside your server's database, allowing them to persist across server restarts.
Open your preferred database manager (such as phpMyAdmin, HeidiSQL, DBeaver, or Navicat), select your server's database, and execute one of the SQL files included in the [sql] folder — the one matching your framework:
Framework | File to import |
|---|---|
ESX |
|
QBCore / Qbox |
|
Import only one of them. Both scripts use CREATE TABLE IF NOT EXISTS and ADD COLUMN IF NOT EXISTS, so running them multiple times is completely safe and will never overwrite or delete your existing data — you can re-run the same file when updating the resource.
The script creates the qs_motel_* tables, adds the current_motel_room column to users / players, and inserts one example motel (Richman Motel, IPL type) so you have something to test with right away.
ESX only: the script also inserts a
propertyrow into thedatastoretable. If your server does not have adatastoretable, delete that line before importing.
This step is only needed when Config.MetaKeys = true (the default). The item name is defined by Config.MetaItem (motelkey), and the icon qs-motels-creator/motelkey.png must be copied into your inventory's image folder.
ox_inventory — ox_inventory/data/items.lua:
['motelkey'] = {
label = 'Motel Key',
weight = 10,
stack = false,
close = true,
description = 'A key to a motel room',
client = { export = 'qs-motels-creator.motels:UseKey' }
},qs-inventory / qb-inventory — shared/items.lua:
motelkey = {
name = 'motelkey', label = 'Motel Key', weight = 10,
type = 'item', image = 'motelkey.png',
unique = true, useable = true, shouldClose = true,
description = 'A key to a motel room'
},ESX — items table:
INSERT INTO `items` (`name`, `label`, `weight`, `rare`, `can_remove`)
VALUES ('motelkey', 'Motel Key', 1, 0, 1);With ox_inventory the key is consumed through an export; with every other inventory it is consumed through the net event
motels:UseKey. Both are registered automatically — you only need to declare the item.
Physical keys require a metadata-capable inventory. If yours doesn't support metadata, set Config.MetaKeys = false.
This step is optional. Config.raid.item defaults to police_stormram.
If that item does not exist on your server, either register it in your inventory, or remove the requirement entirely:
Config.raid.item = falseAfter completing the installation, restart your FiveM server.
If everything has been configured correctly, the following message will be printed once on the server and once on the client:
[INFO] Successfully loaded the framework. esxIf it reports none instead of your framework, your core is not started before qs-motels-creator or has been renamed. Check the loading order in your server.cfg, and add your resource name to the frameworks table in config/main.lua if needed.
Finally, join your server with an administrator account and execute the following command:
/motelcreatorIf the Motel Creator interface opens successfully, Quasar Motels Creator has been installed correctly and your server is ready to create its first motel.