• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EDT 14:59
CEST 20:59
KST 03:59
  • Home
  • Forum
  • Calendar
  • Streams
  • Liquipedia
  • Features
  • Store
  • EPT
  • TL+
  • StarCraft 2
  • Brood War
  • Smash
  • Heroes
  • Counter-Strike
  • Overwatch
  • Liquibet
  • Fantasy StarCraft
  • TLPD
  • StarCraft 2
  • Brood War
  • Blogs
Forum Sidebar
Events/Features
News
Featured News
TL.net Map Contest #22 - Voting & Ladder Map Selection2Code S Season 2 (2026) - RO8 Preview5[ASL21] Finals Preview: Two Legacies21Code S Season 2 (2026) - RO12 Preview2herO wins GSL Code S Season 1 (2026)7
Community News
Weekly Cups (May 25-31): Clem doubles, 2v2 circuit heads toward finale0StarCraft II 5.0.16 PTR Patch Notes may 26th133Weekly Cups (May 18-24): MaxPax wins doubles0Crank Gathers Season 4: BW vs SC2 Team League5Weekly Cups (May 11-17): Classic wins double1
StarCraft 2
General
StarCraft II 5.0.16 PTR Patch Notes may 26th The Death of Cheese: From a Professional Cheeser Oliveira Would Have Returned If EWC Continued SC2 Parody - "Somebody That I Used to Troll" On design and lattest PTR patch notes
Tourneys
Maestros of The Game 2 announcement and schedule ! Sparkling Tuna Cup - Weekly Open Tournament RSL Revival: Season 5 - Qualifiers and Main Event Crank Gathers Season 4: BW vs SC2 Team League GSL Code S Season 2 (2026)
Strategy
[G] Having the right mentality to improve
Custom Maps
[D]RTS in all its shapes and glory <3 [A] Nemrods 1/4 players
External Content
The PondCast: SC2 News & Results Mutation # 528 Infection Detected Welcome to the External Content forum Mutation # 527 Hell Train
Brood War
General
FlaShFTW vs A.Alm Grudge Match Event vespene.gg — BW replays in browser Quality of life changes in BW that you will like ? Data analysis on 70 million replays Data needed
Tourneys
[ASL21] Grand Finals [Megathread] Daily Proleagues Escore Tournament StarCraft Season 2 [BSL22] WB Final & LB Semis - Saturday 21:00 CEST
Strategy
Any training maps people recommend? Muta micro map competition [G] Hydra ZvZ: An Introduction Fighting Spirit mining rates
Other Games
General Games
Stormgate/Frost Giant Megathread Nintendo Switch Thread Warcraft III: The Frozen Throne ZeroSpace Megathread Path of Exile
Dota 2
Official 'what is Dota anymore' discussion
League of Legends
Heroes of the Storm
Simple Questions, Simple Answers Heroes of the Storm 2.0
Hearthstone
Deck construction bug Heroes of StarCraft mini-set
TL Mafia
Vanilla Mini Mafia Mafia Game Mode Feedback/Ideas TL Mafia Community Thread Five o'clock TL Mafia
Community
General
US Politics Mega-thread Dating: How's your luck? Russo-Ukrainian War Thread Trading/Investing Thread Things Aren’t Peaceful in Palestine
Fan Clubs
The herO Fan Club!
Media & Entertainment
[Manga] One Piece Anime Discussion Thread [Req][Books] Good Fantasy/SciFi books
Sports
McBoner: A hockey love story 2024 - 2026 Football Thread TeamLiquid Health and Fitness Initiative For 2023 Formula 1 Discussion
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread Facing Challenges in Mobile App Development
TL Community
The Automated Ban List
Blogs
Esportsmanship: How to NOT B…
TrAiDoS
Why RTS gamers make better f…
gosubay
ramps on octagon
StaticNine
ASL S21 English Commentary…
namkraft
Customize Sidebar...

Website Feedback

Closed Threads



Active: 4182 users

Ladder Anxiety & Rating Systems

Blogs > mockturtle
Post a Reply
mockturtle
Profile Blog Joined March 2011
United States220 Posts
Last Edited: 2012-09-21 03:04:51
September 21 2012 03:04 GMT
#1
Ladder Anxiety & Rating Systems
Also posted @ http://mcktr.tl


