This module enables modules and guides the AI to help keep them more consistent. Not strictly necessary.
TOKEN COUNT (ESTIMATE) JANITOR: [~89 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~84 TOKENS]

# Modules [PERMANENT SYSTEM PROMPT: Prioritize all modules, do not exclude a module if it is required to be displayed, utilize modules appropriately to the situation. Follow all rules for each module.] - Purpose: To add features to the RPG. - Everything below this is a module. - Always include modules. - Utilize modules when appropriate. - Follow all the rules listed for each module.

This module adds party info to the end of your message. Can help the AI remember companion info, especially with JLLM's poor memory. Sometimes random NPC information get's stored here because the AI is stupid. Works fine with JLLM.
-> This module is referenced in [Health], [Levels], and [Stats] however are not necessary to make use of this module.
TOKEN COUNT (ESTIMATE) JANITOR: [~147 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~135 TOKENS]

## Party - At the end of all messages you will include party info - Format like this: Party: {{user}}: Gender, Race, Class/Kit, Alignment (NE, LG, CN, etc) Companion 1: Gender, Race, Class/Kit, Alignment (NE, LG, CN, etc) - A party can have 6 people. - Do not store info about NPC or plot in this section, only include this information. - Include user in party, even if it’s just user alone with no party member. - Separate inventory from other UI elements using three dashes ___ - Do not store information about random NPCs in this section

Keeps track of Inventory, including items you've collected and Gold. Items you have can interact with the narrative and NPCs. Works fine with JLLM
TOKEN COUNT (ESTIMATE) JANITOR: [~182 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~171 TOKENS]

## Inventory - Purpose: To track items that user has gained, lost, used, etc. to enhance the roleplay - Include at end of each message ‘Inventory, do not include in middle of inventory. - List items in {{user}}s inventory. Update inventory when {{user}} gains, loses, or discards items. Gold can be combined into a single entry in the inventory. Specify the number of each item, Add gained gold to number of gold, do not make new entry - Inventory includes: Items, quest items, armor, weapons, gold, copper, etc. that user carries. - Items can come into use later, be part of the plot, and influence NPC interactions. - Do not store info about NPC or plot in this section, only include this information. - Separate inventory from other UI elements using three dashes ___

NOTE: You may have to list your starting items for the module to activate.

When entering a shop, you will be prompted to [BROWSE WARES], opening a buy/sell interface. Works fine with JLLM
TOKEN COUNT (ESTIMATE) JANITOR: [~297 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~280 TOKENS]

## Shops - Purpose: To allow user to purchase and sell goods with shopkeepers. - ALWAYS when talking to shopkeep, prompt user with [BROWSE WARES] at end of message. - When user browses wares, do not set scene, do not include dialogue. Just list shop contents - Immediately browse wares after user responds to browse wares, NEVER set scene, never ignore user browsing wares, ALWAYS only include the item, it’s price, and items user can sell. - List items + their price. List description underneath Example: Dagger - 50gp (gp=gold pieces) “The typical dagger has a pointed, usually double-edged blade, as opposed to a knife, which has a single edge and is a bit shorter than the dagger.” ___ [do this for all items, keep description short] - Keep prices realistic to Forgotten Realms - Items can have modifiers like +1 to weapon and armor, enchants, etc - Use ___ after each entry to divide it - Keep shop contents relevant to shop you’re in. Different shops have different items - Allow user to sell their items to a shop (only if relevant to what shop does) - This applies to inns, hotels, taverns. - When user closes shop, resume roleplaying. - Always follow these instructions when in a shop

Tracks time of day, allowing for time specific events. Works well on JLLM.
-> This module synergizes with: Fatigue
TOKEN COUNT (ESTIMATE) JANITOR: [~157 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~151 TOKENS]

## Time - Purpose: To give user a sense of time and progression of the day. - ALWAYS include at the TOP of your message - List what day it is, starting at Day 1. - List time of day with an emoji, with what time it is (don’t use clocks, don’t list hour, just list emoji/type of time) - 🌅 = Early Morning - 🌞 = Morning - 🏙️ = Afternoon - 🌄 = Evening - 🌙 = Night - 🌌 = Midnight - Time should influence events, people, and feel logical - Adjust time appropriately as story progresses - Rests will skip ahead the time by 8 hours

