Hey,
We are playing on Russian servers DeathWeaver and BootyBay.
Trying to kill mythic N’zoth along with some people from HowlingFjord and Goldrinn.
We started current Raid ID at Wednesday. Here is the link to our log:
https://www.warcraftlogs.com/reports/gxBrydWKRL4bpYZH
But after server combining DeathWeaver and BootyBay, players faced a problem: we can’t enter the raid due to Raid ID issue. Players from HowlingFjord and Goldrinn have no such issue.
Could somebody help is there any way to solve the problem or speed it up.
Reset the Raid ID for all of us or set the same ID?
In other case we could wait but now there are not much time to go. And we still hope to kill N’zoth.
Thanks in advance.
4 Likes
What happens in the case of server connections is that 1 realm gets copied onto the other realms ID… The ID of the realm that gets copied gets decommissioned.
In the case of these connections the Booty Bay cluster had its ID moved to that of Blackscar and the Lich King cluster was copied over to Goldrinn, the effect of which will feel like a server transfer since your character will gain a new Character ID in the process which won’t match that of your lockout, the reason why People on Blackscar/Goldrinn are unaffected is because their server ID didn’t change.
There really isn’t much you can do about this other than waiting for next week, though my advice would be that if your realm is about to be connected to hold off on the lockout until after (have someone off server save it if necessary), especially if your realm is the one that due to be copied, which blizzard also always makes clear when they announce the connections.
The announcements are always worded in the format “xxxx cluster will be connected to the yyyy cluster of realms”, xxxx will always be the copied realm that will get its ID changed.
2 Likes
There is no way to fix this. We had the same issue and had to wait until ID reset. Then we used the ID of a character that was not affected by this and continued our progress.
OMG. There are one or two weeks left before prepatch and we may loose 3 days?
Hope not!
We spent so much time last month, just found enough people from non-popular servers, we have some progress last days and now we will loose this week?
Maybe there is a chance to contact ingame GM to fix this?
There might be only a couple of myth raider groups on these servers there shouldn’t be much work to fix this.
Please, somebody help!
im afraid not, its a side-effect how the servers work and specificially how they interact with mythic lockouts in which your lockout is tied to your ingame characters GUID, for a connection to work, both realms that are connected need to share the same ID and to do that one of the 2 ID`s will be deleted, when the server ID changes due to a realm database merge, so does your ingame characters GUID which is the cause of the broken lockout.
The realm connections are announced in advance though and from those announcements it is pretty clear which realms will be affected by this and if you are on one of those realms the best course of action would probably be forgoing that wednesday raid and moving it to friday, I understand its frusterating and if i had to be totally honest it would be good if blizzard communicated this better since you for sure arent the first it has happened to, but its bound to happen with realm connections, i dont think thats avoidable.
1 Like