[GW2] “A Good Fight” Part 1

I admit that I don’t have much of a competitive bone, so I need someone else to help me understand the meaning of this elusive term, “good fights.” Exactly what would be defined as one?
Jeromai

I characterize “a good fight” as one with roughly balanced forces, where “balance” mixes quality and quantity. This applies to the two levels at which WvW takes place.

WvW competition happens at two levels: individual fights and overall score (“PPT,” points per turn). Individual players are rewarded according to individual fights, where you get points for kills and captures. (There are rewards for defending, but the system is weighted towards rewarding offense over defense. More on the virtues of defending below.) Servers are rewarded according to how many objectives they control over time (plus points for stomps). This post addresses the server level (“a good matchup”), and tomorrow we discuss the individual fights (“a good fight”).

At the PPT level, population and coverage are key. How many fights you win is more important than your winning percentage. A server with a small, elite WvW population can win every single fight but still lose the week because that small force cannot be everywhere. Having a large population lets you attack and defend multiple points across multiple maps. More bodies means more caps and longer defenses.

Quality also matters, but probably less than quantity for PPT. All things being equal, you prefer having more skilled and experienced players who communicate well. As population shrinks, quality matters more; as population grows, as Stalin said, “quantity has a quality all its own.”

Coverage is the other element, particularly as server population shrinks. Consider two servers with equal WvW forces, where one is concentrated in the American time zones and the other is spread evenly over the globe. The American server will dominate American prime time, appearing to have twice the population or more; the global server will lose for four to six hours a day and then sweep the map once the Americans start going to bed. Controlling the map for 18 hours yields more points than controlling it during prime time.

Note that off-hours flips affect prime time play. When I went to bed Sunday night, our server controlled Stonemist Castle and had it fully upgraded. If there is one hour in which we have no meaningful coverage, SMC will flip and lose all its upgrades. It is enormously frustrating to win the battle but lose the war because you have a job and need to sleep. This can lead to not bothering to upgrade or to WvW at all. Off-hours ninjas can demoralize opposing forces.

Quantity, quality, and coverage are the three major factors I see in what makes a good matchup. Theoretically, over time, most servers will settle into balanced matchups based on that because of how scores come out. That settling out time will involve painful mismatches as one server dominates or gets utterly crushed due to mismatch. The first weeks after launch were like that, and Season One has caused the same on a smaller scale as transfers shifted WvW populations in ways that will take weeks or months to settle out.

Note that WvW population matters; server population matters only as a pool of potential participants. The dedicated WvW playerbase will be a fraction of the overall population, so small shifts like the transfer of a dedicated WvW guild will have a disproportionate effect on WvW population. It is the more dedicated WvWers who are likely to transfer on that basis, increasing the effect. There is also a feedback loop whereby winning servers get a higher percentage of the overall population participating (“bandwagon” or “fairweather”). There is a terminal point on that feedback loop as there is a WvW population cap and as the average player skill drops when casual WvWers keep dedicated WvWers in the queue (“the bandwagon before the horse”?).

To demonstrate the outsized effect of small WvW population shifts, consider Fort Aspenwood. Before Season One, Fort Aspenwood was rated as potentially competitive in Silver League. Hardcore WvW guilds transferred to Fort Aspenwood. After Season One, Fort Aspenwood is winning Tier 2 in Gold. 40 or 50 people is just a blip on the overall server population, but if most of them are spending most of their time in WvW as a coordinated group, that can flip an entire map. The effect is smaller with existing Gold population levels, but it’s hard to argue with success.

: Zubon

13 thoughts on “[GW2] “A Good Fight” Part 1”

  1. WvW match-ups seem to have a problem when what’s supposed to be the auto-correcting mechanism of a three way fight (that #2 and #3 both hit #1) goes awry and instead teams #1 and #2 ignore each other and carve up poor old #3 between them – in European history, this is known as ‘the Poland problem’.

    I don’t recall DAoC having this problem to any great extent, so there’s probably a key difference in incentives to attack the overdog between the two games. Maybe the points for stomps should be awarded based on team position, so stomping a player form the dominant team is worth extra points (or even just drops more loot) whilst killing the underdogs is less rewarding.

    1. Relics were a major difference in DAoC. Both underdogs had an incentive to assault the winning team to take a relic. In GW2, attacking the weaker server is a better idea because they produce the same points with an easier fight.

      1. Indeed – though I think Darkness Falls might have had even more effect. Relic Raids weren’t an everyday thing on my server, but DF access depended on holding the most keeps and changed hands regularly. And of course, once your side was winning and opened DF, half of your army promptly deserted the battlefield to go and farm diamond seals while they could.

        1. Good call, particularly that last effect. It siphoned off the bandwagon, which meant that the “winning team” flipped more often, as coppertopper below advocates.

          1. DF – best part of any MMO i have ever played. I said it before on posts by you – PvP to increase PvE is always the answer.

  2. These are all good points that have been part and parcel of PvP since Dark age of Camelot (my most distant MMO memory). But this is war done in 10x speed. Logging in and seeing map changes is exciting – gives you goals to do. As long as WvW and PvE are separate, it will always be at a breakneck pace just to keep things interesting. Now if that keep were your home base and the towers surrounding it an essential part of PvE, the devs could making conquering map points a bear so that territory conquering would be rare. GW2 is not that game.

  3. A minor point: Fort Aspenwood is a tier 2 server that junked their rating in the leadup to Season 1 to ensure they had Silver League to themselves.

    But there are essentially two major problems with the WvW format (and they’re well-known) – PPT makes coverage much more important than fights, and there are relatively few alliances so two smaller servers generally aren’t willing to work together to contain the third.

    1. I have heard that said about most servers at the top of Silver and Bronze. I know the strategy was discussed, but I do not know how true it is in any particular case. Given discussion that SBI was favored, I think FA did badly in early transfers and gained a lot just before Season One started. After those transfers, FA nommed.

      Agreed on the other points. I am really enchanted with the Darkness Falls discussion above as a means of addressing the last one.

      1. The main issue I see with adding something like DF to GW2 is GW2 doesn’t have the gear grind that DAoC had. People didn’t fight for access to DF just to have access, they wanted it to get better pixels. Unless GW2 starts down the gear grind path, I don’t know that different skins or fluff will have the same effect as DF had.

  4. Oh well, I had a good fight once in WvW: being a total PvP noob, my amazing char (Gath Gealaich – Elona Reach – a mortal Norn ranger babe) could stand against 3 Jade Sea offenders quite a long time until they killed me. XD

Comments are closed.