Since this is clearly a limitation for bots can we please get someway to bypass this as a legitimate player. Like maybe account authentication can remove the 30 cap on players? While this helps a bit…I only want to farm Blade of Eternal Darkness on one character.
6 Likes
Well that’s a nice change overall but it really seems silly this 30/24hr even got used.
I understand the attempt to slow down bots but it’s not really that effective from what I have seen.
Can we change it to a 210/week for the “weekend warriors” it would still be 30/day just putting 7 days together. This would also make setting a tracker system for players to see their instances used much more effective and simpler as it would be a weekly reset like raids so setting a tracker UI would be easier and less conveluted with the 24 hr tracker having to keep track of start times of every instance used.
Just a bit of advise to simplify a possible tracker system and make it easy to put into a UI.
3 Likes
I play on a locked realm where most of the bots are gone.
That means banned bots cannot join this server anymore.
Why would I be affected by this restriction?
If we’re all legitimate players on these realms now, we shouldn’t be targeted by that.
RIP all those arguments claiming the change was made to stop boosting.
2 Likes
Because by “take action” they mean banning. You’re confusing “take action “ with “affect.”
Now, if we could just get the quest chain for Seal of Wrynn to work…
Thousands of people watching the thread, waiting for a response, since… Sept? Wow.
2 Likes
As a hunter main I really agree with this. The strength of a hunter in PVP is not the raw output, it’s the utility and the team’s ability to utilize a hunter. They’re still the weakest PVP class because of their deadzone and range restrictions, but they can be incredibly deadly when their team utilizes their kit and doesn’t just tell them ‘shoot the healers from the back’.
We are all waiting with breath that is bated. I do recommend, everyone submitting a ticket and a bug report for Infiltrating the Castle. This is still ongoing.
2 Likes
July 22, 2020
WoW Classic
- On a realm that is currently layered, turning in Head of Onyxia, Head of Nefarian, or Heart of Hakkar will now start the event dialogue for each layer in which the NPC is currently alive.
4 Likes
if im on a layered realm and the head of onyxia is turned in on layer 1, both layer will get the buff but both layer will have their cooldown reseted?
What about the rend buff?
What about Rend head though? This is the exact same issue for horde players who end up on the wrong layer when a Warchief’s Blessing goes out.
I’ve added the Head of Rend Blackhand to the note. It was a subject of this fix.
1 Like
How does this play with the cooldowns. Will a drop on one layer trigger the cooldown on the other or are cooldowns entirely unimpacted?
3 Likes
It sounds like announcing a buff is dropping, but not specifying the layer. Please correct me if I am wrong.
ony head just dropped on my server and only people on 1 of 2 layers got buffs !?
If you killed a NPC on either layer the NPC’s get out of sync and the buff no longer drops n both layer, basically breaking this implementation. You need to make it start the event on both layers even if the NPC isn’t reset on the other layer, NPC’s are out of sync on every server atm also until server restart. Basically the buff won’t drop on both layers any time the NPC’s are out of sync and it will stay broken for the whole week until server restart in most cases, all it takes is one NPC kill during the week and it’s out of sync until the realm manages to not drop any heads for hours on both layers.
Edit: This has been tested already btw, it’s not just a guess.
7 Likes
Just purge all the world buffs when we zone into a raid, the whole thing leads to such degenerate behavior.
2 Likes
Remove layering
Remove cd’s on world buffs that have a cd (Ony/nef/rend) etc.
This isn’t hard concepts
Open the transfer PLZZZZ
1 Like