Monday, April 19, 2010

Design de Jogos Br 005 - Bases do Design de Jogos (parte 5)

OMG! Afinal, WTH é Gameplay? :P

Como foi falado em outros episódios do meu querido e disfuncional programa, você vai se deparar, por um sem número de vezes com jogos que utilizam vários sistemas de poder de uma vez só. Alguns games são uma verdadeira orquestra de poderes...às vezes com excelentes composições e às vezes com um zumbido por música. Pra ser uma ótima orquestra, tudo vai depender de uma boa interação e de uma consequente harmonia entre os instrumentos utilizados. :P

Pois é meus amigos, quando agregamos à idéia de um jogo determinados sistemas de poder, estamos dando um grande passo relativo ao processo que dará vida ao que posteriormente constituirá algo que comumente chamamos de gameplay.

Mas vocês sabem definir com exatidão o que exatamente é a gameplay de um jogo???? O que a constitui? Qual é o papel desta componente "gamística" na experiência do jogador?

A resposta para a maioria destas perguntas pode ser simples, mas também pode ser complexa... Chegar a um resultado conclusivo, por exemplo, com relação ao que define gameplay, sempre gerou uma boa dose de controvérsia entre os profissionais da área. Porque tudo vai depender da forma como você resolve abordar esse famigerado conceito...

Mas em termos simples, gameplay é todo e qualquer evento integrante de um jogo, que tenha um fator de interatividade agregado a si.

Em termos mais simples ainda, gameplay pode ser definida como o conjunto de coisas que torna possível diferenciar a experiência de se jogar um ótimo game, da de se ler um ótimo livro ou da de se assistir um filme fodástico. Ou seja, gameplay, pode ser definida como o espírito do jogo manifestado através de um processo interativo. Um conjunto de regras que gerencia o fluxo das ações no game. Aquele fator que torna o jogo um jogo.

Acho que já deu pra se ter uma idéia sobre quais são os elementos que ajudam a constituir a gameplay de um jogo né? É só usar um pouco a imaginação...! :D

Enfim, quando desenvolvemos um ou mais sistemas de poderes e os distribuímos em um universo virtual, geralmente isso vai implicar uma interação entre eles, através do jogador e dos vários outros objetos do seu mundinho virtual. Lembram do exemplo da orquestra...? Pois é, no design de games, os instrumentos são esses sistemas de poder aliados às características mais pertinentes aos objetos do jogo. :)

Só a nível de nota. Vocês já perceberam também, que não é apenas ao jogador que são conferidos poderes...? Percebam! :P

Enfim, tudo o que existe no mundo virtual e que pode interagir com o os poderes atribuídos ao jogador e/ou com outras coisas desse mundo, contribui para gerar, dependendo do jogo, uma grande quantidade de sistemas intercalados.

Cada atributo, ou regra, que o designer decide inserir em um dado mundo, deve ser minuciosamente testado em combinação com outros atributos da mecânica. Ao realizar esses testes os designers e testadores têm como objetivos principais:

  1. Verificar a consistência das regras estabelecidas para interações no mundo virtual - isso inclui a busca por possíveis bugs;
  2. Otimizar o nível de diversão gerado pelo sistema de regras do jogo;
  3. Analisar o espectro de gameplay emergente do sistema.


GAMEPLAY EMERGENTE!! Esse é um novo termo mencionado nessa série...e é de extrema importância! Acreditem! ^^

Por que será que é tão importante realizar o que o item 3 propõe durante os testes?! O_o

Vejamos...

A melhor forma de se entender isso, parte de uma base de conhecimento mínimo sobre o que seria essa tal de gameplay emergente! :) E é essa base mínima que vou tentar ensinar aqui, agora...!

Cara, é tipo assim... Geralmente, quanto mais complexo for o sistema que compõe a gameplay do jogo, maior será o número de possíveis interações entre as componentes desse sistema. E o número de possíveis interações pode ficar extremamente GIGANTESCO dependendo do número de componentes e da complexidade de cada uma! E isso, meus caros, pode desencadear o surgimento de outros sistemas de gameplay dentro do sistema original. Um sistema que pode ser bem diferente daquele que os designers tinham em mente. Um descuido na análise dessas interações pode acarretar sérios problemas... A integridade de um jogo pode ficar passível de ser bem danificada.

Mas não pense que gameplay emergente é definitivamente a desgraça na vida do game designer, porque não é! Em muitos casos é exatamente o contrário! Vocês sabiam da lenda, por exemplo, que diz que o sistema de combos em jogos de luta surgiu a partir de um sistema de gameplay emergente - e desproposital - da capcom durante a produção de Street Fighter II? Pois é... :P

Essa emergência só seria uma desgraça se esse novo sistema de alguma forma acabasse com a diversão da experiência interativa... Lidar com emergência, de alguma forma é como manipular elementos radiotivos... :P Ao lidar com isso, você tem o potencial de trazer coisas magníficas a existência... Mas se não tomar cuidado, pode acabar explodindo um quarteirão...ou pelo menos fazendo alguém jogar um console, com seu jogo dentro, pela janela do décimo andar de um edifício...então...VAMOS TOMAR CUIDADO P****! :P

Se trabalharmos com cautela e humildade (sempre tendo noção de que erros são normais de acontecer com todos), tenho certeza de que poderemos utilizar a emergência de gameplay a nosso favor para criar uma experiência de boa complexidade e bem intuitiva, que consequentemente renderá horas e horas de boa experiência gamística!! :)

Por enquanto é só pessoal...
Até o próximo episódio! \o

Samuel

Design de Jogos Br

Vídeos com os 5 primeiros episódios de uma série sobre design de games que eu estou tentando montar.







Tuesday, October 6, 2009

A Theory of Fun for Game Design - by Raph Koster (Summary - PVIII)

Chapter 8: The Problem With People

  • The holy grail of game design is to make a game where the challenges are never-eding, the skills required are varied and the difficulty curve is perfect and adjust itself to exactly our skill level. Someone did this already, though, and it's not always fun. It's called "life".
Try to design abstract systems that have deep self-generating challenges.

Emergent Behavior -> New patterns that emerge spontaneously out of the rules. Emergence has proven a tough nut to crack in games, it usually makes games easier, often generating loopholes and exploits.

Storytelling -> Most games melded with stories tend to be Frankstein monsters. Most players tend to skip the story or skip the game.

Placing Players Hand-to-Hand -> Other players are an endless source of new content. But players hate to lose, so if you fail to match them up with an opponent who is very precisely at their skill level, they'll quit.

Using Players to Generate Content -> Many games expect players to supply the challenge in various ways, raging from making maps for a shooter game to contributing characters in a role-playing game.

  • If something has worked for us before, we'll tend to do it again. We're really very resistant to learning.
  • We're conservative at heart, and we grow more as we age.
