Day1:
Entered the raid and eventually killed 10H Magmaw. Tried Omnotron for a bit then killed Omnotron on 10man normal.
Day2:
Attempted to enter the raid with a 1 player roster difference, found out that we cant, struggled to enter the raid with 9 of our previous raid members then got into a different lockout with Magmaw back alive. Died and couldnt return back in. Had many members try to enter our original lockout so we could continue and eventually were able to.
Day3:
Same situation, constant struggles to enter our own raid IDs getting the same error message of heroic instances requiring the same raid comp.
Problem appears to only persist for 10man heroic to normal swapping over multiple days.
Honestly not being able to ADD to a 10man heroic roster is criminal, specifically meaning having a 10man roster, 1 person cannot make day2 so now you’re stuck 9manning it, or continuing on normal without any way to bring in a different player.
I dont think thats very healthy for the game and needs to be reconsidered.
3 Likes
I concur with this issue on 25m. Did Heroic Halfus on Thursday and Normal Valiona. We come back to BOT on Sunday and it just won’t let us join cause it says we’re ineligible because we were locked to heroic already. Same thing happened in BWD. We still had Chim and Nef up and we did heroics on Thursday.
All in all, it was a very frustrating Sunday night with this bug.
1 Like
This also occurred for us.
New player came in and couldn’t continue our heroic prog. It let us do one attempt at a boss on heroic then after attempting to zone in after a wipe they were saved to a different ID. They hadn’t zoned into any other raids or joined any other raid groups.
1 Like
My raid team also encountered this bug.
It seemed to start with us as soon as we downed a boss on normal, then came back the next day with a slightly different roster. We got this message every time we tried to zone back in after a corpse run. For us to get back in, we would have to swap it to normal to be able to zone in, everyone logged out except raid lead, raid lead sets it to heroic, then everyone logs back in. We didn’t do the whole raid on the same night, so idk if that had anything to do with why it affected us.
It’s wasting a lot of time for raid teams trying to prog heroics.
We experienced this tonight as well with our guild.
Tuesday we did Heroic Magmaw/Normal Trons/Heroic Chimeron and Atramedes. We had to bring in a replacement on Atramedes. Killed it with the new member.
Today the original member we had is back and we run into these issues with where we cant zone in to our raid. We were able to get 1 pull on heroic maloriak but when we corse ran in, we got the error. Would love to have this solved or how to avoid it.
We had same issue on 25 man. You cant bring in a new player into your raid and wipe on heroic otherwise the new player will be bricked on a separate lockout for some reason.
Can we get this fixed already? Like seriously… this happened to us last night. 5 players couldn’t enter BwD after a heroic Atramedes wipe. 4 out of the 5 members were there on Thursday with us when we killed ODS on heroic but now they can’t enter the same raid. The last member had a totally different raid ID than the rest of us because he wasn’t there on Thursday.
We had to finish the night on normal instead of progressing on a heroic fight
fix ur stupid lockouts… you cant even enter a raid or you get saved to it.
We get the same bug on the second week of raids, and still have this week. On 25 and 10 mode. Always happend when get a new player to fill progress on our 2° raid day and also when we tried to swap normal>heroic to do attempts on X boss. On my guild we try to do progress on multi. days and this stoped us 2 weeks, days and time for ppl who come prepared to raid are for nothing.
they got 7 devs working on all classic modes. it’ll get fixed next phase.