| Author | Message | Time |
|---|---|---|
| Godzilla | Am I able to send BNLS_CDKEY (0x01) to bnet right after receiving 0x50 without breaking the logon? (using war3)Example: [code] Send Protocol Byte (1) Send 0x50 Receive 0x25 Receive 0x50 Send 0x25 (Optional) Send 0x01 (BNLS_CDKEY) <--- Receive 0x01 (BNLS_CDKEY) <--- Send 0x51 Receive 0x51 Send 0x53 Receive 0x53 Send 0x54 Receive 0x54 Send 0x45 Send 0x0A [/code] | April 19, 2007, 8:10 PM |
| Barabajagal | Battle.net does not expect packets in any exact timeframe (within timeout limitations). BNLS is a different connection to a different server, so it doesn't touch BNet at all. | April 19, 2007, 8:21 PM |
| Godzilla | So it doesn't affect the logon... ? | April 19, 2007, 8:26 PM |
| dlStevens | He said no.... | April 19, 2007, 8:42 PM |
| HdxBmx27 | You should be fine: Connect to BNET BNET C->S: Protocol Byte (1) BNET C->S: 0x50 BNET S->C: 0x25 BNET C->S: 0x25 BNET S->C: 0x50 Connect to BNLS BNLS C->S: 0x0D BNLS S->C: 0x0D BNLS C->S: 0x01 BNLS S->C: 0x01 BNLS C->S: 0x1A BNLS S->C: 0x1A BNET C->S: 0x51 BNET S->C: 0x51 BNLS C->S: 0x02 BNLS S->C: 0x02 BNET C->S: 0x53 BNET S->C: 0x53 BNLS C->S: 0x03 BNLS S->C: 0x03 BNET C->S: 0x54 BNET S->C: 0x54 Disconnect from BNLS BNET C->S: 0x0A BNET C->S: 0x0B BNET C->S: 0x0C BNET S->C: 0x0A BNET S->C: 0x0B <Crapload of BNET S->C: 0x0F's> Off the top of my head, thats the order you should be going in to use BNLS for everything. (Which I don't recomend, use BNCSutil.dll for cdkey/password stuff) ~Hdx | April 19, 2007, 8:43 PM |