After publishing

Publishing is rarely the end. People swap clans late, real life happens, and lineups change after the announcement. The dashboard's post-publish tools keep the published state truthful without spamming your channels.

Check-in

Check-in gives leaders an on-demand snapshot of movement: per clan, who has arrived, who is elsewhere, and who could not be verified — the same data behind the reminder-post markers, in one summary. Run it the evening before war starts and you have your chase list.

Refresh

Refresh re-verifies every rostered player against the game API and updates the reminder posts in place. No repost, no pings. Use it when you want the markers current right now rather than on the next polling cycle.

Repost

Repost re-publishes the month's announcement and reminder posts from scratch — for when a channel got purged or the originals were deleted. This is the noisy option (it pings like the original publish), so reach for Refresh first.

Amending

Amend (from the dashboard, or the Amend button on any reminder post) changes a published roster properly:

• Add a player — picked from the same searchable, town-hall-filterable list as the builder, vetting checks included. Players already rostered in another clan that month are excluded automatically.
• Remove a player.

When you confirm, the bot updates the announcement and reminder posts in place, posts a green (additions) / red (removals) audit record to your review channel, and fixes up DMs: added players get a placement DM, and affected players' existing DMs are edited to match reality plus a short note about what changed. Nothing is deleted-and-reposted, and nobody gets re-pinged.

DM audit and resend

Under Tools, DM audit reports delivery per player — who got their placement DM and why any failed (DMs closed being the usual culprit). Once the player fixes their privacy settings, Resend DMs re-delivers just the failures.