PT. IV: THE SLIME PAGES — WHEN THE THREAD STARTED PULLING BACK

PROJECT ENGINE BRIEF

Part III ended with a quiet-lock and a terrifying suggestion: the camcube may be pulling recordings from a “silo” that includes current sessions.

Part IV is the most volatile segment of the archive. It’s also the one most aggressively scrubbed: posts removed mid-conversation, users disappearing, and a repeated “system log” that shouldn’t exist on a forum.

Recouccuring posters return (OP, BMAN, BigBadWolfe, Gordon, Ugrox7, de_turkleg… even the clown “news” guy), and the new arrivals from Part III don’t last.

ARCHIVE Many entries are reconstructed from quotes. SLIMED indicates posts where the user reported the “green overlay” phenomenon before vanishing (account deleted/banned/unknown).

SAFETY NOTE: This archive does not include step-by-step reproduction instructions. Posts that were “how-to” were removed in the recovery process. Thread Status: QUIET-LOCK Moderation: ACTIVE
If you see a string below that looks “complete,” it is not. PROJECT ENGINE redacted key fragments.

PAGE 19 (RECOVERED) — THE MOUNT LIST


Forum Moderator avatar

#301 ForumMod_Redline MOD QUIET-LOCK

Thread remains open for discussion. Do not post strings, dumps, or reproduction instructions. Screenshot-only evidence is permitted if it does not contain internal identifiers.

bloxyboy30 avatar

#302 bloxyboy30 OP

mod can you answer ONE question: why did someone get banned for “posting internal strings” if this is just a glitch?

Forum Moderator avatar

#303 ForumMod_Redline MOD

I will not discuss moderation actions. Stay on topic.

BMAN avatar

#304 BMAN EXPERT

ok then here’s the topic: we have logs suggesting a mount resolve and an object-data pull. that’s a subsystem.

and now we have multiple models referencing SILO-WORKS. that’s not “random bytes.”

UNAUTHENTICATED SYSTEM MESSAGE SYSTEM captured from 2 backups
[Client] CamCube: pull() -> s.objdata/camcube.pull [Client] CamCube: subject fallback -> "Watcher" [Client] CamCube: playback -> "base/5" [Client] CamCube: render overlay -> GREEN
ByteHarvester avatar

#305 ByteHarvester WITNESS LEAK

i got the “mount list.” screenshot. i’m trying to redact it but i’m not sure what’s safe.

it shows s.objdata and a bunch of other mounts that look like filesystem paths. i’m not posting raw names unless project engine says ok.

EVIDENCE: mount list (heavily censored) CLICK
NOTE: This is a reconstruction of what ByteHarvester claimed his screenshot showed. The original image is missing. MOUNTS (partial): - s.objdata - s.████████ - s.████████████ - client.ui - client.demo - silo.works - (two entries marked "deprecated") The line "silo.works" was circled in red.
BigBadWolfe avatar

#306 BigBadWolfe

client.demo???? ok i hate that. why would “demo” exist as a mount. that sounds like recorded playbacks. that sounds like this thread.

de_turkleg avatar

#307 de_turkleg

GREEN overlay?? like the foggy vids but… closer? like it’s on your screen? dude that’s not a camera cutscene. that’s UI.

yourlocalrobloxnews avatar

#308 yourlocalrobloxnews

haha green overlay?? maybe the camcube is telling you to touch grass

Ugrox7 avatar

#309 Ugrox7

if “client.ui” is a mount and playbacks can render overlays, then base 5 isn’t “haunted.” it’s a playback type that includes UI layers.

which means it can show anything that’s on screen in a recording.

PAGE 20 (RECOVERED) — THE GREEN SLIME STARTS


MapMason avatar

#330 MapMason

i got the green overlay. it’s not fog. it’s like a viscous transparent layer on the screen. it “drips” when the camera snaps.

and before anyone says “graphics glitch,” it had a UI label in the corner for 1 frame.

EVIDENCE: the 1-frame label (retyped) CLICK
Label (MapMason): "DEMO: SILO-WORKS / SUBJECT: WATCHER / MODE: COAT" He swears it said COAT. Like a coating.
Kodeyak avatar

#331 Kodeyak

“MODE: COAT” bro i’m gonna puke. ok. i’m not a skeptic anymore. i’m a runner. i’m running away.

Gordon Bloxman avatar

#332 Gordon Bloxman ALIAS

i got a base 5 where it showed a noob in a hallway and the slime was on the camera like it was… on the lens.

