Three guys in a room, somewhere in Buenos Aires, Argentina. Thatâs what HeavyBoat looked like back in 2010, when it was born after its founders (David, Juan and Leo) decided to leave the company they worked for. As an amateur musician, I soon joined them on a freelance basis, making music and sound FX for their games. A failed attempt at creating an original IP was traumatic enough for the guys to decide weâd focus on work-for-hire from that point on. So with a little luck and a lot of work, three years later weâd done more than 20 flash and HTML5 games, mainly for Cartoon Network and Disney.
It was appropriate that âJumping Finnâ, our fairly successful Adventure Time flash game, would be the one to take the leap into the mobile world, expanding into a version called âJumping Finn Turboâ (or âSuper Jumping Finnâ depending on where you live). But the scope got considerably larger in our next mobile game, based on another important Cartoon Network IP: Regular Show. âBest Park in the Universeâ was released in May 2013, by far our biggest project up to then.
HeavyBoatâs steady growth meant that soon after âBPUâ was released, the company moved to its fourth office in four years. Only this time, it wasnât a simple relocation. We had reached a point in which it seemed we could simply get stuck doing the same thing forever â or at least until our clients got tired of us. So if we really wanted to keep growing, there was no small step we could really take: the only real option was to try to jump forward ourselves and go for broke.
As a result of that decision, HeavyBoat went from around 10 employees to almost 25, in about six months. The goal was to have three teams that could run in parallel, each producing a mobile game. Coincidentally, this big experiment was to be bookended by the production of our next big Regular Show game, eventually known to the world as âGrudgeball: Enter the Chaosphereâ.
This is the story of Grudgeballâs development â but more than that, itâs the story of how it got trapped under the weight of the business risks HeavyBoat took during that time, our most difficult period to date. In the end, the game managed to dodge the mistakes we made along the way and became quite successful â though our big plans for the company wouldnât turn out as well.
We only had two things to start from: we knew weâd return to Mordecai and Rigbyâs bizarre universe (if youâre not familiar with Regular Show, go watch a couple episodes now!), and that the game was expected to have âuniversalâ gameplay, with simple control schemes. Early talks included ideas for an endless runner, a management game, a racing game, a dungeon crawler - even a âLost Vikingsâ-style puzzle game. But then our guys came up with the basic âdodgeballâ idea: controls would be kept simple by having characters move on their own, so players could concentrate on the most positive actions: shooting, blocking and counter-attacking. It would be somewhat reminiscent of the old Windjammers for NeoGeo arcade (hey, many of us are thirty-something, but donât hold that against us), only this time with three-player teams, as CN was understandably interested in having a lot of character presence in the game.
The recent expansion of HeavyBoat (henceforth HB, for simplicityâs sake) gave me the chance to hand over my sound & music responsibilities, and focus on my actual area of expertise, which is writing. The first âaction-packed dodgeball gameâ pitch document we presented to CN back in November 2013 featured the working title of âDodge the Chaosâ, and a basic storyline about a dodgeball match gone wrong. Skips, the all-powerful immortal yeti, would throw the ball âwith such power and furyâ that it managed to rip space open and tear a portal into a dimension where dodgeball was the main form of warfare. If you havenât seen the show, trust me â itâd have fit in.
Â Â Â Â Â Â Â Â Â Â Â Â Â ÂThe original prototype, with a post-apocalyptic âMad Maxâ style theme.
Together with a fairly close-to-the-end-result prototype, the document helped sell the idea â but not too easily. By the end of 2013 one of HBâs founders, Juan, was flying around the world trying to strengthen our relationship with our clients and searching for some new possibilities. In a chat, he told me people at CN were concerned that the basic concept we had might not be as wide-appealing as intended: making what would essentially be a sports game didnât sound wacky enough for a Regular Show game, especially considering there was actually a dodgeball-themed episode about to air.
Ironically, I was worried about the other half of the concept. Recent Regular Show games had been built around the basic âWarâ idea: there was âPaint Warâ, âThe Great Prank WarââŠ were we really going to do a WAR too? I suggested a different setting: the show is known for its 80s references, but had never really used the âfuturistic sportsâ subgenre, seen in movies like âRollerballâ or âTronâ. So I pitched it in my next draft of the story: it had Pops (a cheerful old fellow) putting the other characters through some group exercises âto strengthen their teamwork spiritâ, until an innocent ball game would get out of hand, and a serious, technologically advanced version of himself would emerge from a portal to kidnap the whole group into the future.
The guys at CN liked the basic setup of Popsâ compliment game and the futuristic timeline, but were still wary of any kind of sports metaphor. Fortunately, once I explained my concerns about overusing the war theme they quickly agreed, and we started going back and forth with the story during January 2014, in true collaborative fashion. Working via message boards, we re-wrote each other keeping whatever we liked from the latest version. They came up with the idea of Popsâ tears giving life to the compliment gameâs ball, and I suggested he buried it so that itâd grow underground for centuries, influencing a whole city filled with gentlemen who used âthe GAMEâ to run wild. Even the idea for the final boss was there early on - though they wisely simplified my over-complicated motivation for Future Pops to kidnap his younger self.
There were still a couple of issues to solve, but everyone was happy with the story. On March 7th I happened to be in Los Angeles, so I was invited to pitch it to J.G. Quintel (creator of Regular Show) and his team, which I happily did. It went great: they got the references immediately, it didnât contradict anything they were planning, and they really seemed to enjoy it. J.G.âs comments were short and wise: donât flood the game with too many cutscenes, just make it fun!
âGrudgeballâ would be the third and last game to be released from our initial plan to develop as many mobile games at the same time - but that doesnât mean the other two were any smaller. Although they couldnât be more different in gameplay (one was a classic âsnakeâ game and the other a runner), both had a protagonist called Jake, and would eventually get an eerily similar name: Adventure Timeâs âTreasure Fetchâ (another mobile expansion of a previous game of ours), and Jake and the Neverland Piratesâ âTreasure Trekâ (based on the Disney Junior TV show).
While discussions progressed on the context and storyline of our new game, the first few months were dedicated to recreating the original prototype and defining the core gameplay. Yet slowly but steadily âand largely unbeknownst to us, in those optimistic days-, every unresolved issue and delay that the âJakeâ games suffered started snowballing into âGrudgeballâ. The Adventure Time game, in particular, had been in development for so long it seemed determined to mirror its main characterâs elastic powers. Consequently, by the time it was finally done, another long-gestating project (to be released as of today) was just being greenlit, so with âTreasure Trekâ also in its final stages, âGrudgeballâ became the victim of some sort of middle child syndrome. Its brothers were getting all the attention: the elder ones as their release dates approached, the new baby as it needed to define its concept in order to get underway.
Doubling the number of employees meant there were lots of new people thrown into production almost as soon as they walked through the door. So delays were to be expected, but things started to get a little out of hand. We realized we were still not enough, and started bringing in people to save our troubled projects. Some of the new guys had little to no experience, so they had to learn along the way: the inevitable process of detecting personal strengths and weaknesses (so each oneâs responsibilities could be properly defined), would have to be done during production.
And no area suffered these changes as much as our Art Department.
HBâs Art Director, Leo, worked on the concept art for the pitch document, but soon he would find himself stuck in Neverland as âTreasure Trekâ was nearing completion. Discussions then started on who should be Grudgeballâs Lead Artist. One of the candidates was a very talented guy who did the first round of cyberpunk concept art once the futuristic setting was approved, but he unfortunately didnât have enough experience to lead the group. Eventually, he got transferred to the âbabyâ project I mentioned before, only to find himself trapped in endless months of redefining the basic game concept â but thatâs a whole other story.
Â Â Â Â Â Â Â Â Â ÂThe original court design we had in the game, closer to âAliensâ than âBlade Runnerâ.
For about three months, Grudgeballâs Art team was almost exclusively comprised of two artists whoâd just entered the company. They did a great job, but couldnât count on the guidance they should have had. Finally, around march, one of HBâs most âveteranâ artists (who had been working on the Adventure Time snake game), requested the job.
The Art guys had a LeaderâŠ until he decided to leave the company a couple of weeks later.
Juan thinks it was âprobably the first big blow we got as a consequence of HBâs growth. Back then we were starting to think about how to communicate things to twenty-five people instead of six. I think he left partly because this wasnât what he had in mind.â Grudgeball carried on without a unified view of how it should look like, and many decisions that should have been taken in those early days would haunt us til the very end of production. The gameâs UI (User Interface) was particularly hurt by this situation, as each artist inevitably started doing his own particular take on any given screen.
It wasnât until âTreasure Trekâ was finally done that Leo could dedicate full time to steer Grudgeballâs visual design in a definitive direction. There was the expected friction, of course: the ânewâ person coming in to take over, unapologetically focused on finishing the game in timeâŠ you know how the story goes. But it was hardly the last big personnel change along the way.
Halfway into development, the other two HB founders started moving away from day-to-day operations, which lead to Grudgeballâs Game Designer, Fersis, being promoted to GD Director. Our QA Lead, Gustavo (Gus), was offered the chance to take his place, after showing interest in designing for a long time. The transition was handled as smoothly as possible, with at least a couple of weeks of Fersis and Gus working side by side, but it nevertheless slowed things down in an already delayed project. âWhen I took over from Fersis, the game was little more than a prototype. There were a lot of things still not defined, and I wasnât very sure what I could change and what was already set in stoneâ, Gus remembers. âIt was a ton of work for Gus; we threw the guy right into the oceanâ Fersis admits.
As much as youâre willing to pick up from where your predecessor left off, bringing in a new GD obviously means bringing a new take on the project. Fersis had more of a turn-based structure in mind, where each side could perform a single action at a time; Gus was more keen on an action-based style. Somewhat inevitably, Grudgeball today has a little bit of both tendencies. Some team members wonder this mixture might have made the game too fast to feel truly strategic, and too slow to have a strong action feel. Would we have a more âsolidâ product with a single Game Designer?
âWhat tends to happen is that when there are constraints, the impulse is to ignore them and design a separate game, with features which donât gel with the core gameplayâ Fersis thinks. Gusâ view on the subject: âPeople with a programming background usually want to have a lot of control over their design. I do like turns and strategy, but I prefer adding a little chaos, which is one of the most basic forms of fun.â You might even argue the end result is the best of both worlds, but there are as many truths as people out there, and this lack of definition resulted in the core gameplay taking a long time to find its final shape.
In any case, changes in team members were born out of necessity. Changes in technology, on the other hand â well, they were risky choices that our CTO describes as âan open wound. We didnât quite know neither how to adapt, nor to argue against them.â
The project was built using the Cocos2d-x framework. At some advanced point during development, the team decided to incorporate tools weâd never used before: FMOD for sound and LWF to export Flash files into Cocos â the latter of which promised to be particularly useful for interface design. In retrospect, the brief time dedicated to evaluate and study both tools proved not to be enough. They undoubtedly opened up a lot of new possibilities - but also meant new problems. Lucas, one of our most experienced programmers, ended up dedicating a lot of time fixing issues found in LWF (and then sending them to its developers for the world to enjoy), while FMOD made the game crash so frequently that when time to experiment with it started running out, we made the tough decision to pull it out from the game and rebuild the whole sound using Cocos2d-x's library.
It wasnât either toolâs fault in the first place, of course â we wouldnât have chosen them if they hadnât seemed like great additions from the start â but we just didnât have enough time to study them and make them work well enough with the other tools we had. At least the LWF story had a slightly happier ending: it took months, but the artists could rely on it to make things that were not possible with Grapefrukt, and without the need of a Coderâs permanent assistance. All those different light patterns on the court reacting to whatâs going on in the match, or animations running at the same time within different panels of a same cutscene â we wouldnât have been able to do those kinds of details (nested animations) before.
Â Â Â Â Â Â Â Â Â Â Â Â ÂWork on the second cutscene, from my own sketch to the guysâ awesome final version.
As 2014 went by, the game started moving away from the prototype, until it ended up returning to the original basic design - particularly in terms of controls. For example, the idea of giving each playable character a different shooting range was tried for a while, before going back to just being able to shoot in any direction. âIt always goes like thisâ Fersis describes; âWe work on the basics, move forward, and get to a point where we decide itâs not working. We take a completely different path - then we decide thatâs not good enough either. So we go back to the original path, and solve the issue that had pushed us to move away from it. In between, weâve lost sight of production.â Why has this happened to us more than once, I ask him. âBecause we think weâre better than we really are.â
Harsh self-criticisms aside, the truth was the core game still needed many adjustments to get right on track. Particular issues were brought into focus as Argentina was celebrating its Independence Day on July 9th, and the first big batch of feedback notes arrived from CN. Thankfully, we were already working on some of the reported issues. Input was certainly not quite there yet, but it would soon get vastly improved. We also agreed that the single player mode needed variations to avoid getting repetitive, and boosters definitely needed some work. But there was a single piece of feedback that was of particular importance for us, mainly because it had also been the single most recurrent complaint raised at our previous Regular Show game: the fact that characters werenât feeling different enough from each other.
Â Â Â Â Â Â Â ÂA match from the Release version, with the Portals & Multicannon âcourt featuresâ in action.
Features like Special Attacks, Counterattacks, and the Team Buff (which went through many permutations), were developed to find a way around this particular issue, yet most of us think it was the one thing we couldnât really solve. âCourt Featuresâ worked great though: weird things that show up during the match, like barriers, portals, or the almost-unstoppable ricochet ball. Itâs a good thing we also managed to squeeze these wacky effects into the âVersusâ mode, considering playing against a friend in the same device is the one aspect of Grudgeball everyone always agreed was as fun as we hoped it would be.
Around June 2014, the long-awaited closure of the two âJakeâ games meant more care could be taken of our beloved âGrudgeballâ. Leo was able to finally lead the Art team, and Fersis found the time to turn his gaze at the gameâs day-to-day affairs. That was when a careful look at the projectâs Backlog (the long list of tasks required to deliver the product) revealed we would miss release date by a whooping three months.
In retrospect, it might have been the kind of panic the team needed to focus on getting the work done. The cold, hard numbers had spoken, and drastic measures had to be taken. Fersis restructured Grudgeballâs Backlog to make sure the team would stick to the gameâs priorities - and then swiftly cut out everything else. âThere were more boosters, obstacles, features, a whole help screen, Arcade Mode was going to be way more complex â all goneâ, he remembers. âBut once everyone saw the real problem we had, each area was able to find its own solutions.â
We obviously lost some cool stuff in the process (guess weâll never know how the âinvisiballâ would have turned out), partly because the team hadnât given boosters any kind of priority order: the ones youâll find in the game are the ones weâd produced before these measures had to be taken. And as if working without a Lead Artist for months hadnât been enough, the ever-expanding Art Department was put to the test once again, with most of the guys put into âtimeboxâ mode. That meant each artist would get a fixed amount of time to pull off a certain portion of the gameâs visuals: a character, a certain background, etc. No complains there: everyone agreed it quickly helped building a sustained production rhythm, avoiding endless iterations. We were finally starting to crawl out of the hole we had dug ourselves into.
For several reasons, release date was changed a couple of times. Originally, it was set around July, then it was moved to September, and CN finally settled on February 2015 so as to separate the gameâs launch from that of other titles already in production. We couldnât really keep a full crew working past October without complicating our own internal timeline, so the main Grudgeball team disbanded at the end of the month, while a few of us picked up the pieces and carried on.
Incorporating the localized lines of text was one of many remaining tasks: thereâs a substantial amount of words in the game (in 10 languages!), so checking if every single line fit within the text boxes was no quick thing for the QA guys. That much was expected, anyway - there were more complicated issues to tackle. October saw the arrival of another set of tough-but-true feedback from CN: the game definitely needed more explanations and a better presentation of progression.
Â Â Â Â Â Â Â Â Â Â Â Â ÂThe Loading Screen â Before and After
Curiously enough, an important chunk of the adjustments both partners came up with in order to address those issues were laid over the gameâs loading screen. For example, we incorporated around 30 gameplay tips I was asked to write to better show the extent of the gameâs contents, and most importantly - the elevator you see on that screen (which is basically the moving court the characters stand on) got the animation it deserved. It seems crazy it didnât move until then: youâd see it fixed in the current level. But it was the kind of key detail that got buried under the huge amount of small adjustments required at the same time, and CNâs feedback helped bringing it to the forefront.
Aside from re-implementing the gameâs music and SFX after pulling FMOD from the project, November and December were mainly re-balancing and bug-fixing months â and there were tons of them. By then, energy was running dangerously low. February would blissfully take the game off our hands, and into the world.
âIt was the project in which they tried everything. Technology changes, team changes, administration changes â everything changed along the way. But surprisingly, against all odds, it turned out pretty well.â
Those are the basic feelings shared by the team, as eloquently put by Fede, the gameâs QA Lead. Most of the guys are satisfied with the end result, but the single thing everyone agrees on is that the game looks awesome - so everything the art department had to endure at least bore its fruits. Little victories for HeavyBoat -considering our past mistakes- include the following: we finally have a final boss that feels like a final boss, cutscenes are way better than in âBest Park in the Universeâ, and the volume of content is great â especially considering the wide variety of animated characters we managed to pull off.
Â Â Â Â Â Â Â Â Â ÂThe playable section of our colorful futuristic cast.
Regrets? We have a few, as the song goes. Some of the issues along the way we couldnât really fix: it still can get a bit repetitive, characters donât feel wildly different, and some information might not have been shown as clearly as it should have.
Ultimately, everyone is as happy as exhaustion permits. âI think itâs amazing that the game more or less looks just like (the prototype). Thatâs a first for usâ says Juan. âItâs inevitable to say that it turned out pretty good considering the chaos it was to produce. Compared to âBest Park in the Universeâ, we achieved what we set out to doâ, Ale (our CTO) thinks. Fersisâ summary: âI like the way it turned out. It feels good, the art is great, the cutscenes are by far the best weâve done, the tutorial is by far the best weâve done (itâs inside the story, as it should be). Itâs a cool gameâŠâ
ââŠbut production was a disaster.â
So, the Grudgeball project was expected to define whether we had âgrownâ successfully or not. It was the last, definitive stage of a test to prove ourselves if we could really manage three games at the same time. So how did that go?
Well, we were clearly not ready. All three parallel projects took us longer than we had estimated, and release dates determined which ones would get the experienced people needed to pull them off in time. Unfortunately, in the end neither of the âTreasureâ games did as well as expected, and development of our very next project wasnât any simpler.
This chapter of HBâs history had begun alongside Grudgeballâs inception, so it was appropriate that it would close around the gameâs release. That happened on February 19th 2015, one day after 13 people - basically half of HeavyBoat - were told weâd have to part companies by the end of March. It was time to admit our grand experiment had failed, and a close look at the numbers offered two possibilities: to keep on until we all went bankrupt, or to react as soon as possible, go back to being a small group, and give people no longer in the company enough time to get other jobs, paying them every penny the law indicates for these situations â a practice not many companies around here honor, sadly to say.
So, by the time you read this, a small number of us will have returned to our previous, smaller office, back where we were a year and a half ago.
Thankfully, the great reception âGrudgeballâ is having has cast some light over this difficult period. We thought itâd get buried under a mass of new releases or get a mild 3.5 rating, but instead, itâs been featured in the App Store and Google Play, it has a 4.3 rating (as of today), and has gone as far up as number two in Best Selling Games lists in under a month. Professional reviews have been really positive, as well as most customersâ opinions in the stores.
Who knows - it might even turn out to be the best-received game weâve ever done. Yet another old story: you never know how people are going to receive your product, and if youâve been long enough on the inside, you canât really see beyond the pains it took to get made.
So thanks to everyone that made Grudgeball what it is: Gus, Fersis, Santi, Fede Donnet, Nacho, Ale, Diego, Nico, Fuego, Csr, Gera, Leo, Gonza, JuliĂĄn, Fabi, Fede PĂ©rez, IvĂĄn, Lucas, Jere and Juan N. Thanks to everyone at CN Digital for the opportunity and all the hard work, and to CN Studios for creating the show and letting us play with its universe.
Finally, thank you for reading as well - hopefully, Iâll be back in some time to tell you how weâre doing.
Images courtesy Cartoon Network/HeavyBoat