Gamasutra: The Art & Business of Making Gamesspacer
View All     RSS
October 21, 2014
arrowPress Releases
October 21, 2014
PR Newswire
View All
View All     Submit Event





If you enjoy reading this site, you might also want to check out these UBM Tech sites:


 
Will that crowdfunded game ever actually ship?
by Lars Doucet on 07/21/14 12:52:00 pm   Expert Blogs   Featured Blogs

The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.

 

So you come across a neat-looking new game on Kickstarter. It's got fancy concept art, it has some big names involved, and their pitch is really convincing! Surely this will be the game of our dreams?

Well, maybe not. The failure of the Yogscast game is just the latest in a long string of high-profile kickstarter busts. Obviously, backers should do their due dilligence and scope out the project before pledging, but if we're honest, most of us don't have time to run the numbers and dig really deep. So I propose this simple rule of thumb test (I didn't create it, but it has served me well), I call it "the two-out-of-three test":
 

1. Is it a new team? / 2. Is it a new design? 3. Is it using new tech? 2-out-of-three or more is the high-risk zone.

 

A score of one or zero means the developer is playing it safe, but keep in mind failure is still possible (this is game development after all). A score of 2 means it's risky - and that's not a moral judgment, sometimes it's important to take risks, it just means you should understand there's an even-or-better chance of this game not shipping. A score of 3 means you should expect the project to fail.

1. Is it a NEW TEAM?

Have these people ever worked together, and have they ever shipped anything? This is probably the most important question of all. Even if the members are individually talented, shipping is a team sport where synergy, cooperation, and most of all communication are far more important than any individual skillset.

Obviously, a new team composed entirely of industry veterans is not the same as a new team composed entirely of fresh-faced newbies who have never worked on a game at all, but the point still stands. Teams that have worked together in the past and already know how to get a game out the door are much more likely to do it again.

2. Is it a NEW DESIGN?

Have these people ever worked on a game in any way similar to this one before? This question probes how well the team understands the design risk. If you've only ever made 2D strategy games, you will have a lot of unpleasant surprises in store when you try your hand at a full-3D open-world exploration game.

Of course, sticking only to the kind of games you've done in the past can lead to stagnation; we need people to take risks sometime, which underscores this point:

It's easier to pull off a risky new design if you're not also saddling your project with engine and technology risk.

3. Is it using NEW TECHNOLOGY?

When it comes to technology, there is no substitute for experience. Programming languages have learning curves, engines have bugs, middleware has leaky abstractions, and it's a safe bet that a bunch of things won't work the way they're documented (if there's any documentation at all). Nothing beats someone who knows the details of the tech inside and out the way an experienced river-rafting guide knows every rapid, waterfall, and sunken rock.

Every single one of these points brings its own amount of overhead - teams need to gel, designs need prototyping, technology needs learning. The more overhead a project has, the more time and resources are spent just dealing with that rather than dealing with the game. 


Of course, my simple 3-point list isn't a substitute for a hardcore analysis, but it should be pretty easy to do just by scanning the front of a kickstarter pitch and doing some light googling. As for people who are running kickstarter campaigns, I strongly suggest you feature your answers to the "two out of three" test right on your pitch page, and if your score is two out of three, you'd better have a good argument for how you're going to overcome that risk if you want my pledge.

...

"But Lars! Aren't YOU making a crowdfunded game?"

Yup! I guess it's time to put my money where my mouth is and subject my own project Defender's Quest II: Mists of Ruin, to the test. Here's my super-biased self-analysis:

1. Is it a NEW TEAM?

Nope, it's the same (core) team from before. We have a few new contractors and special guests here and there (including musical superstar Nobuo Uematsu of Final Fantasy fame who is doing our main theme), but the core team remains the same as in Defender's Quest 1: Myself as programmer, Anthony Pecorella as designer, James Cavin as writer, Kevin Penkin as musician, Karen Petrasko as lead artist.

The day to day workflow for the new game is very similar to the old one - I sit down at my computer and program from 8 to 5, and coordinate online with the other team-members as needed.

And before our current core team assembled to ship Defender's Quest: Valley of the Forgotten, Anthony, Kevin and I shipped CellCraft, and before that James and I shipped Super Energy Apocalypse. So we like to think we know what we're doing.

2. Is it a NEW DESIGN?

If the "2" in the title wasn't a dead giveaway, this is a straight-up gameplay sequel to the original. We're taking the "Final Fantasy" approach to sequels - evolve the mechanics and experiment with some new gameplay ideas, but with a fresh new story and world each time.

We've learned a lot from the first game and we have a solid grip on our particular variant of the Tower Defense / RPG genre, which I've come to calling the "Tactical Defense RPG".

3. Is it using NEW TECHNOLOGY?

