Playable Game Project
From ReThinkWiki
|
Project Background
The Game Development Project should be based on the game concept demo you created in the game designing unit. The ongoing work on the Playable Game should be based on the project plan you came up with.
Project Assignment
1. Create a playable game based on your game concept demo.
2. Prepare a presentation of your playable game.
3. Publish your playable game (.SWF & .FLA) to the wiki prior to class. Please be prepared to discuss the game development throughout the class and what thoughts or motivations you had in doing your particular take on the project. Additionally, where appropriate, discuss how you satisfied the evaluation criteria below.
Requirements
- Use of Flash - Does the game demonstrate some familiarity with Flash?
- Use of planning - Does the game reflect the pre-production work such as the Design Document?
- Degree of completeness - Does the game feel finished at this point or are things obviously missing such as artwork or interaction?
- Exceptional combination of graphic design, animation, sound and game play.
Project ownership and the Open Source movement
Before you publish your game, you should think about the issues of ownership.
Copyrighting your game means you own it and no one else can use it or edit it or sell it without your permission. This is a good way to protect your ideas and work if you intend to use them commercially.
An open source license is fundamentally and philosophically different from copyright, in that it gives everyone access and the right to use, edit, and republish a piece of software for public use. No one the right to own/make money from it, including you, the author. We use open source licenses for MyGLife content because we want to share our content for educational purposes.
If you want to use an Open Source license for your software and web content, here are some suggestions:
1. For software licensing: GNU
GNU is the gold standard of open licenses and is used by Linux. Here is how they describe theirt philosophy:
“Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:
- The freedom to run the program, for any purpose (freedom 0).
- The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help your neighbor (freedom 2).
- The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3).
Access to the source code is a precondition for this.”
GNU is recommended by OLPC to its developers: http://wiki.laptop.org/go/OLPC_on_free/open_source_software
Here is how GNU is described in Wikipedia: http://en.wikipedia.org/wiki/GNU_Free_Documentation_License
2. For non-software content (tutorials, articles, syllabus, wiki pages): Creative Commons
Attribution Non-commercial Share Alike (by-nc-sa)
This license lets others remix, tweak, and build upon your work non-commercially, as long as they credit you and license their new creations under the identical terms. Others can download and redistribute your work, but they can also translate, make remixes, and produce new stories based on your work. All new work based on yours will carry the same license, so any derivatives will also be non-commercial in nature.
It would be easy to add this license to a website, blog, .pdf file and offline (downloaded) documents. They provide instructions here: http://creativecommons.org/license/results-one?license_code=by-nc-sa
Here is an overview of other Creative Commons licenses: http://creativecommons.org/about/licenses/meet-the-licenses
Here is an FAQ explaining what Creative Commons licenses can and can’t be used for: http://wiki.creativecommons.org/FAQ#Can_I_use_a_Creative_Commons_license_for_software.3F
