Been doing the capstone cathedral of light, the curator went missing, tried this twice and both almost killing him. I can hear the audio queues but he isn’t showing up in the arena/map/mini map.
The dungeon is fairly long and would like some help, I don’t want to waste another 30-45mins of my time doing this dungeon from the start
Tried doing it twice so far and he despawned twice at around 5% after doing the dungeon for around 35min. Still stuck in a boss fight so cannot just tp out forcing you to leave game and do it again entirely. Im doing the dungeon at level 45 so its fairly challenging. Blizzard clearly does not respect the players effort nor time.
This is clearly not the polish i paid 90 euros for.
Thank you Blizzard for making me realize it was yet another mistake buying one of your products.
same thing here, down to about 10% and he vanishes, still hear him making noises but never comes back, had to force close and start over which is very annoying with the amount of time invested
same thing just happened to me, i’m super fkin annoyed because it took a while just to get to him and then he bugs out at like 10% hp?? you can’t be serious.
Now I’m experiencing the same problem. I’m playing a level 48 necromancer and have attempted this twice now. Both times, when The Curator teleports and launches the three line attack with his adds, he suddenly disappears.
The audio queues, particularly the growling attack sound, continue to play in the background, but The Curator is nowhere to be found on the map, mini-map, or in the arena. It’s quite frustrating, especially considering the time investment and challenge involved in reaching this point of the dungeon.
This bug is essentially blocking my progression in the game. Please, please please, address this issue as soon as possible
After doing it twice last night and having both times bug out, i decided to go to bed. Woke up this morning and tried it again and its still happening…please help!!!
This bug is STILL LIVE. It’s literally game breaking, I cannot progress. After wasting hours on restarting the instance I’ve ran into the Bug countless times. I don’t know how this flies under their radar considering how game breaking it is.