| Author | Message | Time |
|---|---|---|
| R.a.B.B.i.T | [quote](DWORD) Cookie (STRING) Clan name (DWORD) Clan tag (BYTE) Number of users to invite (STRING[]) Usernames to invite[/quote] Should the strings in 0x71 (SID_INVITEMULTIPLEUSERS) be NT or not? I can't log this, I lost my discs, so I'd appreciate if someone could help. | June 8, 2004, 3:51 AM |
| UserLoser. | [quote author=R.a.B.B.i.T link=board=17;threadid=7146;start=0#msg64085 date=1086666693] [quote](DWORD) Cookie (STRING) Clan name (DWORD) Clan tag (BYTE) Number of users to invite (STRING[]) Usernames to invite[/quote] Should the strings in 0x71 (SID_INVITEMULTIPLEUSERS) be NT or not? I can't log this, I lost my discs, so I'd appreciate if someone could help. [/quote] Strings are always null terminated when it comes to Battle.net packets! If they were not null terminated, how would Battle.net know when to split up the data for each username? | June 8, 2004, 3:52 AM |
| R.a.B.B.i.T | I don't know, but I've seen some crazy strings in some of my logs. Thanks, though. | June 8, 2004, 3:56 AM |
| Soul Taker | AFAIK, there isn't such a thing as a non-NT STRING. They have a seperate definition :P | June 8, 2004, 10:54 AM |
| R.a.B.B.i.T | They are strings that don't have a null at the end..there, I defined NonNTString. I know they are different, but I am using DM's buffer class. | June 9, 2004, 12:38 AM |
| Eli_1 | IIRC, there's no such thing as a non-null-terminated string. | June 9, 2004, 12:53 AM |
| Adron | [quote author=Eli_1 link=board=17;threadid=7146;start=0#msg64264 date=1086742428] IIRC, there's no such thing as a non-null-terminated string. [/quote] Non-null-terminated strings have been mentioned here. Strings without terminating nulls are common. | June 9, 2004, 1:27 AM |
| Arta | They're DWORD constants... | June 9, 2004, 8:04 AM |
| Adron | In the general case, they exist. One example is pascal strings. In b.net protocols, strings are typically null-terminated. | June 9, 2004, 10:01 AM |
| Arta | Right. They're not common on Battle.net :P | June 9, 2004, 11:04 AM |
| R.a.B.B.i.T | But they're still there ;) | June 10, 2004, 2:27 AM |
| tA-Kane | [quote author=R.a.B.B.i.T link=board=17;threadid=7146;start=0#msg64445 date=1086834472]But they're still there ;)[/quote]Can you show me one example of a real NonNTString in the BNCS protocol? Product (STAR, SEXP, WAR3, CHAT, etc) and Platform (IX86, PMAC, XMAC (and etc?)) IDs are not NonNTStrings, nor are Country Codes (USA and etc). Clan tags are also not NonNTStrings, they're actually DWORDs as well. | June 12, 2004, 5:50 PM |
| Zakath | Yes, I'm not aware of a single example of a "non-NT string" on battle.net that isn't actually a DWORD. The binary connection classes I've written have never had, nor needed, a method for adding a "non-NT string" to the output buffer. It's all VB's fault! If it actually supported the ability to change how you process a data type... [code]Insert( (DWORD)'IX86' ); //Platform ID[/code] | June 13, 2004, 2:27 AM |
| R.a.B.B.i.T | 4 character NonNTStrings, DWORDS, all the same. I was probably wrong, but whatever. | June 13, 2004, 3:29 AM |
| Adron | Check client to client udp communication for fixed length strings? Or perhaps that's D2? | June 13, 2004, 11:47 PM |
| UserLoser. | [quote author=tA-Kane link=board=17;threadid=7146;start=0#msg64856 date=1087062603] [quote author=R.a.B.B.i.T link=board=17;threadid=7146;start=0#msg64445 date=1086834472]But they're still there ;)[/quote]Can you show me one example of a real NonNTString in the BNCS protocol? Product (STAR, SEXP, WAR3, CHAT, etc) and Platform (IX86, PMAC, XMAC (and etc?)) IDs are not NonNTStrings, nor are Country Codes (USA and etc). Clan tags are also not NonNTStrings, they're actually DWORDs as well. [/quote] Never knew that the Country abreviation should be treated as a DWORD, but I checked old Battle.snp because I was curious...: [pre] .text:19017014 push offset aReq_countryabr ; " req.countryAbreviation = 0x%08X" [/pre] | June 14, 2004, 12:08 AM |