-
Notifications
You must be signed in to change notification settings - Fork 42
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
Two issues: Bot hangs on startup, as well as "game version is too old".. Sometimes? #76
Comments
I have the exact same issues. At first I was able to host on 2 bnet servers (the 2 others didnt work) then only a single one worked. Additionally i get the same issue when the bot tries to reconnect (since the connection dies at night i think). |
To both: on which OS does this happen? |
@Josko not sure if related but on gproxy, I debugged custom_exeversionhash on 1.29 version and it changed every time I run it (don't know why). With that hash I tried running old ghost to connect to 1.29 and like 9/10 times it says game version is too old, disconnecting while 1/10 it logs in successfully. Not sure if reconnect tries to connect with same hash as before, but might need to recalculate it |
@Josko Windows 10 Pro. I looked at that page before but felt it didn't quite precisely represent my issue. |
@Josko was on Ubuntu 16.04 |
I can confirm the "game version is too old" error my bot disconnects randomly then trying to reconnect says "game version is too old". Using Ubuntu 16.04 as well. |
Sometimes when I launch the bot, it'll hang somewhere in this process and not continue.
And sometimes, I connect to certain servers but not others.
[BNET: USEast] connecting to server [useast.battle.net] on port 6112
[BNET: USEast] resolved and cached server IP address 199.108.55.57
[BNET: USWest] connecting to server [uswest.battle.net] on port 6112
[BNET: USWest] resolved and cached server IP address 12.129.236.19
[BNET: Asia] connecting to server [asia.battle.net] on port 6112
[BNET: Asia] resolved and cached server IP address 121.254.164.19
[BNET: Europe] connecting to server [europe.battle.net] on port 6112
[BNET: Europe] resolved and cached server IP address 5.42.181.18
[BNET: USEast] connected
[BNET: USWest] connected
[BNET: Europe] connected
[BNET: USEast] attempting to auth as Warcraft III: The Frozen Throne
[BNET: Asia] connected
[BNET: USWest] attempting to auth as Warcraft III: The Frozen Throne
[BNET: USEast] cd keys accepted
[BNET: Europe] attempting to auth as Warcraft III: The Frozen Throne
[BNET: USEast] username [---] accepted
[BNET: USEast] using battle.net logon type (for official battle.net servers only)
[BNET: USEast] logon successful
[BNET: USEast] joining channel [The Void]
[BNET: USWest] cd keys accepted
[BNET: Europe] logon failed - game version is too old, disconnecting
[BNET: USWest] username [---] accepted
[BNET: USWest] using battle.net logon type (for official battle.net servers only)
[BNET: Europe] disconnected from battle.net
[BNET: USEast] joined channel [The Void]
[INFO: USEast] This channel does not have chat privileges.
[WHISPER: USEast] [# Email Service #] Note: Email on record is [---]
[BNET: Asia] attempting to auth as Warcraft III: The Frozen Throne
[BNET: USWest] logon successful
[BNET: USWest] joining channel [The Void]
[BNET: Asia] logon failed - game version is too old, disconnecting
[BNET: Asia] disconnected from battle.net
[BNET: USWest] joined channel [The Void]
[INFO: USWest] This channel does not have chat privileges.
[WHISPER: USWest] [# Email Service #] No email on record. You must first set an email by using the command /set-email [email]
(End; --- is inserted for privacy purposes)
Attempting to launch the bot a few more times, it finally finished executing everything, AND connected to all 4 servers, however it then hung again.
I will note that it sometimes will finish starting and get in-game to the point where it will accept and respond to commands, but it doesn't connect to all the servers.
One time it even got to the point where I hosted a game (only worked on 2 servers,) and other people joined it, but then the bot hung and I couldn't join.
Unusable at this point in time.
The text was updated successfully, but these errors were encountered: