Teleporting Using Memory Writes...

[nathan2022001]

Hey, I've been trying to use the x y and z offsets in order to change my current location but whenever I set it and attempt to move I get disconnected. Im a bit confused as i've seen a few teleport hacks which don't seem to alert warden. Could someone please help me out and perhaps point me in the right direction?

Thanks

[Robske]

Could someone please help me out and perhaps point me in the right direction?

Thanks

I believe this is a facing issue.

Server disconnects you once you change your position by more than 0.137f, search damnit.

[gissuf]

you have to update your position with the server with every change of one of the axis, bigger than 0.137

im not 100% sure of that, but it maybe should look like this:

1) change position by 0.137
2) send hearthbreath packet
3) send new position package
4) goto 1

the biggest proble is the timestamp of the packages I think…

try to log all the packages sent by the client an reveived by the client with an external program like wireshark..

then you should know what packages you have to send…

[kynox]

you have to update your position with the server with every change of one of the axis, bigger than 0.137

im not 100% sure of that, but it maybe should look like this:

1) change position by 0.137
2) send hearthbreath packet
3) send new position package
4) goto 1

the biggest proble is the timestamp of the packages I think…

try to log all the packages sent by the client an reveived by the client with an external program like wireshark..

then you should know what packages you have to send…

You will get dropped for packet flooding for that method. Try spinning your character around at a stupidly high rate for 20-30 seconds and you'll know what i mean.

[nathan2022001]

I made a quick app to test out this but it seemed to be too slow.

Basically my method was this

for(;;Sleep(5))
{
	if(GetAsyncKeyState(VkKeyScan('9')))
	{
		Memory.WriteFloat(WoWInfo.hProcess, (LPVOID)(localObj.dwBaseAddress + OBJ_OFFSET_ZPOS), (localObj.GetZPos() + 0.1));
		SendMessage(WoWInfo.hWnd, WM_KEYDOWN, VK_LEFT, 0);
		SendMessage(WoWInfo.hWnd, WM_KEYUP, VK_LEFT, 0);
	}
}

Anyways, in that loop it appeared to be too slow, perhaps because of the Sleep() and the epicly tiny increment of 0.1 :P

And sometimes the WM_KEYDOWN/WM_KEYUP wouldn't be in time with WoW so would still result in a d/c, (or perhaps as Kynox said was probably some anti-floodig method put in place by WoW).


I gave up on that now anyways, was funny "floating" in front of people for while.