Troubleshooting
Start with brawl_status in the server console and check both startup output and the affected player's F8 console. Reproduce one issue at a time with the default settings where practical.
Resource Does Not Start
Confirm ox_lib, oxmysql, a supported framework, and a supported target are running before sd-smashdown. Keep the complete release folder structure, with fxmanifest.lua directly inside sd-smashdown.
An error about no supported framework means the bridge cannot find QBCore/Qbox compatibility or ESX. A target error means none of ox_target, qb-target, or qtarget is available. Fix the dependency and start order first.
Database Errors or Profiles Not Saving
Check that oxmysql connects to the intended database and its user can create/read/write the resource's tables. The table names still start with sd_brawl_. Use the release's install.sql for manual provisioning; do not drop existing tables to troubleshoot a missing permission.
If only one character appears to have different progress, remember that saves belong to a framework character, not every character on the account.
Cabinet Missing or Using a Fallback Model
Check stream/ contains the supplied cabinet assets and that the manifest still registers sd_brawl_arcade.ytyp. The model name in configs/client/props.lua remains sd_brawl_arcade.
Make sure you are inside SpawnDistance of a configured or saved bank, with valid coordinates. After a model update, fully close and relaunch FiveM to load the new files. Check F8 for streaming errors if the fallback cabinet still appears.
No Target Interaction
Verify the target resource starts before the arcade, stand within TargetDistance, and approach the cabinet itself. If you replaced the target or changed dependency startup order, restart the arcade afterwards. Also check SeatRange and any saved arcade placement: a visual prop and the server's expected seating location must agree.
Black Screen or Blank Menu
The physical idle screen is intentionally black. Use the target interaction to open the arcade. If the game interface itself is blank, check web/build/index.html and its referenced assets are present, inspect F8 for NUI errors, and deploy the complete matching build.
For a blank admin panel, also check web/build/admin.html. For source edits, build all three outputs using the provided npm run build command.
Verifier Is STALE or Rewards Are Missing
Run brawl_status. A healthy build reports verifier: ok and matching content tags. Replace the full game/verifier build together, restart, and check again.
If the verifier is healthy, check progression is enabled, the match reached MinPlaySeconds, CPU/repeated-opponent daily caps have not been reached, and the result was eligible. A match finishing visually is not enough to guarantee a reward. Default leaderboard and match-history settings also exclude solo CPU matches even when progression rewards are allowed.
Fighters or Skins Are Locked
With progression enabled, players must own their selected content. Check the collection and the shared progression catalog. Do not invent a skin index to unlock a model that is not present in the build. To run an unrestricted casual arcade, use the documented progression master switch and review the competitive/social feature dependencies.
Admin Panel Will Not Open or Save
Check the configured command, ACE group membership, and command.brawladmin access. Editing also requires sd_brawl.edit unless you changed EditAce. A view-only user can inspect the panel without editing. Close the game UI before opening the admin panel.
If an arcade cannot be moved or removed, check whether it is occupied. If a Lua coordinate change seems ignored, look for an Edited saved override in the panel and reset that override when appropriate.
Tournament Registration or Ranked Is Unavailable
Check the mode's Enabled switch, progression, and verifier status. Ranked also requires the configured minimum level and, for a premade duo, an eligible two-player party. Cups only accept registrations during their configured window and need enough entrants to start. Check the server clock and configured season/schedule dates.
Friends, Parties, or Quick Play Are Missing
Social requires progression; parties require social. Check all relevant Enabled, QuickPlay.Enabled, and Fill.Enabled settings, then inspect server errors. A disabled underlying feature cannot be restored just by changing the visible menu.
Match Freezes or Players Are Dropped
Check the affected clients' frame rate and connection before changing networking limits. Input stalls, leaving the cabinet, or a disconnect can drop a player. Review StallSeconds, StallGraceSeconds, SeatRange, and the server seat tolerance if the logs point to those checks.
Use brawl_status to identify the group. As an admin, recover a stuck match with brawl_void <group> if necessary. This interrupts the match and follows the normal refund policy.
Money or Payout Looks Wrong
Admission is separate from the wager, and the house cut reduces the winning pot. Leaving a running match forfeits the stake; voiding refunds non-forfeited stakes, not consumed admission. Check the configured account and the audit events for charge, payout, pending payout, and escrow recovery before making a manual adjustment.
Getting Support
Include the resource version, framework and target, exact reproduction steps, relevant server/F8 errors, the brawl_status output, and the affected arcade group or match details. Mention whether the problem started after an update or config change. Never include database credentials, license keys, or a full player database in a public ticket.