Ultimate Game Design : Building game worlds

More documents

Recommendations

Info

Level execution, case study comments on, 45–46 Level goals enhancing game vision, 45 Level mistakes, avoiding common, 30–31 Level of detail (LOD), 122 Level planning and building, 23–52 case study comments on level execution, 45–46 game prototyping, 37–38 interview with John Kreng, 46–51 level stubbing walk-through, 31–37 planning level work, 26–31 post level stubbing considerations, 38–45 Level stubbing walk-through, 31–37 building mesh from contour lines, 35 creating contour lines, 34–35 start checking layout details, 37 utilizing file referencing to build up and populate levels, 35–37 working from topographic sketches, 33–34 Level work, planning, 26–31 avoiding common level mistakes, 30–31 prefabricated geometry and modularity, 27–28 scale and grid sizing considerations, 28–30 Levels architecture for game, 5–6 early evolution of, 42–43, 43–44 utilizing file referencing to build up and populate, 35–37 Libraries, game dynamics, 300 Licensing defined, 111 Light color, 59 Light trigger, 149–150 Lighting, 53, 55–63 basic types, 59–60 falloff, 62 light color, 59 lighting falloff, 62 lighting strengths or multipliers, 60–62 position, 58–59 setups, 62–63 strengths or multipliers, 60–62 three sample lighting setups, 62–63 types, 59–60 Lights animating, 64 directional, 60 point or ambient, 60 Line of sight trigger, 146 Lines building mesh from contour, 35 creating contour, 34–35 Loading, case study comments on actor, 99–100 LOD (level of detail), 122 Loops, developmental team feedback, 175–177 M I N D E X 341 Magazine, industry, 287–288 Major League Baseball (MLB), 111, 330 Mapping or level building, 319 Maps, quick topographic, 13–17 Market research, game industry, 290 Marketing departments, 282 Marketing, exploring, 307 Markets, building cell phone gaming, 228–229 Material, reference, 310–316 Material trigger, 148–149 Mattel, 244–245 Maya Embedded Language (MEL), 77 Mechanics MMOG play, 199–200 puzzle game, 116 workings of primary, 45 MEL (Maya Embedded Language), 77 Mesh building from contour lines, 35 geometry and, 31 Message trigger, 149 Microsoft, 244–245 Middleware, 298 MIDP (Mobile Information Device Profile), 219 Mistakes, avoiding common level, 30–31 MLB (Major League Baseball), 111, 330 MMOG, cost and support considerations for, 191–193 bandwidth support issues, 192 COPPA issues, 193 database/backend construction and maintenances, 192 hardware support and maintenance, 192 QA costs, 192–193 security and attack issues, 193 server installation and redundancy, 191 worldwide support staff, 193 MMOG design features, 197–200 latency, 197–198 MMOG play mechanics, 199–200 modularity, 198 monitoring, 198 pace and balance, 198–199
Building Game Worlds 342 U L T I M A T E G A M E D E S I G N player dropout/lost connections, 199 special events, 198 tools support, 198 MMOG player differences from console players, 189 MMOG production challenges, 188–193 cost and support considerations for MMOG, 191–193 defining titles, 189 MMOG player differences from console players, 189 pure production risks for MMOG, 190–191 saturation concerns for MMOG, 190 MMOGs and design orientation, 200–203 current challenges, 203 deep social factors, 202–203 isolating and MMOG strengths, 201–202 MMOG genre growth, 201 MMOG player categories, 202 NPCs and familiars, 201 MMOGs (massively multiplayer online games) box solutions, 301 construction factors and solutions, 194–197 opportunities, 205–206 play mechanics, 199–200 pure production risks for, 190–191 saturation concerns for, 190 structures, 194–197 testing, 171 MMOGs (massively multiplayer online games), design considerations for, 187–213 case study comments on challenges for UBO, 206–209 interview with Michael Weiner, 209–212 MMOG construction factors and solutions, 194–197 MMOG design features, 197–200 MMOG production challenges, 188–193 MMOGs and design orientation, 200–203 sports fans or groups and MMOGs, 203–206 MMOGs, sports fans or groups and, 203–206 MMOG opportunities, 205–206 MMORPG (massively multiplayer online role playing game), 188 Mobile Information Device Profile (MIDP), 219 Modeling packages, 3-D, 296 Modeling, quick, 317–318 Modularity, prefabricated geometry and, 27–28 Mood, reinforcing, 12 Moonlight forest example, 79–80 Motion capture process, 328–329 Motion-tracking, 300 suit, 109, 110 Multiplay cell phone gaming, 226 Multipliers, lighting strengths or, 60–62 N Networks, wireless toy, 226–227 New opportunities, growth areas and, 244–246 NPC actors, 90–91 NPC conversation templates, 140–141 NPC (nonplayer characters), 17 O Odland, Aaron, 130–134 Online, toys and card games go, 249 Opportunities, growth areas and new, 244–246 Organizations, 288 Outsourced testing services, 290 P Packages, 3-D modeling, 296 Paper-based level blocking, 13–17 quick topographic maps, 13–17 Particle emitters, 68–69 Particles, 53, 67–72 exporting particles and dynamics information, 69–72 using particle emitters, 68–69 Passion, maintaining, 257–259 Pathfinding code, 119 Patterns, shooter flying, 141–143 PC; See also Console/PC PC toys, challenges for, 245–246 Perl sample, 140 Perspective, creating, 257–259 Phones cell, 215–235 design issues for cell, 222–230 Picture in view, keeping big game, 42–43 Pipeline, script, 92 Planning and building, level, 23–52
Page 3 and 4:
A BOUT THE AUTHOR Tom Meigs is a ga
Page 5 and 6:
Brandon A. Nordin Scott Rogers Wend
Page 7 and 8:
This page intentionally left blank
Page 9 and 10:
Page 11 and 12:
Building Game Worlds x U L T I M A
Page 13 and 14:
Building Game Worlds xii U L T I M
Page 15 and 16:
Building Game Worlds xiv U L T I M
Page 17 and 18:
Building Game Worlds xvi U L T I M
Page 19 and 20:
Building Game Worlds xviii U L T I
Page 21 and 22:
Building Game Worlds xx U L T I M A
Page 23 and 24:
2 THE game design process begins by
Page 25 and 26:
Building Game Worlds 4 U L T I M A
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
24 AFTER you’ve completed your pr
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
54 FOR a game to be competitive the
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
86 YOU now understand the developme
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Building Game Worlds 100 U L T I M
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
108 UP to this point, we’ve cover
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
130 Building Game Worlds 130 U L T
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
136 SCRIPTING in games gives develo
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
166 ONCE your game environment has
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Building Game Worlds 174 174 U L T
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
188 A whole new avenue for games ha
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
216 ANOTHER new content horizon for
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
238 THERE is a wide and growing ran
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
266 AT some point in your skills gr
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
274 Building Game Worlds U L T I M
Page 297 and 298:
Page 299 and 300:
Building Game Worlds 278 FIGURE 11-
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
286 THIS appendix includes useful r
Page 309 and 310:
Page 311 and 312: Building Game Worlds 290 U L T I M
Page 315 and 316: This page intentionally left blank
Page 317 and 318: 296 MANY types of software tools we
Page 325 and 326: 304 TO assist you to further define
Page 331 and 332: 310 I’VE gathered together a few
Page 343 and 344: 322 AS a point of reference and as
Page 357 and 358: Building Game Worlds 336 Baseball s
Page 359 and 360: Building Game Worlds 338 support so
Page 361: Building Game Worlds 340 Geometry a
Page 367 and 368: Building Game Worlds 346 crowd, 146
show all

Ultimate Game Design : Building game worlds

Create successful ePaper yourself

Delete template?

Save as template?