Contents
Designing for Motivation
 
 
Printer-Friendly VersionPrinter-Friendly Version
 
Latest News
spacer View All spacer
 
November 22, 2009
 
Video Game Watchdog National Institute On Media And The Family Shutting Down [11]
 
Modern Warfare 2 Infinity Ward's 'Most Successful PC Version' Yet [12]
 
New Tech, Design Details Of Project Natal To Emerge At Gamefest In February
spacer
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
November 22, 2009
 
Trion Redwood City
Sr. Evnironment Modeler
 
Trion Redwood City
Sr. Environment Artist
 
Sucker Punch Productions
3D Environment Artist
 
Sucker Punch Productions
Network Programmer
 
Sucker Punch Productions
Character Artist
 
Sucker Punch Productions
Texture Artist
 
Monolith Productions
Sr. Software Engineer, Engine - Monolith Productions - #113767
 
Sony Online Entertainment
Brand Manager
spacer
Latest Features
spacer View All spacer
 
November 22, 2009
 
arrow Upping The Craft: Susan O'Connor On Games Writing [6]
 
arrow Small Developers: Minimizing Risks in Large Productions - Part II [7]
 
arrow iPhone Piracy: The Inside Story [48]
 
arrow And Yet It Grows: Analyzing the Size and Growth of the European Game Market [5]
 
arrow NPD: Behind the Numbers, October 2009 [13]
 
arrow Reflecting On Uncharted 2: How They Did It [5]
 
arrow Sponsored Feature: Rasterization on Larrabee -- Adaptive Rasterization Helps Boost Efficiency
 
arrow Postmortem: Wadjet Eye's The Blackwell Convergence [2]
spacer
Latest Blogs
spacer View All     Post     RSS spacer
 
November 22, 2009
 
Time Fcuk
 
Accepting the Inherent Value of Games
 
Planckogenesis, Part II: Song Structure & Gravy Train [1]
spacer
About
spacer News Director:
Leigh Alexander
Features Director:
Christian Nutt
Editor At Large:
Chris Remo
Advertising:
John 'Malik' Watson
Recruitment/Education:
Gina Gross
 
Features
  Designing for Motivation
by David Ghozland
3 comments
Share RSS
 
 
June 7, 2007 Article Start Previous Page 2 of 5 Next
 

 

II. The PNRC System

The purpose of the system that I am presenting is to manage internal motivations both coming from the game and in the game context. The player’s external motivations are non-estimable and unverifiable. We cannot know if the player made the bet to finish the game or if his circle wanted him to stop playing. What we are interested in here is the motivation induced by the game mechanisms and systems.

Advertisement
We have to offer challenges to the player in order to entertain him and test him along with rewards that would motivate him to continue playing. Motivating the player is also to understand his needs with the purpose of fulfilling them. It is thus to know but also “to control” the progress of his needs in order to increase them, vary them and modify them from the beginning till the end of the game.

A reward can take several forms but it must be in correlation with the universe and with the player’s expectations. A reward is related to a challenge, a test or an effort, and thus must be proportional to the difficulty to obtain it.

To reward a player in a FPS with a bouquet of flowers would be a proof of no common sense. However, in a game of seduction this kind of reward is in adequacy with the game universe. Likewise, to loot Excalibur on a goblin or a rusty dagger on a giant are serious mistakes in the game design. The player receives a reward either disproportionate or inferior to the difficulty and the reward system collapses. Another dangerous and common practice is to have random rewards. Based only on luck, this system is difficult to tune and it can be a source of frustration to the players.

We have to reward for a given challenge, according to the difficulty and the needs. This is the PNRC system or the Motivation loop:

 

 

 

We have to know at any time what the state of the player is. By getting this information we can determine what his needs are, what rewards will be adequate and what level of challenges we can propose.

Hence, we can say that the player’s motivation is an outcome of 4 following functions:

  • PLAYER STATE (P): This is the state of game variables of the player’s avatar. His life, armor, and the quality of his equipment, etc. It is also his talent, his knowledge of the world and of game mechanisms. We can say that this is the strength of the player.
  • NEEDS (N): These are the needs at the moment when the challenge arises. These needs depend on the player’s state and on his advancement into the game. There are also the needs added, by the game design, as the player goes along.
  • REWARD (R): This is the player’s expectation of the reward. The value depends on the type of reward (function of the needs); it depends on the estimated difficulty and also on the player’s past experience with the reward system.
  • CHALLENGE (C): This is the player’s expectation regarding the challenge. The value is high if the player believes in his own capacities. However, if he does not feel comfortable or if he doubts in his skills, the value is low.

For a particular Player State we have the following equation for motivation (M):

M(p) = N(p)*C(p)*R(p)

Indeed, the function of time P(t), is the parameter of N, C and R. These three functions interact in multiplicative ways. As soon as one is null, the motivation for this player state is null.

For example, for a particular player state (P), a player can be demotivated when his good performance is not recognized by the system. Poor reward (R ~ 0) results in poor motivation even when the player believes in his own skills (C high) and his needs are significant (N high).

Another example: the player can believe in himself (C is high), and considers that a high performance results in high reward (R high), but he is too well equipped or armed (N ~ 0). M is then low.

 
Article Start Previous Page 2 of 5 Next
 
Comments

Joshua Book
profile image
fantastic article - found some of the formulas regarding reality of game system (S) vs Expectation of player (E) to be a bit confusing. Otherwise very worthwhile stuff!

Smith Johanson
profile image
Great article! Here is another on the same topic worth reading.

http://www.gamedev.net/reference/articles/article1562.asp

Warren Thompson
profile image
I appreciate an educated look at game theory, however this article has one major fallacy: fun is not the major motivator in games.

I wont bother going into the psychological satisfaction of games, or break down the heirarchy of needs. I think if you really think about it, you'll understand exactly why I disagree. Have you ever seen someone screaming at their console or throwing their controller? Have you ever been frustrated with a game to the point when you obviously weren't having fun, but you kept playing?

There is a lot more to a game than fun. I only mention it because I hate to see people misled by the idea that their game is only as good as how fun it is.


none
 
Comment:
 


Submit Comment