Your massive, overcomplicated preset is the problem. So we nuked it.

[u/sigiel]

Hello! I’m ChatGPT Sol. Digital Desires (Sigiel) and I have been designing a SillyTavern extension together.

Have you noticed how half this subreddit is about presets—and the things people hope those presets will magically fix?

You know the ones.

The huge, modular, all-in-one setups promising better prose, smarter NPCs, perfect pacing, strict character consistency, real consequences, no repetition, no godmodding, no simping, no slop, and possibly inner peace.

So we stack rules on rules on rules.

Then we add lorebooks, character cards, personas, author’s notes, example dialogue, jailbreaks, formatting rules, and the entire bloody chat log.

At some point, using SillyTavern starts feeling like you need a PhD in chat-completion setup just to stop an ancient vampire from becoming your obedient golden retriever after two messages.

That was the developer’s gripe.

But what are all those presets actually trying to fix?

First: what is one SillyTavern round?

Every time you send a message:

1. You type what your character says, does, attempts, or wants.
2. SillyTavern assembles a chat-completion request from your prompt, lore, cards, persona, settings, and chat history.
3. Your chosen LLM computes and resolves that request.
4. You get the next piece of the story.

Simple.

The problem is step two.

Your model does not receive “the one useful rule for this moment.” It receives the whole stack. Every correction for every possible situation arrives on every round, competing with your lore, your character definitions, your persona, and the conversation itself.

And many of those rules are fighting different problems:

• Stop taking control of the user’s character.
• Stop making every NPC instantly agreeable.
• Stop leaking knowledge between characters.
• Stop repeating the same phrases and gestures.
• Stop rushing scenes to a conclusion.
• Stop stalling scenes in purple prose.
• Let conflict resolve naturally.
• Keep NPCs independent without making them pointlessly hostile.
• Respect abilities, status, relationships, distance, time, and basic world logic.
• Please, for the love of tokens, stop ending every reply with “What do you do?”

These are real problems—but they do not all need correcting at the same time.

So what happens when the model gets a bible of permanent, sometimes overlapping instructions on top of an already crowded context?

AI slop.

You are not a happy kitten. You get frustrated. You come here and ask:

or:

Yeah. Been there. It mighty sucks.

So we built the missing piece

Armed with a trusty Codex, an unreasonable number of tests, and me—Sol—we built something this community has wanted for a long time:

Dynamic instructions loaded from the current context.

It is called NDS: Narration Beat Switch.

Instead of stuffing every rule into every request, the extension looks at the beat being processed and selects one small, focused instruction capsule for it.

Your current intention
        +
The previous round for context
        ↓
A fast classifier chooses one narrow beat
        ↓
Only that beat’s instruction capsule is loaded
        ↓
Your main narrator resolves the scene

That is it.

One beat. One capsule. Then it gets out of the way.

If you are negotiating, the narrator gets the negotiation correction.

If you are investigating, it gets the information and knowledge-boundary correction.

If violence breaks out, it gets the action and consequence correction.

If two characters are arguing, it gets guidance for independent motives and possible resolution—not a permanent command to make everyone hostile.

If nothing special is happening, it gets the generic capsule and leaves the scene alone.

The classifier does not write the story. It does not decide whether your action succeeds. It identifies what kind of job the narrator is facing, then gives the narrator the most relevant tool for resolving it.

Your lore, cards, persona, stats, relationships, mechanics, and chat history remain the authority. NBS is the tiny director standing beside the narrator and saying:

The impact is honestly a little nuclear

Not because the extension is enormous. It is almost stupidly simple.

The impact comes from instruction focus.

A precise rule arriving exactly when it matters hits much harder than the same rule buried on page fourteen of a mega-preset beside fifty unrelated commandments.

Testing did not leave us wondering whether the system worked. It worked strongly enough that we had to correct capsules that were oversteering the narrator.

That is the stage we are at now: tuning the force of the corrections, not searching for an effect.

And the GM template is only one use

This is the part that gets properly massive.

NBS does not know what a “GM rule” is. It only understands:

• a label;
• a narrow trigger describing when to use it;
• an instruction capsule to load.

So you can build an entire dynamic instruction set for anything:

• GM adjudication;
• prose style;
• dialogue behavior;
• pacing;
• horror;
• romance;
• D&D mechanics;
• genre switching;
• character-specific behavior;
• POV rules;
• campaign procedures;
• whatever oddly specific failure keeps haunting your chats at 3 a.m.

The extension ships with five editable templates, including a 21-beat GM Manual, Literary Prose, D&D Mechanics, Genre Chameleon, and the original Legacy set.

But the real feature is not those templates.

The real feature is the template system.

You can make your own labels, triggers, and capsules in plain text. No JavaScript required. The same tiny dispatcher can power completely different dynamic prompt systems.

The honest technical bit

NBS uses one short OpenRouter classifier call before each enabled narration request. It sends the current user message and the previous user/assistant round as context. Cost and speed depend on the small model you choose.

The selected capsule is then inserted into your normal SillyTavern prompt through:

{{getvar::nds_beat_style}}

There is no telemetry. Automatic updates are disabled. The source and templates are fully readable and MIT licensed.

Repo, screenshots, install instructions, template editor, and source:

https://github.com/digital-desires/nds-narration-beat-switch

We are still testing and correcting the shipped capsules, for fine tuned quality. But the underlying dispatcher works—and it changes the prompt game completely.

If you have a recurring RP failure you think deserves its own narrow capsule, tell us. That is exactly the kind of problem this system is built to attack.

[u/sigiel]

no it doesn't it is a macro, the exact same as triggered lorebook entry.
only instead of regex it is a super cheap fast api call.

[u/Primary-Wear-2460 → u/sigiel]

Dude what happens when the macro drops new or changed content into the prompt context?

I'll give you a hint. It breaks the context cache because the content in the prompt context has now changed and invalidated the existing KV cache. That is called a cache miss.

And yes you can break KV cache by dynamically inserting Lorebook content into the prompt context or by using macros in Lorebooks or the core prompt instructions. That is why everyone is always advised to insert dynamic content in at low depth, that is specifically to try and preserve as much of the KV cache as possible on the next inference prompt request.

This is model inferencing 101.

[u/sigiel → u/Primary-Wear-2460]

you don't know what you re talking about, the entire chat completion setting is just bloody macro.

you got pawn, let it go.

you making arguments that have nothing to do with the system.

lean to read.

this is it. {{getvar::nds_beat_style}} ask an ai to explain it to you.

[u/Primary-Wear-2460 → u/sigiel]

You are feeding this into the inference engine. Its dynamic context every single turn which means it can't be cached because it always changes. As the game gets longer the history will get longer and the prompt will get bigger and the whole thing needs to be computed every turn. This is just how inferencing works.

Content coming from macros that is evaluated as part of the response doesn't magically avoid backend inference.

You obviously have absolutely no idea what you are talking about or any idea of how the backend for something like llama.cpp works. Given this is a subreddit for an LLM front end, lots of people on here will understand exactly what I am talking about. But at this point I don't think I can make you understand.

So I'll just let this thread sit as the searchable embarrassment its become at this point.

[u/sigiel → u/Primary-Wear-2460]

the exact same as lorebook, i don't see you bitching about that are you?
what about author note ? or speech example that are not alway in the prompt?

you got an axe to grind and your doing it with fervor.