What works today
There is no built-in 'post to Discord' toggle in ReplayCore yet; we would rather say that plainly than promise automation that does not exist. What works well today is sharing replays into Discord by hand, or forwarding ReplayCore's signed webhook deliveries into a channel yourself.
Share a replay into any channel: open the replay, create a public share link, and paste it into Discord. Anyone who clicks it can watch that one replay in the browser without signing in, which makes share links ideal for staff evidence channels and community highlights. Links are revocable at any time.
Wiring up automatic notifications
Webhook subscriptions are registered against your tenant via the API (see the Webhooks article), and signed delivery to those endpoints is live. Since ReplayCore does not post to Discord itself, the standard pattern is a small forwarder of your own: it receives ReplayCore events, verifies the signature, and posts rich embeds to a Discord channel webhook.
To create a Discord channel webhook now: open the target channel's settings, go to Integrations, then Webhooks, and create one. Treat the webhook URL as a secret: anyone with the URL can post to your channel. Store it securely and rotate it in Discord if it is exposed.
Keeping channels sane
Whatever you wire up, keep the volume sensible: route high-frequency activity to a dedicated channel so important alerts (flags, staff escalations) are not buried, and restrict who can create share links if your moderation policy requires it.