We are looking into this problem. Thanks for the report.
We are looking into this problem. Thanks for the report.
If you have any additional information on how this occurred that would be a big help. Did you experience any disconnections around the time this issue occurred? Did someone crash during your progression? Anything that would seem to be out of the ordinary for progression would help a lot in terms of locating the source of this issue.
We are aware of this problem internally. Thanks for the report.
We are investigating this internally. Thanks for the report.
We have this noted internally. Thanks for the report.
This is a known issue that we’re tracking internally.
It’s intentional that it doesn’t have a void tag.
It’s a known issue internally. We are looking into it.
Thanks for the report, we are looking into it.
This is a known issue. We have a fix in the works. Thanks for the report.
Thanks for the report.
This is a known issue and will only occur if you’re not using Serpent Strike with a Spear.
Are you referring to the NPC in the Risen Lake?
If that was the case, were you the Player that initially interacted with the NPC that gave the quest?
Can you give more detailed recount of your progression right before this point? Did you have any oddly timed disconnects? Crashes? Or were you just moving through the game naturally? Additionally, I’m not sure if this would help, but there’s a chance that leaving the zone and returning to it after a short time might resolve it?
No need to worry about it, glad you found a way to progress!
We’re looking into this on our end, and I’m sorry you’re having this experience. It’s one of our top priorities to fix at the moment.
We’re tracking this and issues like this internally, thanks for the report.
Yeah the LE-51 error is just the unfortunate bit that had you booted out of your loading screen. The issue lies within the actual zone of The Dreadnought’s Deck itself. We’re looking into this.
If you manage to get someone into Shining Cove you should be able to Player Portal to them and continue from there no problem. If not, please feel free to update this thread with additional information.
This is a known issue that we’ve got in mind for our next round of Controller QoL changes.