Jump to content
FORUMS
Sign in to follow this  
Starym

The Final Not a Bug List Update Before Launch

Recommended Posts

45366-new-classic-wow-realms-opening-aug
 

The probably final update to the infamous "Not a Bug" list has arrived and we have a number of things from all over the place, from non-loot roll triggering chests to offhand Windfury procs, invisible quivers and, most importantly, the fact that logging into Classic or BfA while logged in to the other one will disconnect you!

Blizzard LogoNot a Bug (source)

Hi All,

I’ve just updated the OP with the following:

  • The chest at the end of the encounter with The Seven in Blackrock Depths does not prompt a loot roll. Beware of Ninjas!
  • Shield Slam and other off-hand abilities does not proc extra attacks from Windfury.
  • Logging into World of Warcraft: Battle for Azeroth while playing WoW Classic on the same game account will disconnect you from WoW Classic. This is true in reverse as well.
  • Other players do not see a Hunter’s quiver on their back.
  • Hunters can sometimes experience a slight delay before recasting Auto Shot after moving.
    • Note: There is a hidden “retry” timer that occurs if the hunter is moving when the normal swing timer finishes. This timer checks for hunter movement before trying to resume auto shot, and this timer refreshes every 500ms when the hunter is moving. This means that if a Hunter is moving and stops moving just after this timer refreshes, you need to wait until this retry timer checks again to validate that you are no longer moving before you resume casting auto shot. This is not a result of spell batching or server heartbeats, and is specific to the functionality of a Hunter’s Auto Shot and is consistent with Auto Shot functionality on the Reference client

And here's the full and updated list itself:

Blizzard LogoFull List (source)

As we’ve discussed before, the nature of WoW Classic sometimes invokes different memories for different players, and this leads to certain misconceptions for some about what is or isn’t working as intended.

The following is a list of commonly-reported gameplay in WoW Classic that is not actually a bug, and is working as we expect it to:

  • Tauren’s hitboxes and their melee reach is slightly larger than other races.
  • Being critically struck while using /sit to sit does not cause abilities like Enrage, Blood Craze, and Reckoning to activate.
  • Using the “Automatic Quest Tracking” option does not auto-track newly accepted quests. (It instead will start to track an existing quest once progress towards an objective is started.)
  • Warrior health Regeneration is working at the expected rate.
  • Quests objectives and points of interests are not tracked on the map or minimap.
  • Completed quests are marked on the minimap with a dot. (and not a “?”)
  • Feared players and NPCs run fast.
  • Standing on top of other players while facing away allows spells and attacks to be used.
  • Creature respawn rates are much slower than in Battle for Azeroth.
  • NPCs which offer multiple quests may inconsistently display them as a dot or a “!” on the available quests list. They were inconsistent in 1.12, and we’ve reproduced the exact inconsistency they had back then.
  • Quests that are too low level for do not show up as a “!” in the game world.
  • Available quests do not display a “!” on the minimap.
  • On level up, the message: “Your skill in Protection increased to 15” was added in 1.12.1, and we’re intending to keep that.
  • You are unable to Polymorph enemy targets that are tapped by players with whom you are not grouped.
  • At all levels of player characters and enemies, aggro radius is set to the intended distance.
  • Long quest objectives don’t have text wrapping.
  • Fall damage is equivalent to expected and verified values.
  • Broadcast text can be seen multiple times if multiple players interact with the same NPC.
  • WANTED signs do not have “!”, and are also not highlighted.
  • Player characters do not animate when looting/interacting with quest objects (e.g. collecting pumpkins).
  • Gnomes and Taurens are the correct size.
  • “Melee leeway” is working as intended in both PvE and PvP.
  • Cone of Cold is behaving consistently with the reference client.
  • Arcane Missiles does not put the caster in combat .
  • A Hunter’s Frost Trap ground effect will break Rogues out of stealth.
  • The Berserking Troll racial ability is behaving as expected and matches the reference client.
  • The pet that a Warlock has when initially logging into the game world does not restore a Soul Shard when dismissed by taking a flight path or moving out of range.
  • The trigger range on Hunter’s traps are reduced by Stealth when the stealthed player is a similar or higher level than the Hunter.
  • Soul Link cannot be dispelled by dispelling the Warlock’s pet.
  • A Warlock’s Succubus and Felhunter pet cannot cast spells if they are out of line of sight of the target.
  • Manually cancelling Stealth after using Vanish will remove the Vanish buff as well as the Stealth buff.
  • Escape Artist has a very small chance to fail when used to escape an effect that has a decreased chance to be dispelled (e.g. a Rogue’s Vile Poisons talent).
  • Rogues are not broken out of stealth by Blizzard until they take damage.
  • Taunting Hunter pets that are set to Aggressive or Defensive mode will cause them to attack the taunting player.
  • The threat generated by Battle Shout is not capped at 5 party members and is increased when affecting targets such as Hunter and Warlock pets within the same party.
  • The chest at the end of the encounter with The Seven in Blackrock Depths does not prompt a loot roll. Beware of Ninjas!
  • Other players do not see a Hunter’s quiver on their back.
  • Shield Slam and other off-hand abilities does not proc extra attacks from Windfury.
  • Logging into World of Warcraft: Battle for Azeroth while playing WoW Classic on the same game account will disconnect you from WoW Classic. This is true in reverse as well.

