Jump to content
FORUMS
Sign in to follow this  
Stan

Combat Log Range Hotfix: November 21st

Recommended Posts

45232-wow-classic-faq-what-you-need-to-k

In an effort to remove the ability of addons to extend players' senses and detect enemies, the in-game combat log range has been decreased and now only displays information for units that are within 50 yards of the player.

The hotfix has been deployed to live realms earlier today together with the fix for Onyxia's buff which prevented buffs from stacking.

Blizzard LogoBlizzard (Source)

Earlier today, we deployed a WoW Classic hotfix to all regions:

  • The in-game combat log radius has been fixed, and now only displays information for units that are within 50 yards of the player.

This is closer to the original behavior of WoW 1.12, and should eliminate the ability for addons to extend players’ senses and detect enemy actions at a greater distance than intended.

This fix does not affect text logs that the game outputs for raid parses.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Stan
      Blizzard recently posted an update on the Honor Calculation Bug, which has been affecting WoW Classic servers for some time now. They ran a repair script to fix the results of weeks 1 & 2, but the bug caused players to have a higher rank than intended despite the missing kills.
      Blizzard (Source)
      What about 1st 2 weeks Blizzard?
      Did somebody say, “What about the first two weeks?”
      I’m glad you asked, because earlier today, we ran a repair script to fix the results of weeks 1 and 2, and that change should be visible to affected players now.
      During weeks 1 and 2, as many of you have noted here, kills during certain time periods weren’t being counted in the daily roll-ups, which in turn caused them not to count toward your weekly standing. This resulted in players getting the wrong standing relative to one another, and the wrong amount of rank points. Some players got too many rank points, while others got too few.
      Even if you didn’t get all your kills counted, you might have had a higher rank than you ought to, because somebody with a similar standing was missing even more kills (or higher value kills) than you were.
      We had all the kills recorded, but because ranks are a result of relative standings, and each week is affected by previous weeks, we couldn’t just apply a repair for missing kills, we had to re-run the jobs for all 3 weeks to figure out what your correct ranking ought to be right now, and we did exactly that. We didn’t want to take anything away from anybody who might have been blissfully unaware of this problem, so after calculating the correct rank points for everybody in this region, we only adjusted the rank points of anybody who’s rank points were too low, to raise their ranking up to the point that it ought to be.
      Now that that fix has been applied, we’re in a good state to head into battlegrounds.
      Thanks again for your patience!
      See you in Azeroth!
      Related News
       
      Patch 1.13.3 Patch Notes 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
    • By Starym
      Update: The patch notes were edited and the Keyring will in fact only scale to 12 slots for keys.

      We have the patch notes for this week's 1.13.3 update, which will introduce Warsong Gulch, Alterac Valley, Elemental Invasions in Un’goro Crater, Azshara, Winterspring, and Silithus, the Keyring, changes to the lua API preventing certain addons using communication channels in an unintended way, bug fixes and the potential for paid character transfers to be introduced later on.
      You can check out our battlegrounds guide for all of classic here or head to the specific AV and WSG ones.
      1.13.3 Patch Notes (source)
      With scheduled weekly maintenance in each region, we will update WoW Classic to version 1.13.3, which includes several updates to the game. We will deploy this patch with weekly maintenance starting at 7:00 a.m. PST (10:00 a.m. EST) on Tuesday, December 10.
      World of Warcraft Classic Version 1.13.3
      Battlegrounds
      The fields of battle are open, and the Alliance and Horde are set to clash over Warsong Gulch and Alterac Valley.
      Warsong Gulch is a 10v10 game of capture-the-flag, with each faction attempting to carry their opponents’ flag all the way back to their own base, while preventing the opposition from doing the same. Players fight in level-ranges in Warsong Gulch: 10-19, 20-29, 30-39, 40-49, 50-59, and level 60.
      Alterac Valley is a large 40v40 tug-of-war zone, with many quests, objectives, and areas of interest. All players at level 51 and higher are placed into a single level-range in this epic struggle, with rewards via reputation as well as quest rewards. Some Alterac Valley rewards are highly sought, such as Don Julio’s Band, Lei of the Lifegiver, and Ice Threaded Arrows/Bullets.
      The Alliance entrance to Warsong Gulch is in Silverwing Grove in Ashenvale Forest, and the Horde entrance is near Mor’shan Base Camp in the northern Barrens. The Alliance and Horde entrances to Alterac Valley are in northern Hillsbrad Foothills. Both Warsong Gulch and Alterac Valley can also be entered by speaking with the appropriate battlemaster in your capital city.
      Battlegrounds are cross-realm, which means you’ll fight alongside allies and against opponents from all of the realms in your region.
      Elemental Invasions
      Across Kalimdor, Blazing, Thundering, Watery, and Whirling Invaders now occasionally appear in Un’goro Crater, Azshara, Winterspring, and Silithus respectively. The elementals appear to be seeing just how far into these territories they can penetrate before being beaten back by the forces of the Horde or the Alliance.
      Keyring
      The key button in your micro menu now opens your Keyring, an additional bag for keys only, that scales up to hold 12 keys.
      Additional Updates
      The lua API has been modified to prevent some addons from using communications channels in ways that are contrary to the spirit of the game. This patch includes client support for the Paid Character Transfer service, which may be enabled at a future date. The World of Warcraft Classic executable file on your PC has been renamed. Bug fixes. Blizzard is also preventing addons from communicating over custom player-created chat channels in the forthcoming update.
      Lua API Changes (source)
      With the release of World of Warcraft Classic 1.13.3, we’re making a change to disallow calling C_ChatInfo.SendAddonMessage with the CHANNEL ChatType. This will prevent addons from communicating over custom, player-created chat channels.
      Addons will still be able to communicate using PARTY, RAID, GUILD, and WHISPER in the same ways that they can now. Additionally, we are going to test a change to permit C_ChatInfo.SendAddonMessage to be called with SAY and YELL, allowing your addons to communicate with players in your immediate vicinity.
      We support using addons to customize your gameplay experience. However, we also want to ensure that we preserve the social dynamics that make Classic what it is. Ultimately, we decided that the ability for addons to send invisible messages to large, arbitrary groups of players all across Azeroth was something that risked undermining those social dynamics.
      Thank you!
         

      Related articles
      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
      The Phase 3 patch notes are here! WSG, AV, the Keyring and a lot more!
    • By Starym
      The honor system has been having a lot of troubles lately, but as we found out in the previous blue post, it's all just  been a display issue with the statistics which they are now in the process of fixing. Since a lot of players aren't trusting these findings/fixes and are convinced something is off for their honor totals, Classic developer Pazorax went in-depth to explain how the system actually works. He reiterated that honor has been calculated correctly this week and emphasized the long, long road towards the higher honor ranks, including a minimum 12 week journey to the very top, and that's only if you're the very best in your faction ever single week.
      Honor (source)
      I know the honor system can be frustrating, and even more so if it feels like you’re not getting credit for your efforts, so I wanted to post and let you know we are looking at people’s honor for the week, and so far all the checks we’ve done indicate that honor was calculated correctly this week.
      As we mentioned before, our data repair job on Monday caused the “This week” totals to display an inflated value for the rest of the day, and that appears to explain a lot of the confusion we’ve seen so far.
      We also know that some players confuse “estimated honor” with actual honor (estimates don’t account for diminishing returns), or confuse honor with rank (honor is earned from kills, rank is based on your relative standing within your faction). The honor system is slow to progress you through the ranks, even in the best case, so many of these reports aren’t a case of the honor going “missing” as much as they’re a case of an unforgiving system giving you less progress toward a rank than you were expecting.
      In addition to being based on your relative standing within your faction, your progress to the next rank also slows down as you reach higher ranks. Achieving the same standing each week won’t award the same amount of progress toward each rank, it awards a fixed percentage of the delta between your current rank, and your current standing. It is actually impossible to achieve rank 14 in less than 12 weeks, and that assumes that you’re the top player on your faction for every one of those 12 weeks.
      Those are all intentional behaviors, and are not bugs, but they can all contribute to a feeling of difficulty progressing through the ranks.
      We also see reports of missing kills when you’re playing during the daily reset job, and we’ve checked that too. In fact, I just checked right now, on some of the people who reported errors in this thread, and last night’s job did calculate their honor correctly. Those kills are still there, its just a display issue, and they’ll show up on the next day’s daily report now that the underlying issue is fixed.
      We are continuing to investigate, but at this time we don’t see any problems in the week 3 data. Once we conclude this investigation we can move on to investigating the problems that occurred during week 1 and 2, and we’re beginning to do that now.
      Thank you again for your patience as we work through these issues.
    • By Stan
      Free Character Moves are closing for all WoW Classic realms on December 5-6. Will paid character transfers be announced soon?
      Blizzard said they were considering paid character transfers in WoW Classic back in September because the service was available in original WoW, but no other paid services beyond that.
      Blizzard (Source)
      Piggy backing on this...will PAID transfers also be a thing should a server drop heavily in population and a player wishes to move to find more activity or reconvene with friends on another server.
      We're considering integrating a character transfer service once players have reached higher levels. This was available in the original WoW. We'll look at the rules we imposed at that time and also discuss the implications of players moving to a new realm. We believe realm identity is an important aspect of Classic so any guidelines around transfers should support this belief.
      Will there be paid services for Classic?
      We aren't considering other services beyond character transfer at this time.
      While we have no specific details to share at this time, Free Character Moves that have been available since the launch of WoW Classic are going away this week, and perhaps, we're not too far away from paid character transfers being integrated into WoW Classic now that players will be locked to low-population servers.
      EU
      Blizzard (Source)
      On 6 December at 1:00 a.m. CET, we will close the Free Character Move service for all realms in this region. We suggest that any player who has not yet taken a planned Free Character Move please do so as soon as possible.
      Thank you very much!
      US
      Blizzard (Source)
      On December 5 at 11:00 a.m. PST (2:00 p.m. EST), we will close the Free Character Move service for all realms in this region. We suggest that any player who has not yet taken a planned Free Character Move please do so as soon as possible.
      Thank you very much!
    • By Stan
      Last week, we reported about a bug in WoW Classic which caused Honor not to calculate between 3-7 AM. Blizzard has now replied that the bug has nothing to do with the previous caching issues and they're pretty close to fixing it.
      The issue was apparently caused by the daily honor script running before the end of the day, causing it to miss kills that haven't yet happened. The good thing is they have all the kills recorded, even though you can't see them in-game, so you won't lose any Honor when this is fixed.
      Blizzard (Source)
      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.
×
×
  • Create New...