[Problem] Cannot read the ChangeDirection

Patch 5165.
[table="head"]Offset | Type | Value
0 | ushort | Length [0x24]
2 | ushort | Type [0x271A]
20 | byte | Direction [206]
This Direction is wrong, I keep receiving the same direction, but it should be below 8 in all cases.
It doesn't even change, whichever direction I pick.
Anyone has ideas.
Also don't tell me I should do this: Input[22] % 8 because this will give me a Direction below 8, but the same one every time.

Unbelievable I'm having trouble with changing the direction o_o

Which patch are you using? I know that for newer ones the structure changed. I tried using the wiki when I was doing mob directions for my proxy and was super confused lol.

I'd strongly suggest simply printing out or writing to a text file when you receive it from the client, then see which offset is changing, confirm it's under 8 and go with that. I'm positive you'll find it easily enough.

<edit>

Wow... if I was any less blind I'd have noticed that you said 5165. gimme 2 sec

Quote:

Originally Posted by Basser Patch 5165. [table="head"]Offset | Type | Value 0 | ushort | Length [0x24] 2 | ushort | Type [0x271A] 20 | byte | Direction [206] This Direction is wrong, I keep receiving the same direction, but it should be below 8 in all cases. It doesn't even change, whichever direction I pick. Anyone has ideas. Also don't tell me I should do this: Input[22] % 8 because this will give me a Direction below 8, but the same one every time. Unbelievable I'm having trouble with changing the direction o_o

Then do

for(int count = 0; count < Length; count++)
if(Buffer[count] < 8)
Console.WriteLine(count + "~" + Buffer[count]);

Try more than once and make sure you know the number for the direction you just changed to, then take out all possibilities till you found the right offset.

btw, count "~" + buffer[count] <-> offset ~ value

Try a byte at offset 22.
It's what I use, but mind you its a bit newer =P

Edit:
And if that doesn't work, just dump the packet

Quote:

Originally Posted by kinshi88 Try a byte at offset 22. It's what I use, but mind you its a bit newer =P Edit: And if that doesn't work, just dump the packet

OR do what I already said which works 100%.

Quote:

Originally Posted by -impulse- OR do what I already said which works 100%.

But that's ugly =P

Quote:

Originally Posted by kinshi88 But that's ugly =P

Well, that's the fastest way and it works very well in most cases.

Idk what people use, but that's what I use and if someone has a better, faster method, please don't hesitate to tell me.

Ah, about my method being ugly, I don't care if it's ugly or pretty, all I care is about the results.

Quote:

Originally Posted by -impulse- Well, that's the fastest way and it works very well in most cases. Idk what people use, but that's what I use and if someone has a better, faster method, please don't hesitate to tell me. Ah, about my method being ugly, I don't care if it's ugly or pretty, all I care is about the results.

<3

I like pretty code =P

Quote:

Originally Posted by kinshi88 <3 I like pretty code =P

Pretty code doesn't always mean good results. <3

Quote:

Originally Posted by -impulse- Pretty code doesn't always mean good results. <3

In the long run it does; easier debugging, easy to understand, and pretty code is usually damn efficient =P

Quote:

Originally Posted by kinshi88 In the long run it does; easier debugging, easy to understand, and pretty code is usually damn efficient =P

Hmm this thing is not for 'long run', it was all for finding an offset, which by my guess is a pretty short run.

Anyway, I agree with you, on long run I use pretty code too <3

Just do 3 or 4 general data packet dumps and post them here in hex.

Edit:

Direction is stored at offset 22 in 5165.

Quote:

Originally Posted by -impulse- Hmm this thing is not for 'long run', it was all for finding an offset, which by my guess is a pretty short run. Anyway, I agree with you, on long run I use pretty code too <3

Yush

<3

Quote:

Originally Posted by kinshi88 Yush <3

Not commenting on the immaturity readen so far. However, 'pretty code' or clean code as I prefer to call it is indeed easier for debugging and organization is one of the steps to write a successfull source, not necessarily. Though commenting on other programmer's coding style is totally wrong, everybody prefers his own methods and 'programming style'.

Quote:

Originally Posted by InfamousGeek Not commenting on the immaturity readen so far. However, 'pretty code' or clean code as I prefer to call it is indeed easier for debugging and organization is one of the steps to write a successfull source, not necessarily. Though commenting on other programmer's coding style is totally wrong, everybody prefers his own methods and 'programming style'.

Yeah, I was just stating my opinion =P