When it comes to high level hacks like that... NO ONE will say how. How is the same thing as a handout for this type of stuff. I can guarantee you if immune or someone came on here and was like "here's how a proper teleport hack works!" within a week there would be like a billion new proxies competing with their own... They do NOT want that and it WILL NOT happen.Quote:
I asked HOW. Not someone to do it for me.
Can anyone give me a reasonable hint as to this second method? I'm not asking for a hand out like the OP; I just can't think of anything that might work/where to start.Quote:
Anways, there are two ways that I personally know of one of which ways doesn't use jumping at all, but obviously needs to have X/Y coords included in the packet. As ya know there aren't that many so that one is easy to figure out.
As far as the one with timestamps go, can't really shed to much light upon that one since I was told how it worked by someone else. It's much more efficient. But quite odd as well
Nice like 5 month bump...Quote:
Can anyone give me a reasonable hint as to this second method? I'm not asking for a hand out like the OP; I just can't think of anything that might work/where to start.
Good to know about "necroing" rofl.Quote:
You should not be bumping a thread that hasn't been replied to for more than say a week or so... to do so is generally frowned upon and referred to as 'necroing' a topic.
The thread was dead and should generally be left that way.
Timestamp manipulation can easily be done but I personally dislike messing with timestamps.. I'm sure there are better ways then I was doing though.
Certain forms of invalid packets to tq for all intensive purposes reset your last timestamp meaning you can boost the timestamp you are using and send a new jump. It's what I was using for my speedhack system on my last proxy... that being said I'm still positive there are FAR better ways to speedhack (last I heard there were like 4-5 different ones lol).
Thing is... any of the good/efficient/stable ones will obviously be kept closely guarded as posting information about them would just be begging for tq to fix their holes.
But yah, shifting is super fast and there's perfectly good examples of how to use it so that's always an easy option.
A bump is better than wasting database space on making a thread, but a useless bump that's offtopic or contains no information related to the topic is not needed.Quote:
You should not be bumping a thread that hasn't been replied to for more than say a week or so... to do so is generally frowned upon and referred to as 'necroing' a topic.
public void Portal(uint num)
{
_client.SendPacket(GeneralPacket(0, 0, 0, UID, (uint)Environment.TickCount, 85, 0, 0, 0, num));
}
unsafe public Byte[] GeneralPacket(ushort data1, ushort data2, uint id, uint data3, uint timeStamp, uint subtype, ushort data4, ushort data5, uint data6, uint data7)
{
UInt16 Size = 0x25;
UInt16 Type = 0x271A;
Byte[] Packet = new Byte[Size];
fixed (Byte* ptr = Packet)
{
*((ushort*)(ptr + 0)) = (ushort)Size;
*((ushort*)(ptr + 2)) = (ushort)Type;
*((uint*)(ptr + 4)) = (uint)id;
*((ushort*)(ptr + 8)) = (ushort)data1;
*((ushort*)(ptr + 10)) = (ushort)data2;
*((uint*)(ptr + 12)) = (uint)data3;
*((uint*)(ptr + 16)) = (uint)Environment.TickCount;
*((uint*)(ptr + 20)) = (uint)subtype;
*((ushort*)(ptr + 24)) = (ushort)data4;
*((ushort*)(ptr + 26)) = (ushort)data5;
*((uint*)(ptr + 28)) = (uint)data6;
*((uint*)(ptr + 32)) = (uint)data7;
}
return Packet;
}