If you were to bring somebody’s alt in from a different server, somebody you trust, they would be saved to your lockout. Then next week they could start the raid and you guys would zone in to that old raid lockout.
For example, if you found an Alliance alt on, say, Proudmoore, and had them join your raid (cross-realm) and get saved to your ID, they could start the raid next week and you guys could zone in, and get saved back to your raid ID.
There’s absolutely no reason that merging your server would wipe the raid ID of a character on Proudmoore. (In fact, it’s unthinkable.)
I’d offer myself, but don’t have any Alliance 120’s. (Although I’d be happy to offer this service for any Horde guilds worrying about this.)
Find a volunteer in a 12/12 Mythic guild that’s full clearing in 1 or 2 nights every week already. They would have no use for your lockout for their own purposes.
Blizzard is clearly here watching, they fixed the realm connection list above. Why should i expect them to actually fix the game. They KNOW there is a literal game breaking bug related to lockouts and connections, We submitted ticket after ticket last time scilla was connected. Now they are choosing to connect us again, with COMPLETE radio silence on the fact that it WILL break our lockout.
Fool me once, shame on you blizzard. Fool me twice, Shame on me.
If you were to bring somebody’s alt in from a different server, somebody you trust, they would be saved to your lockout. Then next week they could start the raid and you guys would zone in to that old raid lockout.
This would work fine, if Blizzard would do this connection on a tuesday. Being on a Thursday, we either completely skip 2 nights, and then start on thursday, Or we raid tueday and get completely locked to a instance that doesn’t exist.
Understood, unfortunately this has always been a thing.
I remember when they closed down the Phoenix datacenter during Siege of Orgrimmar and migrated all its servers (including my server, Hyjal) to the Los Angeles datacenter. That was also done on a Thursday and that also reset our raid ID.
Last time it still had us as saved to an 11 of 12 lockout but when we zoned in it prompted us to join a 0 of 12 lockout. So it basically we cannot start a new lockout or continue the one we had. We tried