We may have been using a bugged enchanter for 6 weeks, cutting our chances for most rolls by more than 50%. Most people assume there are weighted affixes, but there are no weights in the game files. It feels like weights, and is due to something else.
Certain stats may have an unintentional value that acts as a ‘forced roll’ flag, attached to them in the game data. This results in us always seeing these stats, if available when we enchant a piece of gear. Crit chance and attack speed on gloves, crit chance on rings, among others.
There seem to be no affix weights in the game files. The behavior of the enchanter is basically all affixes have equal probability, but some have a value in their ‘family’ assignment that makes them behave as an ‘always roll first’ affix, if it isn’t on the item already.
The OP is an experienced dataminer and crafting simulator web tool builder. He believes this is a bug or unintended.
"I’d like to mention that I think this is a bug and probably not intended for two reasons:
-
It doesn’t make sense to tie this kind of behavior to the value in question as the value is used to put affixes in the same ‘family’ making it so they can’t appear on the same item (for example dodge and dodge from distant…)…
-
If you look at the affixes that are priority and their base, you’d think there would be some logic to them being tagged as such. But it seems more arbitrary than anything else. As an example Amulets have thorns and +%total armor as priority affixes amongst other things. Doesn’t make much lore sense for amulets to have those be more prevalent, or Basic Skill Attack Speed on helms for that matter."
He made a tool for predicting enchanter crafting: D4Craft,com
I want to raise the awareness on this issue to get a dev comment, and hopefully, a fix to a massively important part of the game that may have been broken this whole time.
This isn’t an invitation to pile hate on the developers, though I’m sure some of you don’t need one. Bugs happen. I don’t expect software to be perfect, but if this is not intended, I’d love it to be fixed ASAP, and that won’t happen without the community alerting them.