SCRAPBOT · FLOODGUARD

Rate suppression. No drama.

When message volume spikes — raids, hype moments, coordinated spam — FloodGuard absorbs the burst without nuking legitimate chat. Calm by default, configurable when you want teeth.

SYSTEM HOW IT WORKS

Burst detection with a sliding window.

FloodGuard tracks message rate per user and across the channel simultaneously. When either threshold trips, it applies suppression — not a blanket ban. The channel keeps moving, the noise gets absorbed.

Thresholds are configurable from the dashboard. The defaults are tuned for a live show environment: tight enough to catch floods, loose enough to let hype breathe.

Configure in dashboard →
BEHAVIOUR CALM DEFAULT

It doesn't shout.

FloodGuard suppresses quietly. No public warnings, no chat noise. The operator sees it in the incident log. Viewers don't notice anything except that the flood stopped.

Scrapbot overview →
TRIGGER RATE THRESHOLD

Per-user and channel-wide.

Two independent triggers: a per-user rate limit catches individual spammers, a channel-wide burst limit catches coordinated floods. Both fire independently and log separately.

SwarmGuard →
OPERATOR INCIDENT LOG

Every suppression is logged.

FloodGuard writes a timestamped entry for every suppression event — who triggered it, what threshold, how long. Review it after the show to tune your settings.

Incident Log →