CRESASTREAM AUTOMATION
All updates →
ANNOUNCEMENT
Private Testing is planned VERY SOON

Selected candidates will soon be able to give the suite a real world test run and provide their feedback and opinions!

← Back to all updates

DEVELOPMENT UPDATE

CRESA Begins Experimenting With Raid Takeovers

UPDATEPUBLISHED

The first standalone Raid visual-effects prototype explores a much more disruptive approach to incoming raids, beginning an experiment that would eventually grow far beyond a normal alert.

Most stream alerts are designed to appear on top of the broadcast. A raid presented a slightly different opportunity.

What if an incoming raid didn't simply appear over CRESA? What if it disrupted the broadcast itself?

On 22 August, the first standalone Raid VFX destruction prototype began exploring that idea.

Starting With Destruction

This wasn't yet the full Raid system. There was no mature takeover architecture, synchronization model or carefully coordinated alert lifecycle behind it. At this stage, the focus was much more experimental. The prototype explored how a Raid presentation could feel significantly more destructive and intrusive than a conventional notification.

Instead of treating the event as another box appearing somewhere on screen, the visual concept could interfere with the presentation around it. That immediately gave Raid a very different identity from Follow and the other alert work that had come before it.

Making Raid Feel Bigger

A raid is naturally one of the larger events that can happen during a Twitch stream. Another creator isn't simply triggering a notification. They're arriving with their community. The presentation needed to reflect that difference.

The early VFX work began experimenting with the idea that Raid should temporarily command much more of the viewer's attention. Not necessarily louder for the sake of being louder, but unmistakably different. Something had arrived.

A Standalone Prototype First

Keeping the experiment standalone was useful. It allowed the visual concept to be explored without immediately forcing it into the existing alert architecture. That meant the destruction effect could be developed around what looked and felt right before answering the much harder questions around event ownership, timing and synchronization.

Those questions would become considerably more important later. For now, Raid was still an experiment.

The Beginning Of A Much Bigger Problem

This first prototype couldn't know just how complicated Raid would eventually become. Later development would push the idea much further, introducing takeover behaviour and increasingly difficult questions about who controlled the broadcast while a Raid presentation was active.

But none of that existed yet. On 22 August, the idea was much simpler:

A raid shouldn't feel like just another alert.

And CRESA had started figuring out what it could feel like instead.

Back to all updates