If the bot fails between logging in and game creation it seems to run into problems. Some failures seem to be handled (cdkey in use, cdkey banned, etc) by killing d2 and trying again. If i run into these though, it appears to stay at that screen indefinately until i kill it myself.
But other issues I have is I get:
1) "The cdkey you are currently using is disabled for REALM PLAY" at the character select screen (not a banned key at the bnet login screen). (my biggest problem)
2) "please wait" after selecting a character, but it never goes anywhere (should have a time out).
3) "loading" at the character select screen, list of characters never appears, so it can never select a character.
4)"Unable to connect to realm server" (not an R/D, just lag)
The "easy" solution would be to put in a timeout for creation of the first game after opening Diablo2. For example: if a game isnt created within 60 seconds of diablo 2 being opened, then kill the process and try again.
Logged In: YES
user_id=2135523
Originator: YES
Forgot this one:
5) "Connecting to server" or "Waiting for response" on bnet login screen, where it never goes to the next step (rain-13 was having issues with that too)
Logged In: YES
user_id=2101395
Originator: NO
i'll look into this. i changed it to close if it can't reach the login part. but i think i pushed it to not reach the char selection.
but i'll validate to see how it handle not able to create the game
Logged In: NO
I haven't been getting any of these problems in a while, so ya it looks like you fixed it (good job :-D).
Logged In: YES
user_id=193557
Originator: NO
I'm still getting the Connecting... at char screen when Redvex has apparently stopped responding, but AO or 3rd party restarter doesn't know it.