I was crafting some stuff to refill my retainers and...
http://i.imgur.com/3K7gboC.jpg
Anyone saw that before??
Printable View
I was crafting some stuff to refill my retainers and...
http://i.imgur.com/3K7gboC.jpg
Anyone saw that before??
Did your HQ bar actually go down? Or is it just a log error?
I recently hit a 27K Byregot's and my HQ bar worked accordingly but I never read my log.
They will have to fix this before the next expansion then, since it will be easy to get to those numbers with the base end-game 4.0 gears, even if its only on lower level gearsQuote:
Katlyna
Yes this issue was posed some time ago. Apparently there is some kind of limit on the quality increase integer and you can break it. The limit is 2Xk I don't recall the exact number. Rather funny when one does break it ;-)
It is only in the logs that it writes "decrease" instead of "increase". The item gets its quality increase and it ends up as NQ. The Quality doesn't "drop" by 30k one shot.Quote:
ChameleonMS
Did your HQ bar actually go down? Or is it just a log error?
I recently hit a 27K Byregot's and my HQ bar worked accordingly but I never read my log.
Weird thing is that it shows this, its because they planned for quality to "decrease" at one point.
No, it's more likely just due to a subroutine used to display numbers in the log considering anything negative to be a decrease, and anything positive an increase. From the symptoms it looks like some of the code is representing the quality change as a 16-bit signed integer, for which any value that would be greater than 2^15-1 (32767) in an integer with more magnitude bits would be considered a negative number: 32768 => -32768, 32769 => -32767, and so on.
This is a pretty ordinary mistake you see in programming: at some point, someone thought "no quality increase will ever be greater than 32767, so let's use signed 16-bit integers to represent the quality increase in this piece of code - because of PS3 limitations." ;)
Shoulda used unsigned integers. Coulda gone all the way up to 65535 without issues, then!
Then again, Goudaba could be right. After all, the text is there to account for decreases - it didn't say "Quality increases by -30001", it said "Quality decreases by 30001". Perhaps there WAS once plans for a decrease to be possible (for example, on a Poor condition?); it was scrapped, but the code outputting text is still there to account for negative quality progress...
Or maybe the text output code is reused across several types of progress, and so the same code used to report negative values of Durability winds up being used to report negative values of Quality. It's hard to say. Regardless, this is a funny bug - I'm just glad it's only a text log bug, and not a case where your Quality ACTUALLY drops if you manage an overflow...