Sort of. The original game was written in Flash Actionscript and published in Adobe AIR, but the new game is being written in Haxe/OpenFL. The programming languages are very similar in syntax, as well as the coding pipeline (I'm still using FlashDevelop, the same IDE I used for the first game), but there are definitely some differences. We made the switch to Haxe because, like Unity, it lets us target multiple platforms from the same codebase (it does this by cross-compiling to the native language of each platform, be that C++, Actionscript, Javascript, etc).

The main thing that made me jump to Haxe was the HaxeFlixel engine. We'd been using the ActionScript version of Flixel for Defender's Quest 1, so having the same basic framework available in the new system meant my Flixel experience mostly transferred over intact.
Our overall score is 1/3 -- most of our risk is in the technology sector, and we've got a solid plan for working around that. Now that I've been working with Haxe for well over a year and am regularly contributing code back to HaxeFlixel, I feel confident.

A word on consoles

Consoles have become more open that ever before, but don't underestimate the complexity of shipping on one. You're dealing not only with technology risk, but also tons of paperwork, contracts, the cost of dev kits, not to mention you have to play completely by the platform holder's rules. 
We are looking into console support for DQ2 very seriously (we've already made some really good progress) but we have never promised we're going to ship console versions of the game, let alone a simultaneous release with the PC version. There's just too many unknowns. I'm pretty sure we can do it, but I want to keep expectations among our backers as low as possible.

 

So there's my simple little test for quickly analyzing the risk in a crowdfunded game. Hope it helps backers and game developers alike!


Related Jobs

InnoGames GmbH
InnoGames GmbH — Hamburg, Germany
[10.21.14]

Mobile Developer C++ (m/f)
Treyarch / Activision
Treyarch / Activision — Santa Monica, California, United States
[10.21.14]

Senior UI Artist (temporary) Treyarch
Treyarch / Activision
Treyarch / Activision — Santa Monica, California, United States
[10.21.14]

Lead UI Artist
Vicarious Visions / Activision
Vicarious Visions / Activision — Albany, New York, United States
[10.21.14]

Art Director - Vicarious Visions






Comments


Ryan Szrama
profile image
Fortunately I haven't backed any lemons yet. Lilly Looking Through is probably my favorite backed project thus far, and it helped that they had a demo at the time of their campaign. My bigger discernment challenge is how much time I'll honestly have in the future to play games. : P

Enjoying Defender's Quest, btw - can't wait to command a turtle tank. ; )

Kyle Redd
profile image
That's a good framework, but do you not think that how far into development the game is should also be a factor? I would think that is actually the most important consideration, given that none of the high-profile failures had advanced past the prototype stage at the time their Kickstarter was running (I think).

Meanwhile, a game like FTL would be considered a risky prospect, with a new team, new design, and a custom (if fairly basic) game engine. But looking at the polished game footage they had ready for the campaign, it would be a very safe bet to believe they would easily make it to completion.

Lars Doucet
profile image
Yeah, that's a good point. This was originally a test used for general development (ie, I first heard about it before Kickstarter was a thing), and KS just seemed like a relevant angle for an article about it.

Greg Quinn
profile image
I would also like to see some sort of prototype as a possible bonus point.

Way to many people are wowed by fancy concept art and a well edited video with sparkling graphics.

Show the world what you've done and believe in your prototype!

Andreas Ahlborn
profile image
Star Citizen falls straight into your "Certain Doom" category.

Let`s see how this goes...

If this project fails, then games+crowdfund will be as impossible to use in one sentence, as "Thermal Detonator" and "Warp Drive".

Simon Ludgate
profile image
I'm under the impression that a lot of the work for Star Citizen is being done at Behaviour and, while not the most high profile team, they have been around a long time (since 1992) and have shipped major 3D titles (like Wet). http://starcitizen.wikia.com/wiki/Behaviour_Interactive

If an old hat like Chris Roberts gets together with an established studio like Behaviour, is it still a "new team"?

Also, even if Star Citizen fails, I don't think it will take crowdfunding down with it, not with other successes in the field. If, for example, Pillars of Eternity and Torment: Tides of Eternity are as successful as Divinity: Original Sin, then at least RPGs will be pretty much locked in to the crowdfunding way. And if Star Citizen fails but Elite: Dangerous is a success, that will point more to Roberts as the source of the problem than crowdfunding of space sims in general.

Andreas Ahlborn
profile image
"Also, even if Star Citizen fails, I don't think it will take crowdfunding down with it, not with other successes in the field."

On this list: http://en.wikipedia.org/wiki/List_of_highest_funded_crowdfunding_
projects

Star Citizen is bigger than all the other high profile video games project combined. So its signal strength is certainly a lot more exposed.

TC Weidner
profile image
I am a star citizen backer but to be honest I am way way more excited about No Mans Sky now, after seeing what that brings to this genre. I think No Mans Sky has to possibility of becoming one of those market disrupting games that come out once every few decades. So Star Citizen may have more headwinds and problems via no fault of their own since they could of not forseen what was cooking across the pond.

James Yee
profile image
Hmmm... Lars what's the source for those questions? I think I might start using it in my Kickstarter Reviews/Interviews and I'd like to properly source the concepts. (Otherwise I'll just source you. :p)

Lars Doucet
profile image
I heard it from someone else in the industry long ago, and now I forget. I believe it was originally some producer's test for doing a super-quick evaluation of a new from-scratch game project that was being pitched.

James Yee
profile image
Thanks, I'll just say I heard it from you then and refer to here for quick reference then. :)

Jonathan Murphy
profile image
Back when I started in 2002 new devs were measured in time. If a team survived past the first year they outlasted 90% of competition. Even with new tech, team, and design. I think the bigger factors are progress over time, practicality in the face of ambition.

Ron Dippold
profile image
Yogsventure was a guaranteed failure with that combination of schedule, unbelievable feature list, and funding even if it had been an experienced team with known tech. But they're definitely not always that cut and dry.


none
 
Comment: