World vs. World in BWE2 was a disaster. The matchmaking paired servers with three times our population against us. Stonehold Castle fell in fifteen minutes. My frame rate dropped to single digits every time two zergs made contact. I spent more gold on armor repairs than on anything else all weekend.
And I have not stopped thinking about it since Sunday night.
There is something about WvW that cuts through the roughness in a way structured PvP has never managed for me. The objective is simple enough to explain in one sentence: three servers, four maps, 250 points per tick, last team standing wins. But the execution opens up a kind of chaos that no arena match can replicate. When it works, when you have a commander on comms and a group that moves together and the enemy zerg is visible on the horizon, it feels like nothing else in the game.
Stonehold Castle: The Center Cannot Hold
The crown jewel of the Eternal Battlegrounds is Stonehold Castle, and on day one of BWE2 it changed hands like a hot potato. Our server capped it within minutes of the map opening. Fifteen minutes later, we lost it. Twenty minutes after that, we took it back. The rhythm was exhausting, exhilarating, and clearly not what ArenaNet intended.
The community is right that Stonehold needs heavier siege requirements for an initial capture. As it stands, the castle rewards whoever loads in fastest rather than whoever fights smartest. But here is the thing: even in its broken state, those fights were the highlight of the weekend. Holding the inner lord room against a full-zerg push, watching the siege rain down from the walls, hearing the commander call targets over the chaos. The raw material is there. The tuning is just off.
ArenaNet already knows. The forums lit up with proposed solutions over the weekend, and the design team has been responsive. I expect Stonehold to feel like a proper fortress within a patch or two of launch.
Three Servers, Four Maps, One Objective
The scale of WvW hit differently than I expected. You read “three servers, four maps, hundreds of players” and you think you understand it. You do not. Not until you are crossing a borderland alone at 2 AM, trying to find your group, and you realize how vast these maps actually are. The empty spaces matter. The travel time between objectives is a real cost. When your server is down to one camp and you have to fight your way back across the map, the geometry of the place becomes something you feel in your play.
This is also where the steamroll problem showed up hardest. Once a dominant server had map control, breaking back in was brutal. Spawn-camping is never fun, and the lack of rally points meant a losing server stayed losing. The community is asking for comeback mechanisms: harder-to-capture final keeps and automated temporary alliances between the two losing servers. Those are good ideas. But even the blowout matches taught us something about positioning, supply lines, and map awareness that no amount of theorycrafting could.
The Beautiful Disaster of Large-Scale Combat
Let me be honest about the performance. When two full zergs met in open field, my client turned into a slideshow. Five to ten frames per second. Skill delays that made staff Elementalist unplayable. The famous Warrior Hundred Blades spike was the only thing that would register through the lag, which is probably why every other player on the map was running it.
And I still loved every second of it.
There is a raw appeal to being in a fight so large that the engine cannot keep up. It is the MMO equivalent of a live concert where the sound system distorts because the room is too full. The performance will improve. The client is still months from release, and ArenaNet has confirmed CPU optimization is a priority. But the feeling of being in a hundred-player engagement is something no amount of polish can manufacture. BWE2 proved the scale works even when the frame rate does not.
The Gold Drain and the New Player Experience
WvW is expensive. Armor durability damage applies the same way it does in PvE, which means every death costs silver. And in BWE2, we died a lot. Between the matchmaking mismatches and the learning curve, our repair bills ran higher than anything else on the character sheet. The community is asking for reduced repair costs in WvW, and that feels like an obvious fix.
The new player experience is another rough edge. Supply is essential: every tooltip tells you that, but the game never explains how to gather it, carry it, or spend it on siege. Low-level players upscaled to 80 get shredded by ambient wildlife on the way to the fight. The barrier to entry is real, and it is probably scaring off players who would love WvW if they could just get past the first hour.
But here is the encouraging part: the community is already building the resources that the game has not yet provided. Guilds are running supply tutorials. Commanders are leading new-player trains. The forums are full of guides written by veterans who remember their own first confusing hour. The infrastructure is forming organically while we wait for ArenaNet to catch up.
What Comes Next
BWE2 was not a polished product. The matchmaking was broken, the performance was rough, and the economy needed rebalancing. But polish is what the next two months are for. What BWE2 proved is that the foundation is solid, more than solid. The vision of three servers fighting across four interconnected maps for week-long campaigns is real, and it works.
When Mike Ferguson acknowledged the matchmaking failures on the forums over the weekend, he did not make excuses. He said they would look into what happened and make sure it does not happen again. That is the right response from a team that knows what they have and wants to get it right.
WvW in BWE2 was broken, laggy, unfair, and expensive. It was also the most fun I have had in an MMO in years. If ArenaNet can tighten the matchmaking, optimize the engine, and add a few comeback mechanisms, launch is going to be something special. We will be here for all of it.
See you on the battlefield.