over 8 years ago - /u/AnetChrisB - Direct link

From https://forum-en.guildwars2.com/forum/game/wuv/Reminder-Skirmish-beta-beginning-soon

Skirmish scoring will go into effect in about 15 minutes (near 18:00Z), with the EU reset.

NA players: while you’ll immediately see the new skirmish data in the WvW dialog, this week’s match will still have its end result scored in the old War Score-only style, ignoring Victory Points from skirmishes.

Sites that use our API for WvW will still display the “vanilla” War Score that accumulates over the week.

External link →
over 8 years ago - /u/AnetChrisB - Direct link

Originally posted by Despondent_in_WI

Is this removing the WvW-granted Artisan and Gatherer bonuses (which I believe was discussed previously)?

The WvW-granted "world bonus" buffs are still there right now, using the week-long War Score that's still being accumulated in the background.

over 8 years ago - /u/AnetChrisB - Direct link

Originally posted by fishlock

Is there any reward for winning a skirmish?

Right now, skirmishes are in a first-phase test to see how they're received.

If skirmishes are liked and stay around, we expect to do more with them.

over 8 years ago - /u/AnetChrisB - Direct link

Originally posted by [deleted]

Is it intentional that US's PotM bonuses have reset? I wrote a thread on the forums before noticing this post and I feel like a bit of a dickhead :(

The display for PotM bonuses in the WvW dialog's second tab is incorrectly showing what bonus would be present with the War Score from only the current Skirmish.

The tooltip on the WvW button in the quicklaunch bar along the upper-left of your screen still shows the real PotM bonus you're currently receiving behind the scenes.

over 8 years ago - /u/AnetChrisB - Direct link

Originally posted by seganku

I've been getting this error for more than 20 minutes, while guildies are in WvW and EotM having the time of their lives. A client restart had no effect.

World vs. World is unavailable while matches are being updated. Please try again in a few minutes. (Code=1068:9:17:4740:101)

Woe.

One source of this error message is when your client isn't in the build that's active for WvW. The error text doesn't communicate that possible cause well. In this case, WvW was still in 66,537, while some clients were in 66,577.

This has been fixed. Thanks for the report!