So I posted this idea on Toast's blog and it seemed like people were receptive, so here's a proposal for y'all.
The conceptBroken telephone is a children's game where each person whispers a message to another person in a chain. By the time the message reaches the last person, it is very different, often comically so.
The idea behind 'Broken Game-a-phone' is to pass development of a game on from person to person. It is the task of receiver to guess and decide how the game should be developed from there forward.
Proposed details- Development allotments of 2-3 days, probably not more. Less is a bit too pressuring.
- Development will be in Game Maker, as it is decidedly the common denominator in the community. We will try to be Game Maker version neutral - if you wish to use an earlier version, say so, but be aware you must go first.
- Collaboration starts as soon as the rules are decided and the first eligible (see above) party wants to start. A loose order is determined, but switch-ups / additions are allowed. From there, development should be continuous, but worst comes to worst, lapses are OK. The last people should be focused on wrapping up the game.
Proposed rules - No discussing the game in development. If you're curious, sign up!
- You may request one version behind the one you are handed for a handful of reasons (suspected vandalism, suspected regressions) but are encouraged to try to work with what you get.
- Incorporating existing resources is OK, use your discretion. Generally encouraged are utility code such as text-box engines, etc, as it will improve the quality and usability of the GM file. Discouraged are sprites and gameplay features ported from another game.
Proposed guidelines Avoid commenting on the further game design and story. But … - Document the code well. Use a consistent explicit bracing style.
Avoid Drag & Drop if possible (but it is forgiven, of course). Revised, Drag & Drop is banned, along with code in unexpected places such as room creation code, time-lines, and object creation code. Avoid implicit blocks (eg if statements without { } ). Indent all blocks.
- Fix bugs if you can, note them if you cannot. Even spending your whole time doing fixes will be greatly appreciated by the people who come after you and should not be down-played as a contribution.
- If all else fails and the game's a turd, polish the turd :-). Better to have a presentable failed experiment than a complete failed mess.
Proposed game start ? It can be all up to the initial contributor, but I think some top-down game with areas and plot would do well. As was mentioned, a game with plot could turn out cool with multiple contributors.
This is a rough draft! Seeing as this will be a community project if we do decide to do it, suggestions welcome! Sign-up here
http://www.surveymonkey.com/s/GC6XJNM !
Survey results:
MMORPGguy
juurianchi
panzercretin
RC
eagly
Cesque
s
SMP
KaBob799
Kilin
Charlie Carlo
link2x101
SpectreNectar
Toast
Pirate-rob
RC
Mega
Does anyone want to volunteer to be arbitrator ? I will participate but I think I'm far too busy at this point in time. If not I will eventually host, when I'm not so busy.
Sorry, pro functions are an absolute must IMHO. It's enough of a stretch for me to program GML, let alone not being able to use stuff like datastructures. If there are enough interested lite users and they don't mind going first, yes that's viable.
I'm in, GM7. When's this even happening?
Also, I think lite's should go first, as long as they don't use too many retarded lite version work-arounds, but they can only use GM7 because the GM7 people would be going after them.I really should have added more to the survey in retrospect. Oh well.
I'll give it at least a week for sign-up and for 64Jam to finish, then we'll try and fit some kind of schedule. But I think there's no need to wait too long.Currently, 7 people have signed up.Also surely this game is called Whisper Down the Lane. I've never heard of Broken Telephone.
[quote=Proposed guidelines]- Document the code well.
Sign me up, I'm using 8.1.Use a consistent explicit bracing style.Avoid Drag & Drop if possible (but it is forgiven, of course). Revised, Drag & Drop is banned, along with code in unexpected places such asroom creation code, time-lines,and object creation code.Avoid implicit blocks (eg if statements without { } ).Indent all blocks.They're just guidelines anyway, right? Not actually important?In with GM8.1 here.
MMORPGguy: They're guidelines. But really, the principle of working on a group project is to be a code chameleon. Professional developers don't fuss over coding standards. I am aware we are not all professional developers, but it is good practice.
This goes for everyone: Remember, coding standards are almost never about 'the right way' to code. They may try to avoid common pitfalls but mostly they are arbitrary choices for consistency. If it's out of your comfort zone – good!Also, sign up via the survey!Charlie: Aware, there's a reason I spelled out what broken telephone entailed in the intro. :-)I just knew it as the telephone game =p
According to Wikipedia it's called Chinese Whispers but people call it other shit because it's racist.
i'd be an ass and comment all my code with "RTFM"
(joke stolen from Kilin)