Updating

Update the resource as a complete package so the game UI, admin UI, roster, and match verifier stay in sync.

Before You Update

1. Let active matches finish and announce any planned arcade downtime.
2. Back up your resource, customized configs, translations, and the database tables below.
3. Stop sd-smashdown in the server console.
4. Replace the release files, then merge your settings into the new configs. Compare new options rather than blindly restoring every old file.
5. Start the resource, run brawl_status, and test an eligible match, profile load, and target interaction.

If model or texture files changed, fully close and relaunch FiveM before judging the updated cabinet. A resource restart alone may leave a client using previously loaded model data.

Migrating from sd-brawl

The current resource is named sd-smashdown. Stop the old resource, remove its old startup entry, install the new package under sd-smashdown, and update server.cfg to ensure sd-smashdown.

Keep existing database tables and data. Internal identifiers intentionally retain their previous names:

Identifier	Keep using
Database prefix	sd_brawl_
Custom cabinet model	sd_brawl_arcade
Admin commands	brawladmin, brawl_here, brawl_status, brawl_void
Default edit ACE	sd_brawl.edit

Do not run the old and new resource simultaneously. If you maintain custom integrations, compare them against the new package instead of doing a global brawl search-and-replace.

Database and Backups

Back up all of these tables together, along with your configs:

Tables	Data
sd_brawl_profiles, sd_brawl_ledger	Progression, ownership, balances, and transaction history.
sd_brawl_stats	Arcade statistics and leaderboard data.
sd_brawl_escrow, sd_brawl_payouts	Unsettled wagers and pending payouts.
sd_brawl_tournaments, sd_brawl_ranked	Cups, brackets, and ranked records.
sd_brawl_social, sd_brawl_friends, sd_brawl_blocks	Social profiles, relationships, and blocks.
sd_brawl_matches, sd_brawl_match_players	Match history and participants.
sd_brawl_arcades	Admin-placed banks, overrides, and saved removals.

Do not delete money journals or restore only a player's balance table from an unrelated snapshot. The related records are used together for settlement and recovery. Follow any release-specific migration instructions supplied with an update.

Matching UI and Verifier Builds

The NUI and server verifier carry a content tag beginning with sdc1-. brawl_status compares those tags and the roster. STALE means they do not describe the same game, or a required tag/build is missing.

Deploy the full web/build/ output from the same release. For a source build, run npm run build in web/, which builds the game, admin interface, and verifier together. Restart the resource and verify status again. Do not copy only a new index.html or one JavaScript asset into an older build.

Rollback

Keep the previous resource package and the corresponding pre-update database backup until your checks pass. Stop the resource before a rollback and assess whether the release changed the database schema. Restore a consistent backup only when needed, remembering that restoring old data discards progress made since that backup.