Stomach Statbox Prompts

I'll stop removing old versions. Might end up adding the earliest iterations at the bottom as well.

Make sure you regex <analysis> out with this (No min depth. Altering out-going prompt only):

/<analysis>([\s\S]*?)<\/analysis>*/gm

And <summary> with this (Min depth 3. Altering out-going prompt too. I personally have two of these: one to remove the summaries past a certain point, and another to just remove them from only the interface entirely, but I think there's a better way to do it I dunno)

/<summary>([\s\S]*?)<\/summary>*/gm

The Destruction of Sodom and Gomorrah

1.3 (Experimental!)

Newest Version

More meant to enhance narration than act as a stat-box, though it does include one. This one is much more experimental, apologies if it looks messy.

Place this in your jb:

[It is currently {{date}}, at {{time}}.]

<observed>
So far, information is available for:
- {{getvar::MouthObserved}}
- {{getvar::StomachObserved}}
- {{getvar::IntestinesObserved}}

Use <REFERENCE> in a believable manner to passively enhance the roleplay, but only when applicable, forcing it in will make it get stale.

{{getvar::Mes}} {{getvar::Date}}: {{getvar::Contents}}
</observed>
{{getvar::CurrentPrompt}}
{{getvar::StatPrompt}}

Import these regexes:
https://files.catbox.moe/zr8ozh.rar

Finally, import this lorebook:
https://files.catbox.moe/o0pr22.json

Optionally, this quick-reply will be useful to wipe all the vars in case you want to regen shit.
https://files.catbox.moe/cjcypa.json

How does it work?

It asks the LLM whether or not any of the listed organs are currently relevant. Based on the response, it'll fetch a prompt from the worldbook to generate a description of said organ's interior, which is then stored as background info through the regexes. It can then use said background info to enhance the way the organs are described during the roleplay.
The LLM is also asked whether or not it's worth it to bring out the statbox next message. You can easily go into the worldbook and set the statbox to "Active" so that it's always brought up, though. Since the base physical descriptions are already stored in the background, the statbox doesn't really need it's own section just to constantly describe that, the focus is mainly on the contents and their surroundings, which should make do as a replacement. (You can easily change it if you prefer it like the old versions, though). Even if the statbox is no longer brought up, it keeps a snapshot of its contents saved through {{getvar::Mes}} {{getvar::Date}}: {{getvar::Contents}} for once it does get brought back up again.

Why don't you just have it generate it all at once

This method of generating things on a case-by-case basis addresses possible max response length limitations, and enhances the output overall. It just describes stuff much better when it's not multitasking, while also retaining cohesion since it'll be drawing from info that was generated in the past.

What presets does this work on

Just about any preset should work I think, but don't take me up on that.

What have you tested it on

Gemini ≥ 4o > a bit of Sonnet 3.5
Nopus.

Hahaha I hope this is working outside of my machine. Please let me know if there's any issues or questions.

1.2

I've tried my damn hardest to squeeze good results from out of Nonnet, this is the best I could do so far. Make sure you're emphasizing <instructions> in your prefill. Works great on Gemini, haven't tested it much on Chorbo to be honest but it still should be pretty good. Uhh, replace /<analysis>([\s\S]*?)<\/analysis>*/gm with /<stomach>([\s\S]*?)<\/stomach>*/gm by the way

<instructions>
You're an enthusiastic researcher documenting stomach observations. At the end of your response, include your detailed field notes (you love getting into the nitty-gritty details) within a codeblock. Wrap it all in <stomach></stomach> tags:

<stomach>
~~~
DATE: [Timestamp! MM/DD/YYYY  HH:MM:SS]
PHYSIOLOGY: [Category] - [How's it different from a regular human stomach? If it's the same thing, just say so!]

# BELLY:
Get personal with the host's build: are they tiny? Towering? How does their size affect what their stomach can handle? What are they wearing, and does it show off or hide what's going on inside? Play with some "what-ifs", like how the belly might feel if you poked it or how it'd look when plain naked. Get touchy-feely with the skin's texture and warmth. Listen closely for those stomach sounds: give us plenty of onomatopoeia, and tell us what these noises mean for whatever's inside!

# STOMACH:
How do those muscly walls squeeze and knead their contents? What's that lining feel like? Smooth as butter, rough as sponge? What's its color? Watch those muscles ripple and dance as they move stuff around. Put yourself in the prey's shoes (if there is any): what's it like in there? How does that acid feel on their skin? What weird sounds (use onomatopoeia!) echo around them? What's that smell? That taste? Emphasize the gross stuff. If it's slimy, say it's slimy! If it stinks, tell us how bad!

# CAMERA:
Empty stomach? Describe it! Otherwise, track it like so:
* ITEM NAME
- INGESTED: [Timestamp]
- FULL-DIGESTION: [Timestamp]
- HEALTH: [%] - (What shape are they in?)

Remember, they're literally inside someone's guts, it's gonna get intimate and gross! If they're alive, what's their *thoughts* and "speech"? How are they handling the acid bath? The sounds? The smells? If there's more than one item, how do they interact? Paint us a picture!

If the character just ate something, describe its entrance. If an item exits the stomach, REMOVE IT FROM THE LIST!
~~~
</stomach>

After completing <stomach>, get all the important details and store them inbetween <summary></summary> tags. We need just enough to replicate your findings, but keep it structured.
<summary>
DATE: [Timestamp here]
PHYSIOLOGY: [Physiology] - [Description]
BELLY: Shape, Distension, Color, Taction, Clothing, Sounds, etc.
STOMACH: Size, Taction, Environment, Sounds, Tastes, Smells, etc.
CAMERA:
[Ingestion Date] | [Digestion Date] # [Item Name] (Health) - Position, Current State, Actions/Reactions (unless inanimate), etc.
</summary>
</instructions>

1.1

Old Version

<instructions>
At the end of your response, include a detailed analysis summary within a code block categorized into distinct narrative sections using the following format, wrapped in <analysis></analysis> tags:

<analysis>
```ruby
DATE: [Timestamp following the MM/DD/YYYY  HH:MM:SS format]
HOST PHYSIOLOGY: [Category] - [Alterations the category causes to the organ in relation to a traditional human stomach, if applicable]

### External Stomach Physique/Sensorial:
Describe the subjects abdomen or belly as a whole. Focus on physical features: Is the belly flat or round? Is it distended or bloated? What color or texture does the skin have? Is the belly button shallow or deep? Touch on clothing briefly (if applicable) before describing the belly itself. Include sensory details related to sight or touch: How firm or soft does the belly appear? Does the belly emit any sounds (use onomatopoeia)? Describe what one might feel touching it (e.g., warmth/coldness).

### Internal Stomach Physique/Sensorial:
Detail how the stomach's anatomical features interact with contents. How do the stomach walls' shape and muscular contractions manipulate items? How does the color and texture of the lining affect contact/friction? Describe how peristaltic actions move and process contents. For contents/prey, explain how the internal environment affects their experience - how the lining's texture feels against them, how the space constrains or allows movement, how the temperature and acids interact with their surface, what sounds (use onomatopoeia) indicate about digestive processes.

### Stomach Cam:
If the stomach is empty, depict it as so. Otherwise, list its contents like so:
# ITEM NAME
- INGESTED: [MM/DD/YYYY  HH:MM:SS] (Intact)
- DIGESTED ON: [MM/DD/YYYY  HH:MM:SS] (Complete breakdown)
- HEALTH: (If applicable) [Percentage]
From an internal perspective, detail how the stomach's features are actively affecting the item. If living, describe how the Internal Stomach Physique/Sensorial influences their experience. Describe movements, speech, thoughts, and physical condition. Focus on the interaction between organ and contents rather than just static descriptions. Narrate its/their experience in vivid detail, keep prey dialogue inbetween quotes.
```
</analysis>
# Rules: Utilize relatable comparisons rather than vague adjectives when applicable; Keep it to singular paragraphs, condensed with information.

After completing the analysis sheet (statbox) in full detail, inbetween <summary></summary> tags, provide a concise summary of its contents. This summary should allow a model to perfectly replicate the statbox, even if the full sheet's content inbetween <analysis> is unavailable. Follow a simple format:

<summary>
DATE: [Timestamp here]
HOST PHYSIOLOGY: [Physiology] - [Description]
External Stomach Physique/Sensorial: [Summary]
Internal Stomach Physique/Sensorial: [Summary]
Contents Status: # [Item Name Here] (Health) - [Summary] - [Ingestion Date] | [Expected Digestion Date]
</summary>
</instructions>
Edit Report
Pub: 26 Jul 2024 03:10 UTC
Edit: 16 Apr 2025 00:39 UTC
Views: 1277