While on another quest to collect 4 Oracle Eyes for Taissa, I came across the side quest “Tangled Memories” by the quest giver Kres. Upon selecting the first dialog choice with the subject line in topic, my character froze with a “eye” icon above the head. I was unable to ESC or advance through conversation, resulting in CTRL + ALT + DEL to bring up the Task Manager and End Task for Diablo4.exe then relaunch and continue on the side quest without issues.
I’ve took a screen shot of the dialog box but unfortunately, Diablo 4 forums does not allow screen shots to depict the issue.
I would advice players who come across the NPC “Kres” with the Tangled Memories to avoid the !!Missing!! - - 1MenuLable dialog or you will need to force shut down Diablo 4 and return in-game without being stuck in dialog animation.
4 Likes
Note: I also just ran across this bug. You don’t have to force quit to get to playing potentially. My character was released back to me after roughly 60 seconds. I am assuming this is the time built in for the NPC dialogue interaction to play through.
While frozen your character will have the icon above there head that a group member has when they are watching a dialogue playthrough (The EYE in brackets).
It look like the missing label name is allowing interaction and forcing a wait for the dialogue timer to run its course. As stated above once the dialogue option is selected the character will appear to freeze with no visible options for ESC from the state. Other in game assets or player may still run around on the screen. I timed the interaction at about 65 sec, before PC is released back to a controllable state.
The first line of dialog looks like this - probably a Dev note
<> !!Missing!!–1:MenuLabel
I also made a screenshot using Microsoft’s snipping tool.
Same bug just hit me. Was released from the not-playing video as described by sorrowsheart after about a minute without quitting out. Just clicking on the quest ending bit worked fine.
1 Like
Just ran across this. The bug is still there months after first report.
No way to exit the interaction other than force closing the game.