Admin

Admin Flow

The recommended end-to-end workflow for building out a production crate setup — from config to live on your server.

The Full Workflow

This is the cleanest path from zero to a fully working crate live on your server. Follow these steps in order for every new crate you build.

Either copy a config file or use the in-game editor. Decide upfront:

/bc editor

Before placing the crate in the world, preview the opening flow and give yourself test keys:

# Preview crate (no key consumed)
/bc preview <crate_id>

# Give yourself 10 test keys
/bc givekey <crate_id> <yourname> 10

Preview first, always

The preview command shows the opening GUI without consuming a key. Use it to verify reward icons, names, and layout before handing keys to players.

Stand at the desired location and set the crate:

/bc setcrate <crate_id>

Open the crate repeatedly (with test keys) and verify each part of the system works as expected:

Key consumption — key is consumed on open

Reward selection — correct rewards appear at expected rates

Cooldown — player cannot reopen within the window

Pity — guarantee fires after the configured threshold

Broadcasts — rare wins show server-wide messages

Stats — /bc stats reflects the opens correctly

If you notice unexpected behavior — wrong rewards, keys not consuming, cooldown not applying — enable debug tracing for yourself:

# Trace your own session
/bc debug on <yourname>

# After testing, turn it off
/bc debug off

Debug output will trace key validation, reward selection, pity state, cooldown checks, and broadcast triggers in real time.

Debug for specific players

You can target debug tracing at a specific player — useful when investigating a reported issue without flooding every admin's console.