Configure a campaign destination
Open Campaign → Status notifications as the campaign GM. Choose Discord channel or Email, and enable notifications. New configurations require an explicit delivery choice. Existing saved connections retain their route. A recent sign-in is required to save settings.
When Discord is selected, follow the on-page setup: open Server Settings → Integrations → Webhooks, create a Hot Spots webhook, select the intended text channel and copy its URL. Enter the server/channel labels and paste the URL into the secret field. Save, then Send connection test and check the selected channel. You need permission to manage webhooks. An illustrated Discord guide opens in a separate tab. PHP cURL and HTTPS access to discord.com are required; forum/media channels and threads are unsupported.
When Email is selected, updates go to the GM and participating players through the site mail configuration. Saving Email removes the saved Discord webhook. Save, then test and check inboxes. Blank secret keeps an existing Discord connection; saved secrets are never returned to the form or audit details. Settings and tests update in place; tests use saved settings and send a real message.
Milestones and fallback
Enabled campaigns report voting opened, contract selected and accepted, completion settlement, mission scheduling, roster submission/locking, mission preparation readiness, results and aftermath finalization. Ordinary field saves and private planning edits do not send announcements. Messages contain campaign name, public contract/mission title, campaign date, milestone and a sign-in link. Private OpFor, briefings, ballot choices, financial details and personal email addresses are excluded from Discord posts. Mentions are disabled. Merchant inventory availability, opening between-contract purchasing and publishing salvage priorities also send task announcements.
When Email is selected, delivery uses the site’s configured email sender/SMTP. Defaults are GM and participating players: mission and contract events use their participating companies when known, otherwise campaign members. Disabled, blocked, unverified and placeholder accounts are excluded; the GM is included. Delivery starts only after the saved action commits. A delivery failure does not roll back contracts, results or accounting.
Discord errors remain in delivery history; they do not automatically trigger another email copy. New configurations affect future announcements, not historical backfill. Notifications are disabled until the GM enables them.
Each new milestone includes a Next step link to the saved ballot, selected contract, mission roster, merchant inventory, salvage priorities or results. The link requires sign-in and rechecks campaign and company access. Players open their own participating company; users with multiple companies choose one. GMs open the corresponding management view. Links do not grant access or perform purchases, votes or submissions automatically. Signed-out visitors are automatically sent to sign-in and returned to the exact original task after successful login in the same browser session. The pending return expires after 30 minutes. Campaign and company permissions are checked again after login. Old notifications are not rewritten. The administrator must configure the public site URL before enabling linked notifications.
Completed mission roster, results and finalized report notifications open a read-only Mission results summary. Historical damage remains the saved end-of-mission evidence; current company condition comes from the equipment record. Use Company actions for outstanding tasks. Old notifications resolve against current saved completion state and do not reopen or replay completed work.
Review delivery
Open Delivery history from Status notifications. Sent means Discord confirmed a post, or the email server accepted the mail; inbox arrival is not guaranteed. Failed events can be retried after correcting configuration. Successful email recipients are skipped on retry.
Uncertain or interrupted sends are not automatically replayed. Wait five minutes, check the channel/provider, and confirm possible duplicate delivery before retrying. A queued Discord event will not be redirected to a changed webhook. Its destination mismatch stays visible for review. Keep the application and its private database protected, and rotate a Discord webhook if it is exposed.