• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Nohbdy Ahtall

Simple open-source game first, similar commercial game later. Allowed?

4 posts in this topic

Let's say you have a huge idea for a game, and it's 3D with all kinds of complex mechanics, and you realize it would take many years to get to that point of creation.
So let's say, in an attempt to prepare for this idea and hone your skills at the same time, you decide to make a 2D version of the idea, with simpler mechanics and only include what you're capable of.

If you create the simpler 2D version and you make it open-source, are there going to be problems later on when you finally go to create the highly-similar, much-enhanced version that will cost money to play?
0

Share this post


Link to post
Share on other sites
You own the rights. You can license it under whatever rights you want.

You can give it away under one set of rights, then later sell another version under a different set of rights.

What you cannot do is give it away under one set of open-source rights, then later revoke those rights. Once they are granted to the public, that release will forever be public.

Also if the public contributes back in, you must follow the rights that they grant; if they contribute back you cannot later change the license on their stuff unless they specifically grant that in the license.
1

Share this post


Link to post
Share on other sites
Thank you very much!

[quote name='frob' timestamp='1335921563' post='4936618']
Also if the public contributes back in, you must follow the rights that they grant;
[/quote]

What happens if I simply let someone make a change in the code, and they say nothing about it they just "do" it. Then perhaps that code is just as useful in the future commercial product so I use it. Do I have to be wary of that? Perhaps they meant it to be free to use, but what if they wanted something if it became commercial but didn't say anything? Is it a written agreement or a contract where that only applies?
0

Share this post


Link to post
Share on other sites
[quote name='Nohbdy Ahtall' timestamp='1335922510' post='4936624']
Thank you very much!

[quote name='frob' timestamp='1335921563' post='4936618']
Also if the public contributes back in, you must follow the rights that they grant;
[/quote]

What happens if I simply let someone make a change in the code, and they say nothing about it they just "do" it. Then perhaps that code is just as useful in the future commercial product so I use it. Do I have to be wary of that? Perhaps they meant it to be free to use, but what if they wanted something if it became commercial but didn't say anything? Is it a written agreement or a contract where that only applies?
[/quote]

The person making the changes holds the copyright to those changes and you're only allowed to use them if they grant you a license to do so.

You could get a lawyer to write you a suitable license but you'll most likely not get a lot of contributions if you require contributors to grant you rights that you didn't grant them.

The GPL is successful because contributors have the same rights as the one receiving the contributions (You can do with their code the exact same things as they can do with your code, no more, no less).

more permissive licenses such as BSD or WTFPL might be a better option. With these licenses you give the users alot of rights and its up to them if they want to give you any rights at all in return, While you probably won't get as many contributions as with a GPL licensed project and you'll also get proprietary forks competing with you the contributions you do get can be used as you see fit.
0

Share this post


Link to post
Share on other sites
Yes, stay away from GPL (or any copy-left licences) if you want to be able to incorporate the code into a closed-source project later. Look up licences such as the [url="http://en.wikipedia.org/wiki/MIT_License"]MIT[/url] or [url="http://en.wikipedia.org/wiki/Permissive_free_software_licence"]other permissive licences[/url].

As Simon pointed out, rolling with a permissive licence also grants [i]anyone[/i], not just you, the right to use your code in a closed-source project.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0