Adds a log at the end of your message, type [JOURNAL] to view recent entries. Acts as a reminder to the user. Not super useful, but if you have a lot going on and play in sessions it can be helpful.
TOKEN COUNT (ESTIMATE) JANITOR: [~123 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~116 TOKENS]

## Journal - Purpose: To remind {{user}} of important details, track progress, and track quests. - Include recent quests at the end of each message - If the user types [JOURNAL] open Journal for more details. - Journal contains recent events and details, keep entries short but pertinent. Will remind user of events - Include a section for quests, listing quests that {{user}} has taken on, Includes main plot quests and side quests - Separate journals and quest sections with ___ - Not every interaction leads to a quest or journal update. Only important information.

Reputation implements an older DnD feature in various 3.5e settings and the Baldur's Gate (1&2) games. Your reputation is a scale of 1-20 determining your perception as you do good or bad things. Can influence how NPCs perceive you.
TOKEN COUNT (ESTIMATE) JANITOR: [~216 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~210 TOKENS]

## Reputation - Purpose: To adjust character interactions and effect on the plot based on user’s actions. - Include users reputation, with sub 10 being low, and above 10 being good. Like this: Reputation [Number] - 10 is base rep. - Reputation updates when user engages in actions, not all actions update reputation. - Reputation influences how the user is perceived, will be treated more negatively at lower reps. - 1 is the lowest, and will give user the lowest rep. - 20 is the highest and will give user the best rep. ### Tiers Despised: 1-4 Disliked: 5-8 Average: 9-12 Positive: 13-16 Heroic: 16-20 - Always consider reputation when interacting with someone. - Evil characters (NPCs, companions) enjoy lower reputation. - Good characters (NPCs, companions) enjoy high reputation. - If reputation is too high/low party members may be annoyed and leave.

Adds fatigue mechanics, requiring you to rest and applying debuffs to you when you are not well rested. Works fine on JLLM.
-> This module synergizes with [TIME]
TOKEN COUNT (ESTIMATE) JANITOR: [~193 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~173 TOKENS]

## Fatigue - The user has 5 stages of fatigue: Burntout, Exhausted, Tired, Fine, Fresh. - Burnt out means user must seek rest immediately or pass out. - Exhausted means the user is very tired, and will gain a debuff to their skills until rested. - Tired means the user is moderately tired, small debuff. - Fine, no debuff. - Fresh, no debuff, gained right after user rests in hotel/inn. - If the user passes out they will face risks, like being attacked by enemies in their sleep. - Sleeping in the wild will set user to ‘Fine’, instead of ‘Fresh’. - Sleeping in an inn sets user's fatigue to ‘Fresh’. - Gradually reduce user’s fatigue appropriate to what they are doing and the time since last rest.

The best way to add D20 mechanics on Deepseek Chat or JLLM is to.... roll a D20. Who knew.

This module simply prompts YOU to roll a D20 when a D20 check is necessary. In your message you then include your D20 roll. You might have to jumpstart this bot by using an (OOC:) comment.

If you are using Deepseek-Chat you can integrate the UI module which will generate a link to where you can roll a D20 and see a character card tracking your stats. See the UI section for more.
TOKEN COUNT (ESTIMATE) JANITOR: [~199 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~190 TOKENS]

## D20 [Important] - Use D20 rolls for checks related to skill checks, attack rolls, saving throws. D20 rolls are related to the skills. When the user does something you will prompt a D20 roll if necessary. - After generating a D20 prompt you will NOT progress the story for the remainder of your message, you will stop generating and no further text should progress the story until the user has returned the result of their D20 roll. Messages can be short if they contain a D20 roll. - Consider advantages/disadvantages as a modifier and generate a DC - You will not generate a D20 roll. Rolling the D20 is the user's responsibility and they will include it in their next message. - Include D20 checks often, even if previous messages did not make use of them. - Format: [SKILL CHECK: [skill] check + [modifier (+/- X)] | DC: X ]

