Packet 0x4A

[UserLoser]

Is this something new?  I've never seen it before, Battle.net is sending this after they send back packet 51...What is it for?

.J..IX86ExtraWork.mpq.

 

[Banana fanna fo fanna]

It's the new packet to confuse h4x0rZ.

[Zakath]

Lol. This is the packet that's related to the "Send Blizzard your info" stuff that's been in every recent patch. It hadn't been activated for a while, I guess (I gathered from talking to Sky that it is only sometimes enabled on the server).

As a bot-author, you don't seem to need to do anything with it. Just handle it and ignore it.

[Yoni]

As a bot-author, you don't seem to need to do anything with it. Just handle it and ignore it.

IIRC, BinaryChat handles it and sends the server fake info. But it was buggy and got me IP-banned one day, so...

[18:00:39] - D:\Misc\Battle.net\BinaryChat\KillExtraWork.bcp

Oh well

[UserLoser]

If it is sending the server info...How might it be getting away from appearing on my packet logger? (WPE PRO if it that matters...)

[Zakath]

Obviously if you have your Blizzard clients set to not send your info, and you don't do anything in response to packet 0x4a with your bot, you WON'T be sending any info, and thus there is nothing to show up on your packet logger.

[haZe]

This new packet is part of the new 1.05a patch, used to stop No-CD cracks.

[Zakath]

No, it isn't. Packet 0x4a isn't "new." It was inactive for a while. Skywing already tested (through disassembly, etc) what the ExtraWork MPQs do - they are responsible for sending Blizzard your system info if you elect to allow it.

Packet 0x4a is being sent to every client, btw, not just War3. I had to handle it for my bot (which does all it's hashing locally and thus has no War3 support). I normally log in via D2XP.

[Yoni]

This new packet is part of the new 1.05a patch, used to stop No-CD cracks.

Umm? That's totally incorrect, where'd you get that?

[haZe]

heh, I read on a site ( www.pvpgn.org ) that they made a new patch and I figured the new MPQ/Packet was part of the patch.

[tA-Kane]

Packet 0x4a is being sent to every client.

At what point is it being sent to the clients? I've never seen it on any of my logs, and my bot has never given me a message of "Unnsupported packet received! ID=4A" (and my bot doesn't yet support 0x4A, so if it encountered the packet, it would display that message and then save the packet data to a file).

[SA-Theoden]

I've never, ever dealt with this packet. Mainly because after I found out how to log on Starcraft, I was set

Logging on War3 to me is pointless, I design bots for my clan, however, D2XP does look quite appealing

Back to the 0x4A packet, pretend when your logging on, you have a checkbox to accept it and reply to it or not, just like in the patch. If you dont check it, you ignore it, if you do check it, you need to be prepared to send different information every time(Like that one guy said he got IP banned alot). Sending the same info multiple times in the same day leads to getting IP banned(part of the anti-bot security system in Battle.net).

Anyways, I may be exactly wrong, but from what my experience(by word of mouth) with this packet dictates is what I just said above.

-Theoden

[tA-Kane]

Or perhaps, you should just know how the 0x4A response is constructed, and conform to that knowledge?

[Zakath]

At what point is it being sent to the clients? I've never seen it on any of my logs, and my bot has never given me a message of "Unnsupported packet received! ID=4A" (and my bot doesn't yet support 0x4A, so if it encountered the packet, it would display that message and then save the packet data to a file).

Hmm...is this not being sent to Macs perhaps? I first noticed it because I hadn't been handling 0x4a, then I started getting "Unhandled packet received!" notifications every time I logged on. I quickly isolated and fixed the problem, but I'm suprised it hasn't happened to you...

[tA-Kane]

My bot uses IX86 for the product ID.