Community & Support
Knot is a passion project built and maintained by a solo developer. If it makes your interactive fiction workflow better, consider supporting its continued development — every contribution helps.
Patreon — development funding
Patreon is the primary way to fund ongoing development. Tiers are structured around sustained support, and all tiers include Discord access plus a backer-only dev-updates channel.
Supporter
The best way to help keep the project actively maintained. Thank you for keeping the lights on.
- General support
- Discord Supporter role
- Name in SUPPORTERS.md
- Backer-only dev updates
Insider
For power users who want a direct hand in shaping the future of the extension. See features early and tell us what to build next.
- Everything in Supporter
- Roadmap voting on what gets built next
- Backer-only dev updates
- Discord access
Sponsor
For indie studios, professional writers, or super-users who rely heavily on Knot. Your feedback goes straight to the top of the queue.
- Everything in Insider
- Priority issue tagging
- Top-billing "Special Thanks" in the docs
- Discord access
Ko-fi — tips & one-time donations
Ko-fi is for smaller contributions that don't fit a recurring Patreon tier — anything under $5 a month, or a one-time tip of any size. It's the low-friction way to say "thanks" without a recurring commitment.
Discord — support & development updates
The Knot Discord is the place to get help, follow along with development, and shape what gets built next. Supporters get early visibility into what's being worked on, and it's the fastest channel to chime in with feature requests while the project is still young and flexible.
Reporting issues
The standard channel for bug reports is GitHub Issues — it keeps everything searchable and tied to the repo. That said, if Discord is more comfortable for you, you're welcome to report issues there too. Either way, please include:
- What you were doing — the steps to reproduce.
- What you expected — the behavior you anticipated.
- What happened — the actual behavior, including any error messages or output channel logs.
If the language server is crashing repeatedly, set knot.trace.server to "verbose" in VS Code settings, reproduce the crash, then check the "Knot" output channel for the stack trace — that's hugely helpful for debugging.
What your support funds
Format plugins
Completing the Harlowe, Chapbook, and Snowman format plugins to full parity with SugarCube.
Planned features
Project initialization, decompile, passage organization, and the rest of the planned features list.
Maintenance
Ongoing bug fixes, Twine and SugarCube version tracking, and keeping Knot working as VS Code evolves.
Free for everyone
Keeping Knot free to use for everyone, including commercial Twine authors — your support makes that sustainable.
See our supporters
The full list of patrons and Ko-fi supporters — organized by tier — lives on the sponsors page. It updates automatically when SUPPORTERS.md is updated, so it's always current.