BattleNet Module System (3.3.5a)

[stoneharry]

I am attempting to make some progress at emulating the battle.net authentication system in the 3.3.5a (12340) WoW client.

So far I have managed to obtain a large range of documentation regarding the subject from people emulating the process for Diablo 3 and SC2. The WoW protocols appear to follow almost the exact same structure, which has allowed me to reach the login proof stage.

However, sending the two modules from SC2, D3, or a higher WoW patch results in the client knowing that it is connecting to the wrong game server and failing the login proof stage of authentication.

So my question is regarding the module system in the 3.3.5a WoW client and if anyone has some information on it? I cannot find anything on google regarding the way WoW works. It notes on this website (bnet2_protcol [DarkBlizz.org SC2 Wiki]) that "Ralek and Kynox firstly contributed with the auth sequence reversed from wow." It is clear that I am not the only person to experiment with this procedure, so does anyone know the correct structure for these two modules to send?

The process I have used to achieve my current situation is:

• Change Battle.net.dll to point to my server
• Listen on port 1119 for battle net packets
• Handle the InformationRequest packet
• Fail at sending the modules in LoginProof response

Thanks,
Harry

edit: Some progress! http://www.ownedcore.com/forums/worl...d-modules.html (3.3.5 - Streamed Modules) Still seems quite confusing. Any further documentation = <3.

[BoogieManTM]

i had a full client side implementation working for my clientless bot (based on Kynox & Ralek's work)

See: WoW Clientless/Headless Bot Framework / SVN / [r1] /battlenet

[jjaa]

You could also take a look at starcrack. It would be outdated. But it may provide some information.

https://bitbucket.org/Greatwolf/starcrack/src