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.

C H A P T E R 1<br />

<strong>Building</strong> an environment to host <strong>game</strong>play is quite different from building an environment<br />

for visual impact alone. You want both—an environment that hosts<br />

<strong>game</strong>play well and is visually striking. The primary idea here is that for your levels<br />

(first- or third-person <strong>game</strong>s), arenas (death match or player vs. player scenarios),<br />

maps (real-time strategy <strong>game</strong>s or role-playing <strong>game</strong>s), and playfields (action,<br />

twitch, or shooter-style <strong>game</strong>s), you want an environment configured in the right<br />

ways to support your main objective: solid play. If you give little or no thought as to<br />

how best to construct an environment in support of <strong>game</strong>play (for whatever reason,<br />

whether it be a tight development schedule time or resource shortages), the results are<br />

often frustrating and do not support solid play.<br />

So, as you consider function and layout, think about the play mechanics and play<br />

goals you’re trying to build. How you begin to set positions or lay out your play space<br />

will depend on the kind of play mechanic you’re trying to build. Of course, this varies<br />

according to which <strong>game</strong> genre you are working in.<br />

Start by asking yourself a question: What is my <strong>game</strong>’s heartbeat? The “heartbeat”<br />

refers to the primary or fundamental <strong>game</strong> mechanic that lies at the root of<br />

your <strong>game</strong>. It is your <strong>game</strong>’s driving force. It is why players will want to play your<br />

<strong>game</strong>. Always try to keep your <strong>game</strong>’s heartbeat in mind. No doubt, this heartbeat<br />

will suffer many palpitations and skipped beats along the beating path of <strong>game</strong> development,<br />

but your <strong>game</strong>’s heartbeat should be kept in mind to help guide the thousands<br />

of decisions that will be posed to your development team along the way.<br />

If you forget about a <strong>game</strong>’s heartbeat, the <strong>game</strong> can grow into a surly five-headed<br />

beast almost overnight, and you’ll be hacking and slashing at your <strong>game</strong>’s Hydra<br />

heads for some time to come. This is a difficult situation. Many <strong>game</strong> development<br />

decisions along the development curve will be informed by keeping simple principles<br />

clear in your mind. It’s always a challenge to learn how to do this under real-world resource<br />

constraints. As a team, you will have <strong>game</strong> direction ideas coming at you from<br />

4002 sources—including those paying for your <strong>game</strong> development and those who<br />

own the character and world rights you are currently meddling with.<br />

What is the heartbeat? Clear up the answer in your mind. Clear up the answer with<br />

your fellow team members. Act on it.<br />

Although many <strong>game</strong> developers disagree on the deep details, many <strong>game</strong> heartbeats<br />

are deceptively simple to express and remain true across genres:<br />

� Kill or be killed by other players or things (examples include Quake III<br />

Arena, Asteroids, and Twisted Metal Black)<br />

� Let me grow my skills, abilities, powers, influence, or recognition in some<br />

way (Everquest and Diablo II)<br />

� Let me control the simulation of a process (Rollercoaster Tycoon and The Sims)<br />

� Take me on an adventure of type X, Y, and Z (Grim Fandango and Myst)<br />

9<br />

Previsualization

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

Saved successfully!

Ooh no, something went wrong!