Help With 0x7A

[ChR0NiC]

Code Select Expand


Packet ID: 0x7A
Direction: Client -> Server (Sent)
Format:
(DWORD)       Cookie
(STRING[])    Target User
(BYTE)       Rank
Remarks: This message is sent when change rank of a member in clan, only shaman or chieftain can send this packet

Possible values for Rank:

0x00: Peon, Initiate that has been in the clan for less than one week
0x01: Peon, Initiate that has been in the clan for over one week
0x02: Grunt
0x03: Shaman
0x04: Chieftain


This is what I am doing below

Code Select Expand


With pBuffer
   .InsertDWORD &H0
   .InsertNTString frmMain.W3Clan.SelectedItem.text
   .InsertBYTE &H2
   .SendPacket frmMain.sckBnet, &H7A
End With


The current user I am selecting is a Peon (Over One Week) And I am attempting to promote him to Grunt.....

Anyone have any suggestions???

Edit: Oh, and the problem I am having.....is that is disconnects me, not IP Ban but it disconnects me. So yeah....and it's not promoting as well...

[UserLoser.]

Always use a Null terminated string unless it says otherwise. Especially if it's STRING[] - That's probably an array of strings and otherwise how else the server wouldn't know where to separate the strings for accounts if there was no Null terminator in there

[Stealth]

Code Select Expand

(STRING[])    Target User


This implies a null-terminated stringlist.

Code Select Expand

.InsertNonNTString frmMain.W3Clan.SelectedItem.text

That's not null-terminated.

[ChR0NiC]

This implies a null-terminated stringlist.
That's not null-terminated.

-.-

Little help then -_-

[UserLoser.]

This implies a null-terminated stringlist.
That's not null-terminated.

-.-

Little help then -_-

Here's a hint: You use Null terminated strings when sending chat messages

[ChR0NiC]

This implies a null-terminated stringlist.
That's not null-terminated.

-.-

Little help then -_-

Here's a hint: You use Null terminated strings when sending chat messages

In other words......InsertNTString
aka String & Chr(0)
right??

[Eli_1]

yes, that would be a string terminated with a null char  

[ChR0NiC]

yes, that would be a string terminated with a null char  

Spare me your smart ass remarks ??

Any other problems That you could point out ??

*leans toward UserLoser and Stealth*?

[o.OV]

yes, that would be a string terminated with a null char  

Spare me your smart ass remarks ??

Any other problems That you could point out ??

*leans toward UserLoser and Stealth*?

You asked.. he answered.

[Arta]

Whoever invented the idea of a 'NonNTString' should be strung up. There's no such thing. Hasn't anyone ever noticed that these so-called NonNTStrings are always 4 bytes long? They're DWORDs. They just happen to look like strings.

[ChR0NiC]

Whoever invented the idea of a 'NonNTString' should be strung up. There's no such thing. Hasn't anyone ever noticed that these so-called NonNTStrings are always 4 bytes long? They're DWORDs. They just happen to look like strings.

........

[effect]

Spare me your smart ass remarks ??

Then stop expecting everything to be served to you on a silver platter.

[Kp]

Whoever invented the idea of a 'NonNTString' should be strung up. There's no such thing. Hasn't anyone ever noticed that these so-called NonNTStrings are always 4 bytes long? They're DWORDs. They just happen to look like strings.

Actually, the ability to insert data of type void is quite useful for dumping in binary objects, such as the password hash.  Of course, NonNTString is a rather stupid name for such an operation.  The operation itself is useful though.

[ChR0NiC]

Then stop expecting everything to be served to you on a silver platter.

Hush NuLL, you always gotta throw in your two cents worth -.-

[Arta]

Whoever invented the idea of a 'NonNTString' should be strung up. There's no such thing. Hasn't anyone ever noticed that these so-called NonNTStrings are always 4 bytes long? They're DWORDs. They just happen to look like strings.

Actually, the ability to insert data of type void is quite useful for dumping in binary objects, such as the password hash.  Of course, NonNTString is a rather stupid name for such an operation.  The operation itself is useful though.

Well, sure. All my typed add functions are overloaded and call a function which takes a void*. I doubt that's what whoever made it had in mind though, people tend to add password hashes as individual DWORDs.