What goes wrong most often, what it actually means, and what to do about it. Most of these are configuration, not faults. Before opening a ticket, set Config.Debug = true, restart, and repeat the problem: the console then prints what was delivered, which garage each car went to and which item names were not found.
Installation and Access#
"Database connection failed — oxmysql did not respond after 30 seconds"
oxmysql is not started, starts after Starter Pack, or cannot log in. Until it connects, the creator shows Database unavailable and players are told the starter pack is temporarily offline. Check ensure oxmysql is near the top of server.cfg and that your mysql_connection_string is right, then restart the resource. Avoid XAMPP and similar local stacks — they drop connections.
"Could not auto-create the qs-starterpack tables"
Your database user is not allowed to create tables. Import [sql]/install.sql by hand in HeidiSQL or your MySQL client, then restart the resource.
The resource stops on start with "Config.Cooldown is set to …"
A typo in config/main.lua. Config.Cooldown must be 'lifetime', 'weekly' or 'monthly', and Config.CooldownScope 'character' or 'account'. The script refuses to start rather than let players claim more often than you meant.
"You do not have permission to use this" on /starteradmin
None of the admin routes matched. Nine times out of ten the ace was added to server.cfg but the resource was not restarted, or the identifier belongs to a different account from the one in game. Add the player's licence to Config.Admin.Identifiers to rule everything else out. The server console names each refused player. See Installation.
The boot banner says standalone or default for something I have
That resource starts after Starter Pack, and detection only sees what is already running. Move its ensure above ensure qs-starterpack.
Every pack and every claim disappeared
Your sv_licenseKey (or sv_hostname, if you have no key) changed. Starter Pack keeps each server's data under that key, so the server now reads a new, empty configuration. The old rows are untouched in both tables — put the old key back, or copy the server_key over to the new one.
The interface is a blank page, or does not open
The interface ships ready in html/build/. If that folder is missing or half-copied the window is blank — re-copy the whole resource from the download. Also check the F8 console for errors from the resource while opening.
Claiming#
"You've already claimed your starter pack"
Correct behaviour with a lifetime cooldown. An admin can give them another go with /starterclear <id>. With a weekly or monthly cooldown the picker opens and shows a countdown instead.
"Inventory full — make space and try again"
At least one item in the pack does not fit. Nothing was given and no cooldown started, so the player only needs to free some space. If it happens to everyone, the pack is simply too heavy for your inventory's limits — lower the quantities.
"N item(s) couldn't be delivered"
The claim went through, but your inventory refused those items — almost always because an item with that name does not exist on your server. This is common with presets.sql, whose items may not match yours. Replace the row in the creator with an item from the search, and hand the missing ones over by hand: the claim cannot be repeated, by design, so nobody receives a pack twice.
Money does not arrive
The account in Config.Money does not exist on your framework — crypto on ESX, for instance — and there is no itemId to fall back on. Point the tag at an account you have. On standalone, money cannot be paid at all.
The ID card has no name on it
Either the item is not listed in Config.IdentityItems, or your inventory does not keep item metadata (classic ESX, tgiann-inventory). Add the item name to the list; on inventories without metadata it can only be a plain item.
Players claim again with every new character
That is what Config.CooldownScope = 'character' means. Set it to 'account' for one claim per Rockstar licence. Claims already made under the old scope are not converted.
"Already processing your request" or "Slow down"
The player claimed twice in a row before the first claim finished. The second attempt is refused on purpose; the first one completes normally.
Using the starter-pack item does nothing
On ox_inventory, the item needs export = 'qs-starterpack.UseItem' in its client table — the red console banner prints the exact block. On other inventories, look for Could not register the starter pack item in the console: the item is missing from your inventory's item list. Remember the item is not removed until a claim succeeds.
Vehicles#
The car was given but is in no garage
The garage id in Config.Vehicles.DefaultGarage does not exist in your garage script. The car is saved but parked nowhere. Use a real id — pillboxgarage in qb-garages, a Config.Garages key such as LegionSquare in esx_garage — and with Config.Debug on, the console prints the garage of every grant. If the garage lists it but will not let it out, set DefaultState = 1.
A helicopter or boat ended up in the car garage
On QBCore and Qbox, set real air and sea garage ids — if they equal the car garage, that is where aircraft and boats go. An addon model missing from the shared vehicle list is treated as a car. ESX has no vehicle classes, so every starter vehicle uses the car garage there.
"N vehicle(s) couldn't be granted"
The vehicle row could not be written: the server runs standalone, the player's character was not loaded yet, or the database refused the insert. Config.Debug prints the exact reason.
The vehicle search is empty
On ESX, the search reads the vehicles table of esx_vehicleshop; without it there is nothing to list. Type the exact spawn code and choose Add vehicle.
An addon car shows a placeholder picture
Pictures come from Config.Vehicles.ImageUrl, which only has the base-game cars. Add the model to Config.Vehicles.ImageOverrides with an image URL of your own.
The Creator and World Peds#
"Couldn't save — image is too large"
A save has to fit in one network message. Use an image URL for backgrounds and the logo rather than an embedded image, and keep text fields short. Your last good save is still in place.
"Couldn't save — the configuration was rejected"
Usually the same item twice in one pack with the same tag, which would pay it out twice. Remove the duplicate, or change one row's tag. The server also refuses over-long names and descriptions.
"Saving too fast"
More than thirty saves in ten seconds. Normal editing never gets there — wait a moment and the panel saves again.
The cropper says the host does not allow cross-origin reads
The image's server forbids other sites from reading it. The picture still shows on the card; only cropping needs it. Re-host it on Discord CDN, GitHub raw, Fivemanage or a server that sends Access-Control-Allow-Origin: *.
The item search is empty, or items show without icons
The inventory had not finished loading when the creator opened, or it starts after Starter Pack. Close and reopen /starteradmin; if it persists, fix the load order. A missing icon means the image file is not in your inventory's image folder under the item's name.
The world peds do not appear
Config.Player.PedOpen is false, which stops peds spawning at all; or the model name is wrong and failed to load. Check the spelling of the model, and that the ped has been placed.
There is no prompt on the ped
The target or text UI started after Starter Pack, or Config.Interaction points at one you do not run. Fix the load order, or set 'textui' to use the built-in [E] prompt. See Integrations.
Error Codes#
Claims and saves return a short code, which the interface shows in the player's language. The ones you are most likely to meet:
Code | Means |
|---|---|
| Already claimed in this period — or for good, with a lifetime cooldown. |
| An item does not fit. Nothing was given. |
| The pack was deleted or hidden while the picker was open. |
| Too many attempts at once; the first one is still being handled. |
| The player's identifier could not be read. |
| The database is unreachable, or refused the write. |
| The server did not answer within ten seconds. Usually a slow database. |
| A save from somebody who is not an admin. |
| The save is too big — usually an embedded image. Use a URL. |
| The configuration broke a rule — a duplicate item or pack, a featured pack that no longer exists, a field too long. |
Still stuck? Open a ticket and include your boot banner (the
✦ Quasar Starter Packline), the console output withConfig.Debug = true, and your framework and inventory with their versions. A screenshot of the F8 console helps for anything about the interface.



