Assemblee is a two-part game-making competition! Each part has its own rules.
1. In the first part, artists and musicians will have a month to create as many art and music assets as they wish. These assets will be voted on at the end of the month based on the quantity, quality, and variety of the assets provided.
2. In the second part, designers and programmers will have a month to take the assets created in part one and make games with them (assets used need not be limited to one person or team). The programmers cannot make any changes to the assets unless it's done during runtime. The best game will be voted on in the normal fashion.
3. Finally, the teams that created games for the second part will each vote on which artists and musicians they felt were the most useful in making their game.
4. The art and music that was created for the competition will be released to the public under certain provisions (non-commercial, credit given, etc.).
PART TWO: DESIGN AND PROGRAMMINGThis is the second part of the competition, so we're looking for designers and programmers (toot toot!). Your job is to create awesome games using only the assets that were created by the lovely entrants from part one.Start Date:
Sunday, January 10th (Around Midnight)Rules for Part Two (Design and Programming):
- Games should be started and ended within the time frame of the competition to be considered for judging (but it's OKAY if you start thinking/prototyping a bit earlier).
- Games must be made for the competition only.
- To enter the competition, start a thread for yourself here
. Each person (or team) is allowed one thread per game. Post a link to all final games in the first post of the thread.
- If you created assets for part one, you may still participate in part two.<<Rules and clarifications added by Melly>>
(Derek, feel free to remove or edit this if you don't like something in here):
- You can use assets made by yourself on part 1 that are also available to all other participants.
- You're not allowed to supplement the assets with your own that have not been made and posted during Part 1. Everything you use must come from Part 1.
- It's perfectly fine to do these changes to assets:
* Adding a transparency layer or changing the background of a sheet to magic pink or whatever other color your engine uses for transparency. Do this ONLY on parts of the sheets that are obviously meant to be transparent.
* Converting files in ways that do not alter the visual quality of the assets. You can, for example, change GIF's to PNG's, but you cannot do stuff like changing a true-color PNG to a 256-color GIF as that would visibly change the colors and quality of the asset. Same goes for audio assets and 3D file formats. You can also transform font images provided into TTF's or another font format of your choice.
* Rearranging sheets so that they'll work better/properly with your engine. As long as you don't alter the graphics themselves, the order the tiles show up on the sheet doesn't matter. This also goes for creating sheets from graphics made by artists that didn't do that themselves.
- You should only do other types of changes (scaling, stretching, blending, etc) using code during run-time. This isn't meant to be a strict rule however as it may be too cumbersome/time-consuming for some people to write this kind of code. Not like we're going to checking everybody's code anyway, so don't worry TOO much about it. Yes you can do simple stuff like pre-flip sprites if your engine is so limited it can't do that. We're not nazis.
- Seriously, as a rule, if nobody could possibly tell whether you did stuff during runtime or not, who are we to judge?
- There are no material prizes, so focus on having fun and making awesomeness. <<End of Melly's additions>>
Okay, let's do it!