I thought of using GPL, but it would mean someone else would be obliged to open their source code if they base their software on my engine. Though open-source is good and must exist (speaking of Ren’Py, which is not GPL, but still an open-source engine considered a golden standard of VN development), I’d like to give others the right to make their derivative works either open or closed, by their choice.
As for AGPL, I know nothing, unfortunately.
What about the non-endorsement clause, then?
Well, the only difference is a so-called “non-endorsement clause”. I wanted to know where can I use it, and if I even should.
Long story short, it all started with an argument between me and a guy who thought only Japanese VN-related anything is usable normally, and that all Western VN-related software (Ren’Py included) are either clunky or laggy garbage. He also gave a Japanese novel engine called Light.vn (don’t mind the link, it’s the engine name) as an example (there is a killer feature in it: WYSIWYG editor). So I started my engine to prove him wrong.
After some time, I really saw that Ren’Py is not as fast as it was when I started to use it long ago. But that’s because it uses modern Python, which is by itself not too fast and lightweight anymore.
That’s why I write my engine in C and aim to make it much faster than Ren’Py and with better UX. Not speaking of a desire to create something meaningful myself.
Horrible? Okay, then. Can you explain why? I mean, I know that Ren’Py is using MIT, and there are no problems with anything as far as I can tell. So, what’s wrong with it?