We currently have a workaround implemented that will allow you to teleport to the next chapter’s starting waypoint at “Soreth’ka”.
We currently have a workaround implemented that will allow you to teleport to the next chapter’s starting waypoint at “Soreth’ka”.
Yeah this is the same issue as the above, we should have a fix for this internally that’ll be out as soon as it can be.
Ok gotcha, yeah this is an issue we’re aware of and are keeping our eyes on internally. I’ll take the information from this thread and update our internal stuff.
So long as you can progress through the next zones, your progression will not be affected even if you did not interact with certain NPCs.
I’m sorry I don’t know. I don’t really have any more info on the situation yet. I know people much smarter than I are working on it though.
We are looking into this thanks!
Can you show me your skill tree?
Yup only a visual bug. Should work as intended. Thanks.
Have a fix them in the works thanks.
We have a fix for this in the works thanks.
We are aware of this bug. It’s only visual, still should work as intended.
They aren’t spawning. I got a fix in the works. Thanks.
Pretty sure its in the works
Yup
We know that people are getting sent to servers far from them. We are working to make sure that this isn’t a problem going forward. In our investigation, we pulled the stats for the ping checks when it is looking for a server and it is successfully placing everyone in the lowest ping server.
This is not giving players the best play experience and we are working to remedy this.
It is placing people in the lowest ping server when it is checking the servers to see which is the lowest ping.
It shouldn’t take us as long as 1.0. That would be terrible.
I gave a bit of context on this topic here: https://www.reddit.com/r/LastEpoch/comments/11q7k6y/mob_density_feels_really_inconsistent_in_this_game/jc4thgt/
This is definitely coming up in the priority list! We’re on it.
I have a ticket in about this specific zone already. Thanks.
We are investigating this bug. Thanks for the report.