They’re not ill-gotten.
mark my words, when the unique table is filled out the current fix will be reverted to how it functioned on the night the shakos dropped.
They were ill-gotten. Their drop rate from the hell-tide chests was multiple orders of magnitude higher than what Blizzard wants it to be.
That’s why in the span of a few hours 142 of them dropped, while in the other entire month since release only 2 had dropped.
That’s why there was an emergency hot-fix to remove them from the chests.
Thats why since they’ve been added back into the chests, not a single one more has dropped.
Loot being given out at a much, much, much, much higher frequency than intended is a bug.
The outcome wasn’t what was desired by Blizzard, every step along the way and every element leading to the outcome was 100% intended. the “fix” breaks intended mechanics because again, everything that forces the unintended result is intended.
If blizzard did some actual work at work none of this would have happened. If sorc and barb launched with possible non uber unique helms this wouldn’t even be a discussion or if blizzard ran a simulator on 100k chest being opened by each class what kind of unique drops and then make adjustments and launch the patch. Blizzard went lazy route patched something in (DID NO INTERNAL TESTING) and people discovered things. Blizzard didn’t like it and then PATCHED it. It’s just lazy. Cosmetic shop season 1 on wards is all they care about.
there was an oversight
So… a bug? By definition any code that does not have the intended effect is a bug.
Lol The fact they didn’t have a unique helm was why the chest was bugged. It automatically defaulted to a super unique if a unique was rolled for those classes. It’s the very definition of a bug and a bug exploit, but cope more.
1 Like
No, GameMaster2D is right.
They are neither ill-gotten, nor bugusing or exploit. They were result of the game mechanic not considered by Blizzard when they activated the unique drop.
Open Head Chest → have luck and get a unique drop roll → “oh you are a barb, the only unique helm is shako” → shako drops.
There are a lot of such oversights from Blizzard in the game. But they choose not to acknowledge they simple overlooked results of there own implemented mechanics.
Nope it was a drop rate bug that was exploited
except for the code literally did everything it was intended to do, nothing more, nothing less. untended consequences aren’t bugs. using a new feature in the intended way isn’t an exploit.
1 Like
They did not intend for you to be able to circumvent the low drop rate of the shako by using this system, it’s absolutely unintended. The code does what it was supposed to do but there was still additional code missing that should have checked if a class actually has a unique for that slot. This again is the definition of a bug, whether you want to argue if it’s good or bad is something else - semantically you are incorrect.
Inside job. It was so controlled, how do you place a bug in and then disable it in 2 hours? Idk blizzard were theses type of guys to get thing done so fast, like shot im still mounting in thin air, tee bagging the air at 100% movement speed. . You ask me theyre just using you and me to fuel the price of those shakos.
It was pretty clearly a bug, not an inside job. They have access to the servers to make emergency patches if necessary, and clearly have access to tweaking droprates. They didn’t fix the bug instantly - in fact the method they used to fix the droprates kind of defeats the purpose of having uniques in helltide chests in the first place.
Well you just said the most important part, they have control over the drop rate, funny how only the most sought out item in the game some how got a normal drop rate for barb, and sorc. Idk if anyone got andys or grandfather, or the other but shako was the main and easiest to put in place.
I target rings for a 4 max roll Umbral ring at the gambler all the time. It’s no different.
And now that it’s fixed, everyone has an opportunity to get Shako from Helltides. It’s just not as targeted anymore. Which frankly, players are skipping over that tidbit as well. Blizzard has made it easier to obtain.
When the patch notes came out, I said the exact thing to myself. “I have zero unique helms, wonder what happens if I do Helltide to target helms”. And I did. But alas, luck was not on my side.
Anyone that understands the game and bothered to read the patch notes should have. So either players don’t understand the game, didn’t read the patch notes, or both.
What’s your point? It makes no sense for blizzard to sabotage their game like this. It makes the players angry, required devs to work overnight, all for what - to make the shako (specifically) slightly less valuable when RMTing? Sorry but with that many shakos out, previously people probably wouldn’t even sell their accounts, now you can bet this is going to make the RMT problem worse. Plus this only applied to the helmets - the only other uber unique that could be target farmed is druids farming amulet chests for the melted heart of selig. No grandfathers, doomblades, etc. could have dropped
The source of a bug doesn’t have to be a coding error in the traditional sense. It can be the result of a gap or deficiency in requirements, a missed use case, etc. In this scenario missed test cases also contributed. I mean, even if none is this makes sense to you, the fact that it was hot-fixed it is a pretty clear indicator.
The shako is a game destroying item, specifically at this lvl. The rest sure but man that plus 4 to all skills…
Why? Why not? The devs deserve to play as gods too, or maybe they just want a little bit of money, idk why, but 142 is a small number and went unoticed for only 2 hours… thats enough for the whole clan. Its small enough number where hey its not that bad but in truth its a god tier item.
It’s a missed use case/unintended consequences. This is a very, very common type of bug. Bugs are usually not from simple coding errors.
Well, according to blizzard…
" In the future, we may need to take action to maintain fairness within the game when a bug or exploit impacts the gameplay of others."
This phrase implies that it actually was a bug or an exploit (or even both)
2 Likes
Why not just use their dev powers to give themselves the shako directly? This is a lot of hoops to jump through to get to the conclusion of this conspiracy