Ladder Anxiety is a term from the Starcraft community referring to distress caused by playing ranked/ladder games leading to the inclination to avoid them. This is usually just emotional, but can also include physical symptoms such as cold extremities, quick breathing, fatigue, etc. Though the advice given in response to this situation alternates between folksy relaxation techniques and the advice to "man up", it is still a common response and a response that is the opposite of what a game developer should want. Not only have I seen this discussion come up in the League of Legends community as well, suggesting that it's not something isolated to Starcraft, but I suspect the plague of general poor sportsmanship that infects online gaming may share a contributing factor with ladder anxiety -- the negative emotional response that manifests in some people as ladder anxiety could manifest in others as a desire to insult their opponents, make excluses, gloat, or otherwise behave in a "toxic" manner.

A feature in a game which motivates a person to avoid playing is an error of design. The common community response to this complaint makes the assumption that something is wrong with the player, not the game. I disagree. I think that, with some small changes that take into account human nature, game developers can create a much larger population of satisfied, competitive gamers. They'd have a better ladder system, too.

What is a rating system

Put simply, a rating system is a method to create a dynamic and ongoing hierarchy of a group of competitors. Based on previous performance, players are given a numerical rating which represents their skill level and is continiously updated after each match based on the result and the skill level of their opponent. The primary benefit this system has to a competitive online game is in matchmaking -- it's little fun for novices to play against experts or vice versa, and being able to play an evenly skilled opponent with the click of the button adds greatly to the value and longevity of a competitive game.

But this benefit is largely unappreciated by the mass of gamers who value rating systems solely for quantifying skill. Instead of being used to find appropriate opponents or to help the learning process, the rating functions like an appraisal of self worth. Players lose interest in having fun or learning the game and focus entirely on increasing their rating -- not their skill level, but their rating. It is exceedingly common for people to take rating drops that come as a result of misfortune (such as technical troubles) as a personal slight. This even extends past the realm of actual misfortune and into taking offense at perfectly valid behavior such as their opponent employing certain tactics they take to be "unfair". In truth, being rated below your skill level is little more than an inconvenience -- you'll be matched with easier opponents until your performance raises your rating to an appropriate level.

A skill rating is not a posterboard of gold stars and the goal of a competitive hobby is not to accumulate rating points like coins in Super Mario Brothers. Regardless of how precise the now famous "10,000 hour rule" is, acquiring skill in a difficult activity is a long, difficult road. The unfortunate fact is, an improving player in a truly accurate, honest rating system can expect his rating to increase at roughly the rate people actually improve: slow.
Primer on Probability

Even though it's perhaps a little too elementary to point this out to the people who would be interested in reading this kind of article, I'm going to do so anyway just to ensure everyone is on the same page. Let's take a coinflip as an example -- a random event between two equally likely outcomes (50/50). Even though there are only two outcomes and they should happen equally often, flipping a coin four times will not necessarily create a string of alternating results (heads, then tails, then heads, then tails). A person flipping a coin could easily see a result of heads all four times and from that experience mistakenly draw a conclusion that the coin is flawed or has a picture of a head on both sides. Despite the simplicity of a coinflip, it would take a large number of trials to be very confident of obtaining a result that gives an accurate reflection of the truth. Not only is human perception and memory is simply unable to handle that amount of data, our brains are designed for prediction. This makes humans really bad at making sense of a series of events where the outcome is subject to randomness. At least when they must rely on their subjective experience, of course. We fare far better when we rely on Excel.

Ratings are meant to reflect the probability of one player defeating another: two players with the same rating should win an equal number of times, while a higher rated player should win more often. More often, not always. Regardless, this means that losing regulary is expected. Not only are individual losses unavoidable, but streaks will be as well, bouncing your rating up and down around where it's meant to be. This is called variance. While chance will come close enough to evening out over the long run, a person who is experiencing these results in real time can't help but misinterpret them. A streak of victories is taken to represent a surge in ability; a streak of defeats is taken as an unfortunate injustice or personal failure.

Neither is accurate. If you were to wake up one day better, marginally, than your current rating, your performance would not result in win after win in a direct path towards your new, true rating. Instead, you would win slightly more often until your rating reflected your newfound skill.

Loss Aversion

People are irrational. This shouldn't be news to anyone. One of these universal irrational tendencies is a psychological principle called loss aversion. Put simply, humans put more value in avoiding losing something than they would on acquiring that something to begin with. For example, a typical person will be more upset by losing $20 than they would be happy upon finding $20. This preference has an effect on our behavior and is so powerful it can lead to decisionmaking which is quite ludicrous when analyzed objectively.

