At first I was going to subtitle this post “Follow your game-making dreams like a crack-crazed, howling, insensate lemming plunging from the peaks of Mt. Everest into the fiery pits of Hell itself.” So… should you?
What am I talking about? I’m talking about big talkers and bootstrappers in videogames. And I’m talking about how to build your dream game.
I’m specifically preaching about Kaos War, an old virtual team videogame project that had some dude in San Francisco – name of Damon Grow – betting the farm and bankrupting not only his wallet but also all of his personal relationship capital. I’m talking about an MMORPG dream that either Jesus or Satan engraved into this dude’s brain with a icy scalpel. Games.net posted a series of video minidocumentaries by Wendy Chan that are unfortunately no longer online (I checked Youtube as well). There are nine of them, all revealing and painful. I regret you can’t see them, because they are full of lessons. And lesions.
It’s old news, but I think you can still profit from some of Grow’s mistakes and successes. And stick around… later I’ll post an update on Kaos War and Grow so you can see what ended up happening in this drama.
If you don’t already know, a virtual team is an international group of dreamers who group together – often never having met in real life – and communicate via the internet to cooperate on a project. Of course, especially when they’re building a game, this fails pretty frequently. In Damon’s case, I have to give him props. He seems to have picked people who are dedicated and have some experience. The video clips gloss over that fact a bit. That’s one of the big keys to success, and Damon seems to know how to pick ’em and hook ’em.
In the documentary, they made a big deal out of the fact that he has no experience. Frankly, the suits don’t need to get their hands dirty, and in the world of Kaos War, Damon’s definitely a suit, and probably best doing suit things. Damon seems to have some of the necessary elements to become a gaming executive, truth to tell. He’s obsessed. He loves to talk. He believes 100% in his game. He inspires people and gets their juices flowing. He sacrifices. He’s abusing drugs (okay, caffeine and energy drinks). He’s insane. He makes bad decisions and has skewed priorities. If you can find the video, check it out. Let me know what you think.
p.s. Nice work, Wendy.
Damon’s did a lot RIGHT with Kaos War. He worked hard. He motivated people just by his presence and his words. He recruited talented people from around the world – people he’d never even met.
This guy has charisma, and he was getting stuff done.
For Chrissake, the guy actually managed to get real funding from a game company. He deposited a check. I’ve never deposited a check except as an employee. Many, many pros in the industry have never gotten Funding with a capital F. This boy is delivering.
But what’s he doing wrong, in hopes that someday, someway someone like Damon can follow in his footsteps but do it just a tad better, causing a degree or two less human suffering? What was Damon doing wrong? What not do to when starting your project?
5. Bitch about cosmetics to the guy who just paid your rent.
In one episode, Damon and his forgiving roomie Brian go over to the warehouse district to look at a possible development location. It’s a skunky warehouse and the place is doubtlessly riddled with crime. Surprise – it’s cheap real estate in San Francisco.
Damon immediately carps on the lack of paint and the fact that “it has birds*** all over it.”
Damon, your project has no funding and your team is eating ramen and sleeping in your bathtub. Embrace the birds***.
In fact, you’re not to the birds*** stage yet. You aspire to birds***. I admit that maybe you could skip this stage entirely if you get funded. But you’re not. Why’re you even shopping? Later, Damon and the boys go over to the Boardwalk of SF real estate, Lucas’ digs in the Presidio. Someone mentions that he could hire (and pay!) a programmer a year’s salary with the rent. Hmm. I wonder which one will win in a pinch? Employee salary or fancy-pants suite next to Lucasarts? Hopefully Damon will get this one right.
4. Assume that human suffering is a substitute for excellence.
Damon tells us that one of his teammembers has been homeless for two weeks. We’ve sacrificed so much! he avers.
I’m sorry, Damon. This is wrong in two ways. First, you’re kind of using this guy’s horrible situation to further your project, and in a way, YOU made it happen because he’s spending energy on your game instead of on finding a decent crackhouse to sleep in. This is a bad example for the troops. If you don’t mind bragging that a guy went homeless to work on the game, maybe you won’t mind bragging about having the whole art department on the street.
And second, there are a lot of homeless guys in the world who suffer every day. How many hit MMORPGs have they made?
3. Tell your team to shoot for Goliath.
Taking on World of Warcraft, geez, Damon. What kind of expectations are you trying to set? “Plan B” might be good to have. Good leaders prepare for all cases. Good leaders pick achievable goals that won’t crush the troops if they aren’t met.
A real MMORPG team is 30+ professionals working fulltime… and building ungodly amounts of art, script, story, characters, monsters, and code. These guys have done it before. They have all the tools and training. They can concentrate on their jobs without having to worry about spaghetti supplies or being pushed off the futon at 3 am by the kid they’re sharing it with. These are significant advantages.
Dreamers keep the gaming industry alive. But practical dreamers achieve their goals and start out with baby steps.
2. Shop for your Blofeld-style mountaintop headquarters.
It’s rough to see these game newbies picking their game dev “mansion” when the guy has no money and his rent is due. What the hell? Seriously, who’s supplying these boys with nose candy and uppers?
This is the equivalent of a high school baseball player shopping for bling at Shaq’s favorite jewelry store in Beverly Hills. Helloooooooooo in there! Earth to Skyler!
1. Force your CTO to pull up roots for a pitch meeting – or quit the project.
Lead programmers are gold. They make everything happen, and the whole game is built on their tech design. If your CTO is in Europe and living with his folks, you respect that and let the poor SOB telecommute.
It’s nice to have warm bodies in the boardroom with you when you meet with the publisher, but warm bodies can be hired at the local Walmart. Sure, you want the CTO there to talk tech with the brain trust, but if your publisher doesn’t have the ability to call a guy in Europe you don’t want them.
You don’t force your #1 guy to choose between leaving the country and leaving the project. Most of the time he’ll choose the latter.
Seriously, kids. I urge you. Be realistic. Do some research. Stay focused.