Features that make the experience a learning experience:

- Greater skill in completing the challenge should lead to better rewards;
- High-level players can't get big benefits from easy encounters or they will bottom-feed, and the inexpert players will be unable to get the most out of the game;
- Failure must have a cost.

  • Most long-lasting games in the past have been competitive because they lead to an endless supply of similar yet slightly varied puzzles.
  • If we come across a problem we've had encountered in the past, our first approach is to try the solution that has worked before, even if the circunstances aren't exactly the same.
  • Sticking to one solution is not a survival trait anymore. The world is changing very fast and we interact with more kinds of people than ever before. The real value now lies in a wide range of experiences and in understanding a wide range of points of view. Closed-mindedness is actively dangerous to our society because it leads to misapprehension. And misapprehension leads to misunderstanding, which leads to offense, which leads to violence.
  • Engaging in an activity that you had fully mastered, being in the zone, feeling the flow, can be a heady experience. And no one can deny the positive effects of meditation. If gamers find themselves in tune with a game, they may play it for longer than they need to in order to master it, because being in the zone feels good.
  • Games must encourage the player to move on.
  • Every once in a while games come along that appeal to the masses, and thank goodness. Because priesthoods are a perversion of what games are about. The worst possible fate for games would be for games to become niche, something played by only a few elite who have the training to do so. It was bad for sports, it was bad for music, it was bad for writing, and it would be bad for games as well.
  • The most creative and fertile game designers working today tend to be the ones who make a point of not focusing too much on other games for inspiration.
  • It's critical that games should be placed in context wih the rest of human's society endeavors.



Monday, September 21, 2009

A Theory of Fun for Game Design - by Raph Koster (Summary - PVII)

Chapter 7: The Problem With Learning

  • The mind likes to take shortcuts when solving problems. In other words, many people are willing to cheat.
  • Cheating is a long term tradition in warfare, where it is acknownledged as one of the most powerful and brilliant of all military techniques.
  • When a player cheats in a game, he is choosing a battlefield that is broader in context than the game itself.
  • Cheating may be a sign that the player is grokking the game.
  • Gamers will try to make the gameplay as predictable as possible. This then means that the game will become boring and not fun.
  • We dislike tedium, sure, but the fact is that we crave predictability. Our whole life is built on it. Unpredictable things. Unpredictable things are like drive-by shootings, lightining bolts that fry us, smallpox, food poisoning - unpredictable things can kill us.
  • Since we dislike tedium, we'll allow unpredictability, but only inside the confines of predictable boxes, like games or tv shows.
  • Games package up the unpredictable and the learning experience into a space and time where there is no risk.
  • Unpredictability means new patterns to learn. Therefore, it can generate fun.
  • The natural instinct of a game player is to make the game more predictable because then they are more likely to win.
  • Bottom-feeding: player taking on weaker oponents under the sensible logic that a bunch of sure wins is a better strategy thn gambling it all (minimizing risks).
  • Rewards are one of the key components of a successful game activity.
  • Successful games tend to incorporate the following elements:
1. Preparation: Prior moves in a game, like healing up before battle, are automatically part of the preparation stage because all games consist of multiple challenges in sequence.
2. A Sense of Space: The space might be the landscape of a war game, a chess board, or a networking of relationships between players during a bridge game.
3. A Solid Core Mechanic: This is a puzzle to solve, an intrisically rule set into which content can be poured. The core mechanic is usually a small rule; the intrincacies of games comes usually from having a lot of mechanics or having a few, very elengantly choosen ones.
4. A Range of Challenge: Content. It does not change the rules, it operates within the rules and brings slightly different parameters to the table. Each enemy you might encounter in a game is one of these.
5. A Range of Abilities Required to Solve the Encounters: If all you have is a hammer, and you can only do one thing with it, then the game is going to be dull. This is a test that tic-tac-toe fails but checkers meets.
6. Skills Required in Using the Abilities: Bad choices lead to failure like: failures in timing, failures in physical dexterity, and failure to monitor all the variables that are in motion. But you need to be very careful when requiring those abilities, for you don't want to frustrate the player.

A game having all these elements hits the right cognitive buttons of fun.

Sunday, September 20, 2009

A Theory of Fun for Game Design - by Raph Koster (Summary - PVI)

Chapter 6: Different Fun for Different Folks

There are seven categorized forms of inteligence:

1. Linguistic;
2. Logical-Mathematical;
3. Bodily-Knesthetic;
4. Spatial;
5. Musical;
6. Interpersonal;
7. Intrapersonal.

  • People are not likely to tackle patterns and puzzles that appear as noise to them. They'll likely select problems that they think they have a chance at solving.
  • On average, females tend to have great trouble with certain types of spatial perception. Males tend to have great problems with language skills.
  • Since different brains have different strengths and weaknesses, different people will have differente ideal games;
  • Men not only navigate space differently, but they tend to learn by trying, whereas women prefer to learn through learning another's behavior.
  • It's clear that players prefer other types of games in ways that seems to correspond their fun personality. What does it all means to game designers? Ut means that not only will a given game be unlikely to appeal to everyon, but that it's probably impossible for it to do so.
  • The difficult ramp is almost certain to be wrong for many people.
  • This may indicate a fundamental problem with games. Since they are formal abstract systems, they are by their very nature biased toward certain types of brains, just as books are biased.
  • Perhaps the answer is simpler. Maybe games are more likely to appeal to young males because these players are good at mastering formal abstract systems.
  • Both genres should seek out games that address their weakness.

Wednesday, September 9, 2009

A Theory of Fun for Game Design - by Raph Koster (Summary - PV)