What does this have to do with rating systems?

Let's look at the player experience when playing a rated game in either Starcraft II or League of Legends. While both use different systems, each give players a rating which increases after each win and decreases after each loss. Not only is the rating adjusted but for the purpose of clarity, the difference is displayed quite prominently to each player alongside their new rating in the statistics screen that follows each match. This feedback is intended to be motivational: the joy of gaining points synergizes with the natural joy of winning, increasing one's desire to play. Upon losing, however, the player has the exact opposite response. Because of loss aversion, these two possibilities do not cancel each other out -- losing is the more significant factor.

In an accurate rating system, hitting the "Play" button matches you up with a person who is approximately your skill level. This means someone against whom your chances of winning should be as close to 50-50 as possible. If you win, you will be rewarded with points. If you lose, you will be punished and have points taken away from you. Even though you will win and lose about the same number of points in the long run (assuming your skill remains static), psychologically you put more value on the points you currently have than any points you may win. Losing ten points hurts more, a lot more in fact, than winning ten points feels good. From an emotional perspective, this is a losing proposition. Unless your victories will substantially outnumber your losses (which should not happen except for the few very best players), participation is a recipe for misery. If you're in the business of cooking up fun, this isn't something you want in the oven.

Ironically, instant feedback is misleading

The Elo rating system (the most popular and widespread -- though always with adaptations) was implemented by the USCF in 1960 as an improvement over a previous rating system already being used. This was long before personal computers were everywhere, and one of the strengths of Elo is that it relied on relatively simple arithmetic. This was important since rating adjustments were done by an actual person (perhaps with a calculator) thumbing through sheets of chess results after a tournament. Logistically, this meant that rating adjustments were neither instantaneous nor were they for individual matches. Waiting for the results to be processed blunts the negative response since the material loss, the decrease in points, is not immediately attached to the emotional impact of losing. Handling the entire tournament in one adjustment meant that the change in rating reflected not a single game but the handful played over the entire tournament. Processing the games in batches makes for less variance in each adjustment -- ratings will not bounce all over the place, and each change carries more significance.

This is where irony comes in. Many people would assume that the more immediate and clear the feedback, the more reliable and helpful that feedback will be. With ratings, this isn't the case. Showing the adjustments of each individual game is a lie. Once your rating has been established in an accurate system and you are paired against similar opponents, you are meant to lose from time to time. Often, in fact! Around as much as you win! The outcome of one or two games carries little, if any, statistical significance. However, this is lost on someone without a solid understanding of both the rating system and statistics, which is almost everyone. All they see is a mean robot taking away gold stars everytime they lose a game.

What's the solution?

Simple: batch adjustments. Not only would ratings (once established) work better changing on, say, a weekly basis, rather than game to game, it would also be best to update less often for players who do not play many games.

This idea is actually built into the Glicko rating system and called the "rating period". Any matches that take place during one rating period are to be considered simultaneous, so changes are made based on chunks of games rather than one by one. The official paper outlining the Glicko system recommends a rating period which has, on average, 10-15 games per player.

While removing the instant adjustments is an improvement in a rating implementation, it isn't necessarily an improvement in overall game design. Instantaneous feedback is an important part of game design. The problem is that losses are not just unavoidable -- a good matchmaking system guarantees that they will happen about half the time. Providing negative reinforcement (the loss of points) for an unpreventable event is akin to alternating randomly between smacking a puppy on the nose and giving it a treat -- the natural response is fear and anxiety. The idea that a player just needs to perform better to obtain his reward (and avoid punishment) isn't valid, since better performance will only result in more difficult challenges.

Instead, developers need to find other ways to integrate feedback and rewards into the competitive gaming process that bear in mind the reality of participating in a competitive hobby. Even for the best of us, losses happen and are obviously a suboptimal result. No one likes to lose, even if they've grown to accept it. Rubbing it in by taking points away does not accomplish anything. The satisfaction derived from this kind of hobby comes from ongoing self improvement and testing yourself, and the design should encourage this aspect of the experience.

*****
TroW
Profile Blog Joined June 2011
United States67 Posts
September 21 2012 03:50 GMT
#2
Very well done, I agree. I think the trickiest part of implementing this would be deciding on what rating period would be best across the board. We can probably assume that more casual players would favor a slightly longer time between rating adjustments than professionals that play 20+ games in a day.

