JustinC

Sorry about this, everyone! We’re looking into this. We’ve identified the source of the problem, so we won’t need any more player logs, but we don’t have a timeframe for a fix yet.

We’ll be looking to get it into a hotfix, but I’m not sure when that will be.

Spirit Thorns has 40% less chance to apply ailments, which is visible when holding alt on the tooltip. This puts your poison chance at 196% with Spirit Thorns, which means it’s technically possible to apply only 2 poisons when hitting twice, but very unlikely.

I’m seeing the same results as you when testing. I suspect there is a bug at play here, I’ll look into it further. Thanks for the report!

I’ve found the problem, we’ll get this fixed. Thanks for the report! I’ll also update that tooltip which has a couple mistakes.

We’ve reproduced the issue and will work on a fix. Thanks for the report!

It’s separately giving +3 to Cold Minion Skills and +3 to Necrotic Minion skills, which isn’t clear based on the tooltip, but it is intended.

In your second video, what’s happening is you’re unable to use Dancing Strikes because it requires you to be dual wielding, but instead of telling you that, it incorrectly plays an animation and locks you in place. We have a fix for that internally, although it may not make it into an upcoming hotfix.

I’m not sure what happened in the first video, but your description is accurate, there’s some sort of foul bug at play. I’ll look into it. If you have any more information or find a way to recreate the bug, let me know.

Thanks for the report!

We’ll work on a fix for this. Sorry for the delay!

I haven’t been able to reproduce this yet.

To confirm, your melee normal Wraiths and ranged Flame Wraiths are both attacking Lagon, but then their melee attacks and projectiles don’t appear to hit or damage Lagon at all?
Are these permanent Wraiths? If so, does resummoning them have any effect on their ability to damage Lagon?
Is this in offline or online play?

Your player log from a play session where this occurred may also help us figure out the problem. Thanks!

Warpath’s movement speed modifier is 20% less movement speed, which is multiplicative with other modifiers. This is different from sources of increased or reduced movement speed, which are all added together before being multiplied by each source of more or less movement speed. So your movement speed while not using Warpath is 1 * (1 + 0.3) = 1.3, and while using Warpath it’s 1 * (1 + 0.6) * (1 - 0.2) = 1.28.

The game guide has a detailed breakdown of how these different modifiers work. You can find it in-game by hitting G and then typing “more” into the game guide’s search box.

There’s certainly something strange going on. Could you try veryifying the integrity of files in Steam? To do that, right click Last Epoch in your Steam library → Properties… → Local Files → Verify integrity of game files.

Let me know if that reports any files that had to be corrected, or if it has any impact on the issue. Thanks!

We made a change in 0.9.1 that was intended to significantly reduce the chance of this accidentally occuring, but expected it to still happen to some extent.

Is it accidentally occurring often enough to cause a problem for you? If you’re using it intentionally to keep Warpath active without needing to hold down the button that’s fine, I’m just wondering if it’s causing frustration and we should work on a more comprehensive fix.

Thanks for the report!

Thanks! We’ll update that text.

We’re working on a fix for this. Thanks for the report!

Based on the video, the game appears to believe that you are immediately releasing the Rampage button after pressing it. I’m not sure why yet, but I have some questions to rule out possible causes:
Does this problem occur every single time you use Rampage, or only sometimes?
Do you have a controller connected?
Does this occur when using any other channelled abilities that have a cooldown, such as Sentinel’s Rebuke or Mage’s Focus?

We’ve got a fix for this and are working on getting it into a hotfix. Thanks for the report!

You’re right, there’s a second bug at play here as well. We’ve identified the issue there and will fix that too.
Either way of contacting is fine.

We have a fix for this internally and are working on getting it into a hotfix. Thanks for the report!

We’re looking into this. Thanks for the report!

We have a fix for this internally and are working on getting it into a hotfix. Thanks for the report!