Quick Question

[R.a.B.B.i.T]

(DWORD)       Cookie
(STRING)       Clan name
(DWORD)       Clan tag
(BYTE)       Number of users to invite
(STRING[])    Usernames to invite

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.

[UserLoser.]

(DWORD)       Cookie
(STRING)       Clan name
(DWORD)       Clan tag
(BYTE)       Number of users to invite
(STRING[])    Usernames to invite

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.

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?

[R.a.B.B.i.T]

I don't know, but I've seen some crazy strings in some of my logs.  Thanks, though.

[Soul Taker]

AFAIK, there isn't such a thing as a non-NT STRING.  They have a seperate definition  

[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.

[Eli_1]

IIRC, there's no such thing as a non-null-terminated string.

[Adron]

IIRC, there's no such thing as a non-null-terminated string.

Non-null-terminated strings have been mentioned here. Strings without terminating nulls are common.

[Arta]

They're DWORD constants...

[Adron]

In the general case, they exist. One example is pascal strings. In b.net protocols, strings are typically null-terminated.

[Arta]

Right. They're not common on Battle.net

[R.a.B.B.i.T]

But they're still there

[tA-Kane]

But they're still there

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.

[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 Select Expand

Insert( (DWORD)'IX86' ); //Platform ID

[R.a.B.B.i.T]

4 character NonNTStrings, DWORDS, all the same.  I was probably wrong, but whatever.

[Adron]

Check client to client udp communication for fixed length strings? Or perhaps that's D2?