Sandstorm less sandstorm-y

[Jerebear]

With Sandstorm bugged, do folks have a workaround for the Flowing and Whispering fights? Even level 15+ carry pets are dieing to the aoe damage the spirit teams put out. Any suggestions welcome!!

The teams listed in our WCP site guide work still and are more efficient than the Anub strats for Aki, Flowing, and Whispering:
http://www.warcraftpets.com/community/f ... =10&t=7556

I actually use a modified one for the Flowing:

Flowing Pandaren Spirit - Location: Dread Wastes (61, 87)
Team 2: 15 rounds

• 1: [pet]Wildhammer Gryphon Hatchling[/pet] [4-P/P] (1,2,2)
  2: Carry pet (needs 700+ health, non-elemental type)
  3: [pet]Blackfuse Bombling[/pet] [-] (2,1,1)
  *any pet with explode (minfernal, pet bombling, etc.) just make sure it explodes for enough.
  
  vs Marley
  • - Peck x2 > Lift Off > Peck until Marley dies
  vs Tiptoe
  • - Peck > Adrenaline Rush > Peck until Tiptoe dies
  vs Pandaren Water Spirit
  • - Peck > Adrenaline Rush > Peck until Wildhammer Gryphon Hatchling Dies (should be due to Whirlpool/Geyser Combo) > Explode

This ensures the minimum amount of tidal waves (2-3 from the Flowing + 0-4 from Tiptoe). If you use Rematch, you can set it to not allow carry pets below a certain health for safety.

[Drudatz]

Seems for me today Blizzard "fixed" this bugged without EVER acknowledging it....

[Jerebear]

TheCrafticus said he was looking into ... maybe a couple weeks ago. If it is fixed, that's awesome.

[Maizing]

With Sandstorm bugged, do folks have a workaround for the Flowing and Whispering fights? Even level 15+ carry pets are dieing to the aoe damage the spirit teams put out. Any suggestions welcome!!

These are the teams I use...

Flowing Spirit:
[pet]Axebeak Hatchling[/pet] 2/1/1
Leveling pet (I only use this team for pets that are at least level 20)
[pet]Emperor Crab[/pet] (or pretty much any good aquatic, use what ever abilities you prefer, I rarely ever need to use this pet)

Start with the Axebeak. Peck until Marley dives, then lift off. Peck & heal (as needed) until the elemental comes out. Switch in the leveling pet. Switch back to the axebeak. Lift off to avoid the big damage. Peck and heal as needed. If the axebeak happens to die, bring in the aquatic to finish.

Whispering Spirit:
Leveling pet (I use one that is at least in the mid teens)
[pet]Sprite Darter Hatchling[/pet] or [pet]Nether Faerie Dragon[/pet] 2/2/1 (these pets are pretty much interchangeable)
[pet]Sprite Darter Hatchling[/pet] or [pet]Nether Faerie Dragon[/pet] 2/2/1

Start with the leveling pet, do one attack, then switch in one of the others. Moonfire first, then arcane blast (alternate as needed to keep the weather up). When you have killed the moth, use life exchange on the dragonkin, then repeat with moonfire and arcane blast until it is dead. (Note: if your first pet dies before killing the moth, I have found that it is best to restart the fight from the beginning. The hardest part of fighting this team is the risk of the moth dust putting your pet to sleep. If that happens too often, the fight tends to go sour.) I generally need to bring in my last pet by the time the elemental comes in.

[Quintessence]

"Sandstorm should be working again (pet battles)." - Twitter

[Drudatz]

"Sandstorm should be working again (pet battles)." - Twitter

Great they ignore the bug thread on the us forum for OVER A WEEK, don't put it on the bug list and 2 days AFTER its fixed they aknowledge it.....ActiBlizz at its best....

[Vek]

Working as in it now provides a shield again or Working as in it actually works with elemental racial and provides a shield again?

[Jerebear]

Working as in it now provides a shield again or Working as in it actually works with elemental racial and provides a shield again?

TheCrafticus indicated that it was completely fixed (or should be), including the racial bug. I haven't tested it yet.

[Kel]

It was listed in the patch notes for last Tuesday's hotfix. So yea, they did "officially" state it. It should be working correctly now.

[Mahri]

It was listed in the patch notes for last Tuesday's hotfix. So yea, they did "officially" state it. It should be working correctly now.

And it is working