Event details

A chat event is anything happening in the channel that isn't a plain message — a subscription, a raid, a moderator action, a channel point redemption, a pinned announcement. Stream Chat Summary captures these from both Twitch and Kick during live monitoring, surfaces them in a dedicated Events tab, and preserves them through export and re-import.

This page lists every kind of event the app recognises and where each one comes from.

Where events show up

The Events tab appears on the right side of the main window whenever the loaded log contains at least one event. It's hidden if there are none — a VOD import or a quiet live session may have no events at all.

Each row shows the time, an emoji indicating the event type, the user who triggered it, and a human-readable description.

Where events come from

Events take three different paths into the app depending on the source:

The two live capture paths (Twitch and Kick) are the only ways to record events in real time. VOD and CSV imports never contain events — the source data doesn't carry them. Saved log files (Chatterino-format .log or .txt) can contain events if they were originally exported from this app or any tool that uses the same format.

Twitch events

Twitch live monitoring captures the full range of subscription, raid, moderation, and reward events:

Twitch occasionally adds new subscription or reward variants. If live monitoring sees one the app doesn't yet recognise, it's recorded for diagnostic purposes but not shown in the Events tab — support catches up in subsequent app updates.

Kick events

Kick supports a smaller set of event types. The app maps each one to the same category as its Twitch equivalent, so behaviour and exports stay consistent across platforms:

Events in saved log files

When you export to a .log file, events are written with their type preserved so they can be re-imported without losing any detail:

[14:32:24] [raid] Raid from another_channel with 47 viewers
[14:35:12] [sub] new_user subscribed at Tier 1
[14:41:05] [timeout] viewer123 timed out for 600 seconds

The bracketed tag identifies the event type. On re-import, the app recognises these tags and restores the original event category. Lines without a known tag are imported as generic events.

You can also hand-write a .log file using [time] [type] body lines and the importer will pick up the typed events — useful for testing or annotating an existing log after the fact.

CSV imports never have events

The CSV format (TC Downloader and similar) only carries messages — there's no column for event data. CSV imports produce a chat log with zero events, and the Events tab stays hidden.

Per-source summary

Live monitor sessions automatically save to disk in .log format with tagged events, so a captured live session can be re-analysed later and the Events tab will populate exactly as it did during capture.