Snarknado wrote:
One question, how do people generally distribute the work for this event between the two partners?
Aside from having one person look over and review scripts over the other person's shoulder and throwing out design ideas while their partner actually makes the game, there doesn't seem to be a lot for them to do.
![Question :?:](./images/smilies/icon_question.gif)
This strategy might not work for other pairs, but it definitely worked for both teams at our school--essentially, there's a "front" person and a "back" person. The "front" person designs all of the sprites, draws everything, writes up all of the text and scientific explanations, etc. The "back" person does the code as fast as possible.
Preferably both people should be familiar with the code/able to fulfill either role, though. It's just useful in case your partner chokes during the competition or something. Also, when my partner and I re-did our game in 35 minutes at MIT, since we already had most of the design elements/text ready I was basically watching over his shoulder and making sure he didn't mess up on the code. A lot of times it's really easy to make silly mistakes in Scratch, and honestly debugging the game can be so annoying... If the other partner isn't doing anything then just have them do that lol. It might seem kinda dumb but it is quite helpful.
But yeah, preferably while one person is coding the other person is planning things, and while the "front" person draws things the other person is reviewing everything. Idk, Game On is kinda weird as a partner event; dividing work is something every pair struggles with as far as I know.
EDIT: nice beatboxing idea
![Smile :)](./images/smilies/icon_e_smile.gif)
, i never thought of that... one time i proposed that my partner sing theme music but that idea was rejected
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)