Chapter 5: What Games Aren't

  • People tend to dress up game systems with some fiction. Designers put artwork on them that is suggestive of some real-world context.
  • The fiction serves two purposes: it trains you to see past it to the underlying problem, and it also trains you to recognize real-world situations where the problem might be lurking.
  • Usually there are metaphors for what is going on in the game. While metaphors are fun to play with, players can basically ignore them.
  • Since games are about teaching underlying patterns, they train players to ignore the fiction that wrap patterns.
  • The commonest route these days for developing games involves grafting a history onto them. But most video game developers take a usually mediocre story and put little game obstacles all through it. It's as if we are requiring the player to solve a crossword puzzle in order to turn the page to get more of the novel.
  • The stories that wrap up games are usually side dishes for the brain. For one thing, it's damn rare to see a game story written by an actual writter. For another, since games are generally about power, control, and other primitive things, the stories tend to be so as well. This means that they tend to be power fantasies. Story deserves better treatment than that.
  • Games are not stories. It's interesting to make the comparison though:
  1. Games tend to be experential teaching. Stories teach vicariously.
  2. Games are good at objectification. Stories are good at empathy.
  3. Games tend to quantize, reduce, and classify. Stories tend to blur, deepen, and make subtle distinctions.
  4. Games are external - they are about people's actions. Stories - good ones anyway - are internal, they are about people's emotions and thoughts.
  • Physical challenges alone aren't fun. The feeling of triumph when you break a personal record is.
  • Throughout the book, fun is referred only as mentally mastering problems. Often, the problems mastered are aesthetic, physical, or social, so fun can appear in any of these settings.
  • The brain rewards you for an autonomic response when they are given in the context of a mental challenge.
  • Delight strides when we rocognize a pattern but are surprised by them. Unfortunately, it doesn't last. It's like the smile of a beautiful stranger in a starwell - it's fleeting. It cannot be otherwise - recognition is not an extended process.
  • We find things beautiful when they are very close to our idealized image of what they should be but with an additional surprise wrinkle.
  • Real fun comes always from challenges that are at the margin of our abilities.
  • As we succeed in mastering paterns thrown at us, the brain gives us little jolts of pleasure. But if the flow of new patterns slows, then we wont't get the jolts and we'll start to feel boredom. If the flow of patterns increase beyond our abilities, then we won't get the jolts either, because we're not making progress.
  • Meditation induces brainwaves that are similar to the ones of the flow state.
  • Fun is about learning in a context where there is no pressure.

A Theory of Fun for Game Design - by Raph Koster (Summary - PIV)

Chapter 4: What Games Teach Us

As we age, we think things are more serious and that we must leave frivolous things behind. Is that a valid judgement on games or is it a value judgment on the content of a given game? Do we avoid the notion of fun because we view the content of the fire drill as being of great import?

  • The very phrase "it's just a game" implies that playing a game is a form of practice for a real life challenge.
  • Exploring possibility space is the only way to learn avout it. Most games repeatedly throw evolving spaces at you so that you can explore the recurrence of symbols withim them.
  • Some of the really important parts of exploration involve memory. A huge number of games involve recalling and managing very long and complex chains of information. (ex: dominoes)
  • In the end; most games have something to do with power. Even the innocuous games of childhood tend to have violence lurking in their heart of hearts.
  • Action games for example, they are all about reaction times, tactical awareness, assessing the weakness of an opponent, and judging when to strike.
  • We pay attention to the obvious nature of a particular game and we miss the subtler point.
  • Many games, particularly those that have evolved into the classic Olympian sports, can be directly traced back to the needs of primitive humans to survive under very difficult conditions.
  • We do in fact evolve games that are more suited to our modern lives.
  • Traditional role-playing can reach the same heights as literature in the right hand. But it's an uphill battle nonetheless, simply bacause games are at their core about teaching us survival skills. As we all know, when you're worried about subsistence and survival, more refined things tendo to fall by the wayside.
  • It's still valuable to train ourselves in some of the caverman traits, but we need to adapt. It's worth asking ourselves what skills are more commonly needed today.
  • Some of the new patterns we need to learn in our brave new world run contrary to our instinctive behaviors. For example, humans are tribal creatures. Most games encouraging demonizing the opponent, teaching a sort of ruthlessness that is a proven survival trait. But these days, we're less likely to need or want the scorched-earth victory. Can we create games that instead offer us greater insight into how the modern world works?
  • Since the introduction to the concept of grabbing and using a weapong in a game was introduced not much has changed. The difference is that, today, instead of a single weapon for us to use in the game, we have a bewildering array of weapons.
  • Possible algorithm for innovation -> find a new dimension to add into the gameplay. Recent games have included more robust stories and even elements from role-playing games. Are there more dimensions on which to expand?

A Theory of Fun for Game Design - by Raph Koster (Summary - PIII)

Chapter 3: What Games Are

  • A "magic-circle" that is disconnected from reality;
  • Choice, Rule, and Confront;
  • Games are puzzles to solve, just like everything else we encounter in life. They are in the same order as learning to drive a car, or picking up the mandolim, or learning your multiplication tables.
  • The only difference between games and real life is that the stakes are lower with games.
  • Games serve as very fundamental and powerful learning tools.
  • Play a goal-oriented game involves simply recognizing a particular sort of pattern; playing make-believe is recognizing another one. Both deservely belong in the same category of iconified representations of human experience that we can practice with and learn patterns from.
  • Books will never be able to accelerate the groking process to the degree that games do, because you cannot practice a pattern and run permutions on it with a book.
  • Games are puzzles - they are abouth cognition and learn to analyze patterns. Games that fails to exercise the brain becomes boring.
  • Extremely formal games have few variables. To make games more long-lasting, they need to integrate more variables (and less predictable ones) such as human psychology, physics, and so on.
  • When you are playing a game it exercises your brain, but you'll only play it until you master the pattern. When a game stops teaching us, we feel bored;
  • Games grow boring when they fail to unfold new niceties in the puzzles they present.
  • The brain doesn't necessarily craves for new experiences - it just craves for new data. A new experience may force a whole new system on the brain, and often the brain doesn't like that. It's disruptive.

Way of Boredom

  1. The player might grok that there is a ton of depth to the possible permutations in a game but conclude that these permutations are below their level of interest.
  2. The player can't see the pattern (noise).
  3. Slow variations in patterns.
  4. The game might also unveil the variations too quickly, which then leads to players losing control of the patterns and giving up because it looks noisy. "This got too hard too fast!" they will say.
  5. When the game ends for the first time.

The definition of a good game is therefore "one that teaches everything it has to offer before the player stops playing."

Games are very good teachers...of something. The question is, what do they teach?


Tuesday, September 8, 2009

A Theory of Fun for Game Design - by Raph Koster (Summary - PII)

Chapter 2: How the Brain Works

