Vote 2020 graphic
Everything you need to know about and expect during
the most important election of our lifetimes

The Problems With A Video Game Reality Show Contract

Illustration for article titled The Problems With A Video Game Reality Show Contract

Yesterday, the game developers community talked about GAME_JAM, a failed reality TV show about game jams. It fell apart for a variety of reasons, all better explained by the links in this article. This blog describes my part of the story, a minor part as I perceived it from the periphery, and includes some important advice on how to deal with contracts as an independent developer later on.


As any terrible legal story starts, this one starts not much longer than a week ago.

It's the third day of the Game Developers Conference in San Francisco, almost two weeks ago at the moment this post goes live. A bunch of independent developers are sitting in a local restaurant having a meal, and one of them is mentioning a contract that they're unsure about. The contract is for something called GAME_JAM. I had been told about the idea: a Polaris-run reality show about game jams, an exciting venture for everybody involved. Not only will it help demystify development a bit more, it will expose the massive audiences of Polaris to an important part of gamedev culture. It's an exciting idea, and like Amnesia Fortnight or Super Game Jam, GAME_JAM has tremendous potential to do good for our scene.


GAME_JAM is being organized by a group of well-liked people in and around the independent game development community – curators, friends and business partners – and the premise is great. Involved in GAME_JAM as participants are my friends Zoë Quinn (Depression Quest), Robin Arnott (Antichamber, Soundself), Davey Wreden (The Stanley Parable) and my partner, Adriel Wallick (Game A Week, Rock Band Blitz), so I offer to read the contract for them.

I am not a lawyer. Never claimed to be, never wanted to be either. I am a game developer that has assisted independent developers with hundreds of contracts and negotiations, small and large, and I try to advise developers that are less versed in legalese.

Like everything in the indie scene, some people know more about certain subjects than others and we try and share and broadcast that knowledge as much as we can. A lot of the more business-savvy developers help out with reading contracts. I just happened to know everybody involved in this story, so they came to me. As you read more legalese, and deal with more companies of varying sizes, you start to recognize certain patterns, phrases and tones in contracts.

In the restaurant, five minutes of my life are spent in disbelief: the contract is awful. The most striking points in the contract include:

  • Exclusivity: participants were not allowed to appear on similar shows or syndicated YouTube networks for the full duration of the main broadcast timeframe for GAME_JAM.
  • Waiver of privacy: participants had to agree to waive all rights to privacy in any area that is not the bedroom or bathroom. This includes the ability to use hidden microphones and cameras in any area of the production, including "co-ed living quarters".
  • Right to misrepresentation: GAME_JAM held the right to, in all and any way, misrepresent the developers, their actions and intent for dramatic effect. This wasn't limited to exaggeration or fabricating stories.
  • Obligation to travel: participants are obliged to travel to the event, and to any other promotional activity or show GAME_JAM required of them. Flight expenses would be paid for only if the participant was more than 200 miles away.
  • Marketing: participants would be required to participate in branded activities, including but not limited to 'drinking Mountain Dew'. On top of that, participants would be required to advertise the show as requested by GAME_JAM, and would not be allowed to speak ill of the jam, its sponsors or its organisers.

It's baffling to read that the full budget for GAME_JAM was apparently over $400,000 considering the fact that there is a clause in the contract that asks developers to risk having to pay for their own flights if they're close to a location they're required to visit.

The full benefits for the developers in exchange for signing this do not exceed $300 each (threehundred dollars, that is not a typo), lodging and return flights. The participants weren't in GAME_JAM for the money or fame, they were in it because they genuinely believed they could show the world this little part of game development culture in an honest and diverse way, and they were willing to try that even if that meant they had to drink Mountain Dew.


The majority of the other clauses were simply deal-breakers: a lot of the developers can't afford travel under 200 miles, the marketing of most of these indies depends in some part on YouTube and the participants were mostly up and coming developers with a reputation to think about. Allowing GAME_JAM to misrepresent their actions and words could have terrible results for their future carreers.

There was a certain tone in the contract that tells you that whoever agreed to send this contract to the developers is completely oblivious to game jams and lacks any respect towards the participant. It also tells you that the organisers did not expect GAME_JAM to yield enough 'drama', and that they felt the need to be able to inject drama into it.


Within minutes, I made the note on my phone at the top of this post, and it encapsulated the entire contract in a few lines. I read it to the potential participant to explain how bad things were. They were shocked and we immediately reached out to fellow participants, one of whom contacted a producer on the show to start negotiating. My advice was to not sign the contract or any other legal document GAME_JAM would send.

While the developers had been approached by friends and good people to participate in the jam, that chain of people had been completely circumvented by the legal team sending the damning contract. The contents of the contract and the restrictive terms were a surprise to pretty much anybody along the chain of command that the participants could reach.


Something was terribly wrong.

