@@bananajoe275 Of course it's bugs. But it's the kind of bugs where they multiply by 25 instead of adding 25. Or like on a previous patch where Crypto was randomizing on the wrong range of numbers (it could be 1 more than was supposed to be possible). It has to make you wonder if they do any QA at all on their code, how they manage their code base, and whether the quick turn around of constant massive patches is something they can actually keep up without working themselves to a breaking point.
In this instance its one "x" instead of one "+" which isnt too unreasonable to see, and according to chat Diamond works as intended. Crypto I struggle to understand how that one worked Im assuming it was very similar, I dont know the symbology but it would be a list inclusive instead of a list exclusive. There are quite a few bugs though yeah. I think theyll be fine, is alot ALOT of unique items and unique interactions. Hell of alot better then like hearthstone which has has the same bugs for years and muti-millions has been put into that.
@justnobody5527 True, it just shows a lack of care. Whether that's from too much time crunch (my assumption) or because they just don't know what they're doing is just speculation. For the plus/multiply issue, it working right on Diamond is even more insane. Why does different rarities have entirely different code for behavior? Why would you program something that way? It's insane to think about. As for the Crypto thing, my theory is that they fixed it one way by adjusting the randomization value range (because it would never get to the max value is was meant to have) and then fixed it AGAIN by just adding one to the randomized value, so they made the issue just go from 'not enough' to 'too much'. This could be a single person just forgetting they fixed it already, or their dev team doesn't communicate changes and multiple people attempted to solve the same problem (which is more likely).
![[The Bazaar] My Most Toxic Pyg Run](http://i.ytimg.com/vi/oF6RC7nyC7k/mqdefault.jpg)
![[The Bazaar] My Most Toxic Pyg Run](/img/tr.png)
![[The Bazaar] The Super Syrup Tech Is Still So Strong](http://i.ytimg.com/vi/WbPHLxBsfLw/mqdefault.jpg)
![[LIVE] : ONE ลุมพินี 96 | คู่เอก "คมอาวุธ vs พันฤทธิ์"](http://i.ytimg.com/vi/ofERaO0gOsE/mqdefault.jpg)
As soon as I manage to stop laughing, I will condemn this shameful, reckless behaviour.
Hey look im one of those cringe people. I commented first!
The consistent inability for the devs of this game to get basic math correct makes me really worry. Are they okay?
I don't think they get math wrong, it's "just" a lot of bugs I think
@@bananajoe275 Of course it's bugs. But it's the kind of bugs where they multiply by 25 instead of adding 25. Or like on a previous patch where Crypto was randomizing on the wrong range of numbers (it could be 1 more than was supposed to be possible). It has to make you wonder if they do any QA at all on their code, how they manage their code base, and whether the quick turn around of constant massive patches is something they can actually keep up without working themselves to a breaking point.
In this instance its one "x" instead of one "+" which isnt too unreasonable to see, and according to chat Diamond works as intended. Crypto I struggle to understand how that one worked Im assuming it was very similar, I dont know the symbology but it would be a list inclusive instead of a list exclusive.
There are quite a few bugs though yeah. I think theyll be fine, is alot ALOT of unique items and unique interactions. Hell of alot better then like hearthstone which has has the same bugs for years and muti-millions has been put into that.
The game is in closed beta buddy.
@justnobody5527 True, it just shows a lack of care. Whether that's from too much time crunch (my assumption) or because they just don't know what they're doing is just speculation. For the plus/multiply issue, it working right on Diamond is even more insane. Why does different rarities have entirely different code for behavior? Why would you program something that way? It's insane to think about. As for the Crypto thing, my theory is that they fixed it one way by adjusting the randomization value range (because it would never get to the max value is was meant to have) and then fixed it AGAIN by just adding one to the randomized value, so they made the issue just go from 'not enough' to 'too much'. This could be a single person just forgetting they fixed it already, or their dev team doesn't communicate changes and multiple people attempted to solve the same problem (which is more likely).