Cannot proceed with the lost expedition quest

Same for me, one thing I can add is that I cleared the entire area before entering the "Sandy vestige". Not sure if different for others.

Hi,

I too have the same problem,
pop hidden zone (2 times on lvl 60 and 61 expedition log),
get in after clearing mobs and chest,
clean the hidden zone,
and I click the "Ancient Kalguuran Text".

The game then tell me to talk to Dannig but nothing happened, he doesn't have a quest marker, no new dialogue, both in expedition log and in hideout.

When i leave the "log map", the game tells me to "Search for Ancient Kalguuran Texts" and when i go back in the log map it tells me "Return to Dannig for the translation" but still nothing from Dannig himself.

And in the hidden zone, the text his back on the ground and nothing happen when i click on it.

I hope it helped to fix this bug, if more information is needed, please let me know.

(I really like the league too, love from France <3)

same issue here. pls fix. ty :)

Have encountered this 4 times, though 4 cleared expeditions. Clearly a bug, please fix this.

Same problem, 2 expeditions 2 times cannot talk with danning

Lucky you i cant even find or spawn this hiden areas and I am alrdy 82lev...

Same issue here, twice in a row.

1. Enter/Complete a log book

2. Found the quest item text in the abyss style door-in-the-floor.

3. Quest updates to "Return to Dannig to hear a translation..."

4. Dannig does not have any new dialogue in the log book instance

When I return to hideout, the quest state returns to "Search for Ancient Kalguuran texts at Expedition Sites"

I can re-enter the log book instance and the quest wants me to talk to Dannig, but if I go back into the room with the text, the quest item is on the ground but I cannot interact with it.

"

Kapekkkkk wrote:

Lucky you i cant even find or spawn this hiden areas and I am alrdy 82lev...

The hidden areas in log books have a unique icon on the map, you just have to place dynamite on it and it will turn green like a chest/skull.

Same issue here

same thing here.