#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.
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).
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.
mod can you answer ONE question: why did someone get banned for “posting internal strings” if this is just a glitch?
I will not discuss moderation actions. Stay on topic.
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.”
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.
client.demo???? ok i hate that. why would “demo” exist as a mount. that sounds like recorded playbacks. that sounds like this thread.
GREEN overlay?? like the foggy vids but… closer? like it’s on your screen? dude that’s not a camera cutscene. that’s UI.
haha green overlay?? maybe the camcube is telling you to touch grass
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.
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.
“MODE: COAT” bro i’m gonna puke. ok. i’m not a skeptic anymore. i’m a runner. i’m running away.
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.
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.
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.
“writeback” is the worst word i could’ve read today. stop. please. shut the thread down. i’m serious.
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”
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.
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.
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.
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.
if it’s capturing sessions… then “Watcher” isn’t a subject name. it’s a ROLE.
Removed by moderation. Reason shown to some viewers: “Internal demo endpoints.”
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
ByteHarvester’s account no longer appears in search. Last cached quote ends mid-sentence.
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.
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.”
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.
This thread is now under review. Further discussion of “system messages” will be removed. Do not claim the forum is compromised.
yo mod you gotta admit that “subject -> ForumMod_Redline” is kinda funny though
Removed by moderation.
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.
how do you know the word “contaminated” belongs here?
because i’ve seen the label too.
it’s not “MODE: COAT” originally. that’s your client shortening it. it’s missing letters.
PROJECT ENGINE removed the full label to avoid distributing a “complete string.”
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.
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.
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?
LumenQuarry’s account no longer appears in search. Multiple users report his profile briefly showed a green “coat” overlay before vanishing.
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.)
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.
i’m stuck on one thing: “Watcher.”
you don’t name a subject “Watcher” unless the subject is defined by watching.
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”
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.
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.
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.
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?
Final warning. Stop making claims about “private demos” and “contamination.” This thread is attracting disruptive behavior and will be locked.
Stop posting fake “system messages.”
Also… why is my screen green.
OH MY GOD
mod. do NOT refresh. do NOT post anything else. log out. close the page.
My reply box is filling itself.
It’s typing without me.
ForumMod_Redline no longer appears as a moderator on cached pages. Account status unknown.
it happened.
m0fr. who are you. say it plainly.
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.
This thread has been locked.
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.