PTR findings and first impressions

Queegon wrote: 5 hours ago

Schnorki wrote: 11 hours ago

Upon closer inspection..most things do seem to work. I merely apparently went with exactly the wrong items that they can't export correctly..

Crown of Ages for example gets exported with 4 sockets. o.O

I get where you're coming from but for testing purposes extra sockets don't matter.
I once exported a

Coronet with 2 sockets, it showed 4 in game, but only two of those could be socketed. Just a visual bug. If it actually was 4 open sockets I would have socketed two.
No harm done.

Unsure what you meant with wrong weapon damage, as I haven't experienced that.

Aye, the sockets aren't hindering anything. Just wrong which doesn't necessarily instill trust.
Weapon dmg it seems reliably comes out wrong when you export a weapon that already has some form of +dmg on it (e.g.

The Grandfather) with a Stone in it. The 10-30 of the Stone seems to then be randomly subtracted on the resulting weapon, giving you lower weapon dmg than you would have with the same rolls on an actual drop in the real game.

Schnorki wrote: 1 hour ago

Weapon dmg it seems reliably comes out wrong when you export a weapon that already has some form of +dmg on it (e.g.

The Grandfather) with a Stone in it. The 10-30 of the Stone seems to then be randomly subtracted on the resulting weapon, giving you lower weapon dmg than you would have with the same rolls on an actual drop in the real game.

Haven't you been the one to poinpoint it, too? forums/protector-s-stone-bugged-on-ribc ... 18156.html

Or is this something different, unrelated to the above? I'll check.

Queegon wrote: 1 hour ago

Schnorki wrote: 1 hour ago

Weapon dmg it seems reliably comes out wrong when you export a weapon that already has some form of +dmg on it (e.g.

The Grandfather) with a Stone in it. The 10-30 of the Stone seems to then be randomly subtracted on the resulting weapon, giving you lower weapon dmg than you would have with the same rolls on an actual drop in the real game.

Haven't you been the one to poinpoint it, too? forums/protector-s-stone-bugged-on-ribc ... 18156.html

Or is this something different, unrelated to the above? I'll check.

That

Ribcracker is the opposite example actually as it does account for all of it in the total.
Much like my legit, live online version of a Stone weapon that isn't even a perfect roll has more dmg than the perfect roll maxroll-exported version because of it.

That's not a blizz thing, it works fine with legit items. This one's on maxroll.

Schnorki wrote: 57 minutes ago

Queegon wrote: 1 hour ago

Schnorki wrote: 1 hour ago

Weapon dmg it seems reliably comes out wrong when you export a weapon that already has some form of +dmg on it (e.g.

The Grandfather) with a Stone in it. The 10-30 of the Stone seems to then be randomly subtracted on the resulting weapon, giving you lower weapon dmg than you would have with the same rolls on an actual drop in the real game.

Haven't you been the one to poinpoint it, too? forums/protector-s-stone-bugged-on-ribc ... 18156.html

Or is this something different, unrelated to the above? I'll check.

That

Ribcracker is the opposite example actually as it does account for all of it in the total.
Much like my legit, live online version of a Stone weapon that isn't even a perfect roll has more dmg than the perfect roll maxroll-exported version because of it.

That's not a blizz thing, it works fine with legit items. This one's on maxroll.

I exported a grandfather with socketed

Protector's Stone and grandfather with socket and a

Protector's Stone ready to get socketed.
planner shows 203-649 dmg grandfather at lvl99, PTR shows 203-649 dmg grandfather.
planner shows socketed grandfather at 242-737. Game shows 232-707. Socketing a 203-649 sword in game with a jewel shows 232-707.

So is just the tooltip in planner wrong? Game seems to be counting correctly. Planner clearly counts

Protector's Stone differently than the game itself.

Tried with

Ribcracker. Socketing

Ribcracker in game with Stone from planner adds the two min-max together, contrary to what has been posted in the thread linked above. Now says 40-95 dmg.
Goes from 330-493 to 367-546, planner showing 377-576 (and the linked

Ribcracker from thread confirms that).

Windforce no socket lvl 1 35-241, with socket 40-275, planner showing 50-305.

Planner might be making buggy protector's stones?

Queegon wrote: 43 minutes ago

Schnorki wrote: 57 minutes ago

Queegon wrote: 1 hour ago

Haven't you been the one to poinpoint it, too? forums/protector-s-stone-bugged-on-ribc ... 18156.html

Or is this something different, unrelated to the above? I'll check.

That

Ribcracker is the opposite example actually as it does account for all of it in the total.
Much like my legit, live online version of a Stone weapon that isn't even a perfect roll has more dmg than the perfect roll maxroll-exported version because of it.

That's not a blizz thing, it works fine with legit items. This one's on maxroll.

I exported a grandfather with socketed

Protector's Stone and grandfather with socket and a

Protector's Stone ready to get socketed.
planner shows 203-649 dmg grandfather at lvl99, PTR shows 203-649 dmg grandfather.
planner shows socketed grandfather at 242-737. Game shows 232-707. Socketing a 203-649 sword in game with a jewel shows 232-707.

So is just the tooltip in planner wrong? Game seems to be counting correctly. Planner clearly counts

Protector's Stone differently than the game itself.

Just tested a different example where I do have a proper live version for a direct comparison.

Legit live WF:
48 to 587 (285ed, +296 max from lvl 95)
(yeah, yeah, I need to lvl her a bit more and get a better Stone... ^^)

Exported WF:
40 to 581 (300ed, +309 max from lvl 99)

Maxroll export is clearly wrong and offers less dmg at max lvl/perfect rolls than a legit one does with lower lvl/rolls.
It isn't just the tooltip either. Looking at my zon comparison after recreating her (live vs. fully perfect/99 maxroll export), my live zon has ~1k more

Strafe dmg. The maxroll result is just way off.