Scenario Creation Pop-up to help Users create scenarios
FictionLab's Create Scenario Page
FictionLab focuses mainly on roleplay scenarios with multiple characters instead of casual chatting with a bot. Therefore, it has multiple sections that may feel different from other AI chatting services.
{% hint style="info" %}
Want to get feedback about your scenarios? Join our [Discord Community](https://discord.gg/SKcb2C7HjH) and share your scenario!
{% endhint %}
***
### Main Details Section
The Main Details section is used to explain the scenario and make it look appealing to the Users of FictionLab. The details in this section are *not readable by the AI*, but putting effort into this section will make your scenario more interesting for other Users.
Main Details Section
**Main Image**
The box on the left is for the scenario’s main image which will be the first thing that Users see. Choose an image that is visually appealing and relevant to the scenario. You can either:
* **Upload an image** by clicking the **"Upload Image File"** button.
* **Generate an AI image** by clicking the **"Generate Image"** button.
**NOTE:** The minimum dimensions for the scenario main image is 512px by 512px. Images with lower dimensions will return an error.
**Scenario Name**
Choose a name that is **descriptive yet simple**. For better readability, use **Sentence Case** (e.g., *Mystery in the Fog* instead of *mystery in the fog*).
* Minimum Number of Characters: 1
* Maximum Number of Characters: 35
**NOTE:** Using special symbols or UNICODE for your Scenario Name may make it unreadable by the Search feature, which may limit the scenario's visibility.
**Scenario Description**
Write a **short and clear** description that gives Users a quick understanding of the scenario before they dive deeper.
* Minimum Number of Characters: 50
* Maximum Number of Characters: 250
**Scenario Tags & Genres**
Select up to **five genres** that best represent the scenario. Your choices affect how easily other users can find it.
* Example: An **alien-themed** scenario should include the **"Alien"** genre.
* Example: A **detective story** might fit best under the **"Mystery"** genre.
**Bounty & Challenge Participation**
Bounties and challenges are events held by the FictionLab Staff. They will have a specific theme/genre, and Users should create scenarios with that genre to participate.
Please read the challenge announcement and rules before participating in bounties. Participating in bounties will add a Bounty Badge to the User's profile. Winners will get a separate Bounty Winner Badge at the end of the event.
So far, the bounties are as follows:
* [Temporal Tangles](https://fictionlab.ai/?post=time-bounty-2025) (April to May 2025)
* [Neon Skies](https://fictionlab.ai/?post=neon-skies-2025) (June to July 2025)
* [Capes and Chaos](https://fictionlab.ai/?post=capes-n-chaos-2025) (July to August 2025)
* [Haunted Tales](https://fictionlab.ai/?post=haunted-tales-2025) (September to October 2025)
* [The Longest Night](https://fictionlab.ai/?post=the-longest-night-2025) (November to December 2025)
* [Love at First Fight](https://fictionlab.ai/?post=love-at-first-fight-2026) (January to February 2026)
* [As the World Burns](https://fictionlab.ai/?post=as-the-world-burns-2026) (February to March 2026)
***
**Introduction Section (Optional)**
The introduction section is an optional section where you can talk about the scenario and ease the User into the world that you created. It can also be used to summarize and present your scenario details in a readable, visually-appealing manner.
You can add images, custom fonts, and other styling to this space. The introduction section is purely cosmetic and *it is not readable by the AI*.
This section is *required* if you choose to Hide Scenario Prompts (toggle).
***
### Scenario Building Section
The Scenario Building section contains details that will be read by the AI, allow it to create a narrative and run the roleplay. Pay careful attention to the instructions below for the best experience with your scenarios.
Scenario Building Section
**Backstory**
The Backstory/World Details provides context for the AI, explaining how the characters arrived at their current situation and offering details about the scenario’s world.
* Use **`{{user}}`** to refer to the player's character.
* Address other characters **by name** instead of using placeholders like `{{char}}` because `{{char}}` is **not supported** in FictionLab.
* Do not define character personalities or appearances in the backstory. This should be done in the **Story Characters** section.
{% hint style="info" %}
If you're having trouble coming up with a detailed backstory, you can use the AI Writing Assistant located in the bottom right corner of the backstory box! Just write the general idea of the roleplay there, and it will start writing for you.
{% endhint %}
**Greeting Message (Optional)**
The greeting message is the **first message** sent by the AI when the scenario starts. Although this is optional, a greeting message is great for enforcing your narrative format and to create a starting point for your characters.
* Use **"quotes"** for dialogue.
* The greeting message **strongly influences** the AI’s writing style, so craft it carefully to match the tone and perspective that you want. For example, writing in third person perspective on the greeting message will make the AI more likely to use third person perspective throughout the roleplay.
**Custom Scenario Instructions (Optional)**
Custom scenario instructions allow you to **modify the AI’s behavior** and define **specific events** within the scenario. You can also use it to dictate how the AI responds in different situations.
* Examples of custom instructions:
* *"If Joe finds the hidden lever, a secret door will open in the library."*
* *"Jinny becomes shocked when {{user}} tells her that he's a werewolf"*
* *"Joe speaks in a heavy redneck accent"*
*More information about Custom Scenario Instructions can be found* [*here*](/fictionlab/detailed-guides/custom-scenario-instructions.md)*.*
#### **Lore Pieces**
The **Lore Pieces** section is where you define the key elements in your scenario. Defining them is very important and increases the memory coherence of the AI significantly. \
\
Lore pieces should be activated in order to appear in the context(AI's memory). They are activated automatically during the chat when needed, but you can improve the chances by putting right weights, linked pieces and triggers.
There is a **global character text limit** which is 100,000 for free users and 250,000 for FictionLab+. 10,000 characters is allowed per lore piece.
**Type**
Determines the category this piece belongs to. Character-type lore pieces have additional fields for avatar and playability
**Title**
Display name for this lore piece. Use character's name for character-type pieces.
**Description**
Short summary of what the content is about for AI semantic-matching. Autofilled from content if left empty.
**Content**
Describe the piece's content in details. The full text is injected into AI's memory when the lore piece is activated. \
For character-type lore pieces:\
Describe the character’s **appearance, personality, and motives** in natural language. This helps shape how the AI portrays them in interactions.
* Do not use `{{char}}` or any custom formatting, just write naturally.
* Focus on who they are, how they behave, and what drives them.
**Weight**
Controls how likely the piece is to be included in AI's context. Higher weight = higher priority.
**Character Settings**
* *Pinned*: Pinned pieces are always included in AI's context, budget permitting. Use sparingly, as pinned pieces reduce context available for other pieces.
* *Playable Character*: This allows User to select a Story Character at the start of the scenario.
* *Hidden Character*: This hides the character from the POV slash command and from the scenario prompts when it is visible.
* *Smart Activation*: When enabled, AI uses semantic understanding to activate this piece based on context relevance. When disabled, the piece will only activate when its trigger words are mentioned.
**Triggers**
Keywords that activate this piece. When these words appear in the conversation, this piece may be included in the AI's context.
**Linked pieces**
Connect this piece to related pieces. Links boost co-activation scoring, so linked pieces are more likely to appear together. For example, if character has a lore-piece about their house, then it's a good idea to link them.
### Scenario Settings
These settings allow you to customize how your scenario behaves and how Users interact with it. In most cases, you only need to toggle Sensitive Content depending on the scenario that you're making.
**Force Character**
Select a character that the User must play as in this scenario. If left blank, the User can create their own character.
**Separate User Character**
* **Enabled** (On, Default): The User's character is treated as separate from other scenario characters.
* **Disabled** (Off): The User must choose from the characters defined in the scenario.
**Sensitive Content (18+)**
* **Enabled** (On): Marks the scenario as containing mature content.
* **Disabled** (Off, Default): The scenario is safe for general audiences.
**Public Scenario**
* **Enabled** (On, Default): The scenario is visible to all users.
* **Disabled** (Off): The scenario remains private and only accessible to the creator. Private scenarios can still be shared by using the Sharing link.
**Allow Story Customization**
* **Enabled** (On, Default): Users can modify aspects of the scenario to personalize their experience. Clicking Customize will create a "Modified" copy of the scenario which is strictly private. Any changes to the original scenario will not affect a Modified copy, and vice versa.
* **Disabled** (Off): The scenario cannot be Customized i.e. a Modified, private copy of it cannot be created.
**Hide Scenario Prompts**
* **Enabled** (On): Backstory and other fields, except introduction, will be hidden from the user. Useful for avoiding spoiling certain mechanics. Users can still read prompts if "Allow Story Customization" is enabled.
* **Disabled** (Off, Default): Users will be shown the backstory and other prompt fields when viewing the scenario page.
**Allow Commenting**
* **Enabled** (On, Default): Users can comment on your scenario's comment section.
* **Disabled** (Off): The comment section is disabled.
**Delete Scenario**
Permanently removes the scenario from FictionLab. The delete button is visible if you customize an already created scenario and are the creator of it. **This action cannot be undone**.
**Duplicate Scenario**
This button allows you to create a clone of the scenario for editing purposes. You can use it to create multiple variants of the same story. Duplicate scenarios can't be published without heavy editing because FictionLab might flag it as spam.
### Scenario Guidelines
We take User Safety very seriously and require that every scenario follow our [TOS](https://fictionlab.ai/terms-of-service) and guidelines. Before creating a scenario, you agree to follow the terms shown in the pop-up.
Any scenario set as public will go through our review team to ensure it complies with our rules. If we find flaws or issues with your scenario, we will decline it from being publicized and require you to make changes before submitting it for review again. After editing, the scenario will be reviewed again.
Private scenarios are not reviewed by our team, but the same rules still apply. Your account is at risk of getting banned if we find content that violates our [terms of service](https://fictionlab.ai/terms-of-service).
### Draft Scenario
The draft scenario feature allows you to save your scenario with minimum details. To enable the **Save as Draft** button, the scenario must have at least one (1) character in the Scenario Name and Scenario Description.
At the bottom of the scenario builder, you will see a list like so:
**Requirements to Publish Scenario**
* The red text indicates details that are REQUIRED to save the scenario as Private or to publish it as a Public Scenario. Remember to follow [FictionLab's Terms of Service](https://fictionlab.ai/terms-of-service)!
* The orange text indicates details that are OPTIONAL to create a more engaging scenario.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://fictionlab.gitbook.io/fictionlab/getting-started/quickstart.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.