25.12.2012 Views

Ultimate Game Design : Building game worlds

Ultimate Game Design : Building game worlds

Ultimate Game Design : Building game worlds

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Building</strong> <strong>Game</strong> Worlds<br />

10<br />

U L T I M A T E G A M E D E S I G N<br />

Is this level of reduction and simplicity even useful? Definitely. Your heartbeat<br />

might combine a couple of these statements, but be careful. Most successful <strong>game</strong>s<br />

don’t go too wide with their heartbeat statements. You should be able to reduce your<br />

<strong>game</strong>’s heartbeat to one or two sentences at most. Don’t try and be everything to everybody.<br />

How do simple statements like these have any power in an age of never-ending<br />

technological advance and gaming possibility? All I can say is, there is great<br />

power in reduction sometimes.<br />

How do you use a heartbeat statement? After you have defined your heartbeat<br />

statement, you and your development team should evaluate the potential of each<br />

feature, function, mode, asset, or ability based on whether it adds to or subtracts<br />

from accomplishing your heartbeat statement. <strong>Game</strong> building is exploration. You<br />

may not know until you try it, but you can limit the pursuit of “peripheral ideas” by<br />

checking your idea for a feature or function against your <strong>game</strong> heartbeat. If it doesn’t<br />

move you closer to presenting your heartbeat statement for the player, then<br />

don’t bother with it. If it does, then weigh its true impact further and consider its<br />

feasibility.<br />

Keep in mind that building a next-generation <strong>game</strong> is a team function. You will be<br />

working as a team member to help establish the heartbeat for your <strong>game</strong>. You will<br />

not be working in solitude sending down “heartbeat” declarations from your throne,<br />

after servants have set up an afternoon tea. In other words, part of the <strong>game</strong> design<br />

process itself is learning how to work as a team to reach a “buy-in” or group agreement<br />

for the <strong>game</strong> heartbeat. Each team member will bring their own particular<br />

<strong>game</strong> experience, orientation, and passions to lend support or rejection for <strong>game</strong> direction<br />

ideas. Normally, <strong>game</strong> producers and designers help to guide this process<br />

through many iterations and revisions toward establishing a clear <strong>game</strong> heartbeat—a<br />

<strong>game</strong> heartbeat vision that an entire team can share and charge toward.<br />

With respect to function, start by asking yourself the following questions:<br />

� Are you building a <strong>game</strong> where competitive racing gives players the ability to<br />

enhance and customize their vehicle over a series or race circuit?<br />

� Are you building a <strong>game</strong> based on collection and combat with offense and<br />

defense?<br />

� Are you building a <strong>game</strong> based on simulating a growth process?<br />

Knowing the <strong>game</strong> heartbeat is fundamental and will help answer these questions.<br />

Establish the heartbeat first and build from there. The heartbeat will help inform the<br />

details. It will help determine the function. It will help show you how to build and<br />

evolve the right kind of environment in the right ways for your <strong>game</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!