Ultimate Game Design : Building game worlds

Planning level work, 26–31
Plans, writing test, 172–173
Play mechanics, MMOG, 199–200
Play-test feedback, 165, 173–178
Player control, RTS games and, 117
Player creation screen, 323
Players
console, 189
MMOG, 189
using complex strategy, 119
POC (proof of concept), 37, 129
Point or ambient lights, 60
Points
power-up, 7
spawn, 87
stock, 7
Post level stubbing considerations, 38–45
adapting architecture and terrain to games, 39–40
checking character flow throughout level, 40–41
early evolution of levels, 43–44
hazards, 41–42
importance of early feedback, 44
jump heights, 41–42
keeping big game picture in view, 42–43
level goals enhancing game vision, 45
scale, 41–42
workings of primary mechanics, 45
Power-up points, 7
Power-ups; See Items/power-ups
Prefabricated geometry and modularity, 27–28
Previsualization, 1–22
case study comments on, 17–18
case study comments on previsualization, 17–18
interview with Andrew Holdun, 18–22
introducing previsualization process, 3
paper-based level blocking, 13–17
step-by-step previsualization, 3–8
Previsualization function, 8–12
Interior to Exterior, 12
reinforcing mood, 12
room flow, 11–12
Previsualization process, 2, 3
Previsualization, step-by-step, 3–8
architecture for game levels, 5–6
basic environmental design, 6–8
utilizing environmental references and
sketches, 4–5
Primary mechanic, workings of, 45
Problems, common camera, 98–99
Product development departments, 279
Production, 271–273
as career choice, 272–273
exploring, 304
risks for MMOG, 190–191
Production challenges, MMOG, 188–193
Production tools, 298–299
Programming
departments, 281
exploring game, 305
game, 266–268
TV, 289
Programming language for console/PC, 300–301
Proof of concept (POC), 37, 129
Props, 15–16, 85
placing, 93
and their uses, 92–93
using, 93
Prototyping, game, 37–38
Publishers; See Uber-publishers
Publishing; See Self-publishing
Puzzle game mechanics, 116
Puzzle games, 114–116
developing, 116
Python sample, 140
Q
QA costs, 192–193
QA (quality assurance), 165, 166–173
bug tracking, 168–170
as career choice, 274
case study comments on impact of, 179–180
exploring, 306
interview with Melinda White, 181–185
QA setups, 168
technical support, 170
testing MMOGs, 171
three-stage completion process, 172
writing test plan, 172–173
Quick modeling, 317–318
Quick topic summary for designers, 309–320
R
Ramp, difficulty, 88
Rate, frame, 6
I N D E X 343