S4lly's FREE war teleporter+speedhack+nofalldmg, flat style

[s4lly]

Im not really familiar with vstudio 2008 but i can drop the codes here, so people who wanna contribute building or helping rockman319 adding the code into the program can help





Wallhack on
0x506f93 9090909090
0x506f9f 9090909090

Wallhack off
0x506f93 F30F114324
0x506f9f F30F114329


Groundghost On
0x50FB14 909090

Groundghost Off
0x50FB14 8B4E2C

[HansW]

not that easy to help without the sourcecode. But i guess that it uses the c# MemHacking class. So rockman319, you need to "Poke" the those values to the addresses. either byte by byte or as a block. Should not be that hard. just like you poke the coordinates for the teleportation. So to enable the wallhack you poke Bytes with the value 90 to the addresss 0x506f93-0x506f98 and 0x506f9f-0x506fa4.

[rockman319]

Source code added, you can use reflector to "reverse" it anyway .

Edit: I haven't tried very hard but the codes that I have for teleportation is

access.WriteFloat(0x24, value);

(for X)
so I "mimic" it with WriteFloat(0x506f93, 9090909090);
and WriteFloat(0x506f9f, 9090909090);
but it doesn't do anything.

[HansW]

Float is a floating point value, 90909090 is not. look for WriteByte and do 5 times WriteByte(0x506f93, 0x90) and add 1 to the address with each call.
e.g. WriteByte(0x506f94, 0x90) for the second call.

[rockman319]

Well the writefloat has bitconverter...

byte[] bytes = BitConverter.GetBytes(data);
...
Win32Services.WriteProcessMemory(this.hProcess, lpBaseAddress, bytes, bytes.Length, out zero);
...

It's still not the same?

[HansW]

No, but you can easily use WriteProcessMemory . byte[] NOPS = {0x90,0x90,0x90,0x90,0x90};
Win32Services.WriteProcessMemory(this.hProcess, lpBaseAddress, NOPS , NOPS .Length, out zero);

[rockman319]

Still no cigar. Something with my codes

Is 0x506f93 an offset to 0xd3d4fc?

My code snippet:

byte[] NOPS = { 0x90, 0x90, 0x90, 0x90, 0x90 };
        IntPtr lpBaseAddress = (IntPtr)((ulong)(0xd3d4fcL));

        if (!this.GetWarProc())
        {
            return false;
        }
        MemoryAccess access = new MemoryAccess(this.WarHandle);
        if (!access.LoadBasePtr(lpBaseAddress, 0))
        {
            return false;
        }
        access.WriteManual(0x506f93, NOPS);
        access.WriteManual(0x506f9f, NOPS);

WriteManual is practically

...
return Win32Services.WriteProcessMemory(this.hProcess, lpBaseAddress, bytes, bytes.Length, out zero);
...

inside MemoryAccess.cs

When ran, console says the base + offset ( 0xd3d4fc + 0x506f93 ) is:
1029300299

but if I use windows calculator (calc), I get 124446F hex, which is 19154031 dec.
What is this 1029300299?

[s4lly]

//////////////////////////
Wallhack on
0x506f93 9090909090
0x506f9f 9090909090

Wallhack off
0x506f93 F30F114324
0x506f9f F30F114329
//////////////////////////
Groundghost On
0x50FB14 909090

Groundghost Off
0x50FB14 8B4E2C
//////////////////////////
Attack Target Through Walls etc (Eye Of Tiger) on
0x53b106 909090
0x53bbe9 9090

Attack Target Through Walls etc (Eye Of Tiger) off
0x53b106 88480c
0x53bbe9 8803
//////////////////////////
No Fall Damage On
0x50fc30 9090909090909090

No Fall Damage Off
0x50fc30 F30F119E90000000
//////////////////////////
Spawn at Dead Location (Egg of youth) On
5057d7 9090909090F30F10450C9090909090

Spawn at Dead Location (Egg of youth) Off
5057d7 F30F114624F30F10450CF30F114628
//////////////////////////

[s4lly]

Still no cigar. Something with my codes

Is 0x506f93 an offset to 0xd3d4fc?

My code snippet:

byte[] NOPS = { 0x90, 0x90, 0x90, 0x90, 0x90 };
        IntPtr lpBaseAddress = (IntPtr)((ulong)(0xd3d4fcL));

        if (!this.GetWarProc())
        {
            return false;
        }
        MemoryAccess access = new MemoryAccess(this.WarHandle);
        if (!access.LoadBasePtr(lpBaseAddress, 0))
        {
            return false;
        }
        access.WriteManual(0x506f93, NOPS);
        access.WriteManual(0x506f9f, NOPS);

WriteManual is practically

...
return Win32Services.WriteProcessMemory(this.hProcess, lpBaseAddress, bytes, bytes.Length, out zero);
...

inside MemoryAccess.cs

When ran, console says the base + offset ( 0xd3d4fc + 0x506f93 ) is:
1029300299

but if I use windows calculator (calc), I get 124446F hex, which is 19154031 dec.
What is this 1029300299?

No it has no pointer.. its the direct adress.. so no DMA

[rockman319]

//////////////////////////
Wallhack on
0x506f93 9090909090
0x506f9f 9090909090

Wallhack off
0x506f93 F30F114324
0x506f9f F30F114329
//////////////////////////
Groundghost On
0x50FB14 909090

Groundghost Off
0x50FB14 8B4E2C
//////////////////////////
Attack Target Through Walls etc (Eye Of Tiger) on
0x53b106 909090
0x53bbe9 9090

Attack Target Through Walls etc (Eye Of Tiger) off
0x53b106 88480c
0x53bbe9 8803
//////////////////////////
No Fall Damage On
0x50fc30 9090909090909090

No Fall Damage Off
0x50fc30 F30F119E90000000
//////////////////////////
Spawn at Dead Location (Egg of youth) On
5057d7 9090909090F30F10450C9090909090

Spawn at Dead Location (Egg of youth) Off
5057d7 F30F114624F30F10450CF30F114628
//////////////////////////

Holy nuts.

No it has no pointer.. its the direct adress.. so no DMA

Oh I see. Ok I'll try later at home (now at work).

[s4lly]

yah So who needs war ultimate bunch of noobs, they dont belong here, as this is the sharing forum, and not the "give-me-money" forum

[rockman319]

Lol let's not start a war (again).
They do have "ninja jump."

[s4lly]

and ?? ninja jump is spotable much more than other hacks

[rockman319]

Great news, wallhack works!!!
However, when I turn it off, and hit a wall, I get teleported back to rally point, as if I were to teleport incorrectly.

byte[] YES1 = { 0xF3, 0x0F, 0x11, 0x43, 0x24 };
byte[] YES2 = { 0xF3, 0x0F, 0x11, 0x43, 0x29 };
this.Player.PatchMemory(wallhack_1, YES1);
this.Player.PatchMemory(wallhack_2, YES2);

wallhack_1 and _2 are the addresses.
Note that turning wallhack does work.

Edit: Is it maybe because PatchMemory() has a delay and both memory writes should be back to back?
If so I'll create a function just to do wallhack (or any hack that requires 2 areas of memory addresses).

Edit: I changed a bit so it would do memory write back to back. So... here is v0.4e... but it's UNTESTED.
http://filebeam.com/2c60fb1e42d9e6a185cd2799e82d70f1

Please test. I'll test when I'm home . If this works, I'll update the first post and then I'll add the others too.
Big thanks to S4lly!!!!!!!!

[HansW]

Well done , keep it up