it's a fail-safe so you don't salvage rares that you are already wearing or might actually wear (such as 50CHD, 6CC, 7CDR, socket- rings)
If you are wearing them, it does not disenchant. If you intend to wear them, you better put it into the stash.
This fail-safe "feature" has me manually disenchant rares after every bounty, while i never in my 3 years of D3 have disenchantet a rare I did not want to.
This feature makes more work for everybody just so that some clumsy klotz does not accidentaly disenchant his stuff. I am all for teaching the klumsy klotz a lesson while making less work for everybody with a normally functioning mind.
This is NOT a bug. The reason that these rares do not smash is because they are account bound. Just like anything you enchant, these items are not intended to be auto smashed. When you auto smash, it will also not smash anything you have equipped or have a gem socketed into.
This is one of those issues that is barely worth the time it would take to fix it, if at all. We're talking a few button clicks max, only every so often when you do caches. I'm all for cleaning up oddball issues like this, but I can fully understand why this issue is well on the back burner.
This is NOT a bug. The reason that these rares do not smash is because they are account bound. Just like anything you enchant, these items are not intended to be auto smashed. When you auto smash, it will also not smash anything you have equipped or have a gem socketed into.
I think the bug is that the rares from caches are account bound. They should not be spawning as such.
And now i am begging for you guys to "like" it ^^
Its no whining, and only a small request that is totally constructive and easy to understand.
Text : "Please make it so that "salvage all rares" actually salvages all rares."
http://eu.battle.net/d3/en/forum/topic/13987100488#1
http://eu.battle.net/d3/en/profile/Twoflower-2131/hero/47336841
it's a fail-safe so you don't salvage rares that you are already wearing or might actually wear (such as 50CHD, 6CC, 7CDR, socket- rings)
I think not salvaging rares from caches is a bug though.
If you are wearing them, it does not disenchant. If you intend to wear them, you better put it into the stash.
This fail-safe "feature" has me manually disenchant rares after every bounty, while i never in my 3 years of D3 have disenchantet a rare I did not want to.
This feature makes more work for everybody just so that some clumsy klotz does not accidentaly disenchant his stuff. I am all for teaching the klumsy klotz a lesson while making less work for everybody with a normally functioning mind.
http://eu.battle.net/d3/en/profile/Twoflower-2131/hero/47336841
This is a bug:
http://us.battle.net/d3/en/forum/topic/14579398118#10
It seems you can't expect them to fix a bug like this after 6 months...
iirc 2.2 fixes that, or a future hotfix
This is NOT a bug. The reason that these rares do not smash is because they are account bound. Just like anything you enchant, these items are not intended to be auto smashed. When you auto smash, it will also not smash anything you have equipped or have a gem socketed into.
The why do they check if the item is account bound instead of checking if it was enchanted/socketed?
This is one of those issues that is barely worth the time it would take to fix it, if at all. We're talking a few button clicks max, only every so often when you do caches. I'm all for cleaning up oddball issues like this, but I can fully understand why this issue is well on the back burner.
BurningRope#1322 (US~HC) Request an invite to the official (NA) <dfans> Clan
I think the bug is that the rares from caches are account bound. They should not be spawning as such.
BurningRope#1322 (US~HC) Request an invite to the official (NA) <dfans> Clan