This issue is caused by having multiple clients logging in on different realms in a short timeframe.
Client #2 will switch realm right after client #1 checked if currently selected realm is correct.
When doing so client #2 will have set the current realm across all clients (registry) thereby causing client #1 to login to the wrong realm even if the currently selected realm seemed correct.
Two or three ways to fix this :
- Check the login packets to get me.realm before being in char screen
- Disable clients from editing registry or using registry for info to send for login
- have a sep value saved for currently selected realm aside from me.realm
This issue is caused by having multiple clients logging in on different realms in a short timeframe.
Client #2 will switch realm right after client #1 checked if currently selected realm is correct.
When doing so client #2 will have set the current realm across all clients (registry) thereby causing client #1 to login to the wrong realm even if the currently selected realm seemed correct.
Two or three ways to fix this :