u/BranchPy
I’m preparing a new BranchPy release, and this version brings a big step forward: the scanner now supports Godot projects in addition to Ren’Py.
Before I publish it, I’m looking for a few game developers willing to test the new build.
If you have a project in either engine and want to help shape the next version, I’d love to hear from you.
Thanks for the continued support.
ps
To see what BranchPy is about, you can check the website:
I’m preparing a new BranchPy release, and this version brings a big step forward: the scanner now supports Godot projects in addition to Ren’Py.
Before I publish it, I’m looking for a few game developers willing to test the new build.
If you have a project in either engine and want to help shape the next version, I’d love to hear from you.
Thanks for the continued support.
ps
To see what BranchPy is about, you can check the website:
Ok, so... English is not my first language, and yes, I use tools to help clean up wording. I probably made some of these replies sound too polished.
But just to clarify the important part: BranchPy itself does not use AI to scan your game, and it does not upload your project to a model (works locally and offline).
The tool is closer to a local QA/static analysis tool than an AI assistant.
That said, and I am repeating myself here, the criticism is useful: I clearly need to show more actual screenshots, reports, and concrete dev examples instead of sounding like I’m pitching abstract SaaS. Right now I am working on a big update and soon I will have more time and attention to spend on my marketing side.
That’s fair feedback, and it touches the exact branding problem I’m trying to solve.
BranchPy is built for indie VN/Ren’Py creators, but I also don’t want it to feel like a toy. A lot of solo devs still need serious project QA, especially near release, and small teams need tools that feel stable and trustworthy too.
So the intention was not “enterprise SaaS for fintech”; it was “a serious local tool for creators who care about finding problems before release.” But I can see that the post may lean too much into polished/abstract branding and not enough into concrete Ren’Py dev reality.
I probably need to show more actual screenshots, sample reports, broken jumps, unreachable labels, flow issues, asset checks, etc. — less generic marketing, more “here is what it catches in a real VN project.”
It isn’t. The graphic may look AI/startup-ish, but BranchPy itself is a real static analyzer, not an AI wrapper.
It scans the actual Ren’Py project files and reports concrete structural issues. I’ll share more real UI/demo output because clearly the current presentation doesn’t prove that well enough.
Fair question. Lint is definitely part of the baseline, and I don’t want to pretend BranchPy replaces Ren’Py’s own checks.
The difference I’m aiming for is project-level analysis: story flow, structure, asset/reference issues, report history, comparison between reports done over time, and release-readiness checks. So it’s more “QA dashboard for a Ren’Py project” than just syntax/style linting.
But I agree I need to show that difference more clearly.
Thanks for the feedback — this is useful, even if some of it stings a bit.
I think the post/graphic made BranchPy look more like a generic SaaS or AI product than intended. That’s on me.
As I was saying, BranchPy is not an AI wrapper or a mockup. It’s a local static analyzer for Ren’Py projects. It scans .rpy files and tries to catch structural issues before players do: broken jumps, unreachable labels, dead ends, inconsistent flow, missing assets, and release-readiness problems.
The goal is not to replace linting or Ren’Py’s own checks, but to give creators a broader project-level QA view, especially once a VN has many labels, menus, branches, and assets.
I clearly need to show more real screenshots/demo output and less “startup-looking” marketing. Fair criticism.
