Recently Browsing 0 members
No registered users viewing this page.
After the release of Patch 1.13.3, players thought that Paladin's Reckoning was broken, but Blizzard clarified that losing Reckoning stacks when mounting up or initiating auto-attack against a target and canceling it before it goes off is perfectly normal.
On top of that, they've discovered a bug where Paladins lose stacks of Reckoning if they're not facing their target or are out of range to attack the target when the Reckoning stacks are gained. This behavior is inconsistent with the 1.12 reference client and will be fixed next week during the scheduled realm restarts.
I wanted to take a moment to provide some clarification around what changed in 1.13.3 with Reckoning. There were several systemic issues with extra attack procs behaving incorrectly, which we fixed in the patch. A secondary effect of these fixes were two notable changes to Reckoning:
Reckoning stacks are lost when you mount up. Reckoning stacks are lost when you initiate an auto-attack against a target and cancel it before it goes off. However, both of these behaviors were correct behaviors in the 1.12 reference client and as such are considered bug fixes. Both of these issues have been added to the “Not A Bug” list.
Additionally, when investigating the reports around this, we did discover another bug where Paladins will lose stacks of Reckoning if they are not facing their target or are out of range to attack the target when the Reckoning stacks are gained. This is not consistent with Reference client behavior, we have a fix for this now, and it should be fully live the next time we have realm restarts.
Lastly, while we appreciate the reports in this thread, there were many comments and replies that do not apply directly to this issue, or were unhelpful, and we’d like to remind everyone of the bug report forum guidelines 1. We will monitor and remove unhelpful or off-topic replies in threads like this. Keeping these threads on-topic and strictly comprising information that helps us find and reproduce bugs will help ensure that we can get these issues identified and fixed faster.
Marks of Honor Last Longer Than 24 Hrs in the Mailbox Missing Honor and Honorable Kills Bug
You can only carry 20 pieces of Alterac Valley Marks of Honor or Warsong Gulch Marks of Honor in WoW Classic at a time. The rest is sent to you via mail and the expiration time is currently set to 30 days as opposed to 24 hours.
A new bug related to Marks of Honor has emerged in WoW Classic. Currently, the Marks have a 30-day expiration time instead of the intended 24 hours.
Bug: Marks of Honor in the Mailbox are lasting for 30 days instead of 24 hours.
Steps to recreate:
Collect 20 Warsong/Alterac Marks of honor Win or lose the BG of which you have 20 marks Check mailbox The marks will be deleted after 30 days 24 hours is the intended amount:
44 By [bangy][on 2006/12/05](Patch 2.0.1)
“A mark is obtained by playing a game of Warsong Gulch until the end - you do have not to have started when the battle started, but you must be at the end.
If the battle is won, 3 marks are obtained, but only 1 is received if it is lost. Marks are automatically put into your inventory, but if there is no space, it is sent to your mailbox. However, note that it will disappear in 24 hours, so clear some space and get it back fast!”
“once you have 20 of these(inventory and bank combined), you can’t carry any more. when you complete a wsg, if the token reward would give more then 20, they go to your mailbox instead. they are on a short timer (only 24 hours) in your mailbox before they disappear. you can’t get them out of your mailbox until you turn in some of the ones you already have.”
From ThottbotBy tobiason [on 2006/12/16] (Patch 2.0.1)
"Subject: “Marks Of Honor"I have 100 AB marks now. When I continue to participate in raids, afterwards (when we win), I receive no marks, but I get a mail from the battlemaster. It is a message that says that I cannot carry any more marks, and has 3 marks attached. I can save the mail, but for only 24 hours.”
Having marks last 30 days can lead to people saving up marks for a month and grief other people ranking.
We’re working on a hotfix for this issue. After the hotfix is applied and certain servers are restarted, we’re going to try to modify your mail so that anyone who has these will not be able to carry them over into the next week.
And going forward, new Marks of Honor in the mail will have a 24-hour expiration.
Thank you for the report!
Missing Honor and Honorable Kills Bug
Blizzard is working on yet another bug related to missing Honor and Honorable Kills from Monday.
Anyone else missing the monday’s honorble kills and honor ?
This week tab for me displays 1087 and 69k honor which is totally wrong because on monday i did all day 800 kills (around 28k honor) but it seems this numbers are missing. it only counted yesterday activity.
That’s exactly right.
We’ve found a process bug that caused a window of time where Honor appeared to go uncounted, and we’re repairing the missing honor. After the repair:
If you got fewer rank points than you should have, we’ll increase your amount up to where you should be. If you got more than you should have, we’ll won’t change your amount. And of course, we’re working to fix the bug.
Honor Calculation Bug Update: Dec 10
Blizzard today clarified that they have fixed a bug in WoW Classic related to the Runeblade of Baron Rivendare weapon which caused the Unholy Aura weapon buff to be utilized to snapshot the current +Healing gear. The Healing per 5 seconds would be and upon switching to a different set, but maintain the Healing per 5 seconds.
As a result, the Healing per 5 seconds was maintained upon switching to a different set. A demonstration of the bug can be seen in the video linked below.
Based on the latest blue posts, we learned that this behavior was not intended and they have fixed it with the release of Patch 1.13.3.
I wanted to take a second and clear up any misconceptions about the nature of this bug fix. The Runeblade of Baron Rivendare neither scaled with +healing nor snapshotted any +healing effects in Original WoW or the 1.12 Reference client. This behavior was a bug that was introduced into WoW Classic. As such, the fix that went into 1.13.3 that removed the +healing benefit and snapshotting restored this item to it’s original 1.12 state.
As this bug is now resolved we will be closing this thread now. As always, thank you for your reports and analysis!
Patch 1.13.3 Patch Notes Patch 1.13.3 Know Issues List Warsong Gulch Vendor Details and Clarification Honor Bug Calculations Update: December 9th Detailed Honor System Clarifications and Stats Issues Addressed Are Paid Character Transfers Coming Soon? Combat Log Range Hotfix: November 21st Rallying Cry of the Dragonslayer Hotfix: November 21st Jokerd Removed from Method Org After Ninja Looting World's Fastest Molten Core Clear in Phase 1 by Salad Bakers
With the new patch and phase having arrived on NA servers today we now also get a list of known issues, as well as some workaround fixes until the issues are resolved.
You can also check out the full patch notes here, or check out our battleground guides here.
Known Issues for December 10 (source)
Greetings and welcome to WoW Classic patch 1.13.3!
Below is a list of known issues for WoW Classic patch 1.13.3. Please note that this list is not comprehensive and is not a complete depiction of what we’re aware of, but a sampling of issues we believe players may encounter with some regularity. We hope to have fixes to these issues in place soon, but we cannot promise when or if any individual bug will be fixed.
Alterac Valley: The Frostwolf Battle Standard and Stormpike Battle Standard are currently using models that do not match Original WoW Warsong Gulch: The particle effects projected from the Alliance Flag are too bright User Interface
The “Toggle Keyring” option is missing from the Keybinds menu The Oozeling’s Disgusting Aura does not display a debuff in the character’s debuff tray System Settings
Certain PCs may incorrectly default to integrated graphics adapters Workaround: Open the System Menu via the Escape key and select System -> Advanced -> Graphics Card and select the correct GPU Lastly, please also note that we do not list any issues here that we are aware of that could be considered exploitative, and as per the forums Code of Conduct 1 we would ask you not to post information in this forum about any potential exploits that you have discovered. If you believe you’ve found an exploit, please email email@example.com directly with the relevant details.
Patch 1.13.3 Patch Notes Warsong Gulch Vendor Details and Clarification Honor Bug Calculations Update: December 9th Detailed Honor System Clarifications and Stats Issues Addressed Are Paid Character Transfers Coming Soon? Combat Log Range Hotfix: November 21st Rallying Cry of the Dragonslayer Hotfix: November 21st Jokerd Removed from Method Org After Ninja Looting World's Fastest Molten Core Clear in Phase 1 by Salad Bakers