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 MLO Creator, make sure your server meets the minimum requirements. The resource requires OneSync, a working MySQL database, and both ox_lib and oxmysql installed and running.
OneSync is mandatory. The resource will not start without it.
Requirement | Status | Download |
|---|---|---|
OneSync | Required | Enabled in your server settings |
|
Required |
| Required |
MySQL database | Required | — |
Framework | Optional | ESX, QB-Core or QBX — also runs standalone |
Keep ox_lib and oxmysql up to date — outdated versions are the most common cause of a failed start.
After purchasing Quasar MLO 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 MLO Creator in your asset library. Download the latest version and extract the archive.
After extracting the download, you should have the following folder:
[mlocreator]/
├── qs-mlocreator/ the script
├── qs_mlotextures/ textures used by every interior you build
├── [maps]/ the maps you build land here, leave it empty
└── [sql]/ database fileFolder | Description |
|---|---|
| Main resource (required). |
| Texture pack (required). Used by every interior you build. |
| Where your builds land. Ships empty — leave it that way. |
| Database file. |
Do not rename anything inside the folder. The UI and the permissions use the resource name, so qs-mlocreator must keep it.
Do not delete [maps] or qs_mlotextures. [maps] is where your builds live; without qs_mlotextures every interior shows missing textures.
Move the whole [mlocreator] folder into your server's resources directory:
resources/
└── [mlocreator]/Then open your server.cfg and add the following after ox_lib, oxmysql and your framework:
cfg
add_ace resource.qs-mlocreator command.ensure allow
add_ace resource.qs-mlocreator command.start allow
add_ace resource.qs-mlocreator command.stop allow
add_ace resource.qs-mlocreator command.restart allow
add_ace resource.qs-mlocreator command.refresh allow
ensure [mlocreator]The
add_acelines are required, not optional. The script starts and stops the maps you build while the server runs, and it cannot do that without them. Without these lines, every build fails with "could not start resource".
The loading order matters. Always start your framework, oxmysql and ox_lib before ensure [mlocreator].
Open your preferred database manager (such as phpMyAdmin, HeidiSQL, DBeaver, or Navicat), select your server's database, and execute [sql]/database.sql.
It creates two tables. There is nothing else to edit.
Your settings and projects live in the database, which is why they survive every update.
Who can open the studio depends on your framework:
Framework | Allowed players |
|---|---|
ESX | Group |
QB / QBX | Permission |
Standalone | ACE |
To change this rule, edit playerIsAdmin in qs-mlocreator/custom/<framework>/server.lua.
After completing the installation, restart your FiveM server.
If everything has been configured correctly, the console will print:
[INFO] Successfully loaded the framework. esxIt will say qb or standalone depending on your server. If it reports the wrong one, check that your framework starts before [mlocreator].
Finally, join your server with an administrator account and execute:
/mlocreatorIf the studio opens, Quasar MLO Creator has been installed correctly. Press the gear icon at the top to set your language, command and keys — everything is saved in the database.
A few settings — the command and some keys — need
restart qs-mlocreatorto take effect. The panel tells you which ones.
Replace qs-mlocreator and qs_mlotextures with the new version, and keep your [maps] folder.
Your settings and projects are in the database and are never touched. If you edited config/, custom/ or locales/, copy those back afterwards.