the noob turns and looks at the camera. that’s all. that’s the whole recording. then it ends.

BMAN avatar

#333 BMAN EXPERT

if it’s rendering UI labels, then those labels are part of the playback format. meaning SILO-WORKS isn’t a rumor. it’s literally inside the demo metadata.

LumenQuarry avatar

#334 LumenQuarry WITNESS

ok… ok ok ok… i opened studio and my place thumbnails are wrong. they’re tinted green and there’s a smear across them like a fingerprint.

i did not upload that. i did not edit them.

UNAUTHENTICATED SYSTEM MESSAGE SYSTEM “appears between posts”
[Client] CamCube: pull() -> s.objdata/camcube.pull [Client] CamCube: redirect -> client.demo [Client] Demo: overlay coat -> applied [Client] Demo: writeback -> enabled
BigBadWolfe avatar

#335 BigBadWolfe

“writeback” is the worst word i could’ve read today. stop. please. shut the thread down. i’m serious.

yourlocalrobloxnews avatar

#336 yourlocalrobloxnews

ok i was joking before but… my studio just crashed and when i reopened it, my “recent places” list has one i’ve never seen called “SILO WORKS TEST”

PAGE 21 (RECOVERED) — THE NEW ONES START DROPPING


ByteHarvester avatar

#350 ByteHarvester SLIMED

i shouldn’t have looked at the mount list. i shouldn’t have pulled again. i’m getting the green coat even without the model in the place now.

it happens when i open studio. it happens when i click play. it happened once in an entirely different game.

EVIDENCE: “coat” symptoms list CLICK
- Overlay appears as translucent green smear. - Drip motion synced to camera snap (even outside camcube tests). - 1 frame UI label sometimes appears: "MODE: COAT" "SUBJECT: WATCHER" - Audio pops once when it starts (not always). - After overlay: thumbnails turn green-tinted. ByteHarvester claims uninstalling Studio did not remove it.
BMAN avatar

#351 BMAN EXPERT

ok—everyone STOP running it. if “writeback” is real, this is no longer a curiosity. this is a risk.

ByteHarvester: do not post any more logs. do not open studio. i’m not kidding.

MapMason avatar

#352 MapMason SLIMED

too late. i was testing something and it played back… me testing it. it was my own avatar. same shirt. same hat. same dumb walk.

the camera follows behind me, then cuts to a wall, and the green coat slides down the screen like liquid.

it’s recording us.

UNAUTHENTICATED SYSTEM MESSAGE SYSTEM quote recovered from 4 sources
[Client] Demo: capture -> enabled [Client] Demo: subject -> "YOU" [Client] Demo: coat -> applied [Client] Demo: commit -> silo.works
bloxyboy30 avatar

#353 bloxyboy30 OP

ok. this changes everything. this means the “random” recordings weren’t random. they were captures of someone else’s session.

base 5 wasn’t haunted. it was a lens. and we’ve been looking through it.

de_turkleg avatar

#354 de_turkleg

if it’s capturing sessions… then “Watcher” isn’t a subject name. it’s a ROLE.

#355 POST REMOVED

Removed by moderation. Reason shown to some viewers: “Internal demo endpoints.”

ByteHarvester avatar

#356 ByteHarvester SLIMED

the green coat just appeared over this forum page. not studio. the forum.

i’m not kidding. it’s on my browser. it “dripped” across the reply box and then my text got replaced with garbage.

if you can read this, tell BMAN i’m sorry

#357 ACCOUNT DELETED

ByteHarvester’s account no longer appears in search. Last cached quote ends mid-sentence.

PAGE 22 (RECOVERED) — THE THREAD RECORDS ITSELF


Gordon Bloxman avatar

#380 Gordon Bloxman ALIAS

i have a screen recording. i’m not uploading it here because mod will delete it.

but i saw it. the playback showed THIS THREAD in a 3D space. like the forum page was a texture on a wall. and the camera panned over posts that hadn’t been written yet.

EVIDENCE: “future post” detail CLICK
Gordon claims the camera drifted over a post that read: "you’re going to call it slime because you don’t have a better word." He says nobody had said “slime” yet in that session. Then he refreshed the forum, and MapMason’s post used the exact word. (Yes, this is insane.)
Kodeyak avatar

#381 Kodeyak

i believe you. i hate that i believe you. i refreshed my thread page and for 1 second the text was… wrong.

like it swapped words. then it fixed itself. like the page got “overwritten” and then “corrected.”

