KissingAiur

We think we have a fix to this in the next hotfix. Let us know if after upcoming hotfix it doesn’t fix the issue.

I made a note of this thanks.

Thanks for the report. I made a note of it.

Thanks, I made a note of this.

Thanks for the report, made a note of it.

I made a note of this, thanks.

I tested this node just now and it definitely still works with Soul bound and with both nodes. Be aware that Triage mentions that Eterra’s Blessing targets an ally that is low health, if it doesn’t target your Spriggan it will not trigger Soul bound. This means if it targets yourself or other companions it will not activate the spell power increase. This might be why it doesn’t display an increase for you.

If you think this is not the case, a video or screenshots would help look more into the problem.

I am not sure if this is intentional or not. I made a note of it internally. Thanks for the report.

I believe this was a small side effect of the trees design. It doesn’t add much power because that comes from the specialization tree so we decided to allow it. I would like in the future these nodes to be more exclusive, needing the player having enough points in the passive tree to unlock these benefits. I’ll make a note internally.

Can you show me a picture of your Ic Thorns specialization tree when it crashed you?

What was the passive you suspect is broken?

Indeed it looks like something is not working correctly with this node. We will take a look at it. Thank you for the report.

This might be because it could counting as a double conversion which we don’t currently have support for. I’ll make a note of it regardless. Thanks for the report.

This is a known issue. Thanks for the report.

Can you post a player.log?

The Game’s Log File – Last Epoch Support

Can you show me a picture of your Ice Thorns specialization tree?

Llama is correct. They should be removed on logout, this is purely a visual bug. Thanks for the report.

You are absolutely right. I missed this one. We will get that fixed. Thanks for the report.

I believe we found the problem to this. Next hotfix should resolve this issue. If it doesn’t please report back in the same thread. Thanks.

This is a known issue, thanks for the report.