Polyhack Suite | Glow ESP | Bunnyhop | NoFlash | RCS | Radar

[saminas30]

is it ud????????????????

[maestro1994]

[B]Oh and there is still a memory leak in "FindPattern" function =]

Why the hell are you surprising there is a memory leak in that function if that's not the only one place where there are memory leaks?;)
That's nothing of interesting, there are operators such as "new" and "delete" to manipulate heap memory; the first one allocates memory in the heap, the second one frees the memory from the heap :

BYTE* data = new BYTE[size];
...
delete data;

It would be discounted to know:).

[Yemiez]

Why the hell are you surprising there is a memory leak in that function if that's not the only one place where there are memory leaks?
That's nothing of interesting, there are operators such as "new" and "delete" to manipulate heap memory; the first one allocates memory in the heap, the second one frees the memory from the heap :

BYTE* data = new BYTE[size];
...
delete data;

It would be discounted to know.

EDIT: My bad, misunderstood you

Did you even read the code?

If ReadProcessMemory fails or if the pattern is not found the memory is leaked.

[jahc0rew]

is it ud????????????????

maybe yes, maybe not

[maestro1994]

A moment, I wasn't talking about memory leaks, but just about memory manipulation (this happens often to me because I'm a non-native english guy, I could counfound some terms), as I saw you were talking about that, see what happens when someone doesn't think?...

Did you even read the code?

If ReadProcessMemory fails or if the pattern is not found the memory is leaked.

Of course, you must always ensure that:
delete [] data
is always called.

- - - Updated - - -

Basically it has memory leaks, because you have:

if (!ReadProcessMemory(_process, (LPVOID)start, data, size, &bytesRead)) {
    return NULL;
}

which fires then you have leaked data as he never calls delete [] before returning. He also leaks at the end of the function as he never calls delete [] before returning. @Yamiez I'm sure you noticed there is an incorrect delete in this part:

for (DWORD i = 0; i < size; i++) {
    if (DataCompare((const BYTE*)(data + i), (const BYTE*)sig, mask)) {
        delete data; 
        return start + i;
    }
}

It's an ub (undefined behavior) to call delete on an allocated pointer with new[] (if you use new[], you need to use delete[]).
Also probably you noticed that a smart pointer would be nice:)

[idanb323]

Thanks for posting this!!

[DizZy13]

Played 7 games, no ban. I recommand it

[Tra1ner]

It sucks how there is no triggerbot :/'

[[MPGH]T-800]

The offsets are good; Tested and working ; Status not changed.

[zerox06]

dude i've a question, im french and i dont understand one things, can you explain me what strings mean ? after i'm going to search dw but i need to understand why change strings is important to don't get banned.
And can I play 'safe' without change strings ? only change offset i mean when I have to change

[DizZy13]

@gerassss By recompiling do you mean deleting the last compiled executable, and compiling a new one? How does it help?It generates random code, or?

[[MPGH]T-800]

@gerassss By recompiling do you mean deleting the last compiled executable, and compiling a new one? How does it help?It generates random code, or?

Yep.

[DizZy13]

Yep.

Ok, thanks
Thanks for release
//But why would you recompile it 3 times?Isn't the same thing?Sorry for these dumb questions ^^ i'm new to this.
//Just got permanently untrusted

[A_RM]

Ok, thanks
Thanks for release
//But why would you recompile it 3 times?Isn't the same thing?Sorry for these dumb questions ^^ i'm new to this.
//Just got permanently untrusted

You only need to recompile once. It's like when people use hash changers, it really doesn't do anything and is unnecessary.

[zerox06]

and i've another question, why we should not have the hack on in the main menu etc ?