Emotions in Games

Computer game developers, almost to a one, are blind to the emotional resonance of their games, but they don’t think they are. Quintessentially, they’ll talk about fun as an emotion and focus on that. They’ll talk about other emotions that they want to create, in particular: love and hate. The near universal conceit is that those sorts of emotions are hard, especially in single player games, so don’t even try.

They are blind to the emotional resonance that they do create, because they don’t think it can be done.

As an example, let’s consider an indie game called Card Crawl. It’s got wonderful art, music, sound, and gameplay. It’s the whole package, both in my estimation and that of VideoGameGeek

That’s a typical gameplay situation, sans the wonderfully subtle animations and music score. Quick run-through on the game follows. You’re the hapless adventurer in the bottom row of cards. Your sword and shield which can do, and block, 5 points respectively. You’ve managed to collected 14 loot points so far. It’s early yet with 44 cards to go, but you’re pretty beat up, and your skull is showing through…
To play, you drag cards around. In this case, I’m going to use my sword to slash the Troll, then drag him onto my shield. That’ll use up my sword, and leave me with a one point shield, and only 4 health. So, without healing, the spider would kill me. (For a moment, as I wrote this, I wondered if the adventurer was actually my younger daughter experiencing her worst fear.) Luckily there’s a Leech spell on the board which will heal me right up, based on the damage that I’ve taken at that point. One of the real fun parts of this game is the significant variety of blue spell cards and how they interact with the cards in play.

Oh, and of course there’s some LOOT on the board in the form of the coin, so into my backpack that goes… A victory will allow me to use the loot I’ve collect to acquire new blue cards.

So far, great. Really great. It’s a happy fun romp through cards with the whole Sir George and the Dragon sort of feel to it.

Until it isn’t.


I  just used my last healing potion. I’ve pulled all of the cards out, and here I am at the end of the game.

“How do you end the game?” you ask.

“How do you loose the game?” is what you should be asking.

I’m of the school that there’s winning and learning. How you “not-win” is central to what are we going to learn. In this sort of game, you really don’t know what’s going to come next card-wise, because randomness plays a huge factor. That’s the central learning of this sort of game, otherwise stated as sometimes bad things happen to good people. An interesting lesson, and necessary, as without it, nothing good could happen to good people either.

It’s how you loose the game which is of issue.

I pulled the Slime onto my shield, which softened his blow by 2 and took three damage, so down to 7 health. The only recourse I have available is to drag the Souleater onto me and die. The only thing I can do is to feed myself to the Souleater. I get to kill myself with a Souleater. Killing one’s self is the only path to more.

I killed myself with a Souleater.

The only path forward is to commit suicide.

That lesson not OK with me.




Apple Watch

A few snap impressions:

  1. It’s both more and less than what I expected. It just screams (un)realized potentially.

  2. Apple packaging is quickly becoming a parody of itself. 

  3. There’s a sync process really early on which is crazy slow and prevents one from using you device. Man does that need to get kicked to the curb at the soonest possible opportunity.

Thinking Fast & Slow – Experienced Utility in Game Design

Utility is one of those words which mean something different to psychologists than it does to us normal humans. People aren’t who researchers would like to assume we are. We know what made us happy, or hurt us. However, our memory is subject to how we process the world – something we’re not rational about. So it’s our memory of events which matters, not what actually happened that determines if we like something, or not. That understanding ought to impact how we design games.

First, some background on memory – or experienced utility to use the psychologist’s term. From Introduction to the Principles of Morals and Legislation by Jeremy Bentham, “Nature has placed mankind under the governance of two sovereign masters, pain and pleasure. It is for them alone to point out what we ought to do, as well as to determine what we shall do.” The term utility, in the psychological sense, includes pleasure and pain in the its scope, and our recollection of them. It’s completely subjective, and verity has nothing to do with it.

Don Redelmeier and Daniel Kahneman did a pain study on… a really painful medical procedure. They tracked two different measures of “utility”: pain at any given moment and a global retrospective rating. They charted the results for a variable length and variable pain intensity procedure. Summarizing their results as two rules:
* Peak-end rule: The global retrospective rating corollated to the worst level of pain, and at its end.
* Duration neglect: Duration had no effect whatsoever on the ratings of total pain.

1. If you’re in maximum pain at the end of a procedure, you will feel the whole procedure was more painful.
2. The average level of pain maters, if it matches the pain at the end.
3. How long a procedure lasts doesn’t matter to your perception of pain-level.

Applying that to medical procedures, if you’re goal is to minimize pain, lower the peak intensity and gradual relieve pain at the end, rather than reducing duration of the procedure. If you’re goal is to reduce the actual amount of pain experienced, reduce the duration, even if doing so causes patients to have a more awful memory. Reduction of the actual amount of pain experienced is the rational goal, but not the one that participates will select given the choice. They’ll opt for a duration increase of 50%, because their memory of the pain will be less severe.

