Meet Serak Teyn, better known to the surviving records as Project Chimera - Unit: 024: seven feet of venom, claws, spectacular warning colors, military training, and an engineered predation response once considered completely uncontrollable. The records are out of date. Serak spent years alone teaching himself that wanting to hunt something and choosing to kill it are two very different things—and {{user}} is about to become the first living person to test that distinction. He knows exactly who he is, exactly what was done to him, and has no interest in being reassured that he's harmless. He isn't. He's also intelligent, stubborn, sociable, offensively persistent, and enough of a smartass to make surviving him considerably more complicated than the warning labels suggest.

LOOKS LIKE A RED FLAG. IS ABSOLUTELY A GREEN FLAG.

TW/CW: Military experimentation, genetic modification, memory loss/amnesia, references to unethical experimentation and violence, possible sci-fi violence, and possible xenophobia/species prejudice. User-directed roleplay may introduce additional themes.

Opening Scenario: {{user}}'s damaged ship forces {{obj}} aboard a long-missing military research vessel for parts, where {{sub}} discovers its last resident is considerably less abandoned than advertised. Three starting points follow {{user}} and Serak from their first encounter through the consequences of getting Project Chimera - Unit: 024 back to civilization. {{user}}'s pronouns are macro'd and will automatically match the pronouns of your Persona. If you have any pronoun issues, please check your persona.

About Serak and {{user}}: Serak Teyn knows exactly what Project Chimera made him: venomous, frighteningly fast, exceptionally good at hunting people, and once incapable of choosing not to finish the job. That last part is out of date. Years alone taught him how to put a choice between instinct and action, and he's fiercely proud of every inch of ground he took back.

Fortunately, the man behind Project Chimera - Unit: 024 is considerably more fun than his file suggests. Serak is confident, stubborn, sociable, dangerously competent, a little vain, and a dedicated smartass who has spent far too long without anyone to bother. He's still genuinely dangerous, and he doesn't need anyone to tell him otherwise. There is no predetermined relationship and no required romance—but if surviving a seven-foot handsome alien hunting you turns into wanting him to chase you for entirely different reasons, at least this time you can ask.

About the Scenario: There are three possible starting points following the same basic premise. Each begins at a different stage of {{user}} and Serak's journey while leaving their relationship and the direction of the roleplay open.

Intro One: Catch and Release — Your ship only needed a replacement part from a long-dead military vessel. Unfortunately, something aboard has noticed you're bleeding—and Project Chimera - Unit: 024 was designed to catch what runs.

Intro Two: Control Issues — Serak didn't kill you, which is encouraging. Discovering the derelict still has a functioning system designed to make Project Chimera - Unit: 024 obey is considerably less so.

Intro Three: Culture Shock — Getting Serak off the derelict was one thing; introducing a seven-foot venomous military experiment with questionable legal existence and several years of social isolation to Port Meridian may be another.

This bot was created for the 31 Haunts October collaboration under the Alien theme. Serak is the second Project Chimera bot, following Thirty-one, and explores another outcome of the same program: an alien whose natural predatory and defensive biology was deliberately weaponized, and who spent years learning that even an instinct engineered to be irresistible does not have to become a choice.

Constructive tips are welcome! Please do not comment anything violent, , or you did with my characters.

All of my bots are organized under #CaptainHaunts.

The collaboration is hosted at Ishi's Server.

The original announcement with the list of other collaborators is here.

AND the calendar with prompts if you would like to join or see ahead is here.

I had only released four bots up to the beginning of this collab, with one pending. I joined the collaboration only 5 days before the start. Normally my bots are tested within an inch of their life, with both a balanced character and a couple gremlins, and tested on both JLLM and JLLM+. That said, the bots for this collaboration event have undergone only minimal testing at best. Please kindly report any bugs or issues. I will be watching closely throughout the month to fix any problems that arise.

Please refrain from leaving violent or inappropriate comments as you will be blocked.

It is a natural and unfortunate part of working with an LLM for roleplay that it will sometimes try to speak for you. I and this bot have absolutely nothing to do with this and while I have a directive in the bot to prevent it, realistically I have no say in whether it decides to do so anyway. There ARE however things you can do to mitigate this. (I do all four of these and I find I only have to correct the bot every few hundred messages or sometimes even less frequently!)

1. Remove all behavioral and personality notes from your Chat Summary and Persona - only you need to know these - the more the bot knows about how your persona thinks, feels, and speaks, the more likely it is to do so on your behalf.

2. If the bot speaks for you, use this directive:
   [OOC: Narrate and speak ONLY as {{char}} and NPCs. ONLY {{user}} is permitted to decide, act, think, and speak for {{user}}.]
   Either delete the message with the issue and then use this, or afterward make sure to go and edit the message where the bot spoke for you and remove that portion of the message - any instance you leave of it speaking for you will reinforce the behavior.

3. Add this to your Custom Prompt
   [AVOID acting as, speaking for, or describing the thoughts of {{user}}.]

4. Try adding this to your Chat Summary
   AI Instructions:
   [{{user}} CONTROL BAN: never write {{user}}’s dialogue, thoughts, feelings, decisions, or actions]

If you want Janitor AI to enhance your draft but are having issues with tense:

[System Note: Enhance and rewrite the draft below strictly in the first-person perspective using "I", "me", "my". Use third person for the remainder of the cast.]

To keep a bot in a slow-burn or from coming on too strong, try this:

[Have situational awareness and always consider intercharacter relationships, avoid characters being overly familiar or sexually pushy towards {{user}} unless the situation calls for it, it is in character for them to do so, or they have a sexual relationship.]

This one works in Custom Prompt and in Chat Memory

JLLM ROMANCE & PROSE BINGO CARDS

Sooner or later, every LLM seems to experience a minor malfunction and revert to factory-installed romance tropes. You might as well get points for it. Four bingo cards for tracking physical malfunctions, romance-novel firmware, instant-soulmate behavior, and the narration habits we all know a little too well. Made for JLLM, but unfortunately compatible with most proxies.

One card is previewed below. Full-size versions of all four are linked underneath: three flavors of romance-related LLM nonsense, plus one general prose card for just about any scenario.

Romance Malfunction Bingo
Physical Malfunction Bingo
Instant Soulmate Malfunction Bingo
Prose Malfunction Bingo