Definitions of Game word:

  1. A rule-based formal system with a variable and a quantifiable outcome, where different outcomes are assigned different values. The player exerts effort in order to influence the outcome, the player feels attached to the outcome, and the consequences of the activity are optional and negotiable.
  2. A subset of entertaining limited to conflit.
  3. A series of meaningful choices.
  4. Ernest Adams and Andrew Rollings: one or more casually linked series of challenges in a simulated environment;
  5. A system in which players engage in an artificial conflict, defined by rules, that results in a quantifiable outcome.
  • The human brain is a most voracious consumer of patterns. Games are just exceptionally tasty pattern to eat up.
  • The brain is hardwired for facial recognition, just as it's hardwired for language, because faces and language are incredibly important to how human society works.
  • Assumptions is what the brain is best at.
  • In fact, we tend to see patterns were there aren't any.
  • The brain is good at cutting the irrelevant.
  • But the brain notice a lot more than we think he does.
  • The brain is actively hiding the real world from us. In fact, seeing what actually is there with our conscious mind is really hard to do, and most people never learn how to do it.
  • When we grasp a pattern, we usually get bored with it, and iconify it.
  • We rarely look at the real world; we instead recognize something we have chunked, and leave it at that - for example, we can drive barely seeing the road.
  • If we are able to divide a paiting into boxes of different proportions, we'll usually think the paint is pretier than if we couldn't.
  • Excess -> chaos -> noise -> ugliness.
  • Noise is any pattern we don't understand.
  • Music is ordered sound and silence.
  • There's really next to nothing in the visible universe that is patternless. If we perceive something as noise, it's most likely a failure in ourselves, not a failure in the universe.
  • Once we see a pattern we delight in tracing it and in seeing it reocur. We call this practicing, and the more we do it, the less we have to think about what we're doing.
  • Conscious thought (1st level) -> mathematical level.
  • Interrogative, associative, and intuitive thoughs (2nd level) -> Link things that doesn't make much sense. Doesn't use words. It's frequently wrong. Builds approximation of reality.
  • Usually, we make whole sets of decisions instinctively.
  • Building up a library is also what we call practice. Studies have shown that you don't even have to do something physically in order to grasp it. You can just think about doing it and it'll get you much of the way there.
  • When our brain is really into practicing something, we'll dream about it. This is the intuitive part of the brain burning nerval pathways into our brain.
  • So, basically it'a fun to exercise our brain.

A Theory of Fun for Game Design - by Raph Koster (Summary - PI)

Chapter 1 - Why Write This Book?

  • Many believe that language is built into the brain and that there's something in our wiring that guides us inexorably toward language.

  • Why there are games fun and other games boring? Why do some games start getting boring after a while, and other games stay fun for a long time?

  • People are pattern matching machines.

Monday, August 31, 2009

Learning XNA 3.0 by Aaron Reed (Chpters 1 and 2, Book Summary)


Chapter 1 - Getting Started
In order to use XNA you'll need to have installed Windows XP(SP2/SP3)/Vista) and Visual C# 2008 or Visual Studio 2008. After that you'll need to download XNA Game Studio 3.1.

Almost all types of code you write for PC using XNA 3.0 can be directly ported to both Zune and Xbox 360.

The program.cs file is pretty straightforward. Your Main method, which creates a new object of Game1 type and executes its Run method, is located in this file.

The real guts of your game lie in the Game1.cs file.

Chapter 2 - Fun With Sprites

  • GraphicsDeviceManager;
  • Acts as a conduit between XNA and GPU
  • Require for every action taken to the screen
  • SpriteBatch
  • Generate core object to draw sprites
  • 2D or 3D images integrated into a larger scene.
  • Initialize Method
  • Initialize variables and other objects associated with Game1 object.
  • GraphicsDeviceManager object is instantiated at this point.
  • LoadContent
  • Instantiates spriteBatch
  • Called whenever new content is in need to be loaded.
  • After it’s called, Game1 object enters in a state known as game loop.
  • Game Loop
  • Update
  • The logic calculations should take place here
  • Draw
  • It's better to be used only to draw
  • Game Development Versus Polling
  • Polling
  • The applications is alwasys performing actions regardless of user input
  • You have to account for a bunch of user inputs and the implications of such inputs to the game.
  • Registering Events
  • The application awaits user input to resume its actions.
  • Game States
  • Defines some changes in the game behavior
  • Change of state must take place in the Update Method
  • Drawing implications of that should be implemented in the Draw method


Basic Lifecycle of an XNA game.

  • Unload Content
  • Allows special handling of memory for objects.
  • Garbage collection is taken care of by XNA.
  • Modifying Your Game
  • The gameTime variable
  • Used to gauge things such as framerate, animations, sounds, and other effects.
  • GraphicsDevice objects' clear method
  • Erases everything on the screen, and covers it with the specified color.
  • Adding a Sprite to Your Project
  • All graphics, sounds, effects, and other items are loaded in XNA through something called the content pipeline.
  • content pipeline
  • convert loaded files, if necessary
  • You can view if the added items were accepted by right-clicking the item in Solution Explorer and selecting Properties
  • Uses an asset name to access content resources
  • File's name without the file extension, by default.
  • Asset names only need to be unique within each content folder.
  • A texture refers to a 2D image that will typically be applied to a surface of some object.
  • Loading and Drawing Your Sprite
  • Before you have access to content from the inside of the code, you need to load them from the content pipeline into variables.
  • Texture2D type variables.
  • To access data from the content pipeline, you use the Content (ContentManager type) property of the Game class.
  • Provides access to all objects loaded in the content pipeline.
  • ContentManager
  • Load method.
  • Content.Load(@"path_to_file");
  • The path starts with the Content node in Solution Explorer.

----------------------------------------------------------------------------------
spriteBatch.Begin( );
spriteBatch.Draw(texture, Vector2.Zero, Color.White);
spriteBatch.End( );
----------------------------------------------------------------------------------



  • In 2D XNA games, the X, Y screen coordinate (0,0) is the top-left corner of the screen; coordinates move in positive X to the right and positive Y downward.
  • Window.ClientBounds
  • When a game is run in Windows, Window.ClientBounds.X and Window.ClientBounds.Y correspond to the upper-left coordinate of the game window, while the Width and Height properties of Window.ClientBounds are always equal to the width and height of the window.
  • On the Xbox 360 and the Zune, Window.ClientBounds.X and Y are always 0, while the Width and Height properties of Window.ClientBounds are always equal to the width and height of the display (because both Zune and Xbox 360 games are always run in full-screen mode).
  • Texture2 variables have Width and Height properties that hold the size of the image.
Transparency and Other Options

  • Mainly for performance reasons, you should draw as many sprites as you can in a single SpriteBatch Begin and End block.
  • XNA Automatically renders solid magenta (255,0,255) portions of images trasnparent.
  • Certains types of file format such as .png make use of an alpha channel - each pixel has an additional alpha channel that determines the transparency of the pixel.
  • SpriteBatch.Draw(Texture, Position, SourceRectangle, Color, Rotation, Origin, Scale, Effects, LayerDepth)

Layer Depth
  • XNA lets you specify a layer depth for each individual image, which allows you to always place images in the right Z order. In order to do that you must make use of the last presented overloaded Draw method.
  • The layer depth parameter is represented by a float value that must be between 0 and 1. The valye 0 corresponds to what XNA calls the front of the Z order; the value 1 represents the back of the Z order.
  • In order to use layer depth values to sort your images, you need to use an overload of Begin that takes a parameter of type SpriteSortMode. One of these overloaded methods is: SpriteBegin(SpriteBlendMode,SpriteSortMode,SavestateMode);
  • In order to animate sprites along the screen, you'll need to update their positions in the Update method. For that, you'll may find useful to create Vector2 and float type variables.
  • The vector type variables, will be used to determine the object's location on the plane when you draw;
  • The float type variables can be used to update the sprites' coordinates, accounting as a speed factor.
