This is a repost, since my initial post was acknowledged but esentially ignored.
I was trying to complete Dreamrift Mythic before work but got wiped a few times. I left the raid and turned the game off. When I logged back in, 10 hours later, I was popped the question if I want to lock myself to the raid with 1/1 bosses defeated. Obviously I chose no, when I left the instance, I noticed I was locked for this week. I never defeated the boss or contributed to the loot. What is this about? I’ve been struggling to get that trinket and I had bonus rolls ready for it, now I need to wait another week because of a bug? I demand a reset for my instance lock.
I guess nobody cares about the state of the game anymore. Mythic Raiding has been out for a while now, still there’s issues like this that ruin the experience for loyal players. How come we’re paying for the game and a monthly subscription if you guys can’t simply reset a malfunctioned lock. This is absurd.
This is defintely a not-intended feature of the game, and I’ve seen other people that experience the same issue.
I’ll repeat myself, once I leave the party it means I don’t want to commit to a Mythic Raid in that group.
Let me put it like this, 20 players complete Dreamrift (the 1 boss raid) and 21 players (potentially more) get locked. It doesn’t make any sense that more players than the maximum raid size are locked on a single Mythic Raid ID. Does it?
Yes, my problem was acknowledged but they ignored the fact that it was a bug. I know that sounds weird, but it’s possible at Blizzard.
I stated a simple fact, that more players are being locked, in this case 21 than the maximum nythic raid size allowed (20). If they deem that as intended behaviour, than they must’ve missed their math class back in primary school and they lack basic reasoning. It’s obviously not an intended feature, it makes no sense. The way it should work, and you don’t need to be a game developer for that, is when you leave a party, you automatically unlink your character from that Mythic ID, simple binary logic. Instead you got to leave the Raid Instance otherwise you’ll be locked along with the other 20 players that completed the raid.
I created another post because I couldn’t post again in the same topic unless somebody else replied.
It’s always been possible for more than 20 players to get locked out on Mythic - raid teams routinely rotate players (or alts) in and out of their bench.
The design goal of the Mythic lockout is to encourage players to commit to the same raid team for the entire week and to deter folks from quitting the group before a kill. Allowing players to escape the lockout by leaving would be contrary to that goal.
I’m not sure if your issue was due to a DC - if it was that obviously sucks that the group didn’t wait for you to return - but that is part and parcel of the risk you take if you pug into Mythic raids (which are most defiantly not designed to be PUG friendly).
There is for sure a valid discussion to be had around if the Mythic lockout restrictions make sense for the modern game - I’m not a fan of it - but not liking a design decision does not make it a bug!
You interpreted how a Mythic lock works wtih your opinion*. For a detailed fact, please review Furydin’s post on how Mythic locks work. This is kind of always how it has worked and it can lock beyond the initial starting raid size. You yourself clearly acknowledge that Mythic Raiding has been out for awhile and nothing has really changed.
The way you want to see it work* is like how regular ID’s work, such as LFR, N/H also known as “Loot-based lockouts”. The type used for Mythics is “Instance-based Lockouts”.
You edited your last post fine and an Blizzard post is not guaranteed on these forums. There’s no need to bump or create duplicate topics, if you think it is bugged you’d need to report it through the ingame bug reporter.
I think that what you both said makes sense and applies perfectly in a raid with more than one boss. But in my case I got locked before defeating the first (only boss).
Few weeks ago when I’ve got my cutting edge I lead a group, we tried for 4 hours to defeat it and we failed. I woke up the next day, I formed another group and we succeeded. I wasn’t locked to the same ID. Same thing on the next kill, a week later.
I understand that Mythic raids use an instance-based lockout and that Customer Support generally cannot reset raid IDs.
The issue I’m trying to report is more specific: I had wiped on Mythic Dreamrift, left the raid group, and logged out. Hours later, when I logged back in, the instance showed 1/1 bosses defeated and I received the lockout confirmation prompt. I selected No, because I did not want to accept that completed lockout. After exiting the instance, I was still saved to the 1/1 Mythic Dreamrift ID.
If the intended behavior is that I was already committed despite leaving the group and selecting No, then the confirmation prompt is misleading. If selecting No should prevent the lockout, then this appears to be a bug.
I’m not asking for a debate about whether Mythic should use instance-based lockouts. I’m asking whether the lockout prompt is functioning correctly in this case, and I’ll also submitted it through the in-game bug reporter.