Commands & Logging

Admin Commands

Use a leading / in in-game chat. In the server console, enter the command without it.

Command	Where	Purpose
/brawladmin	In-game	Open the arcade admin panel. Name and access are configurable.
/brawl_here	In-game	Copy and print a cabinet vec4 based on your position and heading.
/brawl_status	In-game or server console	Check the match verifier and list arcade lobbies, occupants, and active matches.
/brawl_void <group>	In-game or server console	Void a stuck match at the given arcade group and refund non-forfeited stakes.

brawl_here, brawl_status, and brawl_void use group.admin restrictions. The panel has its own configurable view/edit permissions in Admin Panel.

Example using the default arcade group:

brawl_status
brawl_void delperro_pier

Void interrupts an active match

Use it to recover a stuck match, not to end a normal game without consequences. It follows the normal stake-refund policy; it does not refund already-consumed admission.

The brawl_* command names are retained even though the resource folder is sd-smashdown.

Audit Logging

configs/server/logs.lua enables logging through ox_lib's lib.logger. Configure your server's ox_lib logging backend using its ox:logger configuration; this resource does not have a separate built-in Discord webhook field.

Available event categories include:

Category	Tracks
match_start, match_final, match_void	Match lifecycle and settlement.
forfeit	Players leaving active matches.
charge, payout, pending_payout	Money movements and deferred delivery.
escrow_recovery	Recovery of unsettled wager records.
suspect	Suspicious or conflicting result reports.
admin_command	Administrative actions.

Keep the relevant categories enabled while diagnosing payment or match issues. Share the specific match/group details with support rather than an entire player database.

Integration Points

Use the supplied framework/target bridge and configuration files for supported setup changes. The current resource does not declare a public client/server export API. Internal NUI callbacks and network events are implementation details and should not be called as if they were documented reward or money-grant APIs.