I've been retooling my workstation since yesterday. Really looking forward to this competition.
The following is pure speculation, and letting my mind run down a thought. The following are not contest rules, or suggestions for contest rules, simply my thinking out loud.
Sometimes I think too much, and I had an idea I thought I'd share with everyone. I think... Someone should program a Goblet of Fire for future competitions. The Host company sets up a Goblet of fire, entrants put in their email address, submit their three words, and on the date of the event everyone gets an email with their three words, and the full contest details. Perhaps if The Game Creators host it, in exchange for a DLC asset pack to the winner, the winner submits the game to be included in a special DLC pack of contest winning games.
And I'm just talking out loud here, but there's a couple more things to think about. Most importantly is 'What makes it worth it to the hoster of the contest?' Obviously we're using their product to create a game, but how do they benefit best from the contest?
I see a few options moving forward.
First Option, is that the winner is required to submit source for their game. and that source becomes included in DLC packs where people can see examples of games that won contests before. Except for the following points:
1. The winner has to submit source code, which may contain proprietary code that they don't want to share with anyone. (trade secrets)
2. That source code will likely start showing up in public repertoire as standard in contests. Granted as long as the Hosts are paying attention, they'll be able to see when code is regurgitated.
3. This means that everyone that participates in the contest where source is revealed at the end, runs the risk of exposing code they may not want to share. And if getting a DLC in exchange for that source code, they may not wish to part with code. There might be a sudden upset so don't go printing fliers until the chickens hatch.
4. This levels the playing field for all contestants. Knowing that proprietary code might be shared with the public for free, ('GASP!') participants are likely to not include proprietary code they've written for streamlining their processes in a game. This means that everyone likely will start from scratch, and may use alternate methods to accomplish a frequent goal.
4a. There's always more than one way to accomplish a task when programming. This option will definitely make participants grow in new ways if they desire to succeed in this contest. With any task one undertakes, the opportunity for learning new things increases exponentially as they try and try again.
Second Option, the winner submits source to a game that was created with the software, but with the agreement considered signed by participating in the contest, the source is only accessible by the host, and will not be distributed as source.
1. The host compiles the source into an executable and the winner agrees that the host has all rights to distribute the submitted game compiled, in any format they choose. The hoster can then include the game in promotional materials, or a special DLC of games that were created and won this contest. If this DLC was made available exclusively to people that purchased the software that made the game, ie AppGameKit, This would inherently boost sales of AppGameKit, along with the inclusion of a regular contest to create games with it on a deadline, where the winner can choose a DLC they don't already have, or comparable phrasing.
2. The host also agrees that the winner can take the game further, and distribute it as they please, with the condition that they cannot distribute it at the same level of completion submitted to the host for the contest.
2a. This point here means that the contest will shift focus from creating an entire game in 7 days, to creating a fully functioning demonstration of concept, (Demo Game).
2b. The winner can choose to fully develop the game into it's full potential, and also sell the full game under their banner.
3. No chance that proprietary code inadvertently winds up in public repertoire.
I think there are pros and cons with either option. I'm sure there's more pros and cons than I've put here. But I think I've run all my thoughts on the idea to ground.
I'm sure there's a lot more to discuss on this subject should a host decide to make this a regular thing.
Disclaimer: All of the above is just my own rambling. I have no association with The contest host, The Game Creators, or AppGameKit, other than owning a copy of AppGameKit, and using it frequently.
