Support
Help with orders, downloads, refunds, installations, and account problems. Most issues resolve themselves with the self-service steps below — escalate to a human when they don't.
Most common issues are listed below with their fastest resolution path.
Open your account's Orders page — every purchase is re-downloadable there permanently. If the file itself is corrupt, message the seller from the order page for a fresh build.
Open a dispute from the order page. Message the seller first — most issues resolve within a day. If no response in 48 hours, support takes over. Full details in the Refund Policy.
Use "Forgot password" on the sign-in page. If the reset email doesn't arrive (check spam first), email support@fivem.market from any address — include recent order IDs for identity verification.
Every gig ships with setup documentation. For scripts, check the README and config.lua. For runtime errors, paste the console output when messaging the seller — it's the fastest route to a fix.
Every gig page lists supported frameworks (ESX, QBCore, QBox, standalone). If it's not listed, message the seller before ordering — compatibility is their expertise.
Duplicate charges, wrong tax calculation, invoice requests, payout queries for sellers — email billing@fivem.market with the order ID.
Payment confirmation can take up to 2 minutes to reconcile. Refresh your Orders page — if it's still missing after 5 minutes, the payment likely didn't go through (check with your bank or PayPal). If your account was charged but no order shows, email support@fivem.market with the payment reference and the amount charged.
Download links in your email have an expiration for security, but your Orders page holds the permanent download. If both fail, the underlying file may have been updated by the seller — download again from the Orders page to get the latest version.
Upgrade path: if you want to move from Basic to Standard or Premium, message the seller from the order page. Most sellers will honor an upgrade for the price difference without requiring a full new purchase. If the seller declines, support can still process a refund on the wrong tier under standard refund terms.
Most sellers respond within an hour on business days, with the outer limit being 24 hours. If you've waited more than 48 hours without a reply, that's grounds for escalation — open a dispute from the order page and support steps in. Unresponsive sellers lose their marketplace listing if it becomes a pattern.
Custom commissions have agreed delivery dates shown on the order page. If the seller is behind, first check for a message — they may have flagged a delay. If there's been no communication and the date is missed by more than 48 hours, escalate via the dispute button. Late delivery without communication is a refund-eligible event.
Check the gig page description against what you received — it's the source of truth. If there's a material mismatch, first message the seller with a screenshot or video of the difference; most cases resolve with a free revision. If the seller disputes it, open a marketplace dispute and support reviews both sides.
Open your server console and look for the actual error line — almost every FiveM script issue writes a real error to stdout. Common causes: wrong framework (ESX script on a QBCore server), missing dependency (ox_lib, oxmysql, etc.), or ensure order in server.cfg. Paste the error into a message to the seller and you'll usually have a fix within the hour.
Most scripts ship with a SQL migration file. Make sure you ran it against your framework's database and that oxmysql / mysql-async connection details are correct in server.cfg. Errors like "table doesn't exist" almost always mean the migration wasn't run.
Means the asset streaming didn't load properly. Check that the resource has an fxmanifest.lua (or __resource.lua) with correct files and data_file entries, and that ensure resource-name is in server.cfg. For vehicles/weapons, also confirm the ytd file is in the same folder as the yft.
MLOs stream on approach; if the interior stays empty, the most common cause is a missing ymap or conflicting ytyp between two MLOs. Check for dupe resources with overlapping coordinates. If you're using a teleport script to reach the interior, double-check the teleport coordinates match the MLO's entry point.
Check resmon on the client and profile on the server — both are built into FiveM. If a single resource is eating more than ~1ms consistently, flag it with the seller. Performance regressions are revision-eligible on every gig.
Start with the FiveM server log in server-data/. The line before the crash is almost always the cause — usually a malformed server.cfg entry or a broken script. Isolate: comment out resources in batches until the crash stops, then narrow down to the culprit. Forward the log line to the seller of that resource.
Four channels, four different types of question. Picking the right one up front usually gets you a faster answer.
Use for: anything gig-specific — compatibility questions, install help, runtime errors, revisions, upgrade path, custom variation requests, delivery status on commissions. The seller built the thing; they're the fastest route to a fix. Message button is on every gig page and every order page.
Use for: order-level problems — unresponsive seller, disputes that can't be resolved with the seller, account access issues, payment went through but no order, refund requests that need a human. Response in under 4 hours most days, 7 days a week.
Use for: duplicate charges, wrong tax calculation, invoice/VAT requests, tax-exempt business purchases, chargebacks, seller payout queries. Include the order ID and the specific amounts.
Use for: anything about how the marketplace works in general — pricing structure, refund policy, how commissions work, ESX vs QBCore, what counts as a valid refund. The FAQ covers ~35 common questions across 6 topics.
Complete context up front cuts the resolution cycle from three email rounds to one.
