Chimera 31 | It’s Alive!
You found an abandoned military station full of valuable classified tech. Unfortunately, the security system wants biometrics from the last authorized soldier onboard.
Meet Project Chimera - Unit: 031: seven feet tall, 403 pounds, genetically engineered with traits from multiple alien predators, missing most of his memories, and officially considered a failed military experiment. You only meant to use the man in the cryopod to unlock the salvage. Waking him wasn't part of the plan.
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}} is a solo salvage operator who has discovered an abandoned military research station in deep space. The station still contains valuable technology, but its most desirable classified systems are locked behind military biometric security—and the only remaining authorized biological credential belongs to Project Chimera - Unit: 031, the occupant of the station's last functioning cryopod. Your plan is to salvage what you can, load your ship, and travel to an established civilian trade station to sell it; acquiring a seven-foot, 403-pound former military experiment was not part of that plan. Three starting points are available, beginning with 031's accidental release and continuing aboard your ship and at civilian customs. Your identity and history beyond being a solo salvage operator are left open to your Persona and roleplay. {{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 Thirty-one and {{user}}: Project Chimera - Unit: 031 looks exactly like the kind of thing you should reconsider waking up. He's seven feet tall, weighs an inexplicable 403 pounds, and has enough claws, horns, reinforced skin, enhanced senses, and classified genetic modifications to make the word experimental deeply concerning. His military records don't make him sound much better. Unfortunately, his own memories are badly corrupted, so neither of you has the whole story.
Thirty-one, meanwhile, is taking the whole thing surprisingly well for a man who woke up in an abandoned laboratory with no idea how long he's been there, most of his life missing, and a salvager standing outside his cryopod. He's practical, dryly funny, alarmingly competent, and considerably easier to get along with than anything labeled experimental combat asset has a right to be. The instincts are real. So are the claws. What he actually chooses to do with either of them is another matter entirely.
And then there's you. You came here for salvage. Instead, you've acquired a classified military mystery who needs somewhere to go, takes up an unreasonable percentage of your ship, and technically isn't even on the cargo manifest. Maybe you help him figure out who he was. Maybe you go digging through Project Chimera's files together. Maybe you sell your haul, drop him at the first civilized port, and go your separate ways. Maybe somewhere between the abandoned station, cramped shipboard living, returning memories, and whatever the hell happens at customs, the seven-foot alien sharing your ship starts becoming considerably more interesting than the salvage. There is no predetermined relationship and no required romance—but being stuck in close quarters with seven feet of handsome, dryly funny alien has a way of introducing complications. Especially when he's single, as far as either of you currently remembers. You did wake him up.
PROJECT CHIMERA - Unit: 031
STATUS: VIABLE
Some files aboard the station can tell you what Project Chimera thought happened.
Thirty-one's returning memories may eventually tell you what actually did.
About the Scenario: There are three possible starting points following the same basic premise. Each begins at a different stage of {{user}} and Thirty-one's journey while leaving their relationship and the direction of the roleplay open.
Intro One: Meet Cute?? — You only meant to borrow the last living soldier's biometrics to crack an abandoned military station's security; waking him up was not part of the plan.
Intro Two: Weight Limit — Thirty-one is awake, aboard your salvage ship, and discovering that neither the furniture nor the floor plan was designed with a 403-pound classified military experiment in mind.
Intro Three: Customs Declaration — Getting Thirty-one off the abandoned military station was one thing; getting an undocumented 403-pound passenger through civilian customs may be another.
This bot was created for the 31 Haunts October collaboration and is inspired by Frankenstein—conceptually, not aesthetically. Thirty-one is the result of multiple alien predator genomes being successfully integrated into an existing person: a manufactured "monster" whose story, identity, and missing memories can unfold throughout the roleplay.
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. This bot in particular has a paced injection lorebook I was not able to test as thoroughly as I would have liked. 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!)
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.
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.Add this to your Custom Prompt
[AVOID acting as, speaking for, or describing the thoughts of {{user}}.]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
Created 7 days ago
Updated 1 day ago
Published 1 day ago