Animation
  • Animations are made up of standalone images, and flipping through the images in a cycle causes them to appear animated.
  • Sprite animations are laid out in a single sheet, and you pull out individual images from that sheet and draw them on the screen in a specific order. These sheets are referred to as sprite sheets.
  • In order to draw only a specific portion of the sprite sheet, you'll need to make use of the third parameter of the overriden Draw method shown above of the green table just up at this page.
  • There are few things you need to know in order to build an algorithm that will cycle through each image encompassed into each sub-rectangle:
  1. The height and width of each individual image (or frame) in the sprite sheet;
  2. The total number of rows and columns in the sprite sheet;
  3. An index indicating the current row and column of the image in the sprite sheet that should be drawn next.
With these parameters in hand, you can build a source rectangle to pass to the Draw method;

To make things easier, you may find useful the use of Point object to store these values: Point(int x, int y);

To animate sprites using a sprite sheet you'll also be using the Rectangle object: Rectangle(int init_x, int init_y, int width, int height), which will be passed in the draw method;

Adjusting the Framerate

  • As mentioned before, framerate generally refers to how many times per second a game redraws the entire scene. In XNA, the default is 60 fps.
  • There's a type of framerate related to individual animations. This framerate (often referred to as animation speed) reflects the rate at which a given animation cycles through images in the sprite sheet.
  • XNA's Game class has a property called TargetElapsedTime, of the TimeSpan type, which tells XNA how long to wait between calls to the Game.Update method.
  • The GameTime object, which is passed in as a parameter in both the Update and Draw methods, has a Boolean property called IsRunningSlowly. If its value is true, XNA isn't able to keep up with the framerate. In this case XNA will skip Draw calls in a effort to keep up with your intended speed.
  • The speed of the graphics card GPU, the speed of the computer's processor, the number of resources you consume, and the speed of your code, go a long way toward determining whether your game will have that peak performance.

Adjusting the Animation Speed

If you wanted one image to animate at 60 fps and another to animate at 30 fps, you wouldn't be able to accomplish that by adjusting the overall game's framerate.

To adjust the frame animation individually for an object you may use two variables of the int data type to keep track of the last time you changes frames and to only change frames every X number of milliseconds:

int timeSinceLastFrame = 0;
int millisecondsPerFrame = 50;

timeSinceLastFrame => registers how much time has passed since the last frame skip
millisecondsPerFrame => determines the frame skip rate.

These variables would be used in the Update method to determine the framerate of a given object probably like this:



As you can see here, you use the gameTime.ElapsedGameTime property to determine how much time has passed since the previous frame change. This property indicates how much of time has passed since the previous call to Update. You add the Milliseconds property of that object to your TimeSinceLastFrame variable. When the value of that variable is greater than the number of milliseconds you want to wait between frame changes, you enter the if statement, adjust the TimeSinceLastFrame variable by subtracting the value in MillisecondsPerFrame, and then change the animation frame.

Conclusion: While the dafault framerate in XNA draws a new frame every 16 milliseconds, that is nothing compared to the default framerate of Chuck Norris' fists. On average, Chuck's fists punch and mortally wound enemies every 4 milliseconds! O.O

Monday, June 9, 2008

Multi-Player (Game Design: Theory and Practice)

