What goes wrong most often, what it actually means, and what to do about it. Theme Park explains itself in the server console: every problem it detects is printed on a line starting with [qs-themepark], naming the resource, table or setting involved and the fix. Read those lines first.
Installation and Access#
A ride or the darts booth is invisible
One of the asset resources is not running. Ten seconds after the start the console says which:
[qs-themepark] resource qs_amusement_park_anim_prop is not started (state: missing), so the rides it streams are invisible.Make sure both
qs_amusement_parkandqs_amusement_park_anim_propare in your resources andensured beforeqs-themepark.Every file must sit directly in their
stream/folder. A.ytypmoved into a subfolder is not loaded.Renamed a folder? Put the new name in
Config.AssetResource(rides) orConfig.DartsAssetResource(darts booth) inconfig/config.lua.
"You do not have permission to change the theme park settings"
The player lacks the command.themeparkconfig ace. The console names them and prints the line to add:
add_ace group.admin command.themeparkconfig allowBeing an ESX or QBCore admin is not enough for the panel: it only looks at that ace.
Nobody can pay for a ride, even with money
The framework could not be reached, so payments are blocked on purpose. The console says which case it is:
es_extended is running but qs-themepark stayed on "standalone" — the framework starts after Theme Park. Move its
ensureaboveqs-themeparkand restart.could not get the es_extended object within 60 s — the framework did not answer; check that it starts without errors.
an ESX player operation failed — ESX keeps accounts in an inventory (such as qs-inventory) that is not started.
Meanwhile you can set the ride and darts prices to 0 in the panel to keep the park open.
The settings panel does not open
The player sees The settings panel could not be opened: the panel's page did not load within five seconds. It ships ready in the web/build/ folder of qs-themepark; if that folder is missing, the resource was copied incompletely. Download it again from the CFX Portal, replace the whole folder and restart.
No ride moves after the server starts
The rides wait for the saved settings, and the database has not answered:
[qs-themepark] the saved settings could not be read from the database within 60 s ...Check that oxmysql is started and that mysql_connection_string in server.cfg is right. After 60 seconds the park starts with the settings saved before the last stop and reads the database as soon as it answers. Until it does, the panel cannot save.
Everything is in Spanish
That is the shipped language. Open /themeparkconfig → General and pick yours; also change the notification title there and the blip name under Map blip.
Rides#
I switched a ride on or off and nothing changed
Correct behaviour. Whether a ride or the darts run is read when the resource starts — the panel marks those fields Needs restart. Restart qs-themepark (or the server) after saving. Until then every player keeps riding as the server started.
"The train already left" or "This round already started"
Boarding closes a few seconds before departure — 8 s on the roller coaster, 6 s on the towers, 2 s on the bumper cars — and stays closed while the ride runs. Wait for the next countdown, or give the ride a longer wait in the panel.
"You are too far away"
The server checks the player's real position when the key is pressed. Stand at the boarding point where the help text appears — on the roller coaster, at the seat you want — and try again.
I cannot get off the Ferris wheel or the coaster
Correct behaviour. Only the bumper cars can be left early, with F. Every other ride lets its riders off when it ends: the wheel after its laps, the others back at the station.
Darts#
Nobody ever wins a prize
There is no valid score tier, or the lowest one is out of reach:
[qs-themepark] the darts have no valid reward tier: the targets work, but nobody can win.Add tiers in Settings → Darts → Score rewards, or press Restore default rewards. If you lowered Darts per game, lower the tiers with it.
"The prize could not be delivered"
Usually an item prize whose name does not exist in your inventory. The console names the item and the tier:
[qs-themepark] Config.Darts.Rewards[2].prizes[1] gives the item "teddy", which does not exist in the inventoryFix the item name in the tier, or add the item to your inventory. When the player's inventory is simply full, they get a money prize of the same tier if there is one; otherwise the game is refunded.
"You won a prize recently, try again in … s"
The prize cooldown (120 s by default) is running for that player. Shorten it, or set it to 0, in Settings → Darts.
"You are not allowed to create dart targets"
The player needs the qs-themepark.build ace or the admin / superadmin group — see Permissions.
"Could not write to the database" in the target creator
The target could not be saved to qs_themepark_darts. Check oxmysql and the console line above it. If the database accepts it later, the target is placed after all and the console says so.
I edited config/darts.lua and nothing changed
Correct behaviour. That file is only read once, on the first start, to copy the starter targets into the database. Add, move and delete targets in game with /themepark_dianas; the console reminds you on every start while the file differs from what was copied.
Panel Messages#
Message | Means |
|---|---|
The settings could not be saved | The database refused the change or did not answer in 15 s. Nothing was changed; the console says why. |
You do not have permission to change the settings | The ace was taken away while the panel was open. |
That command name is already used by the other command | Give each command a name of its own. |
Restart the resource to apply | A saved field takes effect on the next restart. |
Fix the fields marked in red before saving | A prize tier breaks a rule: a repeated score, a tier without prizes, a bad item name, min above max. |
Still stuck? Set
Config.Debug = trueinconfig/config.luafor extra console output, restart, and open a ticket with every[qs-themepark]line from the server console and the F8 console.



