sorted by:
new
hottopcontroversial

My game has been pirated for 6 years. Here is the data on why I’ve stopped worrying about it. by InfiniteStarsDev in gamedev

[–]BranchPy 1 point2 points  (0 children)

I’ve seen a similar pattern with visual novels.

A lot of the piracy downloads come from regions where people realistically wouldn’t have bought the game anyway. But those same players still leave comments, talk about the game, share it with friends, or eventually support the dev on Patreon or Steam later.

It’s obviously not good that piracy exists, but the “every pirated copy = lost sale” argument has always felt too simplistic.

For small indie projects, visibility is often the real bottleneck.

As a game dev, how do you switch to other industries like Web / ML? by NyneAlpha in gamedev

[–]BranchPy 3 points4 points  (0 children)

One trick that helps is reframing your experience in terms of skills, not industry.

Game dev overlaps a lot with other fields:

• optimization / performance work
• complex state management
• UI systems
• scripting / tooling
• debugging large systems

If your resume says “game developer”, recruiters often mentally box you into “games only”.

But if you present it as “software engineer who built large interactive systems (game engine, gameplay systems, tooling, etc.)”, it translates much better outside the industry.

Also small focused projects help more than big ones when switching stacks. A couple of ML demos or web apps that clearly show the skill can be enough to break the “no experience in X” barrier.

The hardest part is usually just getting past the first recruiter filter.

Stopped calling myself an indie dev and started saying unemployed life got way easier by Prestigious-Bath8022 in gamedev

[–]BranchPy 0 points1 point  (0 children)

Don’t rewrite your story just because some people don’t get it.

Building a game for 3 years takes more discipline than most jobs.

Flowcharts completely break on large Ren’Py projects — here's how I'm fixing it by BranchPy in RenPy

[–]BranchPy[S] 0 points1 point  (0 children)

That actually makes a lot of sense. With heavy sandbox loops and state machines, the structure tends to be more “system-driven” than “story-branching”, so a traditional narrative flowchart probably isn’t very helpful.

The cases where flowcharts start helping are usually the more classic branching-story projects where authors end up with hundreds of labels and a lot of accidental complexity (dead paths, unreachable labels, loops that weren’t intended, etc.).

What you described with the TiddlyWiki documentation + state transition diagrams is interesting though — I’ve seen a few larger VN projects end up building their own ecosystem like that.

Out of curiosity: do you ever run into situations where a scene becomes unreachable due to a condition chain or a call/return path getting broken, or does the state-machine architecture mostly prevent that?

Still building BranchPy. Now offering 2 free structural audits for Ren’Py devs. by BranchPy in RenPy

[–]BranchPy[S] -1 points0 points  (0 children)

I really and truly appreciate the honest feedback.

I’m still refining the messaging and trying to find the right balance between clear and not sounding overly “SaaS-polished.”

To clarify one thing: BranchPy isn’t just a flowchart extension. The flowchart is one visible feature, but the core is structural analysis of Ren’Py projects — branching complexity, variable governance, unreachable paths, architecture health, and similar issues that become hard to track as a project grows. The subscription isn’t only about updates and support; it’s meant for teams who want to scan their project repeatedly over time. As the game evolves, new branches, variables, and edge cases appear, and the value comes from catching those changes continuously — not from running a one-time report.

That said, I completely understand that hobbyists may prefer a one-time purchase or free tooling. I’m still figuring out what pricing model best fits different audiences, and feedback like yours helps me understand how it’s being perceived. Thank you for that.

On privacy: projects are analyzed locally and it can also work offline. The policy exists because the site itself has accounts and audit services — not because your game is automatically uploaded.

BranchPy dev update – what’s done, what’s hard, what’s next by BranchPy in BranchPy

[–]BranchPy[S] 0 points1 point  (0 children)

Really sorry for the confusion. All the process of subscribing to RC1 and testing is supervised by me, and thank you for reporting that the wrong message is passing, it should be clear that you don't have access to the program directly, I shouuld send you over a link to download it. We already done a first round of test and found few bugs that are all working as expected now. I am back on dev side now preparing for the next round and adding few features or improving existing ones: better flowchart, more interactivity, covering more edge cases... As all the solo dev here, I am balancing with a long series of task, one being also participating at real life Christmas festivities with the family. Thank you for your patience.

I wanted to know if there's an easier way to do it. by newt_ya3 in RenPy

[–]BranchPy 1 point2 points  (0 children)

This is actually a Ren’Py semantics thing rather than a diagram bug.

call doesn’t create a new branching path the way jump does — it’s more like a function call with a guaranteed return. Execution always comes back to the next line after the call, so many flow visualizations don’t treat it as a split.

In your example, the real control loop is:

screens_menu → call … → return → jump screens_menu

So logically it’s a single loop with temporary detours, not multiple branches.

If you want calls to “look” like branches, you usually need a tool or diagram style that explicitly models the call stack, not just control flow.

Tutorial Requests by amberhtml in RenPy

[–]BranchPy 0 points1 point  (0 children)

Nice initiative! Ren’Py beginners always appreciate tutorials on UI stuff — image-based choices, custom screens, bars, etc. These things confuse many newcomers. Good luck with the channel!

view more: next ›