Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more ➡
Standard view
Full view
of .
Add note
Save to My Library
Sync to mobile
Look up keyword or section
Like this

Table Of Contents

The Shock of the New
The Creative Road Map
Having the Idea
Shaping the Idea
Dramatic Effect
The Treatment
Taking Stock
Case Study 1.1 The One-Page Pitch
Getting it Down
Case Study 1.2 Initial Treatment for Conquerors
What Is a Game?
Cool Features
Fancy Graphics
Setting and Story
Games Aren’t Everything
Games Mean Gameplay
Case Study 2.1 Story Versus Gameplay
Case Study 2.2 A Missed Opportunity?
Creating The Game Spec
Case Study 2.3 Integrating Game Objectives
The Dominant Strategy Problem
Near Dominance
Case Study 3.1 Environment Plus Rules Equals Gameplay
Supporting Investments
Case Study 3.2 Unexpected Versatility
Compensating Factors
Case Study 3.3 Balancing Compensating Factors
Shadow Costs
Case Study 3.4 Shadow Costs in Age of Empires
A Final Word About Gameplay
Kinds of Interactivity
Case Study 3.5 A Different Kind of Interactivity
“Why?” Versus “What?”
The Designer’s Role
Case Study 4.1 A Development Timeline
Design Documentation
The Gameplay Spec
The Designer’s Notes
Case Study 4.2 The Need for Documenting the Spec
Using The Design Documents
Fitting Design To Development
Tiers and Testbeds
Why Use Documents at All?
Player/Player Balance
Player/Gameplay Balance
Case Study 5.1 Is This Supposed to Be Fun?
Reward the Player
Let the Machine do the Work
Make a Game You Play With, Not Against
Case Study 5.2 The Save Game Problem
Gameplay/Gameplay Balance
Component and Attribute Balance
Intransitive Game Mechanics Guarantees Balance
Case Study 5.4 Attribute Balance Using SPS
A Game Balance Checklist
Case Study 6.1 Sound Effects at Their Best
Case Study 6.2 A Discordant Note
Case Study 6.3 Meshing the Interface with Look and Feel
Case Study 6.4 Sometimes Less Is Less
A Toolbox of Storytelling Techniques
Case Study 6.5 An Example of a Look-and-Feel Document
Case Study 6.6 An Unexpected Development
Case Study 6.7 An Unsatisfying Conclusion
The Sum of the Parts
The Professionals
The Game Concept
Planning for Change
The Technology
The Team
Costs and Timelines
The Future
The Necessity of Design
Don’t Be Afraid to Plan
Case Study 8.1 Design Saves Time
Why Design Is Fine
Case Study 8.2 Keep the Design up to Date
Essentials of Game Design
Is it Original?
Is it Coherent?
Is it Interactive?
Is it Interesting?
Is it Fun?
The Future of Design
Making Designs More Generic
Nonsymbolic Design
The Future of Games
The Next Decade
The Strengths of Software
The Crossroads of Creativity
Case Study 8.4 An Example of Mise En Scene
Games as Entertainment
The Way Forward
The Current Development Model
The Origins of the Industry
The Trouble with Game Developers
The Problem Developer
Excessive Long Hours Mean an Unsuccessful Project
Exceptions to the Rule
Morale Booster Caveats and Warnings
Spreading the Risk
What Is a Software Factory?
Why Use a Software Factory?
Solving Game Development Issues
Case Study 11.1 The Effects of Losing Key Personnel
Case Study 11.2 Code Reuse
Organizing a Software Factory
A Structural Overview
Group Responsibilities and Interactions
Case Study 11.3 Ineffective Problem Handling in Action
Case Study 11.4 Effective Problem Handling in Action
Case Study 11.5 The Benefits Of Tool Reuse
Applying the Software Factory Structure and Methodology
Getting off the Ground
Rotating and Reassigning Team Members
Case Study 11.6 The Indispensables
The Suitability of a Software Factory
Smaller Teams
The Final Word
How Milestones Currently Work
Fuzzy Milestones
Milestones and Mini-Milestones
When to Use Milestones
Making Your Milestones Accurate
Case Study 12.2 The Costs of Canceling Projects
Checkpoint 1.0 General Requirements Gathering
Checkpoint 1.1 Technological Requirements Gathering
Checkpoint 1.2 Resource Requirements Gathering
Checkpoint 2.0 General Feasibility Study
Checkpoint 2.1 Technological Feasibility Study
Checkpoint 2.2 Resource Availability Study
Checkpoint 3.0 Draft Architecture Specification
Checkpoint 3.1 Project Initialization
The Next Steps
Defining Milestones
Bad Milestones
Good Milestones
Case Study 12.3 A Real-Life Milestone
Research Versus Deadlines
Evaluation of Milestones
Testing in General
Case Study 13.1 Process Gone Mad
Procedures: Where to Use Them?
The Design Phase
The Development Phase
The Testing Phase
Source Control and Code Reviews: A Synergy
What Should Source Control Be Used For?
The Importance of Information Transmission
Proactive and Reactive Information Transmission
Design and Architecture Problems
Case Study 14.1 The Case of the Deaf Manager
Schedule Threats
Case Study 14.2 Applied Schedule Readjustment
Organizational Problems
Contractor Problems
Personnel Problems
Development Problems
Process Problems
The State of the Industry
The First Era
The Second Era
The Third Era
Violence in Games
The New Model Developers
Case Study 15.1 It’s Hard for Developers
The Online Revolution
Delivering Games Online
Playing Games Online
The History of Development Techniques
The Rise and Fall of the Original Game Idea?
The Development Environment
The Present Day
The Beginning
Case Study 17.1 Abstraction in Quake II
Hardware Abstraction
Graphics Hardware Abstraction
Sound Hardware Abstraction
Other Hardware Considerations
“Not Built Here” Can Be Better
The Twilight Zone
The Problem Domain
What Is a Game? (Revisited)
Thinking in Tokens
Tokenization of Pong
Case Study 17.2 The Inflexibility Trap
The State of the Art
The Rise and Fall of the 3D Engine
The Perception of Technology
Case Study 18.1 A First Impression
Blue-Sky Research
Research Types
Case Study 18.2 Losing Sight of the Ball
Case Study 18.3 Tetris: A Caveat
Case Study 18.4 Outcast: Good Use of Technology
Keeping a Journal
Reinventing the Wheel
Use of Object Technology
The Pros and Cons of Abstraction
Reusability in Software
Code Reuse
Case Study 19.1 Reuse of Engines
Design Reuse: Patterns
Game-Specific Patterns
The Birth of an Architecture
Architectural Concepts
The Tier System
Tier Zero: The Prototype
Tier One and Beyond
Case Study 20.1 A Database-Driven Approach
Architecture Design
Applying the Tier-Based Approach to Architecture Design
Case Study 20.2 Discussing the Architecture of Warbots
Architecture Orthogonality
The Development Process
Code Quality
Coding Standards
Coding Priorities
Debugging and Module Completion
Types of Bugs
Case Study 21.1 Class A Bugs or Not?
The Seven Golden Gambits
Case Study 21.2 Reusable Architecture
Design First
Catch Mistakes as You Go Along
Limit R&D
Know When to Draw the Line
The Three Lead Balloons
Bad Management
Feature Creep
Coder Insularity
Late Evaluation
Final Analysis
Case Study 22.6 Keep Something Back
Case Study 22.7 How Did They Miss These!?
Focus Groups
The Web Site
Getting Ready for the Gold Master
Case Study 23.1 A Tale of Two Projects
Team Dynamics
Case Study 23.2 It’s All Gone Horribly Wrong!
Case Study 23.3 Misjudging the Climate
Software Planning
Case Study 23.4 Oubliette
Business Aspects
Case Study 23.5 Secure Your Revenue Stream
The Postmortem Postmortem
Development in Context
Future Development
Case Study 24.1 Marketing Means Targeting
Case Study 24.2 Development Without Strategy
Small Is Beautiful Too
Building the Team of the Future
New Directions in Development
The Holistic Approach
“Jurassic Park” Software
Immanent and Transcendent Worlds
The Shape of Things to Come?
Sample Game Design Documents
➤ Detailed design discussions
Detailed Design Discussions
1. Balls! Introduction
2. Overview of Gameplay
3. Platforms
4. Time Scales
5. Why Puzzle Games Aren’t as Good as They Used to Be
6. Puzzle Game Appeal
7. Why Balls! Would Be Good
8. Game Design: User Interface Elements
9. Physics of Balls!
10. Blocks
11. Special Case Block-Block Collisions
12. Playing the Game
13. Further Embellishments
Initial Treatments and Sample Designs
Racketeers: Gang Warfare in the Roaring Twenties
1. Overview
2. Game Objectives
3. Graphics
4. Playing a Game
5. Character Types
Non-Gang Members
6. Personality
7. Orders
8. Combat
9. The Game World
10. Joints
11. Messages
12. Tutorial Campaign
13. Target Platform
1. Introduction
2. Game Elements
3. How Does it Play?
Technical Specifications
Code Review Form
Test Scripts
Bibliography and References
0 of .
Results for:
No results containing your search query
P. 1
Game Architecture and Design

Game Architecture and Design

Ratings: (0)|Views: 9,427|Likes:
Published by Alexander Cage

More info:

Published by: Alexander Cage on Apr 07, 2011
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See More
See less





You're Reading a Free Preview
Pages 20 to 73 are not shown in this preview.
You're Reading a Free Preview
Pages 93 to 272 are not shown in this preview.
You're Reading a Free Preview
Pages 292 to 521 are not shown in this preview.
You're Reading a Free Preview
Pages 541 to 720 are not shown in this preview.
You're Reading a Free Preview
Pages 740 to 960 are not shown in this preview.

Activity (4)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
kkkk1330 liked this
dave_765 liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->