World of Warcraft News and Raiding Strategies

The following changes are now live:

• When a character makes any hostile action against an opposing faction Lieutenant (e.g. Keepers of the Grove, Blademasters) or faction leader in the various objective areas, they will receive reputation when that enemy dies.
  
  • It must be an offensive action (harmful spell, harmful ability, melee attack, or ranged attack) against an enemy to receive reputation.
    
    • This also affects Healers who must use an offensive actions against the Lieutenant or faction leader.
• Characters will receive reputation even if they are dead or no longer nearby as long as they are still in the zone when the enemy dies.
• Characters will receive 200 reputation for killing a Lieutenant and all members of the winning faction will receive 200 reputation when the faction leader dies.
• The winning team will also receive 100 reputation per friendly Lieutenant remaining.
  
  • Example: If there are two Lieutenants alive when the battle is won, a character will gain 200 reputation plus whatever was earned from defeating objectives plus the 200 reputation from killing the enemy faction leader (assuming the character used an offensive action against the faction leader).
• The Trainee’s Sentinel Nightsaber and Trainee’s Outrider Wolf now require Friendly reputation with the Silverwing Sentinels and Warsong Outriders respectively (was Honored).
• Players now have 60 minutes to complete the Ashenvale PvP event (was 30 minutes).

The Battle.net Authenticator is now available within the Battle.net Mobile App. The Battle.net Authenticator provides two-factor authentication to keep your Battle.net Account secure. All users must migrate their Battle.net Authenticator to the Battle.net Mobile App by January 5, 2024, as the old Authenticator App will be retired at this time.

Migrating An Authenticator

If you currently have your Battle.net Authenticator in the Battle.net Authenticator App, you should migrate to the new Battle.net Mobile App now! Once you migrate to the new app you should remove the legacy Authenticator app from your device as the codes will no longer be usable. When migration becomes required on January 5, 2024, users who have not yet migrated will have their old Authenticator removed from their account and will receive a password reset to their registered email inbox. Until the Authenticator is active in the Battle.net Mobile App, users will lose access to the perks associated with having an Authenticator on their account such as the Corehound pet, extra bag slots, and access to LFG features.

Managing An Authenticator

If you have never used an Authenticator, or had an old Authenticator, additional details and information on installing and setting up your Authenticator in the Battle.net Mobile App can be found on our support article, Battle.net Authenticator. If you need to remove an old Authenticator from your account, follow the prompts here to remove your Authenticator temporarily.

Can't Access My Account

If you are unable to access your account at all, follow the steps here to recover your account credentials.

If you no longer know the password to your account, it can be reset by following the steps on our support article, Forgot Password.

FAQ

Can I use the same Authenticator Serial Number to secure more than one Battle.net Account?

The Battle.net Authenticator requires a phone number be attached to an account, and a phone number can only be attached to a single Battle.net Account.

Can I set up the same Authenticator Serial Number in more than one smartphone?

Your unique Authenticator is tied to your mobile device and we do not support setting up the same Serial Number on more than one device.

I don't have a mobile phone number

A mobile phone number is required to set up and use the Battle.net Authenticator. If you are unable to access your previous Authenticator contact support.

I'm not receiving the text message during setup

Battle.net Phone Notifications are designed for text-enabled mobile phones. Messaging apps like iMessage (iOS) or WhatsApp (iOS, Android) are not supported. Phone notifications cannot be used with Voice over IP (VoIP), and VoIP numbers that are transferred to a local provider are not eligible for the service.

I have a physical Authenticator. Can I still set up an authenticator in the Battle.net Mobile App?

Before you can attach the mobile Battle.net Authenticator you will need to remove the physical authenticator from your account.

Dungeons

• Throne of the Tides
  
  • Updated the model used by the Ink of Ozumat to reduce the visual effects at its base.
    
• Amirdrassil, the Dream’s Hope
  
  • Smolderon
    
    • Fixed an issue where players would sometimes gain multiple stacks of Ignited Essence from 1 Living Flame.
      
    • Fixed an issue where a Seeking Inferno could explode twice on Mythic difficulty.
      
  • Tindral Sageswift
    
    • Fallen Feathers now spawn 6 feathers on Mythic Difficulty (was 4).
      

Items

• Fixed an issue that caused the Large Renown bag of Dragon Isles Supplies to always unintentionally contain a Dream Wardens Tabard.
  
• Fixed an issue that could cause Gift of Urctos to fail to grant its bonuses.

Quests

• Fixed an issue preventing “Something Different” from being properly completed by PvP Brawls.
  
• Fixed an issue causing a Hunt choice to be unintentionally greyed out for “Aiding the Accord: The Hunt is On”.

Season of Discovery

• Grizzby will no longer rob you of your extra quest items.
  
• Ashenvale PvP
  
  • The lieutenant and general NPCs in the Season of Discovery Ashenvale PvP event now have much higher health.
    
  • Generals are now immune to damage until all of their lieutenants have been defeated.
    
  • While no lieutenants are dead, generals and their nearby allies gain 1000% increased damage.
    
  • The Horde general's chain lightning will now hit up to 40 targets.
    

With a hotfix that we’ll apply to the game soon:

Tindral Sageswift

• Fallen Feathers now spawn 6 feathers (was 4) on Mythic Difficulty.

And as always, this change will be listed later in our Hotfixes Update.