Jump to content
FORUMS
Sign in to follow this  
Stan

WoW Classic "Not a Bug" List Update: January 7th

Recommended Posts

43633-wow-classic-not-a-bug-list-update-

The Juju Flurry buff works just like Seal of the Crusader in that it increases your Attack Speed, but at the same time, lowers your DPS by the same amount. Blizzard filed a bug for this behavior which wasn't fixed until the Burning Crusade pre-patch, so the current behavior is not a bug.

Blizzard LogoBlizzard (Source)

Ok so the first screenshot is of my character pane showing my MH dps to be 100.6…I took off a piece of gear so that the math would be simple and as close to 100.0 DPS as possible. Now when I use JuJu Flurry which gives you +3% attack speed…that should make my base DPS 103.0 correct?

SORRY but Mod/Blizz employee you will have to delete the Space before dot com I don’t know why I couldn’t include my example screenshot. Also is this the place to report a bug?

ZcJW4RR.png

here is the first screenshot of 100.6 dps.

Now below I will post a screenshot of juju flurry being used. As you can see the dps DOES NOT MOVE from 100.6 to 103.6…all that changes it the weapon attack speed AND IN FACT…THE ACTUAL DAMAGE OF THE WEAPON GOES DOWN AND IS NERFED AS WELL? So why would something thats supposed to be a BUFF actually hurt your damage?

G5odVe9.jpg

Below is a BEFORE & AFTER example of how I start with 100.0 DPS and use Slice and Dice (+30% Attack Speed) and you will see how I go to 130.0 DPS which is CORRECT.

G5odVe9.jpg

YcH4nBB.png

Hi All,

Wanted to chime in and mention that the Juju Flurry buff is currently matching the behavior exhibited in the 1.12 reference client. As others in this thread have correctly guessed at, Juju Flurry behaves similarly to Seal of the Crusader in that it increases your attack speed but also lowers your DPS by the same amount.

We also did some digging into our bug database from the Original WoW era and found that we had in fact filed a bug for this behavior while the original game was current, but the issue was not actually fixed until the Burning Crusade pre-patch (patch 2.0.3). As this bug was present throughout Original WoW, we do not currently consider it to be a bug and is merely an aspect of the original game that was carried over into Classic.

We will update the Not-A-Bug list with this information shortly. Thank you!

Below is the current list of all misconceptions that are working as intended in WoW Classic.

