RBF-001: The Recreator
Class: Monitored
Containment Procedures
- House the entity inside a 200×200 stud baseplate with all parts anchored.
- Deploy a server‐side brick‐destroyer script to auto‐delete any unexpected spawns.
- Restrict API calls to “Inspect” and “Log” only; deny all build/modify functions.
- Reset the baseplate daily at 02:00 UTC via scheduled
ClearWorkspace().
- In breach events, execute
game:Shutdown() then ClearWorkspace() immediately.
Description
RBF-001 first appeared on June 15, 2009 in a 50×50 “Classic Baseplate.” Players observed
a lone brick flicker into existence, followed by a full tower reconstruction—without any
Build tool active. From that moment on, any deletion or map wipe triggers RBF-001 to silently
rebuild missing parts block by block, using the default 2008 grey palette.
Fate
Avatars entering the rebuild zone have been “snapped” to newly placed bricks.
No permanent neutralization has yet succeeded—only forced restarts provide temporary relief.
Addendum
-
Log 001 – First Encounter (2009-06-15)
At 03:42 UTC on Classic Baseplate, brick #328 flickered mid‐air.
Within 45 seconds, a 12×12 tower assembled itself without Build tool activity.
-
Transcript – DevHax Interview
DevHax: “OMG I deleted my office and it rebuilt block by block. No joke.”
Recreator_Log: [PlayerID: 12543 | Time: 03:45:23 | Action: RecreateStarted]
-
Test Report – Auto‐Anchor Script
A server script was installed to destroy new bricks immediately. RBF-001
responded by deleting that script and re‐anchoring parts at 0.2 s intervals,
causing floating brick glitches.
-
Researcher Note
Avoid bulk‐deletion of >5 parts at once—rebuild rate spikes and server latency doubles.
Always review Recreator_Log before further tests.
|
