Skip to main content

Lessons Learned while building Village

Since May 2006, I have been designing a game, designing a company, building a game, and building a company all at the same time. It's been fun and hell at the same time too. I thank God for all the cool people that I have met along the way and for the advisors cheering me on. Ironically these veterans of gaming and social enterprise are the same people who never expected Village to get as far as it has. Most first-timers would have long since given up on a game of this magnitude. In a way I'm glad I didn't know how hard this would be. I've learned a lot about game production over the last 10 months and I'm sure there's plenty more to learn in the next 10 months:

1. Don't waste time with dev studios that can't show prior work because it's "cloaked behind NDA's". If they don't have what it takes to make some sample work for their portfolio, then they don't have what it takes period.
2. Managing a remote development team spread all over the planet is possible, but it's a painful amount of email, messaging, and documentation.
3. Collaborating with an artist is 10x easier in person.
4. Rookie mistake: I didn't play strategy games similar to Village with my teammates. That would have helped so much with being on the same page. It's important the programmers and the artists have experience playing similar games. No amount of documentation will better clarify expectations.
5. The lower your budget is the more documentation, gui sketches, and spreadsheets become necessary to prevent wasted time in multiple revisions of the game.
6. There is no such thing as a complete or flawless design document. No matter how anally detailed the docs grow, artists and programmers will mis-interpret, mis-understand the design.
7. When picking a game engine for a 'first project' make sure a similar game has already been built on it. Building an RTS on top of Torque Game Builder is hard with no examples to follow.
8. For a first project, don't worry about innovating on game mechanics; instead throw all your innovation budget into quality artwork and storyline with an established game mechanic.
9. Milestones not only need clearly defined deadlines but also drop-deadlines. When a subcontractor is falling way behind on completion of a milestone it's often better to just call the deal off rather than waste more time waiting for it to get done.
10. Advisors who are veterans of the industry are essential. There are too many wrong paths to figure out everything by trial-and-error without them.
11. Getting press helps boost everyone's motivation on the team.

Comments

Popular posts from this blog

How effective is Blogger at sharing now.

This works great for 1 day trips somewhere if you have a fridge and laptop plugged in.  

Yes I'm reading parenting articles quite pre-emptively. I liked this one

It seems like modern parenting is an exhausting pain in the ass.  Somehow the task has become more difficult not less even with technology to help us do everything.   By the way, why are there still not washing machines for babies.  How has this been overlooked.  There are enough engineering couples who have tied the knot and started a family.  There's no excuse for this to not exist yet. https://www.romper.com/p/i-tried-minimalist-parenting-for-a-week-it-was-a-total-game-changer-74237 Romper Home Flowcharts News Moms Unfiltered Pregnancy Sex & Relationships Baby Toddler Kid Health Entertainment Motherhood Food Fashion & Beauty Company About Contact Terms Privacy Courtesy of goodmoments/Fotolia I Tried Minimalist Parenting For A Week, & It Was A Total Game Changer By  Ambrosia Brody 4 days ago SHARE Being present at all times with my children is an elusive goal. There are times when I am 100

Rant: I hate Google Cloud but I don't want to.

I just wasted 3 hours trying to get Google Cloud SQL to work.  After digging through docs and support forums I couldn't set up IPv6 access to my sql instance. This isn't the first time I've wasted tremendous time getting such a basic access feature to work.  I went through a nearly  parallel issue with Google Compute Engine.  It took over a week to get the answers I needed to get a network access working for Google Compute Engine. I have a problem and I admit it. :  I know Google Cloud will eventually dominate.  I can't help myself from trying to use the inevitable technological leader in the cloud wars, but damn give me back all the money and months I wasted learning these platforms.  If I could just turn off my engineering supremacy OCD ... just get prototypes working on traditional boring crappy tech,  I'd have way more streams of income by now and hate my tech life far less. Speaking of money:  There's still no clearcut way to cap monthly spend on Goog