Ragequitting

From gdp3
Revision as of 14:35, 16 January 2015 by Staffan Björk (Talk | contribs)

Jump to: navigation, search

Quitting a game instance due to anger or frustration without regards to how this will affect gameplay for others.

This pattern is a still a stub.

TV Tropes has a entry for "Rage Quit"[1].

Examples

Online Games such as League of Legends, the Counter-Strike series, the Left 4 Dead series, and the Team Fortress series are well-known for producing Ragequitting since they all require team work under pressure. When teams do not manage to coordinate, agree, or succeed this may become extremely frustrating for players and make them want to quit.

Intrigue and So Long Sucker are games that are noted for causing players to become irritated at each other. This makes them candidates for Ragequitting although this has not been documented or discussed as much as for the games above. There are however several depictions of players Ragequitting games of Go in Japanese art; the covers of the books in the "Get strong at Go" series depict these (see for example "Get Strong at Tesuji"[2]

Sometimes Ragequitting is applied to players that are actually continuing to follow the rules of a game but clearly not trying to win. One such example is the Soccer game between SO l'Emyrne and AS Adema where the former team got so upset with a ruling that they scored a 149 own goals resulting in the other team winning 149 to 0[3].

According to TV Tropes[1], NPCs in Sid Meier's SimGolf can ragequit if their mood value becomes too low.

Using the pattern

A perceived Predictable Winner or an identified Dominant Strategy is typically not enough to provoke Ragequitting since this might just be due to others playing well. Ragequitting depends on players feeling frustrated to the point where quitting regardless of consequences for other players gameplay experience becomes the least bad alternative. This is typically happens to players either on due their own performance when meeting Challenging Gameplay or the inability of succeeding with Cooperation. The latter cause makes Betrayal a potential reason for Ragequitting, but only when players are not emotionally prepared for it. Pubstomping is a typical example of emergent feature that can be frustrating to experience since one is thrown into a disadvantageous gameplay situation with a strong possibility of being killed quickly and then have to experience the exact say thing directly again.

Designing for Spectacular Failure Enjoyment is a way to design against Ragequitting since the two experiences are mutually exclusive. While not directly countering the reasons for Ragequitting, punishing people that do it by negatively adjusting them in Ranking Systems for this behavior can help players control their behavior. Togetherness has a dual relationship with Ragequitting. First, people are less likely to ragequit if they are experiencing Togetherness with some of the other players since this typically would negatively affect these other players. Second, if Ragequitting does occur it will break Togetherness related to that player.

Consequences

The direct consequence of Ragequitting is of course that a player Surrenders. Since this was due to anger at what had happened during gameplay, Ragequitting is a good indicator that the quitting player had Emotional Engrossment. Scapegoats are created whenever a person blames other players for the problems that result in Ragequitting.

Relations

Achievements NPCs Possibility of Own Goals

Can Instantiate

Cooperation, Emotional Engrossment, Scapegoats, Surrendering

Can Modulate

-

Can Be Instantiated By

Betrayal, Challenging Gameplay, Pubstomping

Can Be Modulated By

Ranking Systems

Possible Closure Effects

-

Potentially Conflicting With

Spectacular Failure Enjoyment, Togetherness

History

New pattern created in this wiki.

References

  1. 1.0 1.1 Entry for "Rage Quit" on TV Tropes.
  2. Amazon's page for the book "Get Strong at Tesuji".
  3. Wikipedia Entry for the AS Adema vs. SO l'Emyrne Soccer game in 2002.

Acknowledgements

-