Ultimate Game Design : Building game worlds

A
Action events, scripting, 135–164
applied scripting examples, 140–143
building behaviors, 150–151
case study comments on scripting baseball games,
154–159
engine solutions and Unreal engines, 151–152
interview with Andrew Forslund, 159–163
script/editing system considerations, 153–154
scripting technology choices, 137–140
using triggers, 144–150
Action games, first-or third-person, 121–123
Actor loading, case study comments on, 99–100
Actors
boss, 91–92
enemy, 88–90
hero, 87–88
NPC, 90–91
props, items, and camera considerations, 85
Actors, enemy, 88–90
enemy hazards and blind data, 90
Actors, placing, 87–92
boss actors, 91–92
enemy actors, 88–90
hero actors, 87–88
NPC actors, 90–91
Advergames, 246–248
interesting trends for near future, 247–248
Agents and recruiters, 289
Ambient lights, point or, 60
Index
Anecdotes from game development frontlines,
250–253
sacking Sanka, 252–253
think fish, 251–252
Animating lights, 64
APIs (Application Programming Interface), 222
Applied scripting examples, 140–143
Architecture and terrain, adapting to games, 39–40
Architecture for game levels, 5–6
Art, 268–270
game artists as career choice, 269–270
tools, 297
Artist, game, 269–270
Attack issues, security and, 193
Audio, 53, 74–76, 273, 319
audio composer and engineer as career
choice, 273
composer and engineer as career choice, 273
exploring game, 306
game, 76
triggers, 149
B
Backend construction; See Database/backend
construction, 192
Backstory, developing, 125–126
Bandwidth support issues, 192
Baseball games, case study comments on scripting,
154–159
335