Skip to main content

Add Variable Support for Plugin Expansion

Feature Request
I conducted a search, but there doesn't seem to be much in the way of anything going on since the early part of 2024 for a request for a variable. I'd like a feature request for this, please. This would be a significant improvement to plugin usability. The current Expand tool within Sudowrite has some sort of connectivity with forward text so there are possibilities there. Where there's a will, there's a way. Necessity is the mother of invention. Etc, etc. 🫡 via: Nadgers in Discord
Posted by An Anonymous User ·
Status: Completed2 comments

This request was merged into another request

Comments2

  • Amit Gupta changed status to Completed
    Team•

    Oct 15, 2025

    Pinned

    following_text is now available to newly made plugins. It will be available to existing plugins tomorrow.

  • Sinclair Caldicotte

    •

    Oct 3, 2025

    This isn’t a hypothetical. Novecrafter has had <textafter> for well over a year — I was using it myself when drafting The Library of Debauchery — and it makes an enormous difference. Having both <textbefore> and <textafter> means expansions flow seamlessly into what follows, instead of ending on an awkward edge.

    Sudowrite already supports {{ preceding_text }}. Adding {{ following_text }} isn’t reinventing the wheel, it’s the missing half of the context equation. It brings parity with tools that are already out there and gives writers the continuity we need for professional-level editing and expansion.

    This wouldn’t just benefit one or two edge cases — it would be a boon to every plugin writer and every author who wants smoother, more natural outputs. The difference between “good” and “indistinguishably human” often comes down to exactly this kind of contextual threading.