You are mistaken
Pazorax does not get to pick choose nor decide.
All he can do is take the info, smartly issue a word of caution since he is not the one that would make any such decision, and then pass the info along.
The devs would look at it and decide what, IF anything at all, were to be done in regards to it.
They pick choose and decide based on an issues merits and what impact it does, or does not have, in the game here now and today.
Pazorax does not decide any of that, he is just a liaison.
No point in chasing him for torches and pitchforks.
Look at the Ony reset bug?
Devs looked, yep exists in vanilla
Ok, we will watch in case it somehow bizarrely screws up the game, otherwise not touching it at this time.
But stop with abusing the priest killers, they are playing as intended.
Why punish players when Classicâs spell batchingâwhich Activison has refused to fixâstraight up created this, and this potential event existed for far longer than Vanilla?
I traded librams in vanilla.
They are soulbound, but if you poked an item in trade quick, i could cast the libram on it and hit trade and POOF, you got libramed
For everyone pointing out the character that has it, the reason why is grandfathering. After Blizzard took notice of the situation during the course of retail (whatever point that maybe), they since prevented more characters from doing that behavior. Itâs the whole inspiration of the âexploit early, exploit oftenâ mantra that has come up in the community. Blizzard has shown a tendency to just shut the door on future degenerative behavior only, while not touching prior undesirable behavior. Not to mention, no filter/fish net is perfect. Characters we see now having such things on their characters may have been lucky enough to escape checks done in the past.
As an example for in retail. There was an experience potion stacking oversight that happened in early 2019 (it also was a power exploit because the potions gave stats). People who utilized the potions in an unintended way were banned, however their characters were not reverted. All subsequent uses of the potion were locked to operate in the intended way, thus preventing future exploiting.
The latter part of the blue post, is them forewarning the community that they will be having a decision about this come Monday. Anyone who does enchants past the notification of this blue post (maybe a few hours earlier, or all enchants) will be noticed and have them stricken from characters. OR said characters will be allowed to have said enchants, and any characters beyond the hotfix will not be able to have such enchants.
Just because something exists doesnât warrant it to last forever.
You can use librams through the trade window normally and always have been able to. No quick casting required. I used to buy head/leg enchants from a rogue that does vault runs every time I got a new piece of gear. You can also do it with the Fiery Blaze Enchantment that alliance gets from a badlands(?) quest.
And here, even though they wonât use the ranged attack power stat, DPS Warriors and Rogues might prefer the Hunter enchants if they need the +Hit, otherwise the Rogue one is better than a +8 stat from a Libram of Voracity.
Please Pazorax can you fix the shadow oil bug. There is a 10 second internal cooldown on the item when there shouldnt be. Players are going nuts over it.
The item shadow oil has a 10 second internal cd and frost oil doesnt. The most confusing thing about the Shadow Oil thing is that Frost Oil has no internal cooldown, and Blizzard hasnât officially put it on the ânot a bugâ list.
Threads have been made about it and for months we have no answers.
I donât want to patch pre existing bugs but I also donât want them to work in new ways that would change itemisation in ways that wasnât possible in vanilla.
