Sunday, February 1, 2015

Global Game Jam 2015

So I participated in the Global Game Jam again this year.  The game my team and I developed is entitled Escape from Death Island.

One of two giant duck battles

It's a simple game in which you lead a mob of castaways away from danger.  It's definitely silly and a little more than just imbalanced.

This was the first year though that I just didn't have a good time.  I wouldn't say I had a bad time; a bad time would have involved fights and everyone leaving, angry at one another, and that didn't happen.  I think the feeling I left with though after this Global Game Jam was simply, "I would have rather just stayed home."

I found this image while searching "stay home", but also, is that neck pillow Photoshopped?

I do realize the entire setup of the Global Game Jam sort of annoys me and possibly how the Pittsburgh chapter of the IGDA runs it.  First off, the keynotes just weren't overly inspiring.  Only the first one really felt like it had anything to do with game jams, applauding jammers for just showing up.  The second was just sort of another call for diversity in character design, which is great and is something I support, but to inspire for a game jam, where a good portion of games are prototypes and don't have representation of human characters at all, it missed the mark.  The third one was just madness, a board game designer trapped in a CG card tunnel telling us about his projects in which "the magic" happened but nothing about game jams really.

Then the theme was announced.  I'll be honest, the themes over the past couple of years for the Global Game Jam have irritated me leaving me rather uninspired.  Another part of me is even like, "Why have a theme at all?"  I think a theme helps give focus, but sometimes I think a theme can unintentionally deflate inspiration, which I think this year's theme, "What do we do now?" sort of did that.  Also the delivery method was rather eye-roll-inducing.  In an event in which time management is important, I felt both this and keynotes were a waste of time.

I've sat through uninspiring keynotes and deflating themes before and have had great times at the Global Game Jam, so why was this one different?  Why did I have a bad time?  One of my friends even drove from Maryland to visit and participate, and I felt bad that I was grumpy and just not having a good time.
Well, one easy excuse was I was exhausted before the jam, an already exhausting event, began.   I had been playing The Evil Within the night prior and stayed up till 3 AM thinking, "Oh, this will just prepare me for the jam", which was a huge mistake and honestly could have been the main reason I was cranky.  I was just tired and would have rather been sleeping I think.

I blame you, Sebastian!  Why the hell do you have to die so easily?!

Though I learned some new concepts making Escape from Death Island, I had been working with Mecanim and human animations recently, so during the game jam, I was wishing I could have just continued working on that.  I think that feeling of "I'd rather be doing something else," is a major set back when doing a game jam.  I think if I had set the goal of "I really wanna make a game that utilizes this," it may have been more inspiring for me.
Anyway, I was left contemplating a lot of things.  Do I like game jams anymore?  Do I like game development anymore?  Am I too old for this?  While asking these questions, I stumbled upon a Global Game Jam retrospective on Gamasutra by Guilherme Costa.  What I liked in particular is that they listed 10 items to keep in mind when participating in the Global Game Jam, and as I read the list, I think some of these and the fact I didn't really adhere to some could explain why.  So here is that list and whether or not I felt my team did a good job on them or not:

1 - Minimize the team the most possible, short prototypes are produced faster with the smaller number of people. The lower the number of people in a group, the lower the possibility of a conflict as the activities to be performed.

I think we did this well.  We stayed with the same 3-person team we usually do, but even with the low number, I do think there was some conflict, which I'll go into later.

2 - If using any development tool (Unity3D, GameMaker, Construct etc.), avoid using add ons or frameworks. Can be great in the daily development, but if someone from the development team did not know, the project will not progress.

We used Unity3D, but one issue was that Unity now has so many add ons in itself that it can be challenging for someone who doesn't have a lot of experience with it or at least slow down progress a bit when trying to use some of these new features such as the UI system, which I'm not even too keen on yet.

3 - If you are responsible for the design, is incisive as to what's planned. If someone disagrees, prove that this design is really the best choice. If still the problem persists cut the people in the group or leave the group as soon as possible. It seems extreme, but it is best to keep everyone on the team happy with what they do than working in an uninteresting design.

This one is a bit major.  I think a problem we had early on is that I wasn't feeling the design we were going for or some of its features.  Then again, maybe I just didn't like them cause I was tiredI think the issue I had is I knew some features weren't important and trying to do them would slow down and split focus.

4 - Game design should occupy 10% of the total jam time. Remember that time still passes as you eat, sleep and meet other people.

 I think we did this one well; we chose an idea and ran with it rather quickly, but I think one issue that we didn't do is "meet other people."  We usually leave the jam site, this time the Art Institute of Pittsburgh, which creates some bittersweet feelings to begin with, so we didn't meet anyone, we didn't even playtest our game.  It's funny because in previous jams we've done this and it's never been a problem, but since I was feeling a bit deflated already, maybe some of the energy from other jammers might have helped motivate me.  Also we went back to my employer's office to work, which made the game jam feel like work.  At the time I thought this would be a great idea, but game jams are hard work and being there made it feel like work and not something I was doing for fun.

