Author | Message | Time |
---|---|---|
iNsaNe | Hey guys, I'm having a bit of trouble with accepting / sending arranged team invites. (https://davnit.net/bnet/vL/index.php?topic=6205.0) I have made the bot so that it can invite players and accept invites, but every time the bot accepts an invite or the user accepts the bot's invite I get the error from battle.net: "The team game you attempted to join could not be found..." and the inviter gets the firewall message. I'm sending the port (e0 17, 6112) which I use to connect my bot with. I also use that same port with Warcraft 3. Any help would be appreciated | October 21, 2007, 11:41 PM |
BreW | [quote author=iNsaNe link=topic=17126.msg174059#msg174059 date=1193010067] I'm sending the port (e0 17, 6112) which I use to connect my bot with. I also use that same port with Warcraft 3. [/quote] This is a completely wild guess, and I've never worked with this packet before, but aren't you supposed to htons() the port ? | October 21, 2007, 11:49 PM |
iNsaNe | I'm not sure, this is the first time I've worked with this packet as well. In the packet logs I've seen e0 17 a bunch so I don't think you have to | October 21, 2007, 11:50 PM |
-MichaeL- | are you sending the packet in UDP? i think it should be sent in UDP not TCP. i could be wrong. | October 21, 2007, 11:54 PM |
Myndfyr | [quote author=-MichaeL- link=topic=17126.msg174062#msg174062 date=1193010857] are you sending the packet in UDP? i think it should be sent in UDP not TCP. i could be wrong. [/quote] Warcraft 3 uses TCP. | October 22, 2007, 12:19 AM |
iNsaNe | im noticing something different when im packet logging. When you are in the "Arranged Team Lounge" (lol) the packet headers begin with f7 instead of ff. Am i wrong? Instead of replying with a normal ff 63 do i reply with an f7 1e? they seem to have the same structure f7 1e is just like: [code](DWORD) Cookie (DWORD) Host random token value? (BYTE) 0 (WORD) Host port (DWORD) not sure (STRING) Host name (DWORD) not sure (DWORD) not sure (DWORD) 5 (DWORD) 0 (BYTE) 0[/code] laugh at me if you want, im no researcher. | October 22, 2007, 1:41 AM |
squiggly | 0xF7 begins the WC3 in-game header, just as 0xFF does for BNCS messages the structure is similar to BNCS, [code] (BYTE) 0xF7 (BYTE) Message ID (WORD) Message length (including header) (VOID) Message Data[/code] | October 22, 2007, 2:51 AM |
UserLoser | Do you have a TCP socket setup listening and accepting incoming connections? If not, that may be why it says "game not found" | October 22, 2007, 6:30 PM |
unTactical | [quote author=iNsaNe link=topic=17126.msg174065#msg174065 date=1193017310] f7 1e is just like: [code](DWORD) Cookie (DWORD) Host random token value? (BYTE) 0 (WORD) Host port (DWORD) not sure (STRING) Host name (DWORD) not sure (DWORD) not sure (DWORD) 5 (DWORD) 0 (BYTE) 0[/code] [/quote] The last 16 bytes are a sockaddr_in struct that you will need to pass on to any clients (via 0xF706) if you are the game host. | October 22, 2007, 7:06 PM |