Blizzard E-mail Confirming Honor System

#0 - Dec. 6, 2006, 7:33 p.m.

From : <donotreply@blizzard.com>
Sent : Wednesday, December 6, 2006 12:40 PM
To :
Subject : Blizzard Entertainment - World of Warcraft

Greetings,

Thank you for contacting the World of Warcraft Game Master Department.

Petition: Yesterday I started PVPing in Arathi Basi around 11pm O'clock Eastern
Standard time. I PVPed streight until 4 am EST and recieved a total of 20 Arathi
Basin "Marks of Honor" and only an estimated total of 2.1k honor... but 300+
Honorable Kills. After 3 am PST this morning, my honor totals are not even close
to where they should be, because I /ins myself and it shows 14... if I PVPed
yesterday for 5 hours to get 14 spendable points you can cancel my subscription
right now.

Answer: I am very sorry that you feel this way about our new honor sytem. :( It
does appear to be functioning properly at this time.

Should you require further assistance, please submit another help request the
next time you are online. We hope you continue to enjoy your experience in
World of Warcraft!

For any game play questions, please refer to our site at
http://www.blizzard.com/support/wowgm/

*** Please do not respond to this email as all conversations on this matter
would be best handled online. ***

Regards,

Sheritarl
Game Master
Blizzard Entertainment
www.worldofwarcraft.com

Drysc

#15 - Dec. 6, 2006, 10:15 p.m.

The honor calculations were not run last night. Everyone who gained honor yesterday should continue to see 0 honor earned at the top of their honor window. I'm still awaiting further information on how this will affect honor earned yesterday and if the calculations are going to be able to be run tonight. We're still in the process of investigating why the honor was not calculated last night and ensure that it's working properly for future calculations.

We'll get you more information as soon as we're able.

There are some known display issues that may cause the "Today's Honor" field to not display correctly. Either logging out and back in, or using /console reloadui should resolve the display error temporarily. We're of course aware of this issue and a fix is slated for a future update.