On February 3, 2026, ArenaNet shipped one of the most structurally significant endgame updates Guild Wars 2 has ever seen. Strike Missions are now Raid Encounters. Classic Raid Wings live inside the same system. And for the first time, you can queue into raid content alone and get matched with nine other players automatically.
The community reaction landed about where you’d expect: positive from players who could never get into raids before, skeptical from veterans who spent years building the infrastructure that raids required. Both groups have valid points. Let’s go through what actually changed and what it means for each of them.
What Actually Changed on February 3
The February 3 Visions of Eternity update unified the raid and strike mission systems under a single endgame framework. If you used to think of the game as having “raids” and “strike missions” as separate modes with different interfaces and different reward structures, that distinction is gone.
Strike Missions have been renamed Raid Encounters. All content — classic Raid Wings, Visions of Eternity encounters including the new Guardian’s Glade, and everything in between — now lives under one roof with a standardized currency system. Magnetite Shards, which were the legacy raid currency, have been consolidated into a unified reward structure that works across all encounter types.
The interface got a significant refresh. The old LFG panel still exists, but there’s now a dedicated Raid Encounters hub that shows available content, difficulty indicators, recommended roles, and the Quickplay queue entry point.
Key Highlights
- Strike Missions renamed to Raid Encounters; all endgame content unified in one system with standardized rewards
- Quickplay queue automatically groups players for a curated rotation of encounters — no manual LFG required
- New Guardian’s Glade raid added featuring boss Kela, Seneschal of Waves; 10-player, coordination-heavy design
- Magnetite Shards consolidated into a unified currency across all encounter types
- Leaderboards and achievement tracking added across the unified system
- Quickplay does not offer a pick-your-own-encounter queue — curated pool only
Quickplay: The Good News First
Quickplay is the feature that changes what Guild Wars 2 raiding is for people who were never raiding before. And that matters more than most of the discourse around it acknowledges.
Historically, raiding in GW2 required either a stable guild with organized groups or a willingness to spend significant time in LFG building a squad from scratch, often with implicit expectations around build quality, LI (Legendary Insight) count, and role clarity. This isn’t unique to GW2 — every MMO with hard endgame content has some version of this gatekeeping — but it meant that a meaningful percentage of the player base that wanted to experience raid content never got there.
Quickplay removes the friction of squad assembly. You queue. The system groups you with nine other players. You get matched into a curated encounter pool. You play. This is how Fractals of the Mists has worked for years at higher tiers, and the community broadly agrees that Fractal matchmaking improved access to that content significantly. The same logic applies here.
The curated pool — where ArenaNet selects which encounters are available in Quickplay rotation rather than letting players pick any encounter — is a deliberate design choice. It keeps the matchmaking pool concentrated so queue times stay low. It also lets ArenaNet tune which encounters are in rotation based on balance, popularity, and accessibility. Whether you think that trade-off is worth it depends a lot on what you want from the system.
The Legitimate Concerns
The veteran raiding community’s concerns deserve direct engagement, because dismissing them as elitism misses the point.
The role management issue is real. WoW introduced role queues (Tank/Healer/DPS) in 2008, and every MMO since has grappled with whether to formalize role separation or leave it implicit. GW2 has always taken an implicit approach — boon support is a role, healer is a role, condition DPS is a role — but the game never required you to declare a role when queuing. Quickplay inherits this. A Quickplay group of ten players might get five Necromancers and two healers, or it might get zero dedicated boon support. The system has no mechanism to prevent that.
ArenaNet’s position appears to be that this is intentional: the encounters in the Quickplay rotation are tuned with the assumption that groups will be compositionally varied, not optimized. If that tuning holds up in practice, the concern goes away. If it turns out that certain encounters feel nearly impossible without adequate boon support even with casual compositions, the community will find out fast.
The content longevity concern — that Quickplay might “burn through” encounters faster and reduce the incentive to invest in the harder content — is more speculative at this point. The reward structure gives players reasons to engage with all tiers of content. Whether casual Quickplay players eventually want to push into organized hard mode is an open question.
“The best version of Quickplay is the one that creates more raiders. Players who clear three encounters in Quickplay and want more will look for a guild. That’s the outcome ArenaNet should be designing toward.”
Guardian’s Glade: Kela and the Wave Problem
The new encounter shipping with this update is Guardian’s Glade, featuring Kela, Seneschal of Waves. The community consensus on Reddit after the first week is: the fight is satisfying when it clicks, and occasionally frustrating when it doesn’t.
Kela’s design is coordination-heavy in the classic raid style. The fight requires squad awareness and positioning, which the community generally praises as a return to what made the original raid wings compelling. The specific criticism centers on what players describe as high RNG variance in certain mechanics — particularly the wave spawn patterns — where bad timing can create unavoidable wipes that feel more like bad luck than skill failure.
The wave mechanics in particular generate discussion. Fast-moving waves require specific movement options like blinks or dashes, and some players feel this creates implicit class restrictions for groups trying to run non-standard compositions. For an encounter designed to also feed into the new Quickplay system, that’s a friction point worth watching.
Worth noting: the early weeks of any raid encounter in GW2 are always the roughest, both in terms of community understanding and in terms of bug reports. Guardian’s Glade launched with some achievement tracking bugs — specifically around “Special Objectives” credit — that players have been documenting and sharing workarounds for. ArenaNet has acknowledged these reports. Expect fixes to follow.
What We Don’t Know Yet
- Whether ArenaNet will add a role-preference system to Quickplay queueing in future iterations
- Which encounters will rotate into and out of the Quickplay pool, and on what schedule
- Guardian’s Glade mechanic adjustments — whether the wave spawn RNG variance will be tuned based on community feedback
- Hard mode availability for Guardian’s Glade and the timeline for Challenge Mode introduction
For Guild Raid Teams
Nothing about the February 3 update removes the ability to form organized static raid groups through the traditional LFG or guild squad system. If your guild has a dedicated Thursday raid night, that still works exactly the same way. The manual squad system and the Quickplay system coexist. They’re not competing for the same players.
What does change for organized guild teams is that the currency and achievement systems are now unified. Content your guild clears in organized mode feeds into the same progression tracking and reward structure as Quickplay content. That’s a net positive for organized players — it removes the artificial separation between modes and lets your organized clears count toward the same goals.
The leaderboard system is also new for organized teams to care about. For guilds that compete in timed clears, having a formal leaderboard infrastructure integrated into the game rather than tracked externally is a meaningful improvement.
Who Should Pay Attention
Players who have never raided — This update is for you. Queue into Quickplay, clear a couple encounters, and see if you want more. The friction is gone. If you like it, your next step is finding a guild and seeing what organized play looks like.
Veteran raiders — Your game mode is still your game mode. Keep using the LFG and organized squad systems. Track the Quickplay tuning in the first month and give ArenaNet feedback if the encounter balance in the rotation pool needs work.
WvW and PvP players who have never touched PvE endgame — The new Legendary accessories added in “The Only Way” update in May include WvW-earned options. If you want the full Legendary collection, watch what the May update brings.
What to Watch For
The first month of Quickplay data will tell the story. Queue times, group composition reports, and encounter clear rates in the Quickplay rotation will either validate or challenge ArenaNet’s tuning assumptions. If queue times stay under ten minutes and casual groups clear the rotation encounter reliably, the design is working. If either number is consistently worse, expect adjustments in the March maintenance update.
Long term, the question is whether Quickplay creates a pipeline into organized raiding or stays a parallel track. Our analysis suggests ArenaNet is designing toward a pipeline — but the execution of that depends on whether the rewards for organized play are compelling enough relative to the lower-friction Quickplay option.
For full Guardian’s Glade encounter mechanics and the new unified reward currency breakdown, check the GW2 Wiki’s Guardian’s Glade page. We’ll link our own Exitializ encounter guide once we’ve had more time to document the Kela fight.