M2017 1.1 Bugs&Feedback

[phoenixapple]

can confirm symbol of esu isnt working as described. tested under several conditions. seems to be a pure bug. even when in a completely safe area under no de-buffs using a symbol will often fail to heal. there goes our panic all treat. very frustrating.

[Alejandro131]

Even with the increased drop rates, Jitan and Khalimgrad charms are impossible to get with bad RNG. If you just want them to not drop every time, make them drop tokens/parts for a charm always so that when you combine 4 for Jitan and 9 for Khalimgrad in the cube you get the charm.

[willyboy]

Torajan Jungles is like a Botox-therapy at the beauty doc....a small potion will be fine, too much will make an ugly mask....and THIS is too much

[thunderman]

It's too early to write post about first impressions, but I have to agree with others about Torajan Jungles, the fact that red portal to k3k is right outside entrance is fine with me and I was hopingexpecting same situation with Legacy of Blood and Akarat.
Despite the fact I'm not that strong, when I discoverred I have to go quite long distance to get there I was like 'omg what have you done?' I got both charms, but I find problematic farming for trophies when two relatively easy Ubers are placed in two opposite corners of huge jungle. At this point Im willing to pay for these trophies (wishful thinking ) and forget whole thing.

ps. Caldeum looks nice.

[Vessalax]

Shark and Dawn Runewords respectively.

Update to version 1.1.2 vessalax.

Thanks, I updated and it's now fixed.

[whist]

Palas Colosseum debuff ring seems to most of the time appear on your feet, not under the mob you are teleporting to. I remember this being an issue several patches ago but IIRC it was fixed and worked correctly last season.

It's not really a bug but rather a combination of Blizzard's terrible code in terms of syncing, and network latency when playing multiplayer. Chances are you would never see this issue occur in single player, and the occurrence of it is completely random when playing multiplayer. It is much more likely to happen now, in the early start of a new ladder, since the servers are loaded with tons of players and the latency is at it's peak.

What actually happens is, the player's position is not updated before the missile that creates the nova is created. This missile uses the player's position as it's base position, so the missile ends up being created at your starting position. The teleport skill function was never really meant to create missiles in the first place, so it's kind of a punishment for using something in an unintended way.

In MXLS, a dedicated skill function will be added, that will use the target point as the base position to create the missile, so that even if the player's position hasn't been updated yet, it will still create the nova in the correct location. But meanwhile, this cannot really be fixed. One thing you can do to get around the issue is getting closer to the monster(s) before casting the skill so that they're still in the created nova, or luring them in, or even, playing when there's less network traffic going on.

Note: not entirely sure whether the issue is server or client sided. would be worth testing if the effects are still applied on server's side even though the monsters do not visually seem to be affected (ie, are they still taking damage?)

[cnoltz]

Palas Colosseum debuff ring seems to most of the time appear on your feet, not under the mob you are teleporting to. I remember this being an issue several patches ago but IIRC it was fixed and worked correctly last season.

It's not really a bug but rather a combination of Blizzard's terrible code in terms of syncing, and network latency when playing multiplayer. Chances are you would never see this issue occur in single player, and the occurrence of it is completely random when playing multiplayer. It is much more likely to happen now, in the early start of a new ladder, since the servers are loaded with tons of players and the latency is at it's peak.

What actually happens is, the player's position is not updated before the missile that creates the nova is created. This missile uses the player's position as it's base position, so the missile ends up being created at your starting position. The teleport skill function was never really meant to create missiles in the first place, so it's kind of a punishment for using something in an unintended way.

In MXLS, a dedicated skill function will be added, that will use the target point as the base position to create the missile, so that even if the player's position hasn't been updated yet, it will still create the nova in the correct location. But meanwhile, this cannot really be fixed. One thing you can do to get around the issue is getting closer to the monster(s) before casting the skill so that they're still in the created nova, or luring them in, or even, playing when there's less network traffic going on.

Note: not entirely sure whether the issue is server or client sided. would be worth testing if the effects are still applied on server's side even though the monsters do not visually seem to be affected (ie, are they still taking damage?)

I believe that I tested this last ladder. Colosseum ring triggers at feet rather than location pouncing to, however the effects of colosseum appear to be applied correctly to the location you jump to. Appears to only be a visual bug. Same thing happens for me when I play a pounce zon.

Playing in single player, skills work as intended (mechanically and visually).

[Quirinus]

Awesome, so people can stop qqing now.

Cookie.

[Drakks]

Don't know if this is a huge bug, but I found a great rune (Qor) in terror Fauzt. Was this an intended change or just a small bug in the drops?

[Jampula]

Nice to get a detailed answer for Colosseum. +1

Baal is very confusing now. I have mainly started high dps builds this season and I just go in and hope for the best without having a clue what's happening in the battlefield... maybe tune down the teleporting?