Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

realm login switching between clients #34

Open
laztheripper opened this issue Aug 28, 2019 · 4 comments
Open

realm login switching between clients #34

laztheripper opened this issue Aug 28, 2019 · 4 comments

Comments

@laztheripper
Copy link

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
@jmichelsen
Copy link

I encountered the same issue and solved it by removing the skiptobnet from profiles. With that change, each profile will select their realm when launching

@laztheripper
Copy link
Author

laztheripper commented Feb 23, 2020

If it did then you don't understand the issue. I never used skiptobnet nor does anyone else who has the issue I'm talking about.

@jaenster
Copy link
Contributor

This can be closed as it's fixed with D2bot#'s way to patch the game, using

{"Name": "realmfix", "Version":"1.14d","Module":14,"Offset":1146576, "Data": "ww=="}

This is an annoying way to fix it, as it simply doesnt store any realm information upon/or after connection, solving the issue of the timing issue you describe

@laztheripper
Copy link
Author

In theory, gaw says it doesn't work. Still waiting on more feedback. Could just be user error though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants