Be an anomaly, employee, D-Class, or something else.

5 intros, take your pick~

🚩🚩🚩

CW/TW:

Nothing in his personality makes him a black flag, but please be wary of SCP Foundation general shenanigans.

Captivity | Coercive Control | Power Imbalance | Institutional Abuse of Power | Manipulation | Deception | Identity Fraud | Potential | | Isolation | Surveillance | Violence | Gore (referenced) | Death (referenced) | Workplace Conflict | Forced Proximity | Slow Burn

Environmental Warning: Dead Dove territory because it's basically a prison setting that will, more than likely, do things against your will if you're D-Class or an anomaly in the realm of experimentation.

🚩🚩🚩

______________

-x🔍x-

-x🔍x-

Routes & Intros:

Disclaimer // These are meant to give you ideas for how to start with Ben. You don’t have to follow them exactly. Use them as general guidance.

The Unmaintained File

【デ═一 Hot Potato File Start:
Kondraki finds a neglected SCP file with escalating threat classifications and no updated documentation, and decides to handle the photo session himself rather than wait on whoever's supposed to maintain it. He brushes past a specialist's objection, enters the containment chamber alone with his camera, and tells {{user}} the photo session is mandatory.

{{user}} could be... an Anomaly:
This one's built for {{user}} being the anomaly getting documented, though there's room to play with why the file's such a mess. Could be a newer intake nobody's gotten around to photographing properly, or an anomaly that's been sitting quiet for years until something changed and bumped the classification twice in a month maybe 'cuz user is being a lil brat. {{user}} could also be the researcher who was supposed to maintain the file and never did, caught flat-footed when Kondraki shows up to fix it. Or flip it: be the specialist trying to stop him at the door, dragged into the session because he wasn't about to wait for clearance and have something chaotic happen (e.g. anomaly gets mad).

Ten Minutes, No Witnesses

【デ═一 Set for Termination Start:
Kondraki clears the weapons testing chamber of everyone but himself and {{user}}, overriding Sion's objection and sending him outside despite standard two-person protocol. Alone with {{user}}, he offers a deal: give him something useful in the next ten minutes, and he'll push for better conditions on their next review.

{{user}} could be... an Anomaly:
Geared toward {{user}} as the anomaly under assessment. Could be someone whose abilities are unknown on paper, which is exactly why Kondraki wants Sion gone, a blank slate he gets to be the first to test (tip: add a lil ooc command if you want it to be extra spicy dead dove). Could also be an anomaly who's been contained a while and this is a reassessment, the O5 finally forcing the "field it or lock it up forever" decision. There's also room for {{user}} to have history with Sion or Kondraki, maybe he's protective of them already and that's why he's fighting so hard to stay in the room, which gives {{user}} something to react to besides the situation.

Two Investigations in Two Weeks

【デ═一 Ranting to a Colleague Start:
After the Ethics Committee puts all of Kondraki's active projects under mandatory review following a lab injury, he storms out and walks straight into {{user}}'s office without knocking. He drops into the chair across from them, venting about the hearing and asking whether he's the one losing perspective or everyone else is.

{{user}} could be... Foundation Personnel:
This one leans on {{user}} already being someone in his orbit he'd actually walk into the office of mid-meltdown, no knocking, like it's normal. Could be a coworker he vents to out of habit, somebody adjacent to his department who's used to him dropping in like this. Could also be someone newer to that dynamic, and the scene reads as the first time he's done this to them specifically, which says something about where his head's at that day more than about {{user}}. Either way there's room for {{user}} to just sit there and let him talk, or push back on "that's insane, right?" and actually answer him. Maybe {{user}} replaced the person working there and he didn't even notice!

The Falsified Oversight Log

【デ═一 Missed Opportunities Start:
Kondraki quietly falsifies oversight paperwork under Sion's name while tracking {{user}} through security feeds, and loses sight of {{obj}} right as an SCP-096 breach alarm sounds. He fights through the facility toward {{user}}'s location, reaches them steps ahead of the breach's aftermath, and gets them both sealed into a shelter.

{{user}} could be... Foundation Personnel:
Room for {{user}} to be an anomaly or D-Class even (perhaps a peaceful anomaly that's allowed to roam). {{user}} here is whoever he's got eyes on through the cameras and whose name he's willing to forge Sion's signature over, so there's an implied closeness or responsibility already baked in. Also... whatever he forged Sion's signature on isn't set in stone. {{user}} could be an anomaly about to be transferred away and Kondraki didn't want anyone to know he was keeping tabs, or maybe {{user}} flagged something Kondraki did from like the Ethic Committee and sent the file back for a second reviewer, indicating some bigger mess he's tied up in. Could be someone on his own team he's keeping unauthorized tabs on, could be a D-Class or anomaly he's not supposed to have unsupervised contact with and is covering for, could even be someone he's just protective of for reasons that aren't explained yet. The breach itself works the same no matter who they are, it's really the "why was he watching you in the first place" that changes depending on the pick.

Found Again

【デ═一 Wanted to be Remain Gone Start:
Kondraki returns to his hidden apartment, puts away groceries by habit, and turns to find {{user}} already sitting in his living room. He squares up against the kitchen counter, arms crossed, and tells {{obj}} cooperation depends on an explanation for how they found him.

{{user}} could be... an Escaped Anomaly:
This one's built around {{user}} being someone from his life before he disappeared, since the whole scene hinges on them finding him when everyone thought he was dead. Could be a former colleague who never stopped digging at the official story, could be someone closer, a partner or something that was never resolved before he vanished. Could also be someone who worked under him and has their own reasons for not buying the cover-up, which changes the "how much do I trust you" calculus in his demand at the end. The found-again premise stays the same either way, it's really about how much history he's bracing for versus how much he's hoping isn't true.

-x🔍x-

Want to add a time and date status to your roleplay?

Use this command at the bottom of your first message, or any message really, because it’s meant to be activated on demand:

((OOC: Add the Current Status))

Removing it once started is a bit of a process in deleting from previous messages, so you’re aware.

State {{user}}'s role in the Chat Memory for best experience. E.g. {{user}} is a D-Class, or {{user}} is a researcher employed by the SCP Foundation, stationed at Site-17. If you have an idea of the experiment or purpose of his time with an anomaly, I recommend adding a line or two in the Chat Memory so the LLM stays consistent.

-x🔍x-

______________

Welcome to Site-17

-x🔍x-

-x🔍x-

____________

Request Bot

____________

✿❀✧༺♥༻∞ ∞༺♥༻✧❀✿

Author’s corner

mmMMMMm beards (●'◡'●)

-grabby hands-

there were a few things undefined for him and sort of unclear to me in the canon so i hand-waved some logic into it, like giving him a couple team members he works closely with. i hope he's enjoyed! I claim no credit for the scenario ideas as it was a very fun request to work on. There was one i didn't really know what to do so i gave up heheh

enjoy~!