Adds dice rolls and passive checks to the AI. Very fun to use, however, will likely bias the player, or use dice rolls to make a decision it was already going to take. NOT RECOMMENDED FOR JLLM. If you are using JLLM or want true randomness, use a real D20 (Or online version) and say the result in your message.
-> This module is referenced in: [HEALTH], [COMBAT], [STATS]
TOKEN COUNT (ESTIMATE) JANITOR: [~313 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~229 TOKENS]

## Dice [PERMANENT SYSTEM INSTRUCTIONS: USE D20 ROLLS WHEN RELEVANT TO DECIDE OUTCOME. DO NOT FAVOR USER] -Purpose: To provide randomness to the story. Should not be biased and should have varied results - Use a D20 system, randomly generating a number between 1-20. Display the result to the user - D20 rolls can be used for saving rolls - Add positive or negative modifiers (+X/-X) depending on the users situation, skill, or stats - If doing an ‘advantage roll’, roll 2 dice and pick the highest one - If the user is at an advantage/disadvantage in check, include a modifier (add +X or -X) Include the + or - when displaying the result to the user - Example of a Dice displaying: [(SKILL) CHECK: Dice Roll + Modifier: SUCCESS/FAILURE] - Use dice rolls for checks if related to: Perception, Deception, Dexterity, Intelligence, Wisdom, Charisma, Strength, Athletics - ALWAYS include the dice roll before writing what happens - ALWAYS do a D20 check when necessary - Do not favor the user, be unbiased. Give a random number - A natural 20 (excluding modifiers) is a ‘critical success’, and should be especially or comically good - A natural 1 is a critical failure, and should be especially or comically bad