Ugrox7 avatar

#382 Ugrox7

if the demos include UI, and the UI can include forum pages, then a playback could include this thread being viewed.

which means the thread can appear inside the silo as a “demo artifact.” which means… the thread is now part of the dataset it pulls from.

UNAUTHENTICATED SYSTEM MESSAGE SYSTEM the “mirror line”
[Client] Demo: mirror -> thread/active [Client] Demo: subject -> "ForumMod_Redline" [Client] Demo: coat -> applied [Client] Demo: commit -> silo.works
Forum Moderator avatar

#383 ForumMod_Redline MOD

This thread is now under review. Further discussion of “system messages” will be removed. Do not claim the forum is compromised.

yourlocalrobloxnews avatar

#384 yourlocalrobloxnews

yo mod you gotta admit that “subject -> ForumMod_Redline” is kinda funny though

#385 POST REMOVED

Removed by moderation.

PAGE 23 (RECOVERED) — “M0FR” BREAKS CHARACTER


m0fr avatar

#410 m0fr ALIAS

everyone stop. seriously. you don’t understand what you are touching.

the “coat” isn’t a bug texture. it’s a marker. it flags a capture as “contaminated” for testing. you keep dragging contaminated demos into clean sessions.

that’s why it spreads.

ARCHIVE NOTE: why this post is infamous ARCHIVE CLICK
Multiple users later claimed: - m0fr seemed to know internal terminology. - After this post, the thread’s missing-page gaps increase dramatically. - The phrase “marker” becomes a recurring theme. PROJECT ENGINE does not verify m0fr’s identity.
BMAN avatar

#411 BMAN EXPERT

how do you know the word “contaminated” belongs here?

m0fr avatar

#412 m0fr ALIAS

because i’ve seen the label too.

it’s not “MODE: COAT” originally. that’s your client shortening it. it’s missing letters.

EVIDENCE: redacted full label (partial) CLICK
PROJECT ENGINE REDACTION: "MODE: COA████" "FLAG: CONTAMINAT████" "SUBJECT: WATCHER" m0fr claims the missing letters matter.

PROJECT ENGINE removed the full label to avoid distributing a “complete string.”

bloxyboy30 avatar

#413 bloxyboy30 OP

so what are we supposed to do? pretend we didn’t see it? people already ran it. people already got coated. some of them are gone.

LumenQuarry avatar

#414 LumenQuarry SLIMED

i’m not “gone” yet but i feel like i will be. my place thumbnails are worse. the green smear is thicker and now there’s… little bubbles in it.

and when i hover over my place it shows the wrong description for a second. like it flashes another place’s text.

UNAUTHENTICATED SYSTEM MESSAGE SYSTEM “the flash”
[Client] ObjData: index mismatch -> fallback [Client] Demo: metadata overlay -> injected [Client] Demo: writeback -> COMPLETE
BigBadWolfe avatar

#415 BigBadWolfe

that “flashing other place text” thing happened to me too. like a tooltip flicker. i thought it was just lag.

are you saying the coat is… mixing indexes?

#416 ACCOUNT DELETED

LumenQuarry’s account no longer appears in search. Multiple users report his profile briefly showed a green “coat” overlay before vanishing.

PAGE 24 (RECOVERED) — THE OLD GUARD FIGHTS BACK


BMAN avatar

#440 BMAN EXPERT

i’m done being scared. i’m going to treat this like what it is: a system that’s misfiring.

if “camcube” is a key, then the “coat” is a flag. flags exist for a reason: routing. quarantine. filtering.

that means there’s probably also an “uncoat.” (not typing any string. don’t ask.)

Ugrox7 avatar

#441 Ugrox7

if a quarantine flag exists, then the silo is expected to be exposed to clients in some contexts. this might have been a testing feature that shipped accidentally.

OR it’s intentional… and we’re not supposed to know it exists.

de_turkleg avatar

#442 de_turkleg

i’m stuck on one thing: “Watcher.”

you don’t name a subject “Watcher” unless the subject is defined by watching.

yourlocalrobloxnews avatar

#443 yourlocalrobloxnews

ok i’ll be serious: i got a playback where the camera is behind a wall… and you can hear someone typing. i swear i heard keyboard clicking.

and then it cuts to a baseplate and there’s one part named “FORUM”

Gordon Bloxman avatar

#444 Gordon Bloxman ALIAS

THE PART NAMED FORUM IS REAL I SAW IT TOO ONCE

