Author | Message | Time |
---|---|---|
tronico | back in september 2008 the blizz servers went down for some hours and when they were up again my namebot couldnt connect anymore. each time i try to connect it i get 5 min realm down. i guess this is because they updated something serverside? anyone knows what blizz did change back there? | January 26, 2009, 7:11 PM |
Sveet | probably would help to explain what your bot did, so we could figure out what might have changed...... probably just a verbyte. | January 26, 2009, 8:21 PM |
tronico | well its a diablo 2 namebot which creates charnames ^^. its still using the bnetauth.dll. and no the verbyte is correct. it was working fine till blizzard did some maintenance (no new patch or anything) | January 26, 2009, 9:19 PM |
vector | What part in the login sequence does the bot fail? It would be helpful to know this information, as you can pinpoint which part battle.net changed. | January 26, 2009, 9:56 PM |
tronico | hm. [12:48:44,770] Connecting.. [12:48:45,270] Connected [12:48:45,330] You should never get this error. [12:48:45,330] Disconnected. after that im getting 5 min RD. is there any tool which shows the packets im sending? so i could see after what packet im getting RD. also are there any other bots which are using bnetauth.dll and still work? | January 27, 2009, 11:51 AM |
vector | In your packet buffer, place an AddChat after each packet is about to be sent. Ex: [code] Private Sub SendPacker(ByVal PacketID As Byte) AddChat vbYellow, "Send packet 0x" & Hex(ID) ... End Sub [/code] Something like that. | January 27, 2009, 3:35 PM |
fataly | Can i see your packet log and codes ? | January 28, 2009, 2:59 PM |