Before You Begin#
Before installing Theme Park, make sure your server meets the minimum requirements. Two libraries, OneSync and the two asset resources that come in the download are mandatory; everything else is optional and detected on its own.
Requirement | Status | Notes |
|---|---|---|
| Required | Callbacks, the settings panel and notifications. |
| Required | The settings, the dart targets, the hoops lanes, the scores and the day passes live in the database. |
OneSync | Required | Every ride is driven by the server. |
| Required (included) | The park map, the darts booth, the darts and the plush toys. |
| Required (included) | The animated rides: bumper cars and their booth, drop tower, sky drop, flying swings and their lights. |
Framework | Optional | ESX, QBCore or Qbox, auto-detected. Without one, every player gets a wallet of their own. |
Inventory | Optional | Ride tickets, stand items sold in Inventory item mode and item prizes. Without one, the framework's own inventory is used. |
| Optional | Notifications, and a HUD that hides itself while the settings panel or a game is open. Without it, ox_lib notifications are used. |
| Optional | The prompts of the classic interface style and the 3D labels over the vendors. Without it, GTA help texts and a plain 3D text. |
Society account | Optional | Only for the revenue share: esx_addonaccount on ESX; qb-banking, Renewed-Banking or qb-management on QBCore and Qbox. |
Each layer is detected by looking for started resources in this order — the first one found wins:
Layer | Detection order |
|---|---|
Framework | qbx_core → es_extended → qb-core → standalone |
Inventory | ox_inventory → qs-inventory → codem-inventory → core_inventory → tgiann-inventory → qb-inventory → the framework's own |
Notifications | qs-interface → ox_lib → the GTA feed |
Society account | ESX: esx_addonaccount · QBCore and Qbox: qb-banking → Renewed-Banking → qb-management |
Downloading Theme Park#
After purchasing Theme Park, the resource is automatically linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, open Granted Assets, and download Theme Park.
After extracting the download, you should have these three folders:
qs-themepark/ -- the script
├── config/ -- config.lua and webhooks.lua (Discord logs)
├── custom/ -- framework bridges, notifications, society accounts (open)
├── client/custom/ -- the HUD and qs-textui (open)
├── server/custom/ -- inventory items: tickets, stand items, prizes (open)
├── locales/ -- one JSON file per language
├── sql/database.sql -- the tables, the dart targets and the hoops lanes
└── items.md -- the ride ticket item for every inventory
qs_amusement_park/ -- the park map and the darts booth
└── stream/
qs_amusement_park_anim_prop/ -- the animated rides
└── stream/Keep every file of the two asset resources directly inside their
stream/folder, with no subfolders. Their models are registered fromstream/*.ytyp, which does not look into subfolders: a.ytypmoved into one stops loading and its rides turn invisible.
Importing the Database#
Before the first start, import sql/database.sql into your server's database with HeidiSQL, phpMyAdmin or the command line. It does two things: it creates every table and it adds the park's six dart targets and the three lanes of the basketball machine.
mysql -u root -p your_database < qs-themepark/sql/database.sqlImporting it again is safe. Every table is created with CREATE TABLE IF NOT EXISTS and the targets and lanes are added with INSERT IGNORE, so nothing is doubled and nothing you saved is touched.
Table | Holds |
|---|---|
| Every value saved from /themeparkconfig, the prize tiers, the food and souvenir menus and the list of stands. |
| The six dart targets of the booth, shipped in the SQL file. |
| Every finished darts game, for the leaderboard. |
| The three lanes of the basketball machine, shipped in the SQL file. |
| Every hoops round played to the buzzer, for the leaderboard. |
| The day passes sold and when each one expires. |
| Standalone servers only: each player's wallet, by license. |
Installing the Resource#
Move the three folders into your server's resources directory. They can live anywhere inside it, including a category folder:
resources/
└── [themepark]/
├── qs-themepark/
├── qs_amusement_park/
└── qs_amusement_park_anim_prop/Once copied, open your server.cfg and make sure every dependency — and everything it should detect — starts before Theme Park:
ensure ox_lib
ensure oxmysql
# Framework
ensure es_extended
# ensure qb-core
# ensure qbx_core
# Inventory (ride tickets, stand items and item prizes)
ensure ox_inventory
# Optional
# ensure qs-interface
# ensure qs-textui
# Theme Park: the two asset resources first
ensure qs_amusement_park
ensure qs_amusement_park_anim_prop
ensure qs-themepark
# Who can open /themeparkconfig
add_ace group.admin command.themeparkconfig allowThe loading order matters. Detection only sees resources that are already started, so a framework that starts after Theme Park is not found. On purpose, the park does not fall back to standalone money in that case: payments stay blocked and the console says which resource to move up. qs-textui must start before Theme Park too, because the vendor labels pick their style when the script loads.
Permissions#
Only one thing is for staff: the settings panel. It opens for players with the ace command.themeparkconfig, and nobody else. The server console can always use it.
# A whole group
add_ace group.admin command.themeparkconfig allow
# One player only
add_ace identifier.license:YOUR_LICENSE command.themeparkconfig allowA player without it who types the command is told so, and the server console names them and prints the line to add. The ace keeps this name even if you rename the command in Settings → Commands. Everything else in the park is open to every player.
Registering the Ride Ticket Item#
With the default settings the park needs no item at all: food is eaten on the spot, souvenirs are carried in hand, and darts and hoops prizes are money. The one item is the ride ticket, themepark_ticket, and it is only needed if you turn on Ride tickets in /themeparkconfig → Tickets & day pass. Register it in your inventory before you do:
ox_inventory/data/items.lua
['themepark_ticket'] = {
label = 'Ride ticket',
weight = 0,
stack = true,
close = true,
description = 'One ride at the Del Perro Pier theme park',
},qb-core/shared/items.lua
themepark_ticket = { name = 'themepark_ticket', label = 'Ride ticket', weight = 0, type = 'item', image = 'themepark_ticket.png', unique = false, useable = false, shouldClose = true, description = 'One ride at the Del Perro Pier theme park' },qs-inventory/shared/items.lua
['themepark_ticket'] = {
['name'] = 'themepark_ticket',
['label'] = 'Ride ticket',
['weight'] = 0,
['type'] = 'item',
['image'] = 'themepark_ticket.png',
['unique'] = false,
['useable'] = false,
['shouldClose'] = true,
['description'] = 'One ride at the Del Perro Pier theme park'
},ESX with its default inventory: run this on your database.
INSERT IGNORE INTO `items` (`name`, `label`, `weight`, `rare`, `can_remove`) VALUES
('themepark_ticket', 'Ride ticket', 0, 0, 1);codem-inventory, core_inventory and tgiann-inventory need an item named themepark_ticket registered the way each one documents: weight 0, stackable.
items.md, inside the resource, has the same snippets plus optional items (Pier Dog, Boardwalk Burger, Pier Plush…) for when you set a menu row to Inventory item mode or give an item as a darts or hoops prize. Another name works too, as long as it is the same in your inventory and in the Ticket item field of the panel.
Discord Logs#
Optional. Paste a webhook URL (Discord → channel settings → Integrations → Webhooks → Copy Webhook URL) next to each kind of log you want in config/webhooks.lua. The file only runs on the server, so the URLs never reach the players.
Config.Webhooks = {
default = '', -- used by every kind below that is left empty
rides = '', -- who boarded which ride and how they paid
darts = '', -- darts games, scores, prizes and refunds
games = '', -- the basketball machine: rounds, prizes and refunds
economy = '', -- ride payments, tickets, day passes, stand sales, society deposits
admin = '', -- changes made in /themeparkconfig (who, which field, old -> new)
}
Config.LogOptions = {
username = 'Theme Park', -- name of the webhook in Discord
avatar = '', -- picture URL; empty uses the one set in Discord
showIdentifiers = true, -- adds license, Discord and Steam ids to player logs
}Fill only default to send everything to one channel. A kind with no URL, and no default either, is simply not sent. Restart qs-themepark after editing the file. More in Integrations.
Configuring the Resource#
Almost nothing is configured in files. The language, the interface style, the blip, the prices, tickets and the day pass, the revenue, the boarding key, which rides run and how long they wait, the darts and hoops rules and prizes, the menus and every stand are set in game with /themeparkconfig — see Usage. config/config.lua only holds what must be known before the server starts:
-- Extra console output. Leave it false on a live server.
Config.Debug = false
-- Your framework: the first started resource wins. Add a line
-- if you renamed the resource.
local frameworks = {
{ ['qbx_core'] = 'qb' },
{ ['es_extended'] = 'esx' },
{ ['qb-core'] = 'qb' },
}
-- Your inventory. Never run two.
local inventories = {
{ ['ox_inventory'] = 'ox_inventory' },
{ ['qs-inventory'] = 'qs-inventory' },
-- codem-inventory, core_inventory, tgiann-inventory, qb-inventory
}
-- Only if you renamed the asset resources.
Config.AssetResource = 'qs_amusement_park_anim_prop'
Config.DartsAssetResource = 'qs_amusement_park'The open bridge files under custom/, client/custom/ and server/custom/ are covered in Integrations.
Ride positions, speeds, physics, lights, cameras, the dart targets, the hoops lanes and the darts difficulty are fixed and tuned for this map. They are not settings: changing them would put the rides out of line with the buildings streamed around them.
Verifying the Installation#
After completing the installation, restart your server and read the server console. A healthy start looks like this:
[qs-themepark] framework resolved: esx, inventory: ox_inventory
[qs-themepark] server adapter loaded: esx
[qs-themepark] loaded 0 saved settings, 68 fields in total
[qs-themepark] loaded 6 dart targets
[qs-themepark] loaded 3 hoops lane(s)
[UPDATER] Started | local v1.x.x | remote v1.x.x | status LATESTstandalone in the first line means no framework was found running. 0 dart targets or 0 hoops lane(s) means sql/database.sql was not imported. The [UPDATER] line compares your version with the latest release. About ten seconds after the start the script also checks the two asset resources and names the one that is not started. Anything else is explained in Common Errors.
First Steps#
Then join your server and set the park up for your economy:
Open the panel
Type
/themeparkconfig. Under General, the park speaks English by default: pick another of the 41 languages if you like, set the notification title and choose the interface style (Interface panels or Classic GTA help texts).Set your prices
Under Money, set the park ride price, the account it is paid from (cash or bank) and a price for each ride:
-1uses the park price,0makes the ride free. Darts and Hoops have a game price of their own, and Food stands and Souvenirs a menu with a price per item.Turn on tickets and the day pass
Optional. Under Tickets & day pass, switch on Ride tickets (register the item first) and Day pass on sale, and set their prices and the pass length. Both are off on a fresh install; the ticket booth sells them once they are on.
Send the takings to a job
Optional. Under Revenue, switch on Send revenue to a society, name the job and the share. The job needs a society account: see Integrations.
Take a ride
Follow the blip to Del Perro Pier and walk up to the Ferris wheel. Press E on the prompt: the ride panel opens with the price and how you will pay. Board from there and the wheel brakes for a free cabin.
Every field applies at once, for every player, with no restart — except the name of the settings command. The panel marks that field with Needs restart.
Updating Theme Park#
Everything you set in /themeparkconfig — prices, tickets, menus, stands, prize tiers — lives in the database, not in the files, so an update never wipes it.
Keep your edited files
If you changed anything under
config/,custom/,client/custom/,server/custom/orlocales/— your webhook URLs, for example — copy those files aside first.Replace the folders
Stop the server, replace the three folders with the new download and bring your changes back into the new files.
Import the SQL again
Import
sql/database.sqlagain: it adds any table a new version needs and never doubles the dart targets or the hoops lanes.Start and check
Start the server and read the console as in Verifying the Installation.



