NEW Packet Structures

[Grob]

Sure Juapillo, just don't forget that a 0 represents the first byte in both my examples (LongToByte( 31320, 0 )

BYTE LongToByte( DWORD dwValue, int nCount ) {
    BYTE ret;
    ret = (dwValue >> (nCount*8)) & 0xFF;
    return ret;
}

I guess you could just add a -1 if you want to use LongToByte( 31320, 1 ); where 1 is the first byte:

BYTE LongToByte( DWORD dwValue, int nCount ) {
    BYTE ret;
    ret = (dwValue >> ((nCount-1)*8)) & 0xFF;
    return ret;
}

About ASM I'm not sure since I can't try it atm. You could probably just add a sub command:

LongToByte proc szValue:DWORD,nCount:DWORD
    lea eax,szValue ; Set eax to the address of szValue
    sub nCount,1 ; Since people are lazy, subtract 1 from nCount which makes 1 the least possible action
    add eax,nCount ; We add nCount to eax (if nCount is 1 we will return the first byte of the dword)
    movzx eax,byte ptr [eax] ; We move a byte into the 32-bit register using movzx. eax will now hold the correct byte
    ret ; Return eax which holds the correct byte to the application calling this function
LongToByte endp

It all just seems so unecessary to force the computer to do another command just because people rather write 1 instead of 0.

[CooPs]

Convert the string length to a 16b Integer and then insert the high and low order parts. Should look something like this?
short strLen = str.length();
byte lowByte = strLen & 0xFF; //Bitwise AND with 0000000011111111
byte highByte = strLen >> 8; //Bitwise left shift with 8 bits

Edit: I'm way to slow replying.

[Grob]

Juapillo: If you want to continue with the standard of having LongToByte( x, 1 ) as first byte you should use the ASM code that has sub nCount,1 in it.

[Juapillo]

thanks grob

coops, i don't understand your code :S

[CooPs]

Then I supposed you don't understand how Grob's code work either. The only difference is that he packed it in a function that you can just copy in and use. If you look closely you will realize that.

The lowByte would contains what had been returned by LongToByte(strLen,1) and highByte = LongToByte(strLen,2).

[Juapillo]

oh, that's right, i didn't notice bout that
always.. i prefert the LongToByte function because i won't have to put much comments

[CooPs]

okay, it can be good to know what the functions you use actually do and why

[OsQu]

I can notice, that the level of programming skills is rising in TProgramming! That's really nice!

@Juapillo: For beginneers those packet structures can be a bit misleading.. At least they were for me at start. Maybe if you could post whole function (I suppose that you're using functions right) with declarations so it makes clearier image..

[mCsis]

@Juapillo: For beginneers those packet structures can be a bit misleading.. At least they were for me at start. Maybe if you could post whole function (I suppose that you're using functions right) with declarations so it makes clearier image..

YES YES YES Agree in 100%
To every packet structure there shloud be a sample.

[Grob]

The only things I find hard to understand are things like

    packetBuffer(10) = LongToByte(Standing, 1) 'Stack Position
    packetBuffer(11) = LongToByte(BackPacks, 1) 'Slot where you wanna open your backpack

What Standing and BackPack holds is a mystery, brief explanations on variables like these would be great for people who's just starting out.

For example, if there's an item beneith the rotwom, should Standing be 0 or 1?

Oh and Juapillo, it never hurts to hear it too many times; you're doing a great job.