On Friday, December 6th, we will be continuing our raid tests in Ny’alotha, the Waking City. Following the scheduled mythic testing on Friday, the first wing of Looking for Raid will be available for testing.
Friday, December 6th
Dark Inquisitor - Mythic Ny’alotha, the Waking City
13:00 PST (16:00 EST, 22:00 CET)
Ra-den - Mythic Ny’alotha, the Waking City
14:00 PST (17:00 EST, 23:00 CET)
Vision of Destiny - Looking for Raid Ny’alotha, the Waking City
15:00 PST (18:00 EST, 00:00 CET)
As always, this testing schedule is very fluid and subject to the realities of a test environment. We might have to change the time of a testing session, change the bosses being tested, or cancel a test entirely, due to bugs, server hardware issues, etc. Keep an eye on this forum for the latest information, and thank you in advance for testing and providing feedback.
Q: How do I get into the raid zone?
A: In Zuldazar, Boralus, Dalaran, Orgrimmar, or Stormwind, you may speak to Nexus-Lord Donjon Rade III in order to teleport into the raid zone while it is open for testing. (The option to teleport into a zone will not be available when the zone is not open for testing.)
Q: What character should I use to test the raid?
A: Whichever you prefer. We will be scaling players’ effective level to 120 for raid testing, and their item level to an appropriate threshold for the encounter(s) being tested.
Q: How long does testing last?
A: The primary purpose of testing is to give us the information we need to balance the encounters, evaluate how mechanics are playing out in practice, and identify bugs. Once we’re satisfied that we’ve received that information for a given boss, we’ll be shutting down testing. Usually this takes anywhere from 45 minutes to 2 hours, but there are no guarantees.
RT @GCDTV: 🏆 By popular request, we'll also be hosting an EU 2v2 event at the end of the month! 💰 $4,000 USD prize pool 🖱️ Signup today:…
Waaaay too much honor is being added. Looks like previous weeks are getting lumped in or an error in calculation/refund.
Just relogged again and gained another 35,000 honor.
While I appreciate the reports, panic is unwarranted. The incorrect honor values in “this week” are another display bug.
The repair job runs one day at a time, and one realm at a time, so that’s why logging out and back in was displaying more honor. You caught it between days on the first login, and had additional days processed before the next login.
After this repair job completes the running weekly total displayed for “this week” will be a total of:
That will not be the value used for the weekly rank adjustments. The weekly rank adjustment will correctly use the results of the repair.
Tomorrow, after the weekly reset runs, you should see the correct value in the “Last Week” display, which was actually used to calculate your rank adjustment for the week.
We’re working as fast as we can to have this repaired before the weekly job runs, so our focus has been on the data that actually feeds into the weekly honor calculations, not on the display, which actually pulls the data from a different source, that’s optimized for in-game display, rather than for calculation by these jobs. I hope that explains what everybody is seeing, but if you see something inconsistent with what I just explained, please say so. After all, that’s how we found this issue in the first place!
I hope that gives everybody some peace of mind.
Well that really stinks losing about a 1/4th of my total honor gains for the first two weeks all while being told the kills were still “accounted for”.
But thanks for the reply.
Just to be clear, we do have the kills logged (for previous weeks as well).
What I said is that this action doesn’t affect previous weeks’ results, and we’re still investigating the scope of the damage, now that the cause has been identified.
While you are around! Does this fix effect anything for players missing honor Weeks #1 and #2?
Any response would be awesome! Thank you
No, this job will not affect any of the results in previous weeks.
The steps to fully resolve an issue like this are:
While we’re at step 4 for this week’s data, we’re really at step 2 for the problem at large (repairing this week’s summaries keep the problem at large from getting worse).
While we’ve seen anecdotal reports of lost honor, it’s only now that we know the source of the problem that we can identify how widespread the damage from it was, and that investigation is still ongoing.
I want to thank everybody that provided constructive feedback, and detailed information that helped us identify the issue here.
So what do you think? is this fix happening or not?
It sure is! We’re running a repair job for this week right now.
One thing to note about this repair job is that it will zero-out the kill count display for today, but that is just a display issue. In order to get this out as soon as possible, we’re leveraging the existing daily summary code, and one of the things it does is reset the daily kill-count display.
The kills are all still there and will be tracked in the daily summary code tomorrow morning, just before it runs the weekly summary code.
So to summarize, if you see your daily kills get set to 0, that’s okay, and those kills will still be counted.
It would be nice to have a blue at least respond saying there is an issue…
I agree, but unfortunately we didn’t have the chance to respond sooner. We’ve been investigating, and can now confirm that yes, this is a separate issue, that’s not related to the caching issues we were experiencing previously. The caching issues made it more difficult to uncover this issue, and I appreciate the detailed reports of which kills were missing and over what time range which helped us track this down.
We’re getting pretty close to fixing this, and it turns out it was caused by the daily honor script running before the end of the day, causing it to miss kills that haven’t yet happened. But worry not! Those kills are still recorded, they just weren’t getting collected into the daily statistics correctly, so they’re not displaying in-game for “yesterday” or “this week” kills/honor. The source of the issue appears to be a scheduling system treating a UTC time as a local time, and we believe we’ve found and fixed that problem a few minutes ago.
We’re also working on a fix to repair the daily statistics which we’re hoping to run Monday, in advance of the weekly rank adjustment, so it will correctly count all your kills and honor correctly for this week.
I want to stress, that we do have all the kills recorded, even though you can’t see them all in-game, and we’re working hard to get the weekly statistics correct.
Thank you for your patience as we untangle this issue.
BlizzCon is over and the champions crowned, but some gladiators are lurking around
They’re jumping in queues and enthusiastic, with partners who aren’t all just streaming Classic
Wintering warriors spread holiday cheer, each knowing full well that not all is yet lost
For GCDTV tournaments are here, and you can sign up and play at zero cost!53PUQGJsP4jX.png 1280×720
It’s that special time of year again and you know what that means— there’s no better way to celebrate the holidays than a good old fashioned Arena Tournament Series.
|3v3 Winter Brawl [EU] 1||Saturday, December 7th||18:00 CEST / 8 AM PST|
|3v3 Winter Brawl [EU] 1||Sunday, December 8th||18:00 CEST / 8 AM PST|
|3v3 Winter Brawl [NA] 1||Saturday, December 14th||1 PM PST|
|3v3 Winter Brawl [NA] 1||Sunday, December 15th||1 PM PST|
|2v2 Winter Brawl [NA] 1||Saturday, December 21st||1 PM PST|
|2v2 Winter Brawl [NA] 1||Sunday, December 22nd||1 PM PST|
Twitch.tv/GCDTV - Follow to be notified when we go live!
· Each Tournament will have at least $2,000 Prize Pools up for grabs ( NOW $4,000 Prize Pool per tournament thanks to Twitch )
· North American and European regions only (currently)
· Tournament Format will follow Double Elimination (Single Finals)
· Battle.net accounts must be in good standing in order to participate
· All Eligible Teams will be granted access to the Tournament Realms by Blizzard
· Brackets will be seeded by a team average of current rating
· If more than 8 teams sign up - Early round games will be played earlier in the week
Think you’ve got what it takes to compete with the best? Well you should sign up anyway! It’ll be lots of fun!
Join the frontlines and save 50% off World of Warcraft: Battle for Azeroth and select Digital Deluxe items, now thr… https://t.co/X1TEOWQEH2
RT @GCDTV: ⚔️ We're trying out something new with a 2v2 Winter Brawl! 👀 💰 $2,000 USD prize pool 🏆 Registration and more info: https://t.c…
Discussions about changes or game design are always welcome here, but things that focus on harassing employees and/or removing them is not and can lead to actions being taken. Please keep that in mind at all times.
As a result of this, I’m locking this thread. If you have feedback on the brutosaur, please continue to share it here:
There’s a Feat of Strength that was datamined from the PTR for players who purchase the Mighty Caravan Brutosaur sold during Battle for Azeroth. The mount will no longer be sold by the current vendors and will be moved to the Black Market Auction House according to official word.