Vetting warnings¶
Every time a player is added to a roster, BooM BoT checks their history and speaks up if something looks off — before the lineup is locked, while changing your mind is free. Warnings are advisory by design: the bot informs, the leader decides, and nothing is ever blocked outright.
Where warnings appear¶
A vetting message sits below the builder panel and updates with each add. Amending a published roster runs the same checks on the player being added. Batch situations — copying last month's rosters, resuming parked progress, moving a roster between clans — produce a summary of the most notable players rather than one message per person.
The three tiers¶
Info — context, not concern. Rendered small. Example: the bot has little or no history for this account yet.
Caution — worth a look before war day. Examples: below-par star form for the target league, a missed attack on record, short tenure in your clans.
Confirm — serious enough that the add pauses. The player is not added until you press Add anyway or Cancel on the panel. Examples: repeated missed attacks, an active ban flag. Starting a different add first quietly discards the pending one and recaps why.
One special case: when a build is started by copying last month, confirm-tier players are removed from the copy up front and listed as "removed pending confirmation" — re-adding any of them walks through the normal confirm flow. Resumed saved progress is not re-policed this way; those adds already passed through the gates.
What the bot looks at¶
All checks are relative to the target roster's league — a performance that's fine for Crystal can warrant a caution for Champion:
- CWL star form — average stars over recent seasons, against what the target league expects.
- Missed attacks — no-shows in recent CWL seasons, weighted by league.
- League experience — the biggest league the player has actually played versus where you're rostering them.
- Trophy trend and activity — whether the account looks actively played.
- Clan tenure — how long they've been around your family's clans.
- Flags — bans, strikes, and warnings on record, including flags carried by the same person's other accounts. See Flags.
Missing data is treated as unknown, never as a zero — a brand-new account gets a low-confidence info line, not a scarlet letter.
Where the history comes from¶
The bot builds its history from three sources: live tracking of your linked clans (including per-attack CWL capture during war weeks), imported ClashPerk exports for seasons before the bot arrived, and — soon — ClashKing's public API. Profiles are recomputed nightly.