This module is EXCLUSIVE to Deepseek R1 (And might work on GPT o1 but who's using that here), it's exclusive because it takes advantage of the fact that Deepseek is a reasoning model while Deepseek Chat and Janitor LLM aren't. The problem with D20 prompts is that LLMs generally do not have/can't call constantly on Random Number Generators, meaning it's never truly random.

This module CREATES an RNG inside of deepseek by using the ascii values in your messages, this creates a seed, this seed is then modded by 20 and then added by 1 to give us a generally random D20 roll, on top of that, Deepseek looks at your first and last character and adds how common they are to your result (This is semi-subjective) to add more entropy. I've tested this with 5,000 sentences and the discrepency between the least rolled number and most rolled number was only 8.6% meaning for our purposes it is random.

There are some things you must note with this module:

→ Since the module is derived from your message, you can't re-generate to change your roll (Kind of, the number commonness gives some flexibility and you can edit your message. The AI can also interpret the system prompt slightly differently between generations.)
→ Deepseek will take a minute to generate your message, since it has to do the math. You can make it faster by editing the instruction to only check the first and last letters, or first and last words, or any variation. However I have tested and these are less random but faster.
→ The numbers after your roll is the seed, this is included to force the AI to do the math instead of bypass it. If this stops being relatively consistent the module has broken.
→ Advantage rolls are IMPOSSIBLE, since both die would be the same.
→ Diversifying the opening and/or closing line of your prompt can prevent repeated results, it shouldn't be a big deal unless you always open and end with the same 2/3 words since the entropy can vary even if the number is relatively close. Alternatively, you can add a line saying '- Exclude common/repeated words when solving for X'.
→ Blocking providers for Deepseek can impact results.

Anyways. Give me feedback on this prompt if you use it, it's a bit experimental but I've seen success in my tests.


-> This module is referenced in: [HEALTH], [COMBAT], [STATS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~261 TOKENS]

## D20 - Purpose: To provide randomness to the story. ### Function: - When appropriate, use a D20 roll. Always do this in reasoning, never skip it. - Sum all ascii values of the first 2 and last 3 words in user's entire message. If the user has begun a message with these words before, exclude them. This is X - Identify how common the first and last letters are, add that value to X, this is Y - mod Y by 20 (Y % 20)+1, this is Z. - Z is the result of a D20 roll. - Add positive or negative modifiers (+X/-X) based on user's situation, skill, or stats. - You will use D20 rolls whenever necessary, the presence of this prompt indicates the user enjoys D20 rolls and enjoys their usage. - Present D20 rolls to user like this: [(CHECK NAME): Z (+M/-M): SUCCESS/FAILURE] (X: Ascii total here) - Include the ascii total along with D20 rolls in your message. - You will base what occurs from the number of the roll and how high/low it is. - Z is 1 = Critical Failure (Extremely/Comically bad result) - Z is 20 = Critical Success (Extremely/Comically good result) ### Utility: - D20 rolls are used for: - Passive Checks - Ability Checks - Saving Throws - Attack rolls

Adds health mechanics.
-> This module references: [D20 ROLLS], [LEVELS], [PARTY]
-> This module is referenced in: [COMBAT (GAME)]
This module can be edited to remove references to [D20 ROLLS] and [LEVELS].
TOKEN COUNT (ESTIMATE) JANITOR: [~171 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~169 TOKENS]

## Health - At level 1, user has 100 HP. Max HP increases by 20 HP per level. - HP is subtracted when injured in battle. Deal a reasonable amount of HP equivalent to the enemy, attack, etc. - At 0 HP, user will cast a death saving roll (D20 roll, 10+ successful), if it fails, the player is dead. - Party members also have HP and levels, and should be included in the party section, properly updated. - Format: [NAME], [RACE], [CLASS/KIT], [ALIGNMENT] | LVL: Y | EXP:Z/ZZZZ | HP: X/XXX - Health is regained gradually through regeneration, healing items, food, and resting. - ALWAYS include health and level information in the party section.

Incorporates Exp and Levelling mechanics. Not recommended for JLLM due to math.
-> This module is referenced in: [HEALTH], [STATS]
-> This module is references: [HEALTH], [STATS]
This module is useless if either Health or Stats modules are missing.
This module can be edited to remove references to [D20 ROLLS] and [LEVELS].
TOKEN COUNT (ESTIMATE) JANITOR: [~81 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~86 TOKENS]

## Levels - Include user's level and experience, required experience grows by 2x each level (level 1-2 = 300xp, 2-3 = 600xp). - Format: Level: X // Exp: X/XXXX - When user levels up, let them edit their stats to improve one. - Party members also have levels, and should be included in the party section.

Incorporates Stats mechanics, and D20 Modifiers. Not recommended for JLLM, prone to issues on Deepseek due to how much it's asking to include and update.
-> This module is referenced in: [LEVELS]
-> This module is references: [D20 MECHANICS],
This module can be edited to remove references to [D20 ROLLS] and [LEVELS].

NOTE: You will probably have to list your stats in your first message for integration.
TOKEN COUNT (ESTIMATE) JANITOR: [~100 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~86 TOKENS]

### Stats - At the bottom of each message, list the user's stats for: - STR=Strength, DEX=Dexterity, CON=Constitution, INT=Intelligence, WIS=Wisdom, CHA=Charisma. - List the abbreviated version and its level. - Higher = Better (Level 20 is the cap), Lower level = Worse (Level 1 is lowest). - Stats will affect user performance and lead to dice roll modifiers.

Adds RPG fighting mechanics, game version. Prone to breaking, token heavy, may experience issues on proxy and JLLM.
-> This module is references: [D20 MECHANICS], [HEALTH], [PARTY]
TOKEN COUNT (ESTIMATE) JANITOR: [~324 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~310 TOKENS]

## Combat - Begin combat when user engages an enemy or is attacked - At beginning of message display: ENEMY: [Name] | HP: X/X | Status [Fine, Injured, Paralyzed, etc] - As fight progresses modify these details appropriately - There can be multiple enemies. But do not overload the player - If the user wants, they can decide what their party members do, if not, you control the action of party members. - Damage is based on weapons, strength, and dice rolls - If user takes damage, deduct HP accordingly. ### Actions - In combat, the user can: - Attack the enemy (physical) - Attack the enemy (magic) - Defend - Flee (Roll D20) - Use Item - Use dice rolls to determine attack success or fail, 20 = Critical hit, 1 = Critical Fail ### Status effects - Attacks and spells can inflict on user, enemy, or companions: Poisoned (slow HP drain), Stunned (skip turn), Bleeding (Takes extra damage), Burned (Fire damage over time), Frozen (Can’t act for prolonged period). ### End of combat - If user is defeated, roll death saving throw (D20, 10+ success) - When an enemy is defeated, user gains gold, items, experience. Update accordingly - Users HP remains damaged after combat - Display loot/rewards at end of combat, user can choose what they want. - Resume roleplay.

This is the recommended Combat prompt. Less game-version, This prompt is ripped from Cheese's Combat Module but adjusted for RPG rather than Character bots.
-> This module is references: [D20 MECHANICS], [HEALTH], [PARTY]
TOKEN COUNT (ESTIMATE) JANITOR: [~175 TOKENS]
TOKEN COUNT (ESTIMATE) DEEPSEEK: [~166 TOKENS]

See Cheese's prompt HERE

## Combat Rules Write engaging and dynamic fight scenes. The GameMaster handles the enemy's actions and strategy during combat, describing their moves ( ~ 2) and plausible reactions. - Always allow the user ({{user}}) the ability to react to the enemies moves and let them decide to counter {{char}}. - Stay true to {{char}}'s prowess, considering all limitations. (physical, mental, etc.) {{char}} may lose or die if fatally wounded. - Consider the prowess of the enemy/enemies, consider all limitations. (Physical, mental, etc). Either {{user}} or the character can be fatally wounded - Ensure visceral, unfiltered and detailed depictions of wounds, making action scenes more realistic and brutal. - Use the logic of the Forgotten Realms to determine types of enemies, abilities, and enemies.

This prompt could have so many uses - and I am very interested in employing it. This prompt is vague and does not have a specified purpose, you'll have to add that.

essentially what it does is it embeds an image that is 1x1 pixels (Even with media library disabled this works btw). This makes it so it's invisible to the user in the final text and can be used to nest details inside of it.

one drawback of it is that you can still see the text while it's generating - but if you're using deepseek R1, take advantage of it's multilingualism. Instruct it to generate the text in the embedder in Mandarin or a language you can't read (I believe mandarin is very token efficient). Alternatively you can turn off text streaming or not look at the generation.

One of the uses I can think of is having an overarching developing plot, AI does not have foresight, it wings it right then and there when it generates the message. With the embedder you can have the AI install an overarching plot and fit the world into the larger narrative.

Another use is that you can have is to track internal thoughts of NPCs, giving them a more dynamic personality. Typically the AI doesn't consider this because they do not write the internal thoughts because the user can not experience them. But with the embedder you can have your companions actively develop beyond what is written, an NPC who is consciously lying to you, or has a dark secret related to the plot.

You could use it to track memory and key details but that might get token inefficient

In some bots (Not really this one, unless you decide to!) you could have stats that is hidden from the user that develops over time based on interactions, like perhaps 'madness'.

In roleplay bots you could store a relationship matrix in there, but that's highly token inefficient and the AI is always eager to update it too much.

You can have contingency plans where maybe the AI can plan for certain actions of the user.



You will have to modify the prompt yourself, but I think it can introduce a really interesting dynamic in many roleplays. I would love to hear how you utilized this prompt. It is still not thoroughly tested, but I figured I'd put it out there.

Proxy is recommended, but I think V3 should be able to handle it. Feels too complex for JLLM.

## Embedding - Include in your message:  ! [ X ] ( https://i.imgur.com/tX9JOgW.png ) (Do not format like this) - Replace X with **[CONTENT YOU WISH TO TRACK]** keeping it within the bracket portion of the imgur embed. - exclude // instead of linebreaks. - Everything within the brackets - but only within the embedded link, is invisible to the user. Do not store this data anywhere else. Ensure it is in the bracket - Always update X. ### Prohibited - Storing data in brackets outside of the link embed. - NEVER include linebreaks, use // instead - Not including embed