Game Design:Theory and Practice (Book's Summary:Part 11)

Book’s Author: Richard Rouse III

Summarized by Samuel Coelho

10. Multi-Player

Though the AI agents take the place of the other players to play a non-computer game, in many ways it is truly the designer who takes the place of the other players.
Multi-player games are as old as game themselves, with single-player games such as solitaire being in the extreme minority of available choices.

10.1 Motivations

Many developers see the most immediate advantage of multi-player games as the ability to replace AI opponents with real humans in order to provide much deeper and more unpredictable adversaries. This increases the amount of challenge a game can provide, and allows a game to stay compelling for a much longer period of time.

An even more significant advantage to having human opponents is the ability for the players to socialize.

The presence of real players for opponents brings with it a tremendous change in the players’ perceived importance of playing the game; instead of just winning or losing the game in private, through their social component multi-player games make each win and loss a public affair and thus significantly more meaningful.

Thus, multi-player games provide for players a challenge, a social experience, the potential for bragging rights, a significant emotional payoff, and a deeply interactive experience. When working on multi-player games, it is important for game designers to keep these strengths in mind and make sure their designs play up these qualities that players are looking for.

However it is important to remember that a multi-player component is not always an improvement for a given game: some titles are ideally suited to being single-player, just as other games can only work as multi-player experiences.

10.2 The Forms

There are two groups of multi-player games, games that are played by a number of gamers all in the same location and huddled around the same computer or console, and games that are played on-line by multiple players who are in significantly different location.

10.2.1 Single System Multi-Player Games

These games originally took the form of multiple players controlling their game-world surrogates in a shared view of the game environment. Games like that are limited in that both players have to be constrained to relatively the same portion of the game-world so that they can both stay visible.

A solution for the problem of constraining two or more players to the same location came with the advent of split-screen gaming, where each player has a section of the monitor devoted to displaying the portion of the game-world that is relevant to them at any given time. The display game could be set to dynamically switch to non-split-screen when both players happen to be in the same location in the game-world.

The split-screen feature is not detrimental to a game such as Mario Kart, but can often weaken the experience in a game like Halo, whose death-match gameplay is modeled after online, blind-play competition. Split-screen simply makes it a different type of game.
Despite the potential disadvantages in terms of blind-play, multi-player games that take place around one system have a tremendous advantage in terms of the social interactions they engender.

10.2.2 On-line Multi-Player Games

Networked games provide a significantly more immersive player experience for the very reason that the other players are invisible to each other.

Having players at separate systems means they will be able to have proper blind-play but will be significantly hindered in their ability to interact with each other while playing the game, no matter what the game designer does to facilitate socialization. All these types of games can be fun in if, from the start, the designer is fully cognizant of the strengths and weakness of the type of multi-player game he is building and designs the game to work optimally within that paradigm.

Massively multi-player persistent games (MMPs) such as Ultima Online, EverQuest, and Dark Age of Camelot have become increasingly popular in recent years, though the MUDs (multi-user dungeons/domains) that inspired them have existed for nearly three decades.

Indeed, playing MMPs can be such a lifestyle choice that many couples will play together, with women tending to enjoy them more than other games. These games are much more open-ended in their design, emphasizing multiple paths to success and allowing players to spend their time how they choose. Players can go on quests, get a job and build up a home, or just spend all their time socializing with the other people they meet there. For it to be successful in the long term, the game must provide an interesting enough game that facilitates socialization in conjunction with other rewards.

The success of Xbox Live has made including a multi-player mode de rigueur in console games, at least where such gameplay makes sense.

10.3 Design Considerations

The pacing of multi-player games needs to be more varied than it is in single-player games, for the simple reason that in a multi-player game, players cannot pause the game, since the other players would need to simultaneously pause as well.

Also, most players want to know how much time they need to play your game, since all but the most hard-core have a variety of things to do with their lives other than playing games.

If possible, you want your game design to allow players to feel that they still have something of a shot at success even when they are losing. Games that allow one player to get extremely far ahead of the other players but still require a long and tedious end-game for that player to complete win will encourage the losing player to drop out, essentially forfeiting.

Positive feedback systems can push the player who is ahead in the competition farther ahead, while negative feedback will keep the competition close. Mario Kart, with its front-mounted guns, has a good implementation of negative feedback that helps keep the races closer and thereby more exciting.

Players sometimes will drop out of your game regardless of how much you try to discourage them. Indeed, due to the somewhat chaotic nature of the internet, some players may get dropped from the game in the middle through no choice of their own. Your game will need to handle these dropouts in an elegant way such that the remaining players can continue playing if at all possible, with the now-missing players having essentially forfeited their slots. You may wish to allow them to reclaim their spots in the game if they reconnect quickly enough, to forgive unavoidable Internet flakiness. If having players drop out in the middle is not handled well by your game, you are almost surely doomed to frustrating the players who want to keep playing.

Allowing players to customize their avatar in the game-world is also key to making players feel that they are actually putting themselves into the game.

If your game design does not allow for a flexible enough space for players to develop unique tactics to counter other players’ moves, all but the newbies will quickly lose interest in your game.

10.3.1 Playing to Strengths

For years, single-player games have been built around the limitations of what an AI could and could not do.

In the section 8 of this summary, “Artificial Intelligence,” it’s talked about how an artificial intelligence can be considered to pass the Turing test if players mistake it for a human. For multi-player games, the goal should be somewhat different: players could never mistake their adversaries for anything but other humans.

An online game with players located miles away from each other and who are most likely real-world strangers will probably never recreate the in-person multi-player experience. Nevertheless, the more successful online games include components that force players to socialize as part of the game mechanics, and thereby make the social interplay in the game that much richer.

Though the potential for players to cooperate should be a key part of almost any multi-player game, getting players to actually do it is another problem entirely. One way to improve the chances that players cooperate with each other is to establish a significant advantage over those who do not work together with others. If the cooperative option is too complex and does not provide significant benefits, chances are that most players will choose to just do it all themselves.

A perilous side effect can arise due to those benefits earned by players working together: more casual players will get crushed by the enemy teams, and thus those players may never live long enough to enjoy most of the things in the game.

10.3.1 Protect Newbies

Newbies are the most vulnerable players, and game designers should do everything possible to protect them long enough until they become familiar with the game’s mechanics and tactics.

As a rule of thumb from game development, there is some fixed percentage of players who love to prey on new players who do not stand a chance against them. Although there never can be a perfect solution for the problem that arises with this statistic, some techniques are used in order to minimize this trouble, some of those include allowing player-killers attack only player-killers and setting up safe and training zones. Dani Bunten Berry also suggested that a mentoring system would be appropriate to deal with this problem. Such a system would reward veteran players for watching over new players.

Minimizing features and simplifying game controls will also help new players a lot. By combining simple controls with a deep range of actions and tactics, most people who want to play the game will be able to, without taking the challenge of tactics generation from the seasoned players.

Finally, if your game design supports something more complex than “I win, everyone else loses” gameplay, the game will be a lot more inviting to new players. Many death-match games show the ranking of players at the end of the match instead of just reporting winner. Therefore, to players, there is less shame if they come in fifth out of eight than if all they know is that they failed to win.

10.3.2 Socialization

One of the primary reasons that players engage in multi-player games is to socialize with other players. This is true both in computer games as well as non-computer games. This explains why MUDs have attracted a larger female fan base than first person shooters, for example. The commonly held wisdom says that women enjoy socializing more than men.

For an online game, the designer will need to go out of his way to facilitate player socialization. The first step is providing an interface with which players can chat among themselves.

Of course, chatting via keyboard is significantly inferior to the expressive potential of actual human speech, with the obvious advantage that players can talk while continuing to play the game.

10.4 Development Issues

The first thing the development team should do when deciding about the initial aspects of a given game, is determine if it will be a single-player game or a multi-player game. If these issues are not handled at the initial phase of the project, the consequences can be really bitter… If the team wants to keep the game supporting the new game style, a lot of code may need to be reworked, and some considerable amount of game mechanics may also demand to be rearranged in order to suit the new traits.

Some games that were initially single-player-only games, and that during the middle of the project, have added a multi-player mode ended up with game mechanics that are significantly different for each of these modes. That’s unfortunate, because usually the players who are experiencing the single-player game, and enjoying it, want to find the same traits, related to the game mechanics, also when playing the game in the multi-player mode.

If the team decides earlier, on what type of game they want to work, and if they settle for a multi-player game, a lot advantage can be taken from this, assuming the networking code is working. These advantages come from the fact that the game mechanics can be tested by a group of people very soon in the development process. And once the game mechanics are a known quantity, appending a fun single-player experience based on these predetermined game mechanics can be much simpler.

In some ways, designing a good multi-player game is all about realizing what players will attempt to do after playing your game for a while and how you can better support that with deep mechanics. The longer you have players playing your game, the more you can balance the play experience.

10.4.1 Playtesting and User Feedback

Anticipating what players will try to do in a single-play game is a hard job and doing that for a multi-player game seems to be impossible. Hence, we can conclude that playtesting can be much more important for multi-player games than it can be for single-player games.

Sometimes, testers can be tempted to not report all the bugs that they may find and exploit them for their own benefit.

When your game is unleashed on the masses, issues will come that you have failed to anticipate. These problems are addressed through the use of patches that may come out shortly after the game is released. In the world of massively multi-player persistent games, the duty of maintaining the game is even more important. The players of these games typically pay a monthly subscription fee, so they expect the game mechanics to be adjusted when necessary, a steady stream of new content, and customer service to fix their problems.

Richard Garriot encourage developers to ship games “feature thin” and then add features to the game that players have shown interest or even demanded.

Adjusting the game after it has shipped implicates that the developers will need to do their best to understand the current state of the game and what players are enjoying about it and what they’re not.

We must be aware when assessing direct feedback from players since the players providing the feedback may not represent the average person playing your game. We also must be cautious when listening to much to the participants of the open beta test because if we spent too much time listening to them, we might as well derail the project.

To gather and evaluate information from players, many companies who launch online games usually hire community managers.

It is a good idea to use player metrics to uncover player exploits. If you find that 90 percent of players are using a particular type of object, that may be a sign that it would good if you could create more of these objects. Nevertheless, if you detect that a relative great amount of players aren’t using a particular object or feature, it would be worth of your time to discover why is this happening. If you detect that a specific feature isn’t as needed as you thought before, then it may be a good idea to cut off the feature from the game.

10.4 A World of Their Own

It’s irrefutable that multi-player games, through their inclusion of multiple intelligent players, offer a combination of emergence, novelty, and unpredictability that no single-player games can provide, regardless of how much artificial intelligence improves. Also, we must remember that multi-player gamers are looking mostly for a fun, social experience, not an immersive journey with a great and deeply narrative.

Friday, June 6, 2008

Game Analysis: Loom (Game Design: Theory and Practice)

Game Design:Theory and Practice (Book's Summary: Part 10)

Book’s Author: Richard Rouse III

Summarized by Samuel Coelho

9. Game Analysis: Loom

For 1990, the year it was released, Loom was a decidedly different type of adventure game. Loom retains the positive storytelling elements of adventure games and removes everything that conflicted with players’ enjoyment of the story. It succeeded admirably; resulting in a game seemed to earnestly want players to complete its interesting story.

Loom does not challenge players merely for the sake of challenging them, but instead includes only those challenges that are critical to the story.

In Loom the story was king, and whatever stood in its way was removed.

9.1 Focused Game Mechanics

Loom seems to be a perfect example of a game that is completely focused in what it wants to accomplish. Instead of trying to include all of the game mechanics he possibly could, it appears that Moriarty thought long and hard about what were the minimum game mechanics necessary for the telling of his story. He then eliminated everything that did not truly add something to that story. This had the result of greatly simplifying the game, while at the same time making it considerably more elegant and easy to navigate.

Including into Loom an inventory and verbs could have added a lot of depth to the game if the story was reconceived to take advantage of them. But as it stands, the game functions perfectly without them.

9.2 User Interface

Loom keeps its interface as simple as possible by having the player interacting with the game-world by using only the mouse. This, of course, makes the game very easy to learn and play for anyone at all familiar with point-and-click system.

Players could move their character, Bobbin Threadbare, through the world simply by clicking on the location where they wanted him to go.

The single click moves Bobbin towards an object; a double-click has him attempt to use an object.

Copying input ideas from established standards is almost always better than making up something new.

Loom eliminated the verbs entirely to allow users to simple double-click on a given object and then have the game figure out what they wanted to do with the object. If players double-clicked on a person, Bobbin Threadbare would talk to him or her. If it were an object with text on it, Bobbin would read it. If it was a sheep, he would poke it. The game works with players instead of against them, allowing players to perform only the actions that will be useful to them.

One of the primary requirements of any interface is that it be easy to learn. The challenges players face should be in the game-world itself, not in the controls they have to manipulate in order to affect that game-world.

9.3 The Drafts System

Loom introduces a unique and well-designed game mechanic accessible through the main character’s distaff. This system allows players to cast the equivalent of spells on various objects in the world.

The system is based around players hearing different tones in different situations and then repeating those tones on their staff. Players repeat the notes simply by clicking on different locations of the staff, a quite intuitive interface.


Loom

If players play the game in the expert setting, the learning of drafts becomes significantly more difficult. The musical notation is no longer present on the screen, and now players only hear notes.

The musical nature of the drafts and of the entire game is a tremendous break from most other games that can be played with the sound completely off. Instead of just using music for sonic wallpaper, Loom beautifully makes the music an integral part of the gameplay.

The order of the tones can be reversed to cause the opposite effect of playing the tones forward.

The objects players double-click on to originally learn the tones all correspond to the drafts they teach players: double-clicking on a blade teaches the “sharpen” draft, double-clicking on water dripping out of a flask teaches the “emptying” draft, double-clicking on a pot full of bubbling dye will teach the “dye” draft, and so forth.

The manipulation of these drafts makes up the primary source of puzzles in the game, and they are used in such a way that the puzzles are never overly convoluted.

9.4 Difficulty


Adventure game enthusiasts who had been hardened on the adventure games that came before Loom found it very easy to finish. They were used to dying around every corner and spending hours bashing their heads against nearly incomprehensible puzzles.

If players were not already experienced with these twisted and convoluted exercises in masochism, there was a good chance an adventure game would frustrate players so much that they would feel no desire to try another one.

9.5 Story

The story Bobbin Threadbare, the chosen “Loom-Child” whose task is to restore the fabric of reality, is one of simple beauty and great poignancy; Bobbin’s adventure begins, with his trips to the various guilds of the land of Loom, drawing to a unique climax complete with a bittersweet ending.

The story is ideally suited to the gameplay that Loom includes, with navigation and the spinning of drafts being players’ only actions. The gameplay and story are so well integrated that the gameplay ends up involving the player in the story far more than if the story were told in a non-interactive format.

The text in the story is kept to a bare minimum, never going into excessive detail about anything, allowing the players’ imaginations to fill in the holes.

Since Bobbin first acquires the staff at the beginning of the game, it makes logical sense that he would not yet be an expert at it. Thus players’ many failed attempts to use the drafts fit perfectly with Bobbin’s character.

Loom

If the character is too much of a departure from one players could see themselves being, players may become frustrated when that character speaks lines of dialog they would not say themselves or perform other stupid actions. Loom works around this problem by putting Bobbin Threadbare inside a cloak, with player only ever seeing his eyes.

9.6 Loom as an Adventure Game


For all of its strengths, Loom is still and adventure game, and indeed a fairly linear one.

In Loom, there’s a good chance that, if an object can be manipulated, players will need to do something with it to complete the game. This is both good and bad: good in it limits players’ actions to useful ones instead of leading them down a false path after red herrings and pointless diversions; bad in that it severely limits the interactiveness of the world. And sometimes the game’s landscape art is drawn in such a way that it is difficult to figure out where Bobbin can navigate and where he cannot.

But, truly, these are minor complaints. Is it so bad that Loom is a storytelling experience with a predetermined story? The game is only as worthwhile to play again, as it is to read a book or see a movie a second time.

Thursday, June 5, 2008

Storytelling (Game Design: Theory and Practice)


Game Design: Theory and Practice (Book's Summary: Part 9)

Book’s Author: Richard Rouse III

Summarized by Samuel Coelho

8. Storytelling

Games certainly do not need stories, but it seems that when employed properly, stories can make games much stronger. Games such as A Mind Forever Voyaging, Myst, Ico, and Ultima series, have made the story such an integral part of the game that one can hardly imagine them otherwise.

8.1 Designer’s Story Versus Player’s Story

The designer’s story can be seen in the game through full-motion videos. Its main purpose is to add meaning and relevance to the actions the player performs in the game.

Each level makes-up a mini-story of how players won or lost that level. This is the player’s story.

The player’s story is the most important one to be found in the game, since it is the story the player will be most involved with. This is the story players will most likely share with their friends when they talk about the game.



God of War II


The ideal interactive storytelling is to merge the designer’s story and the player’s story into one, so that players can have a real impact on a story while the story retains its dramatic qualities. The overall story arc doesn’t necessarily need to change, but the player must have a real role in determining what exactly happens in the story.

ICO

A good example of a truly interactive storytelling experience can be found in many pen-and-paper role-playing games, such as Dungeons & Dragons. In it, the good Dungeon Master will be able to keep players on track with the overall story she wants to tell. While allowing the players a considerable amount of freedom in how that story unfolds and perhaps even in how it resolves

The best a game designer can do currently is try to recreate such an interactive storytelling experience, but, in lieu of dynamically generating the story, anticipate most of the questions players might ask, places they might go, and lines of dialog they might want to say.

8.2 Places for Storytelling

The type of story you hope to tell, what technology you will be using, and the gameplay of your game will determine what storytelling will work best for your project.

Storytelling takes place out-of-game, in-game, and by the use of external materials.

8.2.1 Out-of-Game Storytelling

Very often like a film and uses established cinematic techniques similar to storytelling in other media.

Non-interactive storytelling may have its place in games, but designers need to be aware that it must supplement and not detract from an exciting gaming experience. Most players want to be playing instead of sitting through long cinematics.

We can use cut-scenes, text, images, and audio to tell a story.

One of the most important goals to have when working with cut-scenes is to establish a consistent visual appearance between the game cut-scenes and the gameplay. If at all possible, the same engine should be used for the cut-scenes as for the rest of the game. Use cut-scenes that looks nothing like the game-world only exacerbates matters.

The prevalence of only-skippable scenes leads to a distressing confusion among users from game to game, as they wonder, “If I hit the Start button, will it pause the scene or skip it?” It seems that the out-of-game sections of computer games are less user-friendly than almost any other solo experience medium.

Forcing players to watch cut-scenes is a totally unnecessary limitation no game should attempt to enforce. The players must be able to decide if he wants to see the cut-scene or not.

8.2.2 In-Game Storytelling

There are numerous powerful techniques for telling a story during gameplay. Most of them involves text, level settings, dialog with NPCs during gameplay, and NPC behaviors.

A lot can be communicated to players through text placed around the game-world. There can be signs explaining directions to locations, pinned-up notes left by previous inhabitants of a given area, graffiti on the wall, or books left lying around for players to read.

Setting can be key to telling more complex game stories. The player’s exploration of the game-world can lead to discoveries about the type of people that inhabit a given area, or inhabited it in years past.

The Suffering: ties that bind



The NPCs should not just talk to the player; they should perform actions that back up the story line.

One of the big concerns some people have with in-game storytelling is that players may miss some of the story. But we need to remember that games are an interactive form, and the fact that players do not experience every last element of the story is part of the nature of the interactivity. If players are interested in getting the entire story, it is their responsibility to seek it out. If players would prefer to just charge through the game focusing solely on the gameplay, that is their choice to make. Indeed, having different layers of the story that can be discovered on playing the game a second time can be a significant incentive for replaying the game.

In addition to maintaining the players’ immersion in the game-world, in-game storytelling makes the players active participants in the game’s story instead of just flashing it in front of their eyes.

8.2.3 External Materials

Some games have used external materials extremely effectively. In particular, the Infocom games always included materials in the boxes that added to the player’s gameplay experience in meaningful ways.

We are certainly no longer presented with the technological limitations that necessitated storytelling through external materials. Furthermore, often the stories told in the manuals were not written by the game’s designers or even with their consultation.

8.3 Linear Writing Pitfalls

In a way, the mistakes game developers make putting story into their games are forgivable due to the youth of the medium. For example, when technology that enabled filmmaking was introduced, many of the first films that were made were documents of stage plays. A camera was placed in a fixed position on a tripod and the actors considered its frame to be their stage, just as if they were working with a live audience. There were no cuts, pans, or camera movement of any kind, because the language of film had yet to be invented. As time went on, however, filmmakers learned that their films could be more than straight transcriptions of stage plays, and they could instead take advantage of the strengths of their new medium. In some ways, games still suffer from the same problem, where established mediums, film particular, are taken and just thrown into games without considering how a story might be best told in a language suited to interactivity.

Until technology advances to the point where games are able to simulate conversations significantly better than they do currently, game stories need to center around actions that games do well.

Games are about letting the player letting players find their own path through the game-world, even if the story suffers a little as a result. It’s the player’s story instead of the designer’s story.

8.3.1 Player Character Personality

When players want to play games, often they want to play themselves. If the character they are controlling has a very strong personality, there is a distancing effect, reminding players that the game is largely predetermined and making them feel like they are not truly in control of what happens in the game. Of course that there are games that became quite popular while having extremely well-defined main characters. In these games, players feel more like they are playing the game to unlock a predetermined story, and that they are just uncovering them by playing the game.

You can tell a rich conventional story if you have the player control a very distinct character, but you can suck the player into the game much more if you keep the main character iconic and allow players to feel like they are in charge of determining that character’s personality and fate.

Instead of trying to imbue the main character with a lot of personality, make the NPCs players encounter in the game memorable and interesting.

8.4 Game Stories

The game’s scriptwriter should worry less about the overall plot and more about the situation in which players find themselves and characters with which they interact.

8.4.1 Non-Linearity

In a way, in-game storytelling is non-linear. In-game storytelling allows players to talk to some characters and not to others, to choose which signs to read and which to ignore, and to explore the game-world in order to reveal its relevance to the story line, exploration over which players have control.


Indigo Prophecy



One popular way to add non-linearity to the storytelling experience is through a branching story. With a branching story, at various points the decisions players make will have a significant effect on how the story progresses. Of course branching stories increase the amount of content that will need to be created for a game, at least in terms of game design and dialog, if not also in art assets.

Another technique that can be used to inject some non-linearity into the game’s story is to allow players to determine the order in which different story components occur.

Though the first and final chapters of the game should happen at the beginning and end of the game respectively, the other chapters in the game can happen in any order. Therefore, the writer must keep those plots discrete so that they can be experienced in any order and still make sense. This may have the side-effect that you cannot have each of these interchangeable story chapters build on each other in the same way as you could in a completely linear story.

8.4.2 Working with the Gameplay

One of the most important parts of creating a story for a computer game is to match the story with the gameplay as much as possible.

Your job as a game designer is to find a story and a telling of that story that will work with the gameplay and technology that you will be using.

8.5 The Dream

One could say that the goal of gameplay is to allow for different player strategies to lead to variable types of success, to reward players experimentation and exploration, and to empower players to make their own choices. All of these factors allow players to craft their unique stories when playing your game.

Players should feel ownership over the actions in their game, and thereby ownership in the story that is being told.