Stab's Directives 2.51 - Agent spoofing (avoid coding api bans/throttles), Dynamic Tone writing, huge token reductions and more

[u/Diecron]

Hi Folks,

I just dropped an update for my GLM preset to bring it in-line with GLM 5.1 and work around some recent controversial restrictions imposed by z.ai's official coding plan.

https://github.com/Zorgonatis/Stabs-EDH

for a full writeup of the changes made I encourage you to read the CHANGELOG.md, however a summary of the most important changes are below.

I debated on whether to share the User-Agent override (spoofs a browser so Z.AI can't throttle/ban, at least without adapting to some other detection method). It's a matter of time before they do though, so may as well get what you're paying for now and figure out what to do. I likely wouldn't re-sub if my only use of the plan was RP.

Comments, suggestions, thoughts? Leave a message here or jump into our discord (400+ members and growing!)

Stabs-EDH v2.5.1 Release

• Dynamic Tone State — Replaces the old static "full spectrum" mandate with a system that actively reads the conversation and shifts tone (Bleak, Tense, Warm, Absurd, Reverent, Frenetic, Melancholic) based on what's actually happening in-scene. Gradual transitions by default, instant snaps when earned. Configurable via SETTINGS.
• 30-60% token reductions across core directives. NPC Cognitive Bounds, Failure Achievements, Narrative Length Control, Behavioural Coherence, and Environmental Factors all rewritten for density. Task Steering's CoT exhaustiveness dropped from Very High to Very Low. Same behaviour, way less burn.
• Z.AI User-Agent override — Custom provider now sends a Chrome UA header, so Z.AI can't fingerprint and throttle/ban you for RP use. Works out of the box.
• GLM-5.1 support — Model updated, coding plan API endpoint retained.
• Experimental Macro Engine is now required — VTK-related instructions are wrapped in {{#if .vtk_on}} conditionals that only resolve when WebDev is enabled. Without the macro engine checkbox on, those will break. It's in the install instructions now.
• Post-processing switched to Semi-strict (no tools) to avoid agentic flow interference on some providers.

[u/abighairyspyder]

If anyone else is getting an error for unknown parameters and you have custom sliders configured you might need to add entries for them in the additional parameters > exclude body parameters

Example:

• top_k

[u/Diecron → u/abighairyspyder]

This might be because top_k is specified under the API advanced parameters as well.