Hunter concerns:

  • Hunter “dead zone” is working as expected and is consistent with the Reference Client.
  • A wolf pet’s Howl buff is consumed by anything that causes damage, even if it does not benefit from the buff.
  • A Hunter pet’s Bite and Claw ability damage will not change in the tooltip based on the happiness of the pet. The tooltip will always display the damage as if the pet were Content (yellow). This is consistent with the Reference client.
  • Traps can sometimes not be triggered if a player moves over them very quickly (i.e. a Warrior’s Charge ability). This behavior is consistent with the Reference client.
  • Auto Shot does not make a sound when cast during the animation of Hunter’s Mark and certain other abilities.
  • Scatter Shot, Wyvern Sting, and Freezing Trap share diminishing returns.
  • A Hunter’s Frost Trap ground effect will break players out of stealth.
  • The rate at which pet focus regenerates is not always consistent.
    • Note: While the actual amount of focus that can be generated per tick is inconsistent, the total amount generated over time is flat and consistent. There are slight variations in the time between ticks that cause this to display inconsistently.
  • Pet aggro radius is working properly and as expected. This is to say, it was extremely inconsistent in original WoW, and it remains inconsistent in WoW Classic.
  • Pets “remember” targets that they have been instructed to attack previously and when sending a pet to attack a different target, the pet will return to attack any remaining targets they were previously instructed to attack when the currently engaged target dies.
  • Pets that have been instructed to attack dead targets with a special ability or attack will attempt to approach and attack the dead target, but will return to the hunter’s side when the ability fails.
  • Other players do not see a Hunter’s quiver on their back.
  • Hunters can sometimes experience a slight delay before recasting Auto Shot after moving.
    • Note: There is a hidden “retry” timer that occurs if the hunter is moving when the normal swing timer finishes. This timer checks for hunter movement before trying to resume auto shot, and this timer refreshes every 500ms when the hunter is moving. This means that if a Hunter is moving and stops moving just after this timer refreshes, you need to wait until the retry timer checks again to validate that you are no longer moving and can resume casting auto shot. This is not a result of spell batching or server heartbeats, and is specific to the functionality of a Hunter’s Auto Shot. This is consistent with Auto Shot functionality on the Reference client.

We appreciate all of your feedback!

