"renpedit" - flowchart-based organizer for ren'py games
Posted: Wed Jun 18, 2014 8:22 am
Howdy. I'd like to spam all y'all about a piece of software I've been writing:
https://bitbucket.org/theshad0w/renpedit
I started working on this as a tool to help with development on the Megatokyo Visual Novel (http://vn.megatokyo.com). I've made it available as open-source.
This software is not really about the nitty-gritty of writing Ren'py games (though I may be working on extending it to do just that). It is meant for organizing the flow of the game, between all the different possible paths. It eliminates the need for coming up with unique jump labels between points, and helps you locate and edit the piece of code you want to work on. The more complex and more paths your VN has, the more handy this tool will be.
Its drawback is it tends to take over the project, making you rely on it to find and modify your code.
If you think this would benefit your project, please feel fry to try it. I'd be interested in feedback on what enhancements you think it needs.
The flowchart and structure behind this project may be applicable to other software systems, and if you know of any you'd like to see this sort of thing applied to, I'd appreciate if you'd let me know.
I could use some assistance in cleaning up and improving the software; if you're familiar with Python and wxPython you could help a lot.
https://bitbucket.org/theshad0w/renpedit
I started working on this as a tool to help with development on the Megatokyo Visual Novel (http://vn.megatokyo.com). I've made it available as open-source.
This software is not really about the nitty-gritty of writing Ren'py games (though I may be working on extending it to do just that). It is meant for organizing the flow of the game, between all the different possible paths. It eliminates the need for coming up with unique jump labels between points, and helps you locate and edit the piece of code you want to work on. The more complex and more paths your VN has, the more handy this tool will be.
Its drawback is it tends to take over the project, making you rely on it to find and modify your code.
If you think this would benefit your project, please feel fry to try it. I'd be interested in feedback on what enhancements you think it needs.
The flowchart and structure behind this project may be applicable to other software systems, and if you know of any you'd like to see this sort of thing applied to, I'd appreciate if you'd let me know.
I could use some assistance in cleaning up and improving the software; if you're familiar with Python and wxPython you could help a lot.