RBF-006: The Scrubber

Class: Custodial

Deployment Procedures

  • Insert the ModuleScript “ScrubberCore” into ReplicatedStorage.
  • Call require(ReplicatedStorage.ScrubberCore).Init() on server startup.
  • Whitelist target IDs in ScrubberConfig.TargetList; unknown objects are purged.
  • Lock the ModuleScript (Locked = true) to prevent client-side replication.
  • Monitor sweep activity in ServerScriptService → ScrubberLog.

Description

The Scrubber is a lightweight custodial module designed to detect and neutralize rogue objects and scripts within live games. Operating silently, it runs continuous sweeps over configured areas, patching broken scripts and deleting any non-whitelisted parts within 0.5 seconds of detection.

It hooks into ChildAdded events on workspace and cross-references new instances against its target list. Unauthorized assets are immediately destroyed, and each action is logged under ScrubberLog:CleanSweep, creating an auditable trail of every cleanup.

First Encounter

Discovered on 2016-06-21 in “Survival The Killers” (Place ID 91234567). A mass-deletion test left stray glitch-bricks behind—within milliseconds the Scrubber module activated, purged 128 anomalies, and logged CleanSweep: 128 items before players noticed.

Fate

Rolled out to over 50 Foundation-controlled games by late 2017. Since deployment, the Scrubber has neutralized more than 2,400 non-compliant assets with zero downtime or perceptible impact on players.

Addendum

  • Log 009A – CleanSweep Test
    DemoArena (2016-07-05): Module removed 256 stale parts in under 2 seconds.
  • Operator Note
    Performance degrades if more than 500 targets are listed. Recommend batch processing.
  • Research Insight
    Latest Scrubber builds include predictive cleanup, identifying anomalies before spawn.