Live data from Hacker News

New open source HTML5 mobile game platform

docs.gameclosure.com

1–10 of 59 posts

Re: New open source HTML5 mobile game platform

#4
post #2

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.

Our focus has been on support for the mobile platforms - iOS and Android. As such, the deployment tooling is really focused on releasing games to the app store.

This may change in the future - for the time being, if you're interested in releasing a game on the web, send me an email:

fairfieldt@gameclosure.com

Re: New open source HTML5 mobile game platform

#6
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?

Re: New open source HTML5 mobile game platform

#8

"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 game.

I'll look into clarifying the copy on the page you linked - hopefully this clears things up.

Re: New open source HTML5 mobile game platform

#9

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.

Re: New open source HTML5 mobile game platform

#10
post #8

"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…

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 logo into your game. (See Exhibit B)"

"3 You must allow Game Closure to use your company and game name and logo for marketing purposes"

Post reply on HN