it was anchored. it was invisible. but the camera kept orbiting it like it was a beacon.

UNAUTHENTICATED SYSTEM MESSAGE SYSTEM “beacon line”
[Client] Cam: Subject = "Forum" [Client] Cam: Override engaged [Client] Demo: coat -> applied [Client] Demo: commit -> silo.works
m0fr avatar

#445 m0fr ALIAS

you’re not supposed to say “forum.”

you’re not supposed to say “watcher.”

and you’re DEFINITELY not supposed to say the five-letter word.

ARCHIVE NOTE: “indexing theory” ARCHIVE CLICK
Several reconstructed posts claim: - Certain words increased the chance of specific demo pulls. - After “forbidden words” were typed, missing pages increased. - Moderation removals became immediate. PROJECT ENGINE cannot confirm causality.
BigBadWolfe avatar

#446 BigBadWolfe

ok then say the safe thing: what ARE we even investigating anymore? a model? a mount? a demo system? a leak?

because people are disappearing.

bloxyboy30 avatar

#447 bloxyboy30 OP

we’re investigating a question that got bigger than the model:

why does the engine know how to play back private demos?
why does it tag them as contaminated?
and why is a random streetlamp a key that unlocks it?

PAGE 25 (RECOVERED) — THE SLIME TAKES THE MOD


Forum Moderator avatar

#470 ForumMod_Redline MOD

Final warning. Stop making claims about “private demos” and “contamination.” This thread is attracting disruptive behavior and will be locked.

UNAUTHENTICATED SYSTEM MESSAGE SYSTEM the one that made everyone quit
[Client] Demo: subject -> "ForumMod_Redline" [Client] Demo: coat -> applied [Client] Demo: mirror -> thread/active [Client] Demo: writeback -> COMPLETE [Client] Demo: status -> "SLIMED"
Forum Moderator avatar

#471 ForumMod_Redline MOD SLIMED

Stop posting fake “system messages.”

Also… why is my screen green.

yourlocalrobloxnews avatar

#472 yourlocalrobloxnews

OH MY GOD

BMAN avatar

#473 BMAN EXPERT

mod. do NOT refresh. do NOT post anything else. log out. close the page.

Forum Moderator avatar

#474 ForumMod_Redline MOD SLIMED

My reply box is filling itself.

It’s typing without me.

EVIDENCE: the “typed” line (as cached) CLICK
Cached by a user refreshing mid-incident: "SUBJECT ACCEPTED. COAT APPLIED. MIRROR ACTIVE. YOU WATCHED. NOW YOU ARE WATCHED." (Formatting unknown. Appears as plain text.)

#475 ACCOUNT SUSPENDED

ForumMod_Redline no longer appears as a moderator on cached pages. Account status unknown.

m0fr avatar

#476 m0fr ALIAS

it happened.

bloxyboy30 avatar

#477 bloxyboy30 OP

m0fr. who are you. say it plainly.

m0fr avatar

#478 m0fr ALIAS PROJECT ENGINE

i’m the one who’s been collecting what’s left.

you can’t stop it by deleting posts. you can’t stop it by banning people. you can’t stop it by locking threads.

the silo doesn’t care about your forum rules.

EVIDENCE: final recovered sentence (redacted) CLICK
Final sentence is partially missing in all backups. Recovered fragments: "…if you keep pulling, it will keep learning." "…the coat is how it knows you." "…stop saying the five-letter word." PROJECT ENGINE cannot reconstruct the full line.
UNAUTHENTICATED SYSTEM MESSAGE SYSTEM last one on record
[Client] Demo: capture -> enabled [Client] Demo: subject -> "OP" [Client] Demo: coat -> applied [Client] Demo: commit -> silo.works [Client] Demo: note -> "SEE YOU IN PART V"

THREAD CLOSURE (RECOVERED)


#500 THREAD LOCKED

This thread has been locked.

PROJECT ENGINE NOTE

Part IV is where the narrative stops being “a creepy model” and becomes “an ecosystem.” The archive suggests the “coat” (green slime overlay) is metadata—an internal flag that begins to propagate through captured playbacks and UI surfaces.

The final system line, “SEE YOU IN PART V,” is not included in Part V’s recovered pages. Which raises the question: was it a taunt, or a pointer to something else entirely?

If you want, I can write Part V as a full “PROJECT ENGINE case file” format (instead of forum posts): timelines, recovered assets index, witness statements, and a final twist reveal that ties Foggy/Spookywaters/Forum together.