I normally tell indie developers to negotiate every contract, even if it's absolutely terrible. This is the first time I told anybody to tear it up and walk away. The contract was terrible, the event was days out, apparently the event was being organized by fragmented parts of a production nobody really had a full grasp on. Renegotiating anything on this scale tends to take weeks. We had days.


I got in touch with someone I know in the organization and tried to get a grasp of what was happening. I just wanted to be near my friends in case something bad happened, so I applied as a last-minute narrator or 'industry expert'. I hoped they could fly me out to Los Angeles, skipping manning our Luftrausers booth at Rezzed in Birmingham, UK to make sure everybody would be OK. Maybe there'd be something I could do to help out, but for now, we needed to make sure nobody signed the contract.

We shifted strategy. With the event happening in only a few days, I recommended the participants to not sign the contract instead and make a request to renegotiate the contract to get rid of the most brazen points. Without the contract signed, they could still participate in the jam, and then they would be able to negotiate the terms, decide which affordances to allow GAME_JAM and select or limit the content of the footage GAME_JAM could use.


In the best case, everything would be fine, they'd be able to negotiate the deal afterwards and use a productions' worth of footage as leverage. In the worst case, they'd still be able to walk away and openly discuss the jam.

After spending a few days winding down from the Game Developers Conference in Los Angeles together, I flew out for Eurogamer Rezzed and Adriel remained in Culver City for the jam. We'd be in touch in case anything bad happened, and she promised not to sign anything under any situation, even if a renegotiated contract was better. We were departing from a bad situation, and anything could look like an improvement. We didn't need improvements: we needed a good contract.


The participants sent a request for renegotiations and the 'team leaders' spent the majority of the next day renegotiating a new contract. They received it a day before the event would kick off.

What I was worried for happened: even though the contract was much better – it revoked the misrepresentation clause and specified the exclusivity much more in the developers favor – it was still quite terrible.


I recommended once more not to sign until all terms were acceptable, and I couldn't emphasize that enough. The potential circumstance of being on-set, with large production crews and your fellow developers waiting for you to being the only one not to sign was always-present, but that doesn't matter in legal cases: if you put your name on the dots, that's your responsibility, and you deal with the consequences.

As the first line of Zoë's completely unrelated article imply, she did cave under that pressure and the slightly better terms. These are not simple emotional forces to deal with, and knowing there's a huge production team literally depending on you signing is paralyzing. The other developers I advised stood ground, and refused to sign regardless of the potential negative effects on the series.


Either way, GAME_JAM didn't go well. Between making a total farce out of game jams, it was misogynistic, misinformed and disrespectful. There are a few times when I'd rather have my gut feeling be dead wrong about something, but this was one of them. I received three tweets from the participants containing the hashtag #ramiwasright.

But I can't be more proud of Robin, Davey, Zoë, Adriel and the other developers for walking away from GAME_JAM. The most expensive game jam in the history of mankind fell apart within a day, and the reason people were able to walk away relatively unscathed was because they had strong principles, they stuck together, and those that didn't sign were able to do that walked away without risk of legal repercussion from the contract.


Gamejams are a wonderful part of game development culture, and as a developer I hope you'll see them in a more genuine and more honest light someday in the future.

Contracts are serious business, and they can be both good and bad. I like to think of them as a way to keep people from arguing over dumb things. Here are some general pointers for contracts:

  • Only trust bad gut feelings. When it comes to contracts, trust your gut feeling only when it's warning you. Don't sign a contract because your gut instinct tells you it's OK: always check with people that are capable of verifying a contract, preferably an actual lawyer. If you feel bad about a contract, do not sign, figure out why, and negotiate those terms.
  • Contracts are negotiable. When you receive a contract, it'll typically be written to be as positive for the sender as possible. It is always possible to renegotiate terms that make you uncomfortable or problematic. When you negotiate, point out the specific clauses that are problematic, point out why they are problematic, and suggest dropping the clause, adding to it, rewording it, or making it more specific.
  • Anything between the lines isn't there. If there is no end date to a contract, there is no end date. If the contract states 'all and any', it means 'all and any'. If the contract says you will be obliged to participate in 'branding activities' for 'Mountain Dew or affiliated companies', you are literally signing a contract that could force you to go skydiving with a PepsiCo parachute.
  • Define as much as possible. What is a branding activity? What are the affiliated companies? How long will you be required to participate in these 'activities'? Will you still be required to do these after recording the original show? Ask every possible question and have the contract redrafted until you can't be forced to do anything that you're uncomfortable with.
  • Nobody really understands legalese. We're talking about words written by someone with an education of nearly a decade with some of the most stringent entry bars of any possible carreer. If any wording is unclear, ask it to be reworded as something that does make sense to you. It's OK to ask for clarification on legal jargon you don't understand, it's not OK to sign something you don't fully understand.
  • You only have obligations after signing. There is no timeframe and no maximum number of revisions. If the other party complains you're taking too long or the deal needs to hurry up, remind them that you are under no obligation to sign quickly. You never have to sign now. You're allowed to request to take the contract home or to run it by legal advisors. Signing binds you to the rules of the contract, not them – of course they are in a hurry.
  • You can walk away. Not signing and missing out is better than signing something bad and being part of it without recourse.

