Take the 2-minute tour ×
Arqade is a question and answer site for passionate videogamers on all platforms. It's 100% free, no registration required.

I can't quite figure out the tooltip for a ruby when socketed in a weapon. I have a radiant ruby, which according to the in-game tooltip adds +12-24 damage, but according to the website adds 12 to the minimum damage and 12 to the maximum.

When I socket it in a weapon, it seems to indeed add 12 to each:

Before:

unsocketed

After:

socketed

So why does it show +12-24? Where did that 24 come from? Under what conditions, if any, will that ruby provide anything else instead of +12/+12?

share|improve this question
    
I completely misunderstood this question. I am confused. –  StrixVaria May 23 '12 at 15:04
3  
Technically, "+12" is within the range of "+12 - 24". That'll teach you to trust those sneaky NPC sales pitches! –  Wikwocket May 23 '12 at 15:35
    
@Wikwocket What's funny is, because of the backwards way things are calculated, your snarky comment and Emerica's deleted answer were basically right all along. The reason it's expressed as a range basically boils down to because it's inclusive of all possible results given the wonky way +12 min/+12 max is actually calculated. –  LessPop_MoreFizz Jun 8 '12 at 20:55

2 Answers 2

up vote 24 down vote accepted
+200

Most of this answer refers to the way rubies displayed their effects prior to patch 1.0.3. I've left it intact because while Rubies no longer display a range, the behavior or applying +Minimum Damage before +Maximum Damage persists, and does occasionally cause some weirdness in exactly how much benefit a Ruby and other similar affixes provide.

So, it's actually a lot more complicated than it first appears - it seems that the benefit of the Ruby is actually subject to a couple of bugs regarding how damage bonuses are calculated. The short version is that weapons with narrow damage ranges - which are usually slower, and lower level weapons - tend to receive a slightly larger benefit from rubies. This in turn is what has caused the vast majority of testing, which tends to be done with low level gems on level 15-20 weapons to be so inconclusive - the effect I'm about to describe basically washes out at higher levels. This is because the calculation is... strange.

As an example, let's take a look at this axe, which provides a useful test case because it doesn't have any elemental damage on it. (Elemental damage is handled slightly differently, and more importantly, is applied after the addition of damage from the Ruby, so you need to calculate it back out before evaluating most weapons. Note however that flat +Min/+Max modifiers are applied at the same time as a ruby, and can be simply aggregated).

Axe

As you can see, the ruby brings the axes total damage from 13-22 to 23-34, a bonus of +10-+12. The reason is because when a Ruby is socketed, it works in the form of two separate modifiers, of +10 to minimum and maximum damage. The +minimum is applied first, taking our 13-22 axe up to 23-22 -- BUT since the max can't be lower than the min, we have to bump the minimum up to Min+1, or 24 damage. Then, after this, the +10 Max damage bonus is applied, bringing us to, you guessed it, 23-34.

This effect tends to get washed out on weapons with a large damage range, so it's typically not noticed at higher levels. If you'd like to see more of the math, including how this interacts with elemental damage, % damage modifiers, etc., I'd direct you to this reddit thread.

The takeaway from this, for most players, is that you can evaluate the value of a ruby in most weapons simply by using the lower bound listed as a flat modifier. The only edge case is at very low levels with very slow weapons - a circumstance in which a Ruby is better than all other options no matter what, anyway.

share|improve this answer
    
Though the gems still fail to list the gold combine cost, so they're still not infallible. –  Raven Dreamer May 23 '12 at 15:50
1  
Do you have any proof? Like screenshots or something. –  Betty Jun 4 '12 at 11:56
2  
I did some testing with socketed items of different kinds and got some interesting results that seem to give creedence to the idea that rubies are either broken or by design alter slower weapons differently to faster ones. i.imgur.com/1HFjG.jpg –  Nimphious Jun 8 '12 at 17:46
1  
Fascinating! This also explains why it's always +X-2X - because in the corner case of a weapon with a constant damage, it will indeed be +X to minimum and +2X to maximum. –  Oak Jun 8 '12 at 21:39
1  
@Oak As noted in the Reddit thread linked, Elemental damage works 'intuitively', adding the range as listed (as do bonuses from rings and amulets). It's just that Elemental damage is added after the bonus from the Ruby, so in order to apply this to Nimphious's data, you'll need to subtract the elemental damage modifiers first, then re-add them at the end. –  LessPop_MoreFizz Jun 8 '12 at 21:53

Since the website reads Weapon: +12 Minimum Damage, +12 Maximum Damage, I suspect it is just an incorrect tooltip

Its likely that at one point during testing the gems increased the maximum damage by twice the minimum, however this probably got scaled back and the tooltip never updated

EDIT: This actually isn't correct.

Rubies provide a flat increase to some weapons, for others however, there is a range that is based on weapon speed. See this answer for more details

share|improve this answer
    
Upon some further testing, this actually isn't correct. (See my answer). –  LessPop_MoreFizz May 27 '12 at 3:10

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.