The Ashenvale percentages sitting at 99 for up to an hour while some behind the scenes timer ticks down is just not a functioning mechanism, Blizzard. Seriously.
If you want to put some arbitrary time limit on Ashenvale, fine. You do you. But you need to have the tracking mechanism actually reflect the actual amount of time until the next match. At present, someone just logging in has absolutely no idea if 99% means one minute or 60 until go time.
Perhaps in the future you could show a shred of respect to your players and just do a little play testing first - it wouldn’t have taken much to discover that being forced to watch an arbitrary static number all night isn’t very engaging.
3 Likes
Completely agree, I wasted 45 minutes with the timer frozen at 89% just sitting at zoram with no idea how long I had to wait until the battle started. It’s an insane indefensible change.
1 Like
It’s ok phase 2 in one month. Another broken battleground on the way baby!
Fully agree, atleast give us a timer. I formed a group waited 50 minutes then everyone called it a bug and left. I’m not gonna sit around in ashenvale for an hour guessing when it will start, I’d rather go farm losses to premades in WSG
1 Like
ashenfail, afkvale… err i mean ashenvale should just spawn every hour at the same time. No one actually pvp’s and 98% of the people that need rep just sit at east (alliance side) and people that only need the scroll (since we are max’d rep) go west, kill a grunt/shaman and go back to town waiting to turn in the quest.
They should make it to go to exalted and open up the vendors to actually sell the level 18 weapons (for the level 10-19 twinks) so people will queue a fun tier of warsong.
1 Like
Ashenvale has been a buggy mess from launch and will likely still be a buggy mess at the start of phase 2.
Crazy
I am sorry to the developers that built this but Ashenvale has pretty much been a failure in my eyes.
Just remove the minimum wait time and keep the maximum wait time. Easy change.
It bugged last night… after a kill the % reset to 54%… then 45 min later was at 99%… but it would go off for another hour…
that is the prob… when it bugs and doesn’t go to 0