Hello, fellow Wuvers. Tired of those same old matchups? Hoping to test your mettle against some different opponents? We here at ArenaNet feel the same way.
Up until now, servers have been paired up literally 3 at a time by their precise rating. This doesn’t create a lot of variety in matchups, and it actually locks servers into distinct tiers from which they can never escape! “Muwaahahahahahaha!” is what the Guild Wars 2 World vs. World matchup system might say if it was an evil overlord instead of a bunch of code. Thankfully it is not, and thus we have the power to change it.
As servers play the same servers over and over again, our ranking data becomes less accurate and therefore a lot less useful. So what are we going to start doing about it? The simple answer is we are going to scramble the matchups from week to week so that while worlds will still be fighting worlds of similar skill level, we’ll be a bit more lenient about who can play against whom.
I want to get into some of the technical details behind this, but first here’s a brief layman’s explanation for those who aren’t interested in details so you can quickly read this and move on.
The TL;DR Version
“…we’re going to partially randomize server matchups…”
Basically, when you have a ladder for any kind of competition, all of the matchups don’t normally happen at the exact same time. You also normally have a pretty big group of entries in the ladder to choose from, which means that you’re matched with the closest opponent at the time the matchup is created. In the case of WvW, there are only 24 servers and the matchups all occur at the same time.
To counter this, we’re going to partially randomize server matchups, with the exception being we won’t match servers against other servers whose rating falls outside of an acceptable range. This range will be determined by using your world’s rating and deviation (already listed on the leaderboards).
Digging Deeper
Let’s check out how the numbers are going to work. In our rating system, each shard’s rating number isn’t intended to be a precise measure of skill. Rather, the rating and deviation can be combined to give a range of certainty, inside of which the server’s true rating lies. This is the concept we use to determine which shards may be randomly matched up against one another. By randomly adding to or subtracting from a server’s rating for the purposes of matchmaking, we can create fresh matches from week to week with shards that are relatively close to one another in rating.
There are two configurable variables that go into matchup rating variation: a fixed base amount, and a percentage of the shard’s deviation. A shard’s potential rating variation is then BaseVariation + DeviationVariation * ShardDeviation. We multiply potential rating variation by a uniform random number in the range [-1, 1] to determine a shard’s final rating variation for matchmaking. Thus, FinalRating = ShardRating + Rand(-1, 1) * (BaseVariation + DeviationVariation * ShardDeviation). We do this for each shard in the pool, re-sort by rating, and then use the shuffled ordering to create our groups of three for the week’s matchups. Just to be clear, this random adjustment only applies to the numbers used for determining matchups. Real ratings are still only changed by winning or losing.
We can look at our leaderboard data and apply these calculations to see how this system might play out if it were active right now. If we let base variation be 40.0 and deviation variation be 1.0, then we might have gotten the following matchups this week (sorted descending by matchmaking rating):
Rank | Name | Rating | Deviation | Potential Variation | Random Roll | Matchmaking Rating |
---|---|---|---|---|---|---|
2 | Jade Quarry | 2180.851 | 176.2303 | 216.2303 | 0.167177763 | 2216.999498 |
4 | Dragonbrand | 2023.817 | 176.8123 | 216.8123 | 0.703595965 | 2176.365059 |
5 | Fort Aspenwood | 1958.548 | 175.8177 | 215.8177 | 0.721069753 | 2114.167116 |
3 | Sanctum of Rall | 2130.115 | 176.3804 | 216.3804 | -0.496884461 | 2022.598442 |
1 | Blackgate | 2200.649 | 175.9742 | 215.9742 | -0.978383984 | 1989.343702 |
8 | Kaineng | 1798.321 | 182.6282 | 222.6282 | 0.146321985 | 1830.8967 |
6 | Tarnished Coast | 1949.458 | 176.1932 | 216.1932 | -0.56815809 | 1826.625884 |
7 | Maguuma | 1803.074 | 178.905 | 218.905 | -0.013139824 | 1800.197827 |
10 | Sea of Sorrows | 1707.325 | 180.5936 | 220.5936 | 0.316896307 | 1777.230497 |
12 | Stormbluff Isle | 1562.257 | 178.6835 | 218.6835 | 0.720972111 | 1719.921705 |
13 | Ehmry Bay | 1489.858 | 180.5763 | 220.5763 | 0.765518262 | 1658.713486 |
9 | Yak’s Bend | 1750.096 | 179.4582 | 219.4582 | -0.873281472 | 1558.44702 |
11 | Crystal Desert | 1576.675 | 178.5518 | 218.5518 | -0.11919477 | 1550.624769 |
16 | Darkhaven | 1290.642 | 180.8669 | 220.8669 | 0.952418273 | 1500.999472 |
14 | Anvil Rock | 1362.433 | 176.8037 | 216.8037 | -0.421012361 | 1271.155562 |
18 | Sorrow’s Furnace | 1202.161 | 180.3537 | 220.3537 | 0.303410949 | 1269.019125 |
15 | Borlis Pass | 1352.966 | 177.0146 | 217.0146 | -0.466159275 | 1251.802931 |
21 | Northern Shiverpeaks | 1070.686 | 176.3384 | 216.3384 | 0.487671274 | 1176.187523 |
17 | Isle of Janthir | 1214.426 | 180.1848 | 220.1848 | -0.346931569 | 1138.036842 |
23 | Ferguson’s Crossing | 910.7169 | 176.9117 | 216.9117 | 0.623797905 | 1046.025964 |
19 | Devona’s Rest | 1090.529 | 179.1055 | 219.1055 | -0.53300383 | 973.7450293 |
22 | Henge of Denravi | 953.2776 | 176.8161 | 216.8161 | 0.049128084 | 963.9293596 |
20 | Gate of Madness | 1082.798 | 178.147 | 218.147 | -0.649966477 | 941.0092629 |
24 | Eredon Terrace | 883.4587 | 177.1358 | 217.1358 | -0.753274572 | 719.8958232 |
We can see that the matches still clearly trend from higher rated shards on top to lower rated shards on the bottom, but some matches have a much larger spread between the ratings of each shard than we’re normally used to (like rank 8 Kaineng going up against rank 1 Blackgate). This is fully random and there are no artificial checks in place to guarantee that matchups don’t get repeated from week to week. The incidence of identical matchups should be significantly reduced though. Ideally, players would see it as a rare chance to get even from the past week, instead of more of the same. We hope our beloved WvW community will enjoy these new opportunities to challenge up the ladder, and the added tension of having to defend your team’s position on the ladder from a wider array of challengers.
Additionally, we’ll add a new “Tier” column to the WvW leaderboards so everyone can see which matchup they’re in. Right now, groups are implicitly displayed because each ordered group of three is a matchup, but this will no longer be the case after the ratings change. Players will be able to sort by the Tier column to see the matchup or by the rating column to see where everyone current stacks up.
In Closing…
Is all this scrambling of matchups going to help your world win more often? No, the power to do so is in your hands now.
Is Kaineng better than Jade Quarry? Before we never knew, but soon they might get a chance to prove it.
How will Ruins of Surmia fare against Gandara? Your guess is as good as mine is.
World vs. World is a lot about tactics, and when you fight the same worlds with the same tactics you never really get to learn anything new and adapt your strategy. This is your chance for your world to rally together, recruit more people, and try to overthrow a server above you. Like most of you, we love a good underdog story and now you’ll be able to write your own in WvW. At the end of the day, this is going to create new fresh matchups, let you see the tactics from different teams, bring some variety to the Eternal Battlegrounds, and help us to establish a more accurate new World vs. World order.