So, what the hell does this have to do with games?

Here’s what getting utterly stomped on looks like in Hearthstone (click for larger):

Priest go BOOM!

Quick recap: The player on the top has utterly crushed the bottom player (me) with a score of 34 to 2. (The first to 30 wins.) Interestingly, in this particular case, I had been doing fairly well, up until the last two turns, at which point I got utterly stomped. Lopsided defeats like this are painful, and do happen fairly often.

Or do they?

Is it possible I’m just remembering wrong? Humans do widely overestimate the frequency intense events…

Hypothesis: By applying the psychological concept of utility, we can reduce the intensity of the negative memory formed by loosing so badly and quickly. In doing so, we can increase near and long-term player retention.

Goal: Reduce the intensity of the loosing player’s “pain” by obscuring the magnitude of their loss. That should result in an increase of immediate replays after substantial losses and corresponding increased long-term customer retention.

Specific actions to be taken:
1. For the looser, do not display a negative (or zero) number for the player’s health (visible in the lower right hand corner of the player’s character.) Assume that players will be lazy, and not do the math, especially because they (initiatively) know that it won’t come out in their favor.
2. For the looser, do not display the damage of the killing blow. This extends the logic from action #1 to it’s logical conclusion.
3. For the victory, do display the negative value and killing blow damage. Those are positives, so hype the hell out of them, possibly even more than they are already. (Supported by the psychological concept of loss aversion.)
4. Prevent end-game “burst” damage. High mana costs cards (the blue crystal in the upper-left) do more damage – that’s desirable and to be expected. However, when a player takes 15 hit points, or more, of damage in a turn, that’s “pain.”
5. Change Archmage Antonidas (the minion in front of the winning player) from “Whenever you cast a spell, put a ‘Fireball‘ spell into your hand.” to “Whenever you cast a spell, put a ‘Fireball‘ spell into your hand*, at the end of your turn.*” Using the existing card, a player can do at least 12 points of damage in a turn, even if they don’t already have a ‘Fireball‘ card in their hand. That is “burst” – arguably too much.
6. Review logs for other combinations which have the same issue. For example, a Shaman could do more than 25 hit points of damage in a turn, but that has been fixed.
7. Ramp down the effect of repeatedly cast spells. A gradual step down will result in a less painful memory. Applying that here, each subsequent ‘Fireball‘ spell should do one less damage than the previous one. Even though the result would have been the same, in this case, the intensity of the negative memory would have been reduced.
8. A more substantial ramp down of 50% would also potentially cause players to reconstitute their decks instead of every Mage deck always having two Fireballs in them. At a minimum, one would expect less back-to-back casts of the same spell on the same target. If those would be desirable outcomes, for other reasons beyond the scope of this document, then that would also bear testing.

How to measure success:
1. Time until next play. Desired outcome: Down for the looser. Remain unchanged for victor.
2. Time until next play of the same class. Desired outcome: Down for the looser. Remain unchanged for victor.
3. Is there a deck composition change. Desired outcome: none, just want to watch for unexpected results.

Why is this important:
It’s critical that players not come to the conclusion that Hearthstone is a “pay to win” game, otherwise huge numbers will never play. Legendary cards, indicated by the orange pip under their name (visible on the Onyxia card in my hand) are extremely rare. For example, after expensive play (261 wins, and more losses than that,) I have five legendary cards, two of which I spent money for. Getting defeated so roundly by a legendary card drives home the concept of paying to win. Spend $50 and you’re statistically likely to get 2.

Blizzard must be ever vigilant at managing the player’s memory of the performance of legendary cards, because, for better or worse, they’re going to be assumed as being bought – even if they weren’t.

(Lots of assertions in this section which bear further study and supporting proof, but that’s for another day.)

New Lens?

Jesse Schell’s “The Art of Game Design: A book of lenses” is one of the most influential design books I’ve ever read. Frustratingly for me, it’s scope doesn’t encompass enough about the humans who are actually playing the game – the social. It’s wonderful at helping you figure out ways to make games better and richer for a player. But, and this is a big one, it only briefly addresses players interacting with each other outside of the scope of the game. Their motivations, hopes and aspirations.

Why are they there?

A classic unknowable. However, it is possible to build a list of things they’re NOT there to do. One such emotion spurred this post. I read this reminder that the Gmail has a really amazingly useful, but never copied, feature that you can Undo sending an email.

Think about that a second.

If that were a baseline feature of every mail program – how would the world be different today? Everyone has sent an email which they didn’t mean to.

Are there ways that users can embarrasses themselves in your apps? I’ve come up with one in mine – a feature with a lifespan measured in days not weeks…

One of the goals of good design is ensure that people interact with whatever it is, game or no. Protecting a user from embarrassment is one of those ways.

I need to re-read Jesse’s book and see what else I’ve forgotten, missed, or could contribute.