First-week fixes
Launch week found the things our testing did not: reconnects, gift trains, and one very confident timezone bug.
Every bug in this release was reported by someone live on stream, which is a humbling way to find out your gift-sub handler treats a 50-gift train as 50 separate events.
The grouping fix was straightforward once we accepted that "one event per gift" is the wrong shape. Alerts now coalesce on a short window and render a single grouped alert with a count. Per-alert cooldowns landed alongside it, because grouping helps a train and does nothing for a raid of individually chatty viewers.
The Kick reconnect issue was a misread of their socket contract: on reconnect they replay recent history so a client can catch up, and we were treating replayed messages as new. We now track the last processed message id per channel and discard anything at or behind it.
The DST bug deserves a mention because it is the classic version. Schedules were stored as a wall-clock time plus a fixed UTC offset captured at creation time. Cross a DST boundary and the offset is stale. They are stored as a timezone identifier now, and resolved at fire time.
Full change list
Added
- Chat AlertsPer-alert cooldowns, so a raid cannot flood the overlay
Improved
- ModerationBulk actions apply immediately and reconcile in the background
Fixed
- Chat AlertsGift-sub trains fired one alert per sub instead of a single grouped alert
- IntegrationsKick reconnects replayed the last 50 messages after a dropped socket
- Timed MessagesMessages scheduled across a DST boundary fired an hour late
- OnCueAlert widgets kept their old anchor after a canvas resize
