Documentation
Stream-end actions
Go-live alerts don't have to linger after the stream is over. Each monitor can clean up after itself the moment the streamer goes offline — from simply deleting the alert to swapping it for a “stream ended” card with a link to the VOD.
Configuring it
The monitor form asks two simple questions instead of one long list — together they cover every combination:
- Post when the stream ends: nothing, a “stream ended” card, or a per-game recap. Each option shows a short description and an expandable real example image rendered by the same pipeline that posts to Discord.
- And the original go-live alert: keep it, delete it, or (for the card option) replace it in place with the ended card.
Once configured, use the Test end button on the monitor row to post a sample of your exact configuration to the configured channels — real streamer data and the real latest VOD behind the jump buttons. A test never deletes or replaces anything.
Every combination, spelled out
| Action | When the stream ends… |
|---|---|
| Do nothing | The default. The go-live alert stays in the channel as-is. |
| Delete the go-live message | The original alert is deleted. The channel is left clean. |
| Post a “stream ended” message | A new card is posted: the last stream title and game, how long the stream ran (e.g. “Streamed for 3h 42m”), and a button linking to the VOD (or to the channel if no VOD exists). The original go-live alert stays. |
| Delete + post the ended message | Both of the above: the ended card is posted first, then the original go-live alert is deleted — so the channel always keeps a record of the stream. |
| Replace the go-live message | The original alert is edited in place: its text is cleared, the live card becomes the ended card, and the Watch button becomes the VOD button. No new message, no extra notification — one message tells the whole story. |
| Post a per-game recap | Instead of one combined card, the bot posts one card per game played, in order — each showing the game's cover art, how long it was streamed, its place in the stream (“Game 2 of 4 · started 1h 12m in”), and a button jumping straight to that game's spot in the VOD. Together the sequence covers the full stream. |
| Delete + post a per-game recap | The per-game recap, then the original go-live alert is deleted (recap first, so the channel always keeps a record). |
The game-by-game timeline
On Twitch, Fated Updates tracks category changes during the stream. When the stream ends, every “stream ended” card automatically includes the timeline: each game listed with how long it was played, and jump buttons under the card that open the VOD right where each game began (landing a few seconds before the switch). Single-game streams render the classic card — no clutter.
- On by default, opt-out per monitor — untick “Include the game-by-game timeline” in the monitor form if you prefer the plain card.
- Rapid category flicking is cleaned up automatically: back-to-back stints of the same game merge, and blips under ~3 minutes fold into their neighbor.
- Marathon variety streams cap at 8 games on the buttons (the card shows “+N more”); jump buttons appear only when a VOD exists.
How it works
When a stream-end action is set, Fated Updates subscribes to the streamer's offline event on Twitch. When it fires, the bot looks up the go-live alerts it posted for that session — across every channel the monitor targets — and applies your chosen action to each. Redelivered or flapping offline events can never double-delete or post two ended cards.