Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Wow, thank you for this amazing feedback! I'm sure Illumenos and I can incorporate this into a future version of this tool! I know he wants to expand it to also offer help to artists wanting to draw the frames/expressions for lip flaps, so I'm sure there'll be an update sooner or later.

We were actually looking at "proper" software licenses first (both of us are coming from a software development background, but neither does a lot of work in the open source community or with Python for that matter), but then figured that nothing would stop us from just slapping CC BY on it and call it a day, especially since we want the rest of the repo's content to be available for people as well, and for the art and music CC BY felt more appropriate. But yeah, definitely a weird choice and we were discussing MIT/Apache as well before just going with one license for everything.

As I already said, neither of us is using Python professionally, so this was all kinda hacked together within the time constraints of several game jams without digging deeper into the language and its best practices or really paying much attention to quality. So getting pointers for this is especially interesting for us. Usually we just take a break after jams because we're all tired, and then when the next jam rolls around it's all deadlines and stress again, so no one ever takes the time to truly figure stuff out. This is super helpful and a great way to get us to sort things out.

Thanks again,

CCL

Thank you for your time to answer and explain your situation.

For licensing, in my case I ended up with MPL 2.0. It's strict enough for my creation but loose enough to allow others to use it. Attribution enforced by the license is really something I'd like it to have. I could edit it but then it's a custom license that is untested and unproven (and couldn't be called MPL or any variation of that).

I'm open to cooperate and help making stuff that is useful for the community. Like these tools you spent a lot of time on. If I can help, I'm open to help. I want Ren'Py to succeed and I believe these tools help achieving just that.

If you ever feel like cooperating with something, I help with what I can. You can find me here or Discord or lemmasoft forums. I'm brunoais pretty much everywhere. See you soon 😉.

(+1)

Hi 👋

Thanks a lot for the time you put into reviewing this! Especially thanks for the pointers. For these alone making this tutorial has already been worth the time. I will adapt the code on gitlab in the next couple days, but for this jam it has to stay on 1.0.1 during rating.

Regarding a chance for a collaboration: On this specific code I think I want to implement some of the things you mentioned on my own to get the learning experience. After that we (community and our team) can manage this project through merge requests and forks. It is intended to be open source.

I'd be happy if you helped with the project after the initial rating period, in case you find code you really want to fix :D

Regards,

Illumenos

Sounds good. 👍

There's some things I really would want to implement such as the concept of namespacing the variables, functions, transforms, etc... so it doesn't clash with other stuff. The rest, that's not as important.

I'm open for discussion or comments, if you want. You can contact me. I'm also on Discord and other discussion forums.