Blizzard LogoBlizzard (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.
  • Non-targeted, group, or AoE buffs will not affect party or raid members if you are flagged for pvp and your party or raid members are not flagged for pvp, or vice-versa.
  • It is much easier to not get quest credit for escort quest objectives in WoW Classic than in Battle for Azeroth. Follow your NPC allies closely to ensure quest credit is obtained!
  • Monsters will respawn more aggressively when reduced past certain thresholds of their original populations in many areas of the game. This is working correctly and is consistent with the reference client.
  • Offhand attacks that occur while on-next-hit abilities such as Heroic Strike are queued do not suffer the dual wield to-hit penalty.
  • Eternal Quintessence is not yet available to players and will arrive in a future phase.
  • Stuns from procs such as Improved Revenge and Improved Concussive Shot do not diminish and are not diminished by Controlled Stun abilities such as Hammer of Justice and Kidney Shot.
  • Various Plans and Recipes from the Thorium Brotherhood are not available until later phases.
  • Practice Dummies in the Undercity cannot be attacked. There are no “Training Dummies” in WoW Classic.
  • Overpower procs will be lost if the Warrior changes targets away from the target that dodged.
  • The Eye of Shadow has a higher drop rate than many players expect.
    • Note: This was changed late in Original WoW to have a much higher drop rate.
  • The objective of the quest “Touch of Zanzil” will fail if the player is not targeting Doc Mixilpizil when they /lay command is used.
  • A summoned Infernal that is no longer under the control of the Warlock will only affect PvP flagged targets and targets that are on its threat table and will quickly despawn when no viable targets are available.
  • Some monsters have a “Thrash” mechanic and can proc multiple attacks against players in a very short duration.
    • Note: Most of these monsters can also “store” these procs and unleash them all several seconds later. An example of this is the Princess Theradras encounter in Maraudon. The Princess will store her attacks if kited and can land several attacks instantly when she catches up to her target. This behavior is consistent with the reference client
  • Righteous Fury grants additional threat on all holy abilities, not just attacks.
  • Sharpening stones have “hidden” level requirements and higher level stones cannot be used on lower level weapons.
  • The Juju Flurry buff increases attack speed but also lowers overall DPS by the same amount.

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.
    • NoteThere 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.
  • 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.

We appreciate all of your feedback!

Related Classic News

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 Starym
      We've already seen the Alliance take down the deep breath queen with only 3 players, now it's time for the Horde to have some fun as well! It seems around 40-50 minutes is the sweetspot for downing Onyxia with 3 players, as all the kills took about that long. The Horde compositions are set for all three videos, as Warrior, Shaman, Hunter is the go-to for 3-manning the dragon lady, which is the faction swapped equivalent of the Alliance kill we covered, which just had Paladin instead. If you want to see further humiliation for basically WoW's first raid boss, you can check out 33 druids killing her, 33 hunters taking under a minute to down her or even naked raids taking her down.
      So let's take a look at 3 videos of 3-man Onyxia!

      The last one is also the most recent, and the title is misleading as it is not the Horde first kill, but it's still impressive!
      Source.
    • By Starym
      Update: the exploit has been hotfixed, as Blizzard announced in the August 28th notes.

      We have a new and major exploit in WoW Classic, which is allowing Mages to have a permanent 100% critical strike stat for as long as they don't die or log out. We're not going to get into the specifics of how to do this, except to say it involves the Combustion talent, which can be stacked up to 10 times for a 100% crit boost, even though it's more likely to be at 5-8 stacks, which is still plenty and can get you to a whole lot of crit.
      Blizzard will hopefully soon be made aware of this issue, as it's already been reported both on the forums and reddit, so a fix should appear quickly. While we won't link to the related threads to not spread the exploit, we will show you the results of it, in a rather painful Warsong Gulch match, as a Mage with 10 stacks runs amok. Warning for quite loud meme sounds.
      Hopefully this post helps bring this matter to Blizzard's attention, and if you manage to dig up the exploit on your own, don't use it - not only is it unfair and clearly not intended, but there might be bans for players abusing it as well.
    • By Stan
      We're looking at a player who soloed Hogger in WoW Classic at Level 1 without dying. It took them 19 minutes and 22 seconds to do so! 
      Here is the VoD with Hogger at ~5% health left, so you can watch how the infamous Level 11 Elite gnoll got down!

      (Source)
      News image source: Marta Nael via ArtStation.
    • By BluePosts
      In a very weird/troll-y forum post named "What bots/hacks are allowed?" where a user asked which of the hacks and botting software is allowed because they keep seeing flying and botting players around, report them and nothing happenes, Blizzard actually responded and gave us some useful information to boot! Apparently the daily number of botting accounts being actioned (no specifics on the amount of time suspended) is in the thousands, as community manager Kaivax clarified:
      Bots (source)
      No hacks or cheats are allowed.
      Our anti-cheat team takes action against botters and hackers 24/7, and every time I’ve asked them “how many botters were actioned yesterday?”, the number is always in the thousands. That’s a global number, by the way.
      Our anti-cheat team focuses on popular botting spots, especially areas that are commonly reported by players. For example, Dire Maul has been one such area for cheaters, so a lot of attention from my colleagues has been put on Dire Maul recently.
      Please be encouraged to keep using the in-game reporting system for cheat/hack reports. Those complement our systems that automatically look for the ever-changing strategies and software that the botters are using, and reports really help us zero in on new hacks more quickly than we would have without them.
      Thank you!
    • By Starym
      Here comes a short hotfix batch for classic, with 1 bug featuring Ossirian's reset being fixed!
      September 14 (source)
      WoW Classic
      Ruins of Ahn’Qiraj Fixed an issue that caused Ossirian the Unscarred to not reset correctly when quickly engaging back into combat.
×
×
  • Create New...