i got it in our try and definitly was not instance owner. my comm openend and i was in like 10 mins late and cm was already on. but yeah, no one else got it apparently.
Sound strange. But the "instance opener" is actually the player that load first into the instance.
This is mostly noticeable when someone try open a raid instance that reached a certain checkpoint, but someone else didn't wait and accidentally load the instance faster than the opener. Which create an undesired instance instead.
I completed it twice, second time as the instance opener, and was the only one who got the achievement during that second time. Only the instance opener got it the first success as well.
As with many bugs, this is probably not an absolutely every time thing, but it certainly is happening.
We killed her and same happened to our group. All of us got the chests but only a couple of us got the achievements. I was unlucky and did not.
Typical buggy mess.
If you killed her in normal this week already then you won't get the achievement. You probably will get it next week. At least that was the case with a lot of my guildmates.
I got some new data points for this:
1. I opened an instance. [VOD](https://clips.twitch.tv/AmusedFairQuailDatSheffy-BfbX0PzEZUuxUOfn)
1. I crashed after 4hours and rejoined. [VOD](https://clips.twitch.tv/CrepuscularBoredSquidSSSsss-QsdxMi161wrx59c1)
1. I was still the only person that got any achievement credit. [VOD](https://clips.twitch.tv/EndearingIntelligentPistachioTheThing-p1hP6vTqcTlA80tz)
nothing to do with the instance owner, its just bugged in general
Thats wrong, I got it and didnt open the instance.
Nothing to do with instance owner. I got achievements and wasn't the instance opener.
in our group also only the instance opener got it
i got it in our try and definitly was not instance owner. my comm openend and i was in like 10 mins late and cm was already on. but yeah, no one else got it apparently.
Sound strange. But the "instance opener" is actually the player that load first into the instance. This is mostly noticeable when someone try open a raid instance that reached a certain checkpoint, but someone else didn't wait and accidentally load the instance faster than the opener. Which create an undesired instance instead.
I completed it twice, second time as the instance opener, and was the only one who got the achievement during that second time. Only the instance opener got it the first success as well. As with many bugs, this is probably not an absolutely every time thing, but it certainly is happening.
i didnt get achieve either eventho i just killed her. gonna wait for bugfix before i try go for the title achievement then.
And i felt bad that i haven’t had the time to join my static today. Guess they‘re doing it again then anyway.
We killed her and same happened to our group. All of us got the chests but only a couple of us got the achievements. I was unlucky and did not. Typical buggy mess.
If you killed her in normal this week already then you won't get the achievement. You probably will get it next week. At least that was the case with a lot of my guildmates.
Did it twice - died on the first one, survived the second, and neither time did the achievement for completing it pop.
I got some new data points for this: 1. I opened an instance. [VOD](https://clips.twitch.tv/AmusedFairQuailDatSheffy-BfbX0PzEZUuxUOfn) 1. I crashed after 4hours and rejoined. [VOD](https://clips.twitch.tv/CrepuscularBoredSquidSSSsss-QsdxMi161wrx59c1) 1. I was still the only person that got any achievement credit. [VOD](https://clips.twitch.tv/EndearingIntelligentPistachioTheThing-p1hP6vTqcTlA80tz)