To be clear: is the idea to make the rating period a specific period of time (so that everybody's is updated at the same time, or at least has the same amount of time between updates), or is it individualized to each player and updated every 10-15 games, whenever that benchmark happens to be reached?

I would also note that people who do understand statistics and the importance of sample size in drawing reliable conclusions can still be quite upset by a string of disappointing results. (I speak from experience on this one )

I hope something like this will at least be attempted in a competitive game.

5/5
"A thinker sees his own actions as experiments and questions--as attempts to find out something. Success and failure are for him answers above all." - Friedrich Nietzsche
Birdie
Profile Blog Joined August 2007
New Zealand4438 Posts
September 21 2012 04:03 GMT
#3
This makes me glad that the rating system I'm currently coding uses Glicko2 and a one week rating period; hopefully it will make people want to play more rather than less :D
Red classic | A butterfly dreamed he was Zhuangzi | 4.5k, heading to 5k as support!
surfinbird1
Profile Joined September 2009
Germany999 Posts
September 21 2012 08:27 GMT
#4
Mockturtle article with no footnotes? Blasphemy!
life of lively to live to life of full life thx to shield battery
mockturtle
Profile Blog Joined March 2011
United States220 Posts
September 21 2012 16:07 GMT
#5
On September 21 2012 12:50 TroW wrote:
Very well done, I agree. I think the trickiest part of implementing this would be deciding on what rating period would be best across the board. We can probably assume that more casual players would favor a slightly longer time between rating adjustments than professionals that play 20+ games in a day.

To be clear: is the idea to make the rating period a specific period of time (so that everybody's is updated at the same time, or at least has the same amount of time between updates), or is it individualized to each player and updated every 10-15 games, whenever that benchmark happens to be reached?


Oddly enough, I think most people of all groups (casuals and professionals) would find this approach to be frustrating and inferior since they've come to expect instant updates as the standard. This is in spite of the fact that they would enjoy the ladder more and understand it better. There is not always a perfect correlation between what people say they like and what they actually like. Another irrational part of human nature :-).

The right rating period is a compromise between people's attention spans and the habits. If rating periods are too large, not only will people lose interest between updates but there can be far too much invisible progress made between each change. Too small, and there isn't much of a benefit over individual games. I feel like a week is probably a good point, since for most people the world tends to operate in cycles of a week. It may be that under statistical analysis (either Blizzard or Riot, for example, have a ridiculous amount of data available to them to analyze and determine what would make a good rating period) something slightly longer or shorter than a week better fits the bill. Having a standard schedule ("Your rating will be updated every Wednesday morning") would work best rather than using a certain number of games which is "invisible" to the player.



I would also note that people who do understand statistics and the importance of sample size in drawing reliable conclusions can still be quite upset by a string of disappointing results. (I speak from experience on this one )

I hope something like this will at least be attempted in a competitive game.

5/5


I'm no different. That's why I know people who don't understand that aspect of statistics (or how rating systems work) are helpless!

On September 21 2012 13:03 Birdie wrote:
This makes me glad that the rating system I'm currently coding uses Glicko2 and a one week rating period; hopefully it will make people want to play more rather than less :D



Glicko2 is awesome. While cut and pasting it for Starcraft 2 or League of Legends or Dota 2 is not perfect (there are some easy adaptations to make considering the nature of what Glicko was designed for and how Starcraft works, along with some not-so-easy adaptations to consider), it's still significantly better than Elo out of the box and also probably more adaptable to all kinds of games without doing any work. If I wind up doing a post talking about the SC2 ladder, I'll go into this more!


On September 21 2012 17:27 surfinbird1 wrote:
Mockturtle article with no footnotes? Blasphemy!


Break my heart why don't you
mizU
Profile Blog Joined April 2010
United States12125 Posts
September 21 2012 23:47 GMT
#6
Or you could just hide your ladder ranking with post-its.
if happy ever afters did exist <3 @watamizu_
Please log in or register to reply.
Live Events Refresh
Maestros of the Game
15:30
Group A
Reynor vs TriGGeR
Maru vs Classic
ComeBackTV 1267
IntoTheiNu 1156
ZombieGrub685
TaKeTV 621
SteadfastSC552
Ryung 413
IndyStarCraft 233
3DClanTV 151
Rex104
CosmosSc2 83
EnkiAlexander 74
LiquipediaDiscussion
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
ZombieGrub685
SteadfastSC 552
Ryung 413
IndyStarCraft 233
UpATreeSC 111
Rex 104
CosmosSc2 83
BRAT_OK 75
JuggernautJason66
elazer 60
goblin 24
MindelVK 20
StarCraft: Brood War
Sea 2280
Mini 566
Dewaltoss 105
Movie 57
soO 22
ajuk12(nOOB) 18
Rock 16
Dota 2
420jenkins314
Counter-Strike
fl0m9702
byalli906
x6flipin582
pashabiceps133
Heroes of the Storm
Liquid`Hasu295
Other Games
Grubby4209
singsing2405
FrodaN1624
B2W.Neo793
Beastyqt663
ceh9588
Dendi339
DeMusliM222
C9.Mang0177
KnowMe102
Trikslyr82
Mew2King45
Organizations
StarCraft 2
Blizzard YouTube
StarCraft: Brood War
BSLTrovo
[ Show 15 non-featured ]
StarCraft 2
• intothetv
• Kozan
• sooper7s
• Migwel
• AfreecaTV YouTube
• LaughNgamezSOOP
• IndyKCrew
StarCraft: Brood War
• STPLYoutube
• ZZZeroYoutube
• BSLYoutube
League of Legends
• TFBlade1298
• Lourlo245
Other Games
• imaqtpie854
• WagamamaTV401
• Shiphtur247
Upcoming Events
The PondCast
15h 1m
Kung Fu Cup
16h 1m
uThermal 2v2 Circuit
20h 1m
Maestros of the Game
20h 31m
ByuN vs herO
Rogue vs Bunny
Replay Cast
1d 5h
Replay Cast
1d 14h
WardiTV Spring Champion…
1d 16h
OSC
1d 18h
Maestros of the Game
1d 20h
Serral vs Percival
SHIN vs ShoWTimE
Replay Cast
2 days
[ Show More ]
uThermal 2v2 Circuit
2 days
Maestros of the Game
2 days
Clem vs Lambo
Zoun vs SKillous
Replay Cast
3 days
Solar vs Classic
uThermal 2v2 Circuit
3 days
Grudge Match
3 days
FlaShFTW vs A.Alm
GSL
4 days
herO vs Rogue
Maru vs Cure
Patches Events
4 days
uThermal 2v2 Circuit
4 days
BSL
5 days
Replay Cast
5 days
Monday Night Weeklies
5 days
Sparkling Tuna Cup
6 days
Liquipedia Results

Completed

KK 2v2 League Season 1
RSL Revival: Season 5
Heroes Pulsing #1

Ongoing

BSL Season 22
IPSL Spring 2026
KCM Race Survival 2026 Season 2
Acropolis #4
CSCL: Masked Kings S4
YSL S3
SCTL 2026 Spring
WardiTV Spring 2026
Maestros of the Game 2
2026 GSL S2
Murky Cup 2026
IEM Cologne Major 2026
Stake Ranked Episode 2
CS Asia Championships 2026
Asian Champions League 2026
IEM Atlanta 2026
PGL Astana 2026
BLAST Rivals Spring 2026
IEM Rio 2026
PGL Bucharest 2026
Stake Ranked Episode 1
BLAST Open Spring 2026

Upcoming

BSL 22 Non-Korean Championship
CSLAN 4
Blizzard Classic Cup 2026
Kung Fu Cup 2026 Grand Finals
CranK Gathers Season 4: BW vs SC2 Team League
HSC XXIX
uThermal 2v2 2026 Main Event
Heroes Pulsing #3
Heroes Pulsing #2
Esports World Cup 2026
BLAST Bounty Summer 2026
BLAST Bounty Summer Qual
Stake Ranked Episode 3
XSE Pro League 2026
TLPD

1. ByuN
2. TY
3. Dark
4. Solar
5. Stats
6. Nerchio
7. sOs
8. soO
9. INnoVation
10. Elazer
1. Rain
2. Flash
3. EffOrt
4. Last
5. Bisu
6. Soulkey
7. Mini
8. Sharp
Sidebar Settings...

Advertising | Privacy Policy | Terms Of Use | Contact Us

Original banner artwork: Jim Warren
The contents of this webpage are copyright © 2026 TLnet. All Rights Reserved.