Simple coding error. The person putting the antivenin values simply dropped 15 instead of 1.15.
I guess the question then is, why in the world would they be touching the values of a potion that hasnât been utilized in several seasons ?
Perhaps theyâre hired a chimp who is just furiously mashing the keyboard to take on some of the additional workload. It WOULD explain a lot recently.
Ano[quote=âSalvus-1893, post:24, topic:207423, full:trueâ]
I guess the question then is, why in the world would they be touching the values of a potion that hasnât been utilized in several seasons ?
Perhaps theyâre hired a chimp who is just furiously mashing the keyboard to take on some of the additional workload. It WOULD explain a lot recently.
[/quote]
Just another push to sell the expansion. If you want a super OP class, buy the expansion now so you can be powerful too.
If it was that simple I donât see why it wouldnât be fixed immediately, no idea why they would be messing with those values either since no patch notes said anything about them changing.
Actually fixing the code probably only took a few seconds. Finding out about it, getting the fix through regression testing and probably a CD pipeline process likely took most of the time.
Funny how many people comment on how easy it should be to fix bugs in games with 0 clue how they are built/fixed/deployed
Also it is entirely possible that it was a change to another system that this older item needed to be updated to work correctly with but was missed. not necessarily a change to this item to break it.
I.e. an older version of a fuction() that applied potion buffs wanted a percent passed in as a parameter, the potion object had 15 as the value for the old system, then they system was changed to want a multiplier and this item was missed in the item update.
They knew about the bug 30mins after the patch⌠We all did ⌠It was found for them and they still couldnât do a quick fix, it is amazing the amount of people that think coding is just so complicated when itâs not at all if you know the language. But that sentiment is used alot by people who have never coded before
i have been coding since 1985 
It often takes WAY longer to get code deployed in modern deployment systems that it does to make the actual code change
Weâve seen them deploy fixes in hours already⌠Whatâs your next excuse?
No inside info so canât say for sure, also Iâm not making excuses I am simply presenting possibilities based on knowledge of software development practices.
Iâm more concerned about how this made it to live than how long the fix took to get live though 
In all reality the value likely wasnât even in code, since most games now use item edit tools that are part of their engine. I only expressed it as code to demonstrate how easy it would be for this error to happen.
1 Like
I will agree there, itâs weird these values were altered at all
It may well be an error of omission though. like if the old system needed a percent (15) and the new system uses multipliers (.15)
If this item did not get updated it would lead to the same situation
1 Like
Rofl, what the hell does Y2K have to do with anything?
âJust a couple of programming errorsâ
Obviously its a programming error you simpleton, but they could of TESTED the damn thing before releasing it to LIVE, they would of found that error FAST.
and WTF does this even mean?
âThink OP never have spelling error in his office when wrote email, and make it like the world will end next week.â
Hey Wang, learn english before posting on here.