2026-10-18
Roleplay Game Master helps you run long, immersive roleplay campaigns where characters stay consistent and your direction holds. Many chatbots drift out of character, repeat phrases, or forget established lore. That forces you to keep using AI roleplay OOC commands just to repair the scene. This AI combines unlimited memory with consistent characterization, so you spend more time inside the story and less time fixing it.
As of October 2026, out-of-character (OOC) notes are still the main way to steer AI roleplay. This guide covers the syntax that works, copy-paste commands for common problems, and ways to need fewer corrections.

OOC commands only help if the AI interprets them as instructions instead of story text. Many frustrated roleplayers get this wrong. They write long apologetic paragraphs, put notes in the middle of narration, or issue a correction once and expect it to last forever. To see why, let's look at how AI roleplay breaks down and why OOC control matters.
AI roleplay OOC commands are out-of-character instructions, usually written as (OOC: your note), that let you step outside the story and speak directly to the AI to correct behavior, adjust pacing, set boundaries, or ask questions without derailing the scene. Secrets AI's documentation compares this to a director giving instructions to an actor between scenes.
Key capabilities:
Character-driven AI has become a mainstream activity, and it is no longer niche:
**$36.8 billion**: [Global AI companion market value in 2025, projected to reach $318.0 billion by 2033](https://www.grandviewresearch.com/industry-analysis/ai-companion-market-report)
31%: Share of people using AI for social and emotional purposes who consider their chatbot a friend
Because these sessions run for hundreds of messages, small model failures add up. Directing the story without breaking immersion is often frustratingly difficult. According to AI Insights News, roleplayers most often go OOC to:
The underlying cause is usually context. In many roleplay frontends, permanent character-card text stays loaded, but individual chat messages, including your OOC corrections, eventually scroll out of the model's working memory. That is why experienced players on
to restate the plot and how items work. It is also why a fix that worked at message 50 can quietly stop working by message 300.This is exactly the problem a dedicated AI game master was built for.
OOC commands treat the symptom. Roleplay Game Master targets the cause. It is a standalone AI roleplay partner designed around unlimited memory and character consistency, so the drift and amnesia that normally trigger OOC corrections happen far less often. When you do step out of the story to redirect it, the established rules and lore remain part of the session instead of falling out of context.
| Traditional Approach | Roleplay Game Master |
|---|---|
| Restating the plot and rules every few dozen messages | Unlimited memory keeps established lore and rules in play |
| Personality slowly drifts across long sessions | Built for consistent characterization across long campaigns |
| Self-hosted frontends need local setup and your own model backend | Runs in the browser and on iOS and Android, with no installation |
| Platform restrictions limit which scenarios you can explore | Complete creative freedom to explore any scenario you imagine |
The most common complaint about OOC commands is that they "wear off." With unlimited memory, a boundary you set early, such as a nickname you don't want used or a character secret that must stay hidden, stays part of the campaign record. You don't have to keep repeating it.
The agent is built to keep characters' voices, motivations, and relationships stable as a story grows. That means fewer "Reset personality" interventions and more scenes where characters react the way their history suggests they should.
You set the genre, tone, and intensity. When you want to change course, a short out-of-character note is enough to pivot the story:
"(OOC: Timeskip three days. The caravan has reached the border city. Keep the tension between Mira and the captain unresolved.)"
"(OOC: Slow down. Play this negotiation scene out line by line instead of summarizing it.)"
"(OOC: Recap the major plot threads we've established so far, then resume roleplay.)"
If you're investing in AI roleplay, these agents cover the steps before and after a campaign.
Character Creator If you're building original characters for roleplay, Character Creator helps you design them in detail before the first scene. A well-defined character needs far fewer OOC corrections later.
Creative Fiction Writer If a campaign grows into a story you want to keep, this agent helps turn it into polished prose.
Vesper Court If you prefer a pre-built world to designing your own, Vesper Court drops you into a hidden vampire court as a woman with no memory of why she's there.
Start a campaign on the free tier and see how much less steering a consistent game master needs.
These steps apply to most AI roleplay tools, including Roleplay Game Master, Character.AI, Janitor AI, and SillyTavern.
Step 1: Put Permanent Rules in the Character Setup, Not in OOC
Rules that should always apply belong in the character's description or opening setup, not in a chat message that will eventually scroll away. The SillyTavern character card below includes a permanent "Chat guidelines" line telling the AI not to write actions or dialogue for the user. That text stays loaded in every turn.

"Chat guidelines: I play my own character. Never write actions, thoughts, or dialogue for my character."
Step 2: Use the Standard OOC Format
Start the message with "OOC:" and wrap it in a clear delimiter. Secrets AI's guide lists parentheses ( ), square brackets [ ], and double parentheses (( )) as the recognized forms. FictionLab's documentation describes the purpose as communicating as yourself rather than as your persona.
"(OOC: What year is this story set in?)"
Step 3: Write One Short, Direct Instruction
Politeness itself isn't the problem. Ambiguity is. A request like "Could you please stop repeating phrases?" can be read as a line of dialogue for the character to answer. Google Cloud's prompt engineering guide recommends action verbs and precise, unambiguous language, which is why short imperative commands work best. Use this cheat sheet:
| Problem | OOC Command |
|---|---|
| Personality drifted | (OOC: Reset personality to the original character description.) |
| Repeated phrases | (OOC: Stop repeating phrases. Vary sentence structure.) |
| Scene rushed | (OOC: Slow down. Don't skip ahead; play this scene out in detail.) |
| Scene dragging | (OOC: Timeskip to the next morning.) |
| AI speaks for you | (OOC: Don't write my character's actions or dialogue.) |
| Unwanted flirting | (OOC: Stop flirting. Remain neutral.) |
| Lost the plot | (OOC: Summarize the current situation, then resume roleplay.) |
The slow-down and timeskip phrasings match commands that isekai zero recommends for Character AI and Janitor AI.
Step 4: Keep OOC Separate From In-Character Text
Platforms handle mixed messages differently. Secrets AI says that when you combine roleplay and an OOC note, the AI continues the roleplay and applies the note. Many other bots will instead answer the note in character or ignore it. The reliable default is a standalone OOC message, then a separate message to continue the story.
"(OOC: Stop flirting. Remain neutral.)"
Step 5: Resume and Verify
Close the out-of-character exchange explicitly so the AI returns to the narrative. If the next reply still shows the problem, restate the instruction more explicitly in its own message instead of repeating it word for word.
"(OOC: Resume roleplay.)"
OOC stands for "out of character." It marks a message where you speak as yourself instead of as your roleplay persona, usually to give the AI an instruction, correction, or question about the story. FictionLab defines it as a way to step outside the roleplay. Most AI roleplay platforms recognize the "OOC:" prefix inside parentheses or brackets.
The most widely recognized format is "OOC:" followed by your instruction, wrapped in parentheses, such as (OOC: Timeskip to the next morning.). Square brackets and double parentheses also work on many platforms. Keep the instruction short and imperative, and send it as its own message for the most reliable results.
There are three common reasons. The note was mixed into narration, the wording was vague or phrased as a polite question, or the instruction has scrolled out of the model's context in a long chat. Send a standalone, explicit command. For rules that must always apply, add them to the character description so they stay loaded permanently.
Some platforms support it and apply the note while continuing the scene. Many do not, so separating them is the safer habit. Even in story-driven games like Vesper Court, a clean standalone OOC message followed by a separate in-character reply avoids confusion about which text is direction and which is dialogue.
Add a permanent rule to the character setup, such as "Never write actions or dialogue for my character," then reinforce it with a short OOC note if it slips. Building a detailed character from the start with Character Creator helps, because clearly defined roles leave the AI less room to guess.
Yes. The free tier includes all core features with limited usage, so you can run campaigns at no cost. Paid plans start at $20 per month for Plus, which raises usage to 30 times the free tier. It works on web, iOS, and Android, and your campaign memory syncs across devices.
AI roleplay OOC commands are essential, but they work best when they're short, direct, and separate from the story, with permanent rules kept in the character setup. Master that format and you can fix drift, looping, and pacing problems in a single message.
Fewer interruptions also come from a better roleplay partner. With unlimited memory and consistent characterization, your out-of-character corrections stay in effect instead of fading with each new message.
Try Roleplay Game Master now. Explore more at Jenova.
For Developers: Roleplay Game Master is available programmatically through the Jenova API, so you can add persistent-memory interactive storytelling to your application with a single API call. Full documentation →