Ultimate Game Design : Building game worlds

Building Game Worlds
42
U L T I M A T E G A M E D E S I G N
As the stubbing phase comes to completion and the level starts to get locked down,
we will want to start implementing collision events as well. When a character walking
on flat terrain collides with a step, for instance, a collision event occurs. We’ll
want to use this event to trigger that character’s stepping animation, for example. On
the same event, we might also want to trigger a door slamming shut. Typically, dependent
on your engine and toolset circumstances, you set or paint collision fields
that generate data for the programmer.
Hazard areas like fire pits, bubbling oil pools, or acid pockets need to be checked
for scale and flow. Are these environmental features working out in the transition
from concept to execution? This is what you’re checking. There’s next to zero play
going on right now, so it can be hard to tell. Later on, in play testing, these areas will
need to be adjusted to build the perfect play setting. You’ll learn more about the play
test sequence in Chapter 7.
Keeping the Big Game Picture in View
Maybe you’re building out or stubbing golf courses for a golfing game or working on
a new vehicle-based combat game. Then again, maybe you’re working on an FPS set
during World War II or in the Old West. In all of these cases, it’s important to keep
the big game picture in view. Literally.
In other words, it’s important to cross-reference your concept drawings, game
heartbeat, and gameplay notes. Typically, of course, you’re working from a game design
document, which is the roadmap and “detail skeleton” for your game. It details
the purpose, functionality, and approach to execution for your game. (Appendix A
provides some reference information on design documents.)
Assuming that we have a well-crafted design document in place and have just completed
building out our first level basics, how do we keep the big game picture in
view? It is largely a matter of mental exercise. By starting with smaller sections of
your level at first, using your documentation and reference material as a launching
pad, try to picture in your “mind’s eye” the game playing right there in front of you as
you intend it to. Start with only a section of your game if it seems easier, and really try
to flesh it out in your mind. Take more gameplay notes. Share them, and refine them,
with your team. Remember, the process is all elaboration and refinement!
Picture in your mind the kind of character and environmental interaction you’ve
been talking about, dreaming about, and obsessing about with your team or on your
own. Try to see the defining gameplay itself. Is it a defensive mechanic? (For example,
guard this pile of loot.) Is it a puzzle mechanic? (Work with these logical or physical
limits to accomplish a solution.) Is it an offensive/defensive mechanic or game operation?
(Attack enemy 1 and enemy 2 while protecting your pile of loot.) Work at it
hard enough and you’ll have a “That’s how it will work!” moment. It’s an exciting
moment. Wonderful. Visualize how it will work. Try to visualize how the play mechanic