The list is sure to grow once the game is released, so we're looking forward to seeing what other problems aren't really real problems but intended problems!

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
      Queue times return to some WoW Classic realms with a high population amid the coronavirus lockdown and character transfers. Firemaw (EU) players report 3-4 hour queue times on a Sunday, urging Blizzard to lock the realm and a similar situation is occurring on Incendius (US).
      Redditor ANTRagnarok came up with a graph while waiting in the queue and it turns out you must log in at 4:45 p.m. if you want to make it to the raid that begins at 7:30 p.m.

      Players are urging Blizzard to lock Firemaw (EU) on the official forums and offer free character transfers, as many do not want to transfer to different realms using the paid character service.
      The situation was apparently worse the day before with queues exceeding 3,000 players which resulted in 5-6 hour queue times. Redditor Aoussar123 reports that people are idling in cities hitting the space bar every once in a while to stay logged in which makes things even worse.

      Incendius (US) is facing a similar situation, but the queues aren't as bad as in Europe. The realm was beyond capacity full even before paid character services, then came transfers from Faerlina, Skeram, and other realms, rendering Indencius beyond unplayable according to Redditors. Players reported 2-3 hour queue times on Incendius during raid time.
      Blizzard has so far not responded to any of the reports and we will keep you updated should they come up with any solutions in the near future.
    • By Stan
      UPDATE: The issue has now been resolved.
      Blizzard (Source)
      The aforementioned fix was completed with restarts at 6:00 a.m. AEDT, and the Battleground Holiday has been operating as expected on Oceanic realms since then. The first Battleground Holiday has been delayed in Oceania due to a bug. Blizzard is currently working on a fix that may require Classic realm restarts.
      Blizzard (Source)
      The first Battleground Holiday should have gotten underway on Oceanic realms at 12:01 a.m. AEDT (about 4.5 hours ago). That has not yet happened, due to a bug.
      We’re working on a fix, and the fix may require realm restarts of Oceanic Realms, which we would undertake very soon if necessary.
      We apologize for the delay.
    • By Stan
      Blizzard today announced they suspended numerous WoW Classic players that were found to be using anti-AFK cheats or bots that automated movement, mainly in Alterac Valley.
      Anything that degrades the gaming experience for other players will result in harsh penalties, according to Blizzard, and they will continue to issue suspensions based on player reports, so if you see someone circumvent AFK rules, make sure to report them!
      Blizzard (Source)
      Yesterday, we issued numerous suspensions to WoW accounts that were found to be violating our Code of Conduct. Affected players were e-mailed with details about the violation and suspension – a great many of which were found to be using anti-AFK cheats or bots that automate movement, especially in Alterac Valley.
      This was the most-recent in a series of similar actions we’ve taken to address unfair gameplay in WoW Classic.
      Please be reminded that using third-party programs to automate any facet of the game, exploiting bugs, or engaging in any activity that grants an unfair advantage is considered cheating. Exploiting other players is an equally serious offense. Scamming, account sharing, win-trading, and anything else that may degrade the gaming experience for other players will receive harsh penalties.
      We’ll continue to monitor reports of and take actions against players who circumvent AFK rules. If you come across a player violating the Code of Conduct policies, please report them.
      Thank you.
    • By Stan
      Blizzard has just posted patch notes for the latest WoW Classic update which includes Arathi Basin, two new factions, Stranglethorn Fishing Extravaganza, Battleground Holidays, and various bug fixes.
      Blizzard (Source)
      Features
      Arathi Basin
      Join the League of Arathor or the Forsaken Defilers as they battle for precious resources. Pitting 15 members of each faction against each other, the race is on to be the first to 2000 resources, capturing strategic landmarks around the Basin to increase your team’s gain and cripple the enemy. There’s never been a better time to join the war.
      Arathi Basin will unlock at 3:00 p.m. PDT (6:00 p.m. EDT) on Wednesday, March 11.
      Battleground Holidays
      Most weeks, Warsong Gulch, Alterac Valley, and Arathi Basin now enjoy holidays that begin on Thursday night at midnight and continue until Tuesday morning. During a holiday, emissaries from that Battleground will be found in the major cities, and honor/faction rewards for performing objectives in that Battleground are increased.
      Bug Fixes and Updates
      There is now a warning dialogue when players enter a raid that has an active raid lockout, giving players the chance to avoid accidental raid saves. Harvesting gathering nodes that are on zone boundaries should now be more reliable. Many particle effects and transparency effects now display more accurately. For example: Thunderfury, Blessed Blade of the Windseeker will appear brighter than before. Perdition’s Blade will appear brighter than before. Particle effects on the Warlock and Paladin class mounts will be less pronounced than before. Fixed an issue that could cause Nefarian to momentarily fly away after revealing his true from at the beginning of Phase 2 of his encounter. Players who are Honorless Targets are now immune to Mind Control. Hunter Player-controlled pets now move in a straight line to their target when commanded to attack, rather than defaulting to behind the target. Shaman Mana Tide Totem should now reliably deliver a fourth tick of Mana Tide. Warlock Blood Pact is no longer re-cast when Amplify Curse is used or Nightfall procs.
    • By Starym
      With Arathi Basin arriving tomorrow to WoW Classic, we have prepared guides for the battleground itself, as well as the two accompanying reputations. Check out all the details of Classic's third BG, its layout and optimal class compositions, as well as the specific roles the individual classes can (optimally) play in a fight, several popular strategies and more in our core AB guide.
      Then, dive in further as we take a look at both the Alliance and Horde's related reputation factions for Arathi Basin, and showcase what the best way to gain reputation with the Defilers and League of Arathor, as well as all their related rewards.

      Arathi Basin Guide
      Defilers Reputation Guide
      League of Arathor Reputation Guide
×
×
  • Create New...