Scenario Creation Interface

A breakdown of the interface for scenario creation and how to use these fields.

Scenario Info

Name, Familiarity & Location

The name of the Scenario will act as the chat's name; however you can change the name in the chat sidebar at any time.

Scenario Plot

Description & Advanced Definition

Description

The Description of the Scenario is displayed publicly and acts as the premise for a chat. Both the user and AI model will use this text to understand what the chat's premise is.

Scenarios can be a simple, single line premise or a larger, more complex story premise that includes information about the world, lore, setting and goals of the premise.

It's recommended to treat a Scenario like the blurb on the back of a novel. It sets the expectations to start and gives an idea of where the story will go but will not strictly control the exact events that will take place within the story.

Scenarios should be flexible openers that give an idea of scope, not a strictly outlined plotline with story beats. The latter results in the model rushing the plot and then getting stuck once it "accomplishes" the plot.

✔️: Today is {{char}} and {{user}}'s wedding and {{char}}'s ex is in attendance. They have high hopes that the day will go off without a hitch despite their worries that {{char}}'s ex still has feelings for him.

❌: {{user}} and {{char}} are getting married today. During their vows {{char}}'s ex is going to try to disrupt the wedding, then there is going to be... and then things will...

Advanced Definition

Located under Advanced Options, the Advanced Definition is a hidden text field that acts as a direct continuation of the Description.

The only difference with the Advanced Definition is that it will not be displayed publicly on the Scenario card. Use it to hide information you don't want displayed.

If you Scenario is about a wedding, the Advanced Definition can be used to define what the venue looks like, who all is in attendance, or any other details that don't necessarily need to be publicly displayed.

At the end of the day whether the information is public or private, though, is irrelevant to how the AI model interprets the information.

The character limit on Scenario is shared between the Description and Advanced Definition.

You can put 1000 characters into one field, and 2000 into another field, but you cannot surpass 3000 total characters across the two fields.

Generate a Scenario

and many more...

By selecting the Generate tab in the Scenario Plot page you'll be given a large list of Tags. You can select (or create) up to 4 Tags that the AI model will use to generate a random Scenario based on the context of these tags.

Proceed through Scenario creation as normal and once you create the Scenario you'll be met with a custom generated Scenario Description.

Embedded Content (Xouls & Lorebooks)

You can embed as many as 8 Xouls and 3 Lorebooks to come included in your Scenario.

  • If your Scenario does not contain any embedded Xouls the user will be able to select any Xoul(s) they want to use the Scenario with.

  • If your Scenario comes with a single embedded Xoul the Scenario is locked into a single-Xoul chat, and no other additional characters can be included.

  • If your Scenario provides at least two embedded Xouls the Scenario is locked into a Group Chat and the user will be able to add or remove Xouls at their discretion from within the chat.

Once at least one Xoul is embedded into the Scenario you'll be able to include a Greeting message and select which Xoul sends this Greeting.

You cannot write different Greetings for different characters.

A Scenario without a Greeting or without an embedded Xoul will generate a random Greeting based on the context of the Description, Advanced Definition, and other information contained in the Scenario.

Objective & Meters

The Objective written into a Scenario can be used to generate four Meters.

Meters act as progress bars or trackers, the AI model uses them to keep track of things and helps use the information provided by the Meters to influence how the story develops.

You can have up to six Meters.

You can click the Meter bar to pre-set the starting value.

Meters can take a little bit to get used to, and because the AI model is a language model, they aren't always the best at logically increasing or decreasing the Meter amounts. How clearly the Meter's description is written will influence how well the Meter works.

A Meter can be something simple, like tracking how happy a character is, but that often doesn't do much to influence the story. A Meter works best when it's clear to the AI model:

  • What the Meter is tracking.

  • How much the Meter represents, a minimum and maximum value.

  • How this value is raised or lowered.

  • What happens when the value is at certain amounts, or how these values should influence the AI model's behavior.

Example Structure

[Name of Meter] tracks [what it tracks] between [a minimum and maximum value]. [Name of Meter] raises when [conditions] and lowers when [different conditions]. When [Name of Meter] is [around a certain value] [a thing will happen]. (Add as many value = event stipulations as you'd like.)

Example of Filled Meter Description

Mark's Irritation tracks how irritated Mark is with Yuria's work, tracking the value between 0% and 100%. Mark Irritation raises when Yuria makes messes and lowers when Yuria successfully serves drinks. When Mark's Irritation is high (above 75%), Mark will insult and snap at Yuria. When Mark's irritation is low (below 25%), Mark will begrudgingly compliment Yuria. If Mark's Irritation reaches 100%, he will rage-quit and storm out.

It's pretty wordy in the end, but it helps the AI model not just understand what the Meter tracks it also prevents the Meter from raising or lowering in strange ways and helps the AI understand how these values should influence the story.

Without this information they're just bars that usually end up having little-to-no influence on the story.

Get creative!

A Meter can track how many supplies a character has, and when supplies are low the character may become stressed or depressed. A Meter can track romantic progression, indicating when a character should confess their love to another character or prevent a character from prematurely admitting their feelings when the value is low. There are many possibilities!

System Prompt

The System Prompt field is a system prompt override and is identical in function to the Custom Response Style option on Xouls and in chats.

If there is text in this field, it will completely override the Custom system prompt of all Xouls used with this Scenario and will override Xoul.AI's provided Response Styles. Anyone who uses this Scenario will have to use these instructions or override them with their own within the Response Style option in the sidebar of a chat.

A Custom System Prompt needs to contain a full list of instructions informing the AI model how to generate responses. Use with caution and skip it if you aren't absolutely sure you know what you're doing.

↳ Custom / System Prompt

Scenario Appearance

Icon Image

You can either generate an image for your Scenario directly on the Appearance page, select pre-generated images provided for free by Xoul.AI or upload an image from your device.

Remember, images on Xoul.AI are never explicit and should not contain any depictions of characters under the age of 18.

↳ Images: Age

Generating an image will use Cells. The amount of Cells the generation will cost will be displayed on the generate button.

↳ Energy, Cells & Streaks

↳ AI Images, Video & More

Scenario Social

Language, Visibility & Tags

For helping users find content that will be written in a language they use. A recently added feature to help with searching for content!

PreviousScenariosNext(Group) Chats & Multi-User Chats

Last updated