[BUG] Heroic raid lockout behavior

balshae commented 3 months ago

1. Current Behavior

1.1. Description

When trying to share your raid ID lockout to a different player because of having to replace a person during a different progession day, you are going to soft-brick your ID, making the new person unable to zone into the raid on heroic mode (and anyone else from the raid for that matter), basically only being allowed to do normal, despite the fact that the one new person in the raid has not done the raid at all during the week.

1.2. How to Reproduce

       1. Zone into a raid instance on 1 day with a raid group of 25 or 10 people depending on the raid size setting, kill half the raid 
         during this day
       2. Try to reenter the same raid instance on another day with 1 different person (this person has NOT DONE ANY RAIDS in the week) in order to finish the other half of the raid
       3. Attempt to set the raid difficulty to heroic, and run into an error message claiming either that you are locked to the instance already, or that you are ineligible to enter this instance (despite the fact that the new person has already accepted your lockout).

1.3 Source Material

https://us.forums.blizzard.com/en/wow/t/cata-problem-with-id-raid-on-heroic/1873750 https://eu.forums.blizzard.com/en/wow/t/10man-raid-lockouts-are-broken/516538/15

2. Expected Behavior

2.1. Description

Seeing as Blizzard themselves have failed to explicitly explain the functioning of Cataclysm Classic raid lockouts, it is not apparent if this is either intended and should be marked as a #somechanges suggestion or if it is a bug. Either way, this system that is currently in place is a step backwards even from Wrath Classic lockout systems, and it ruins the potential for both pugs and guilds to progress the raids seeing as they are eventually soft locked to the same 25 people for the entire week.

Palmie commented 3 months ago

https://youtu.be/QE_2TFW63UU?feature=shared&t=610 this may provide some clarification. Sounds like they miscommunicated that there would be a change to the raid lockout system, but the intention was to just have it like the original Flex system in cataclysm which was for normals only.

Lillyton commented 3 months ago

but the intention was to just have it like the original Flex system in cataclysm which was for normals only.

This report is about being locked to a specific raid team, if you kill any heroic boss. This wasn't a thing in OG Cata. You were not locked to a specific raid team if you killed any heroic bosses in OG Cata, you could switch out players or have pugs come in to fully clear the raid.

The way it is currently, is a bug.

Basskip commented 3 months ago

Another thread discussing this issue https://us.forums.blizzard.com/en/wow/t/cata-10man-lockouts-are-a-nightmare/1867871/4

We experienced it ourselves in week 1, 25M

Made a few attempts on heroic magmaw, did not kill it
Killed magmaw on normal
Came back the next day, with 2 replacement members that did not have a BWD lockout
Experienced issues where nobody was able to zone into the instance, no matter whether it was set to Heroic or Normal
Finally managed to get everyone in on normal by re-forming the raid with a different leader
Changed to heroic
Killed heroic Omnotron
The two replacement players now had a completely different ID from the rest of the raid

Juvelir commented 3 months ago

My guild faced with the same issue today:

Made a few kills on Heroic 10 TB
Came back 2 days later with 2 replacement members. Switched to Normal diff. They accepted raid id. Killed 1 boss in Normal diff.
At the next boss we tried to switch back to Heroic. But we realized that one of the two replacements had a different raid ID.

So we could continue in Normal difficult with 2 new people or without them in Heroic.

scytherr13 commented 3 months ago

Had some lockout problems in BoT.

Thursday we cleared Halfus and Valiona HC, did Council normal, then killed Cho'gall HC.
Sunday we went back to prog Sinestra (23/25 same roster, 2 new people were completely unsaved), first no one could enter, game said : "You are ineligible to participate in at least on encounter in this instance in which it has been defeated"
We disband group and reinvite which lets us enter, the lockout says 3/5 (we thought it was because Council was killed on normal). We go to Cho'gall and he is alive and well. 24 people could enter, except 1 hunter who was with us on the Cho'gall kill on thursday. This is when we started investigating lockout ID's, the 2 new people had completely different ID number than the rest of the raid, despite being in the same heroic instance as us.
We disband the group and reform again, entering and the instance this time is 4/5, however the 2 people with the new ID cant enter. We ended up just going to Nef instead.

Tyco1400 commented 3 months ago

Partial Solve- This happened to my raid this week in BoT. We killed 2/5H on Tuesday, then came back Thursday to do normal council with 1 new person who wasn't with us on Tuesday. Killed council on normal and couldn't set it back to heroic. The one new person had a different raid ID. We ran out of instance and disbanded raid, everyone logged out and logged back in. Alt F4 didnt work, had to logout. couple folks had to exit wow completely. Everyone was able to re-enter on Heroic except for the 1 person who wasn't there on Tuesday. Only problem was, council was back up. We killed it on normal with NO NEW RAIDERS, then had our replacement come in for H cho'gall after re-clearing council.

ClassicWoWCommunity / cata-classic-bugs