Changelog

How can we make Sudowrite better?

Please tell us how we improve Sudowrite for you.

Worldbuilding Changes Needed

I recently came over from an outdated platform to this solution and found that the main component of Sudowrite is amazing and light years ahead of your competition, especially when I tested out several other options writing just under 100,000 words in 3 different programs. However I am hesitant to move my current character information over. There seems to be a lack of functionality in your worldbuilding component. Even an antiquated system such as Scrivener provides more organization context within the worldbuilding format. Don’t get me wrong, comparing Sudowrite to Scrivener is similar to comparing night and day. Sudowrite is superior for writing in every way 1990’s vs 2020 technology. I would ask that some attention is given to the worldbuilding before you fall behind to another competitor as I have sampled some better worldbuilding management features from other programs. Your worldbuilding component has a great foundation with the ability to shut off visibility in each field from the AI. Its also easy to change field names or add traits. But compared to your competition that is the extent of your superiority. Once I started adding new characters and spell skills and their tiers, I found myself scrolling endlessly down a list of names and fields. What I am looking for is an organizational process to manage both the world and the characters. I have 2 books as old school fantasy novels and 2 books as LITRpg as their sequel. And here lies the problem, with one of my LITRpg characters. I have 18+ field boxes. 6 for current spells 6 non-visible fields for spell progression, background, behavior, family (No tie in option in sudowrite), Growth field for life altering events, field for plot exposed both visible and non visible, tie in boxes from the prequel books. So 19-20 fields? What Sudowrite’s needs is more organization within characters and worldbuilding. The suggestions I am mentioning are because I was unable to find fixes in your help and through you tube tutorial videos which most are outdated by a year. If I could suggest a few fixes. Adding in filters, If I want to look up historical events or LITRpg messages that I created a worldbuilding box for. I can select the custom name in the filter and it will bring up all those option. In the fantasy books in Scrivener, I have 221 characters with less than 30 that are ongoing characters. Scrolling in the current sudowrite aspect would be difficult. There I just select a drop down arrow and I pull up the characters while I am writing. Click on that character and I have more drop down options. and so forth. A multiple filtering option for LITRpg if possible. For example LITRpg, filter that category and then subcategory system messages, achievements, warnings from spell misfires for example. Characters need to be easier to manage. I don’t need to see a character that is part of a plot line from book 1 not appearing until book 5. Even though I am adding references to that character mentioned as I write. That character doesn’t need to be scrolled through every time I look for a supporting character. In Sudowrite in 109,000 words I currently have 14 characters that I don’t need to see for another book or 2. I have 21 worldbuilding events that are hints at future events. 11 LITRpg events, 6 cities I mentioned with characters referenced in them, 4 academies that are at this time only as references with professors who came from those schools and talks infrequently about them. These are things I don’t need to constantly fill my list and I should have a process to move them to avoid them from cluttering my field of my main story plot characters but easily accessible to add notes into as they are referenced. In Squibler I had a drop down option to pull cities down, then I have buildings, people, events, misc characters (incase I need a name of someone later on) and I can drop those fields down to find who or what I am looking for add the notes and done. In Sudowrite, I have to scroll through all the characters or fields to find it. Maybe an option to put it into future events so it removes it to another field like worldbuilding, characters, outline, synopsis Spell management- Killer option in Sudowrite. I think Dabble and Squibler were made by the same guy as I tested them as they are very similar but Dabble had a plot management tool which is similar to Sudowrites but A lot more easier to use and build. With every character having spells in my books (for the most part) Having to scroll through the fields is painful. In dabbler I click on the plots window and then the characters, click on the character and one of the blocks or sticky notes is the the spell fields. I open it. I have a blocks with the current spells, horizontally 1-6 and below them I have a block (closed or a single sticky note) with the spells future progression. In Squibler, I click the character name, go to the spell, click the spell and it moves me from the writing window to the spell information. Then I click on the chapter I was writing and I have my information but its not always fluid in the supposed process. In Sudowrite, I open another window on PC, scroll to the spell (I have it in both character and worldbuilding because 20 fields were too much to scroll through to get that one spell information. And I open it up and get the information. When I update it in Sudowrite I update both the character and the worldbuilding spell. Maybe drop down fields under the character to choose what I am looking for?

christopher morin About 1 month ago

💡 Feature Request

Adjust Billing and Membership Correlation

Sudowrite is a great tool and I appreciate what the team has built, but I would like to suggest a change to how billing and memberships are handled because the current system can unintentionally shorten a user’s paid access time. Right now, the system appears to charge on a fixed billing date (for example, the 1st of the month). If the payment does not clear immediately, Sudowrite suspends membership features. However, when the payment eventually processes, it can take several days for the system to recognize the payment, and in some cases the account does not automatically reactivate until support intervenes. Because the billing date does not reset after the payment actually clears, the result is that users may lose multiple days of paid service. For example, last month my payment processed about two weeks after the original billing date, then support manually resynced my account to register the payment a week after that, but the next billing cycle still occurred based on the original date. This meant I effectively paid $29 for roughly a week of access instead of the full 30 days. A few alternative billing models would solve this issue and align with how many subscription services operate: Option 1 Pause service if payment fails, but once the payment clears, restart the subscription and begin a new 30-day billing cycle from that date. Option 2 Allow a grace period and keep service active until the next successful payment, ensuring users always receive the full 30 days of paid access. The key point is that if customers are paying for 30 days of service, they should reliably receive 30 days of service. Adjusting the billing cycle to start when payment actually clears would create a much more consistent and fair experience. I hope the team will consider improving this part of the system because Sudowrite is an excellent writing tool and refining the subscription mechanics would make the overall user experience even better.

Breanna M 23 days ago

1

💡 Feature Request

Minimize the Worldbuilder traits

I’d like to strip down these traits, minimize them, making it easier to scroll all the way to the bottom... where the real action happens. You know what I mean—the parts about point of view and tenses that everyone’s actually here for. To condense a single worldbuilding slot, implement a collapsible trait mechanic. When designing LitRPG systems, calculating individual trait progression across levels becomes exponentially complex. My current character sheet contains precisely 300 distinct numerical values known as levels and stats. Example at Level 1: HP 400/400, MP 42/42, ATK 16, DEF 12, MAT 16, MDF 10, AGI 14. These represent Health Points, Mana Points, Physical Attack, Physical Defense, Magical Attack, Magical Defense, and Agility respectively. Each requires unique scaling formulas. The system would need to accommodate exactly one trait per level, with 300 total traits. According to documentation v2.3.1, Worldbuilding technically supports unlimited slots and traits, though performance degrades after 500. Performance issues aren’t my concern. Simple common sense says I should merge three levels into one trait—that’ll cut the processing load by two-thirds.

Anonymous author 3 days ago

💡 Feature Request

Enable Claude Opus 4.6 Full Context Window Choice

Claude Opus 4.6 can technically handle up to a million tokens, but we haven't actually turned that on in Sudowrite yet. Right now it's capped at the same limits as Opus 4.5. We’d need to update some code to enable it, and it would get way pricier since a multiplier is gonna be added once you go past the base context window. understand that if you blow past that window you double the rates I'd like to be able to blow past that window... One could prevent public access to plugins that turn on this blow past it feature... So one would have to be determined to set this up for oneself.

John Creson About 2 months ago

1

💡 Feature Request

A better ”stream of thought” to prose workflow

I use sudowrite to turn stream-of-thought into almost finished prose. I don’t exactly write drafts, but more like something inbetween a draft and finished prose. When I put these in the draft creator and ask to generate them into prose, I often get a prompt that it’s ”already finished prose”, but it still works as I wish it to if I continue anyway. Using sudowrite this way is a bit wonky with the current work flow. I need to be conscious of where I do the scene splits in order to not have sudowrite cut any of the material, or start inventing stuff on its own to fill out the 1-1.5k words per scene. It’s also a bit annoying to have to work in single-paragraph chunks to create appropriate length scenes within the draft. My suggestion is to have a type of document called ”stream of thought” that works like a normal document, but has the prose generator functions at the bottom; ie without the use of scenes or the confines of ”how a draft should be written”. That way you can write very crude stream-of-thought style prose, making use of paragraphs, etc, to keep things organized and easy to overview, and then when you’re done, get to press the ”generate prose” (with the extra instructions), just like in the draft tool, but without having to worry about sudowrite inventing extra stuff to fill out pre-set word amounts for scenes, or cutting away material because it’s too much.

Kristoffer Lindgren 4 days ago

💡 Feature Request