Twitch Events Connect to CRESA's Shared Engine

CRESA's event architecture takes a significant step forward as the different pieces of its Twitch integration begin coming together. A central event coordinator is introduced to provide a common route for incoming activity, while Twitch EventSub WebSocket support begins bringing live Twitch events directly into CRESA.

Event normalisation is strengthened alongside this work, allowing different Twitch event types to be translated into a consistent format before being passed deeper into the suite. The alert queue also continues evolving, with additional support for upcoming events and channel point redemption activity.

One particularly important change is made to Simulation Lab: simulated alerts begin entering the same shared engine used by live events rather than relying on a completely separate presentation path. That establishes an architectural principle that will remain important throughout CRESA's development testing should exercise the real production pathway wherever it can safely do so.

Centralised Twitch authentication is also introduced as the integration grows, reducing the need for individual features to manage Twitch access independently. CRESA now has the beginnings of an end-to-end event pipeline: Twitch receives the event, CRESA normalises it, the coordinator routes it, the shared engine manages it, and the presentation system can respond.

There is still plenty of work ahead on the individual alert experiences, but the machinery underneath them is becoming substantially more capable.