What BranchPy Actually Does
Stop guessing. See exactly what BranchPy does for you, with real examples from real projects.
BranchPy is a VS Code extension for Ren'Py visual novel developers. For each feature covered on this page, you'll find the real-world problem it solves and a side-by-side comparison of what your workflow looks like with and without it.
π Find Bugs Before Your Players Do
Without BranchPy
β Hope you tested every possible path
β Discover bugs from player complaints
β Spend hours clicking through your game
β Miss edge cases you never thought of
With BranchPy
β See all issues in one report
β Fix problems before release
β Instant analysisβno manual testing
β Catch every edge case automatically
πΊοΈ See Your Story Like Never Before
β Keep story structure in your head
β Scroll through thousands of lines to find scenes
β Draw diagrams on paper (or forget to)
β Wonder if paths are even connected
β See the entire game structure instantly
β Click any scene to jump to its code
β Auto-generated, always up to date
β Track all paths from start to endings
πΌοΈ Never Lose Track of Images or Sounds
β Find out about missing files when game crashes
β Accumulate unused files in your folders
β Manually check if assets exist
β Inconsistent naming causes errors
β Instant report of all missing assets
β Find unused files clogging your project
β Automatic asset validation
β Clear reference tracking
β‘ Jump to Exactly What You Need
β Search through files manually
β Forget which file has which scene
β Waste time navigating your project
β Lose your place while hunting for code
β One click to any label or scene
β Jump from flowchart to code instantly
β Go from issue report to fix in seconds
β Stay focused on what matters
π§ Work Smarter, Not Harder
β Launch game for every check
β Manually test every change
β Spend hours on quality assurance
β Hope you didn't break something
β Instant analysisβno game launch needed
β Automatic validation of all paths
β Complete QA in seconds, not hours
β Confidence in every release
π Know Exactly What Changed Between Sessions
β No record of what changed between runs
β Regressions hide among other issues
β Manually scan two reports to find differences
β Uncertainty about whether fixes actually held
β One-click diff of any two reports
β New issues flagged immediately
β Fixed issues confirmed, not assumed
β Full change history across every session
π Ship in Every Language β Without the Spreadsheet Chaos
tl/ folder and gives you an exact coverage percentage per language. Export every untranslated string to Excel, let translators fill it in, then import and preview every change before a single file is touched.
Without BranchPy
β No idea how complete each language actually is
β Translators work from copy-pasted text β errors guaranteed
β Stale strings linger from old script versions
β One bad import overwrites correct translations
With BranchPy
β Per-language coverage % in one panel
β Clean XLSX export with source text and file path
β Full validation before any file is written
β Preview every change β warnings require confirmation
Ready to Work Smarter?
Stop fixing bugs your players find. Start catching them before release.