11–20 of 59 posts
I'm not really a game developer but it seems weird to me that if you go with the GCFL you cannot release the game on the internet, but only in the appstores.
Earlier quoted context omitted.
We've dual licensed the DevKit - you can choose either the GPL or our free commercial license: http://www.gameclosure.com/license.html That page is about the GPL licensed version. It's basically saying you're free to develop and release a game with the GPL version but (as per the GPL) you need to release the source. The other option is to use the commercial license. Then you do not have to release the source of your…
Thanks for clarifying! So, in a nutshell, if you choose the commercial license, you are going to be helping market GC. Are you planning on offering a paid commercial license at any point? "2 You may not modify or enhance the GC DevKit or Engine whatsoever. The only exception is to perform bug fixes if you contribute your changes back to Game Closure. (See Exhibit A). You must incorporate a Game Closure splash screen…
The GCFL covers what we see as the majority case for game developers - we can work out other options as the are necessary.
I find disallowing modifications to the SDK (under the GCFL) to be a really bizarre choice. Is this allowed with a paid license of some sort? If not, why not? It's basically standard operating procedure in games that if the SDK you're using doesn't cut it, you work around the issues in order to ship. Is this specifically aimed at preventing people from using bizarre derivative forks of your toolset?
The spirit of the requirement is to encourage contributions back to the GPL version. You can fix or modify the GCFL version as needed - the only requirement is that you contribute back any changes to the SDK itself back to the GPL version. This way we can ensure that everyone benefits from having the latest and most bug-free code.
Earlier quoted context omitted.
Thanks for clarifying! So, in a nutshell, if you choose the commercial license, you are going to be helping market GC. Are you planning on offering a paid commercial license at any point? "2 You may not modify or enhance the GC DevKit or Engine whatsoever. The only exception is to perform bug fixes if you contribute your changes back to Game Closure. (See Exhibit A). You must incorporate a Game Closure splash screen…
If you are interested in a commercial license under different terms, you can contact me at fairfieldt@gameclosure.com. The GCFL covers what we see as the majority case for game developers - we can work out other options as the are necessary.
"You can distribute your application commercially, but you must also provide the source code." This little gem in the license information is pretty off-putting ( http://doc.gameclosure.com/guide/license.html ).
We've dual licensed the DevKit - you can choose either the GPL or our free commercial license: http://www.gameclosure.com/license.html That page is about the GPL licensed version. It's basically saying you're free to develop and release a game with the GPL version but (as per the GPL) you need to release the source. The other option is to use the commercial license. Then you do not have to release the source of your…
"You can distribute your application commercially, but you must also provide the source code." This little gem in the license information is pretty off-putting ( http://doc.gameclosure.com/guide/license.html ).
I kind of like it, but it'd be nice if someone set up a comparison table of all these new html5 game engines. There are so many nowadays, am I supposed to learn each one to figure out what suits me?
I kind of like it, but it'd be nice if someone set up a comparison table of all these new html5 game engines. There are so many nowadays, am I supposed to learn each one to figure out what suits me?
I'm not really a game developer but it seems weird to me that if you go with the GCFL you cannot release the game on the internet, but only in the appstores.
Totally agree. The only reason you would develop a game in HTML5 is for the build once, launch everywhere attempt. Otherwise you might as well use Corona.