GAME_JAM is over, and it's an important lesson to all of us. Developers tend to be friends and we want to see each other succeed. We want new people to join the medium, we want to educate and share knowledge. The reality is that outside of our scene, that's not always the case. I'm so glad everybody got out OK. Huge shoutout to the developers involved and to Jared Rosen, who broke the story on IndieStatik, risking his own job. My apologies to those involved in the (great) original concept, who saw the production slowly corrupted by external forces.

Contracts are useful, but they can be extremely dangerous. Handle them with care, and if you're not completely sure what you're signing, get help.


The idea of GAME_JAM was great, and we need to demystify game development. For now, I can recommend Super Game Jam as a good insight into the reality of game development and game jams.

Rami Ismail is the developer & business guy at Vlambeer. He also created Presskit() & travels around the world to speak about game development and culture at events, schools and in emerging territories.Follow Vlambeer on Twitter or like them on Facebook.


Top image via Robin Arnott's blog post about Game Jam.

Share This Story

Get our newsletter


Stephen Totilo

Right to misrepresentation: GAME_JAM held the right to, in all and any way, misrepresent the developers, their actions and intent for dramatic effect. This wasn't limited to exaggeration or fabricating stories.

A note about this stuff that is paraphrased in Rami Ismail's essay here...

I obtained a copy of one of this show's contracts from a source. Here's some of what it says, some of which I guess you'd HAVE to have for a reality show but other stuff... is it really necessary to PLAN to misrepresent things to the people on this reality show?

1.Services: The Developers agree to participate as one of a group of contestants (a "Dev Team") in connection with the production of the Series as and to the extent required by Maker on such dates and at such locations as Maker shall designate in its sole discretion. The Dev Team shall compete in a variety of episodic tasks based around their collective skills as game developers. Developers' participation shall be critiqued by a panel of judges. Developers' services will include, without limitation, all rehearsals, on screen product interactions (e.g., drinking "Mountain Dew"), meetings, interviews, practice/rehearsal sessions, the supplying of personal information and photos, publicity, ADR looping, dubbing, as well as promotional appearances as reasonably required by Maker.


9. Misrepresentations: The Developers acknowledge that the nature of the Series is such that, for dramatic effect, Maker may make certain misrepresentations to others and the Developers prior to and during the course of Developers' participation in the Series (including prior to each Developer signing this Agreement), which misrepresentations may relate to any and all topics of every kind and nature whatsoever; provided, however, that Maker agrees that Maker has not made any misrepresentations to the Developers in this Agreement.

10. Concealed Recording Devices: Maker shall have the right to record any and all Developers using concealed cameras or other devices. THE DEVELOPERS UNDERSTAND THAT FILM, TAPE, AUDIO, VIDEOTAPE, AND OTHER RECORDINGS OF DEVELOPERS' ACTIONS AND STATEMENTS, AND THE ACTIONS AND STATEMENTS OF THE OTHER PARTICIPANTS IN THE SERIES, MAY BE MADE USING CONCEALED OR HIDDEN CAMERAS, AND OTHER DEVICES LOCATED THROUGHOUT THE LOCATIONS, INCLUDING, BUT NOT LIMITED TO, AREAS IN WHICH A PERSON UNDER OTHER CIRCUMSTANCES MIGHT HAVE A REASONABLE EXPECTATION OF PRIVACY (EXCEPT IN THE BATHROOMS, BEDROOMS AND DRESSING ROOMS, WHERE THERE WILL BE NO/ CONCEALED OR HIDDEN CAMERAS). The Developers further acknowledge that they may be placed in co-ed living quarters, and such quarters may be recorded in accordance with this section. The Developers consent to any such recordings made using concealed cameras or any other devices during any period of the day or evening. The Developers need not be given any further notice of the use of concealed or hidden cameras and other devices being used to record Developers' actions and statements. In addition, the Developers gives their express, unconditional and irrevocable permission to Maker to fully exploit all materials made using any type of filming or recording equipment (including concealed cameras and other devices), irrespective of whether the making or exhibition of such materials might constitute a breach of any rights of privacy the Developers otherwise might have in the absence of this express Agreement.

11. Non-Disparagement: The Developers agree that they will not disparage Maker, Pepsi Inc., or Microsoft Inc., or any of their officers, directors or employees. For purposes of this section, "disparage" shall mean any negative statement, whether written or oral, about Maker, Pepsi Inc., or Microsoft Inc.