01-17-2005, 07:32 PM
The basic bug is that if there exists +min or +max on a non-weapon item and you attempt to add %ed by socketing a jewel (or presumably a rune - ie Ohm - haven't actually tested that) then the %ed will not apply to the pre-existing +damage bound (ie if there is existing +max it will only add %ed to minimum damage, if there is +min it will only add %ed to max, and if there is both +min and +max it won't add to either).
Weapons are not affected by this at all.
It happens both in the char screen and in actual play.
Unfortunately, when a jewel with both %ed and +min or +max is socketed, the game adds the +min/max first, then when it goes to add the %ed it hits the bug. This is the most obvious way to run into the bug. However, you can also see it by socketing +max first and then %ed, and also not see it by socketing %ed and then +max (that works fine - +max won't cancel existing %ed, it will just bug any future %ed added).
Weapons are not affected by this at all.
It happens both in the char screen and in actual play.
Unfortunately, when a jewel with both %ed and +min or +max is socketed, the game adds the +min/max first, then when it goes to add the %ed it hits the bug. This is the most obvious way to run into the bug. However, you can also see it by socketing +max first and then %ed, and also not see it by socketing %ed and then +max (that works fine - +max won't cancel existing %ed, it will just bug any future %ed added).
"Thank you. We always have a shortage of unfounded opinions, so this will really help us. " - adeyke