Installation

Get Smash Down: Los Santos (sd-smashdown) running, place your first arcade, and verify that matches and rewards work before opening it to players.

Dependencies

Dependency	Required	Notes
Qbox / QBCore or ESX	Yes	The included bridge selects your running framework. On Qbox, keep its QBCore compatibility available.
ox_lib	Yes	Callbacks, commands, notifications, localization, and logging.
oxmysql	Yes	Persistent profiles, matches, competitive data, arcade placement, and money records.
ox_target, qb-target, or qtarget	Yes	Interacting with the arcade cabinets. Use one supported target.

No inventory items need to be registered for the standard arcade setup. The framework and targeting bridges ship with the resource.

1 Add the Resource

Extract the complete release into your resources directory:

resources/[standalone]/sd-smashdown/

Keep the resource folder named sd-smashdown and make sure fxmanifest.lua sits directly inside it. Include stream/ and the complete web/build/ directory.

Updating an older sd-brawl installation?

Stop and remove the old ensure sd-brawl entry before starting sd-smashdown. Run only one copy. The existing sd_brawl_* database names, brawl_* commands, and sd_brawl_arcade model name are intentional — do not rename them. Follow Updating to preserve your data.

2 Prepare the Database

Use your server's existing oxmysql connection. The resource creates its tables on startup; the database user needs permission to create and use them. If you provision tables manually, import the included install.sql into that same database before starting the resource.

Download install.sql

The tables retain the sd_brawl_ prefix. See Updating for the complete backup list. Do not import a reset or drop existing tables when updating.

3 Set the Start Order

Add the resource after its dependencies in server.cfg. These are ordering examples; keep your framework's own prerequisites and existing configuration.

Qbox

ensure oxmysql
ensure ox_lib
ensure qbx_core
ensure ox_target
ensure sd-smashdown

QBCore

ensure oxmysql
ensure ox_lib
ensure qb-core
ensure qb-target
ensure sd-smashdown

ESX

ensure oxmysql
ensure ox_lib
ensure es_extended
ensure ox_target
ensure sd-smashdown

4 Configure Your Arcade

The default example bank has two cabinets at Del Perro Pier, around -1628.00, -1075.00, 13.02. Check their position against your map or MLO before opening the arcade.

You can move or create banks using /brawladmin, or edit configs/shared/cabinets.lua. A normal arcade bank supports 1–4 cabinets, with one human player per cabinet; unused fighter slots can be filled by CPUs.

Before launch, review:

File	Decide
configs/shared/admin.lua	Who can open and edit the admin panel.
configs/server/economy.lua	Admission price, payment account, and wager limits.
configs/shared/rules.lua	Available fighters, stages, and casual rules.
configs/server/progression.lua	Progression settings and the season pass start date.
configs/server/ranked.lua	Ranked eligibility, its separate season start date, and rewards.
configs/server/tournaments.lua	Cup schedule, bracket size, and prizes.

Season dates

Set the season pass and ranked start dates deliberately before release. They are independent clocks; leaving an example date in the past can start your server partway through a season.

5 Start and Verify

In the server console or txAdmin console, run:

ensure sd-smashdown
brawl_status

The status output should report verifier: ok, with the expected fighter and stage counts and matching content tags. Resolve any STALE, missing bundle, or SQL errors before testing rewards.

Then test in-game:

1. Visit your arcade and confirm the custom cabinet and target interaction appear.
2. Open the arcade, choose a fighter, and complete a match against a CPU.
3. Confirm eligible rewards appear and your profile remains after closing and reopening the arcade.
4. With a second player, test joining, readying, starting, and completing an online match.
5. If wagers are enabled, use a small test stake and check the result and payout.
6. As an admin, open /brawladmin and verify that you can inspect and place an arcade.

Use the server console for server errors and the client's F8 console for model, camera, and UI errors. See Troubleshooting if any check fails.

Building from Source

The release's built UI is ready to use. If you are working with a source edition and change the web source, run this from sd-smashdown/web/:

npm ci
npm run build

This builds the game UI, admin UI, and server verifier together. Confirm web/build/index.html, web/build/admin.html, and web/build/server/verify.js exist, then restart the resource and run brawl_status again. Do not mix UI assets from one build with a verifier from another.