K
GitHub
Phase 15

Stats & Debug

Per-player stat tracking, GUI stats viewer, PlaceholderAPI stat placeholders, and live debug tracing for diagnosing crate behavior.

Player Stats

BloodlineCrates tracks per-player opening statistics across all crates. Stats include total opens, per-crate open counts, rarest reward won, and last reward won.

View your own stats

# Chat output
/bc stats

# GUI panel
/bc stats gui

View another player's stats

# Requires admin permission
/bc stats <player>
/bc stats gui <player>
Stats storage
Player open counts live under the shared stats-backed player data section — keeping limits, broadcasts, pity, and stats all aligned in one consistent data layer. Server stats writes are coalesced with the leaderboard save cycle rather than flushed on every open.

PlaceholderAPI Stat Placeholders

All stat placeholders use the bloodcrates_stats_ prefix. Replace <crateId> with the actual crate ID.

PlaceholderDescription
%bloodcrates_stats_total%Total opens across all crates for this player
%bloodcrates_stats_opens_<crateId>%Opens for a specific crate
%bloodcrates_stats_rarest_<crateId>%Rarest reward won from that crate
%bloodcrates_stats_rarest_chance_<crateId>%Drop chance of that reward
%bloodcrates_stats_last_<crateId>%Last reward won from that crate
Additional placeholders
Placeholders for keys, cooldowns, timed keys, and leaderboards from earlier phases remain active and are not affected by the Phase 15 stats additions.

Debug Tracing

Debug tracing provides real-time output of every meaningful event in the crate opening pipeline — useful for diagnosing reward selection issues, key consumption errors, cooldown state mismatches, and pity counter behavior.

Enable debug

# Trace all players
/bc debug on

# Trace a specific player only
/bc debug on <player>

Disable debug

/bc debug off

Check debug state

/bc debug status
Debug output volume
Tracing all players on a busy server can produce significant console output. Prefer targeting a specific player when investigating a report.

What Debug Output Covers

When debug is active, the console will trace:

  • Key validation — does the player have a valid key?
  • Key consumption — was the key consumed successfully?
  • Cooldown check — is the player within the cooldown window?
  • Limit check — has the player hit the open limit?
  • Pity counter — current pity count and threshold check
  • Reward selection — which reward was selected and its weighted chance
  • Broadcast trigger — whether a broadcast was fired for this reward
  • Stats write — confirmation that stats were updated
← CommandsNext: Changelog →