Let's talk about the recent patch and changes

[Ulfius]

Originally Posted by high6

It has already been posted in this thread...

I've reread the thread and do not see that anyone has posted something that works. 0x013A8468 does not work for me and I do not get an address in the 640000-64FFFF range for CharName.

Edit: Are you referring to this?
"All I am going to say is that the name has a start ptr followed by an end ptr in the Role structure"

[high6]

Originally Posted by Ulfius

I've reread the thread and do not see that anyone has posted something that works. 0x013A8468 does not work for me and I do not get an address in the 640000-64FFFF range for CharName.

Edit: Are you referring to this?
"All I am going to say is that the name has a start ptr followed by an end ptr in the Role structure"

The person who posted it miss named it and called it the mob name address when really it is the Role name address.

[32991304]

0o , why high6 got banned 0o

[Alexios]

Originally Posted by 32991304

0o , why high6 got banned 0o

yeah and after that, I think, he hacked elitepvpers

[clintonselke]

Originally Posted by Alexios

yeah and after that, I think, he hacked elitepvpers

I don't think he did... It might have something to do w/ his "WDB File Structure (ripping in progress)" (in his blog) that suddenly disappeared after he was banned.

[Ulfius]

Originally Posted by high6

The person who posted it miss named it and called it the mob name address when really it is the Role name address.

That was the missing piece of the puzzle that I needed.

[clintonselke]

some warnings i got PMed about

maybe i'm just paranoid but have a look.

0058CE7C  CALL DWORD PTR DS:[<&KERNEL32.GetCurrent>kernel32.GetCurrentProcessId

004AB5AB  CALL DWORD PTR DS:[<&KERNEL32.GetCurrent>kernel32.GetCurrentThreadId

004A1FF9  CALL DWORD PTR DS:[<&KERNEL32.ReadProces>kernel32.ReadProcessMemory

004A1C82  CALL ESI                                 kernel32.WriteProcessMemory

004A201C  CALL DWORD PTR DS:[<&KERNEL32.WriteProce>kernel32.WriteProcessMemory

I was warned that they might have installed code cave checks now.

[Ulfius]

What bots/tools are using codecaving? Chinese ones?

[clintonselke]

Originally Posted by Ulfius

What bots/tools are using codecaving? Chinese ones?

mine xD

[ookamocka]

sup clint, i've been away from coding... actually i've been away from CO entirely for the past ~month... busy w/ classes logic design is a pain in the *** XD... but ne way... just came back maybe starting up again a little to at least keep my self up to date w/ things CO is doing... ne update on this?

Originally Posted by clintonselke

some warnings i got PMed about

maybe i'm just paranoid but have a look.

0058CE7C  CALL DWORD PTR DS:[<&KERNEL32.GetCurrent>kernel32.GetCurrentProcessId

004AB5AB  CALL DWORD PTR DS:[<&KERNEL32.GetCurrent>kernel32.GetCurrentThreadId

004A1FF9  CALL DWORD PTR DS:[<&KERNEL32.ReadProces>kernel32.ReadProcessMemory

004A1C82  CALL ESI                                 kernel32.WriteProcessMemory

004A201C  CALL DWORD PTR DS:[<&KERNEL32.WriteProce>kernel32.WriteProcessMemory

I was warned that they might have installed code cave checks now.

[warriorchamp]

[EDIT] I've read only the thread's 1st page. ****)

You are moving a bit far away from the base addresses of the players on the screen. The offsets in the memory cannot be bigger then 0xFF.. (unless there is few exception eg. to the skillID). So there is no 0x2D4 offset to the coordinates (it can be correct 1 or 2 times, but it will fail after you restart your client few times).
0xE4 to the name is correct

Help: finding the correct base address to the player/monster names you must get a level 4 pointer

[IAmHawtness]

Originally Posted by warriorchamp

[EDIT] I've read only the thread's 1st page. ****)

You are moving a bit far away from the base addresses of the players on the screen. The offsets in the memory cannot be bigger then 0xFF.. (unless there is few exception eg. to the skillID). So there is no 0x2D4 offset to the coordinates (it can be correct 1 or 2 times, but it will fail after you restart your client few times).
0xE4 to the name is correct

Help: finding the correct base address to the player/monster names you must get a level 4 pointer

Sorry, what?

You are wrong. I used those offsets (2 byte long offsets) too for my old COoperative aimbot, and it worked fine for everyone.

[_tao4229_]

Lol?
That makes total sense.
Structures definitely can't ever be over 255 bytes in size.