itch.io

Actually, I am also a game developer but a beginner and don't know where and how to publish my game. So tell me everything clearly with complete and step by step instruction. 

This resonates a lot. I've been running a similar setup for a VN project with a pretty sprawling lore bible, and the "organizing" problem you mentioned is honestly worse than the reading problem for me. A flat folder of drafts turns into chaos the moment you've got v3 of a scene next to three abandoned branches.

What's worked for me:

Splitting by function, not by file type. I keep script drafts, lore/world-building, and asset notes in separate synced folders rather than one big dump — even if that means more clicking around, it means I'm not scrolling past 40 pages of character bios when I just want to proofread dialogue.

EPUB conversion for anything I'm proofreading off-desk, same as you're describing. Reading dialogue as a formatted "book" instead of a wall of script syntax makes it way easier to catch pacing issues — you notice when three lines in a row are the same length, which you'd never catch in a script editor.

TTS is underrated for dialogue specifically. Same experience here — hearing a line read flatly by a synthetic voice exposes clunky phrasing almost instantly. If it sounds awkward with zero acting behind it, it's going to sound awkward in-game too.

For annotation, I've leaned toward apps that sync highlights/notes back to a master doc automatically, because I used to lose half my "fix this later" notes when I switched devices.

As for hardware — no printing for me, it doesn't scale past a single session. I use a mid-size tablet propped on a stand, which sounds trivial but changes how long I can actually sit with a script before my focus drops.

Curious what conversion tools people are using for TTXT → EPUB specifically, since most of the free ones mangle formatting on anything with heavy branching/choice markup. Would be interested to see your full workflow writeup when it's ready.