5 - Games made in game jams are prototypes. Focus only what is really important. Animations, camera effects, lights and shadows, do not affect gameplay, do not invest.

I feel like this is something we fail on every game jam.  We focus on things that are not important -- often when I know it's an issue and am ignored about it -- and the core of the game ends up suffering.

6 - Avoid that someone in the group runs out of tasks. Running out tasks drops the morale of any participant.

 I don't think this happens to us really; the opposite happens were we end up having too much.

7 - Create integration cycles. Avoid integrating all just at the end, integrate everything that is done in cycles of 1 or 2 hours, every two or three cycles, gather the team and make a debate on what has been done and will be done. The lack of continuous integration was the biggest problem of my team in this issue.

This is a good one.  I don't think we messed it up, but having specified cycles for it would help organize time a bit better.

8 - Try to create pause cycles for the group. Stay awake and well fed is always important, but even more important that everyone is the same way during periods of development.

We've never really had an issue with this.  We used to stay up all night, but now we make it a priority to get sleep.  I think my problem is I didn't get enough sleep due to my idiotic 3 AM bedtime the night prior to the jam.

9 - End the project a few hours before final delivery, do let other people play and try to find errors.

 This one irked me because we didn't start the jam until about 7:30 PM on Friday due to the keynotes and other things, but PIGDA wanted the games done by 3:30 pm on Sunday, which made the jam not really feel like a 48 hour game jam.  I think if he had planned that it was really only a 24 hour game jam, I think we didn't budget our time well for this delivery time because we assumed it'd be at a different time.

10 - If everything went wrong, do not worry, failing will not kill you. As time passes, the frustration becomes a thing of the past. Lift, organize thoughts and come back to fight.

I think the problem I had with this one is I sort of did feel bad about failing since we had never done it before.  Though I was so exhausted on Sunday, we did submit our game to the Global Game Jam site, but we didn't go to the closing ceremonies.  I just didn't care, which felt so rude and defeating of a game jam's purpose, but again, I was just exhausted.

Again, I sort of was wondering what else I could have done differently and one thought sort of scared me.  I had done Ludum Dare last year, which was a solo game jam and enjoyed that.  The fact that it was a solo game jam started to make me think:  "Am I just that bad a collaboration now?"  It was funny because the first keynote was given by a solo indie, and though she mentions that she's not really solo because she has friends, families, and contractors that help her in various ways, I wonder if she finds a certain freedom in it.  I can see some advantages.  You don't have to have meeting upon meeting to sell an idea and make sure everyone believes in it or is okay with it.  You don't have to worry about compromising an idea to the point where you don't even like it anymore.

"Johnson!  This is the 16th meeting, and you are now the only one who doesn't believe in the the combat system! WHY?!"

What worries me is that even the prior two assumptions I'm making feel rather selfish.  It's my idea, and I want it a certain way!  or worse, This isn't my idea, so I hate it already.  I'm sure there are designers -- of any field, famous or otherwise -- who think like that, but they are probably terrible to work with or at least if you are someone who doesn't believe in the idea.  Anyway, as I continue to develop and design, especially on side projects, I think collaboration is something I really need to work on.  I think this Global Game Jam was a failure; though we finished a product, I left it, not with a feeling of regret, but with this gloomy dissatisfaction that hopefully I can shake by the next game jam I do.

If I do the Global Game Jam next year, I think some of the following could help:
  • Go in with a goal.  Do I want to learn UI?  Do I want to practice an animation system or a certain mechanic?  Whatever I'm trying to do, pick something and focus on that and tie the theme into it.  Don't tie it into the theme
  • Stay at the jam site or at least don't go back to your office of employment.  I think staying at the jam site would have maybe given me some inspiration or allowed for playtesting or something that would have motivated me.
  • Be more assertive if you don't like something.  I think I took too far of a backseat and ended up working on something I just wasn't in love with.
  • SLEEP!!!!  Sleep the night before, sleep during, just be rested!!!  Again, all of the negativity I felt could have possibly been avoided if I were rested.
I can't guarantee these would help, but I think they'd be a good start.


  1. You've touched upon about 75% of the reasons I don't do Game Jams. 'Cause fuck all o' dat.

    1. Eh, I wouldn't let my opinion sway you really. I tend to be more negative than most, but yea, a lot of people tell me that when I say I'm doing it. Oh! Forgot to add MagFest was going on that weekend and everyone sounded like they were having a blast...which didn't help.