[Help] Help

Help

My Hacker Crash After Giving This Minutes Of Game oq Base Can Be In?
* Menu Selection V4 Update Nightmare
Addresses are updated

Google Tradutor

@Acea @-Bl00d- @supercarz1991 @Flengo @Genesis

if addies are updated doesnt mean detours are :S

check ur detours

@R3d_L1n3 I used the detours q underlie the redux

check the detours as stated above
i just (tried) switched mine over

Originally Posted by -Bl00d-

check the detours as stated above
i just (tried) switched mine over

if I change the Detours For Another that is posted might work? @-Bl00d-

i'm useless to mention bro, i don't know c++ lol. i just mess with things till they break

Originally Posted by supercarz1991

i'm useless to mention bro, i don't know c++ lol. i just mess with things till they break

ook Thanks
No solveld

@Coder.Dias i dunno witch detours he is using but simple if u wana make sure its ur hooking then disale all the functions inside ur base and just keep the hooking and test so if result is success its not ur detours but if u crashed then its detours

some detections are not crashing you straight away, meaning you might get a successful hook going but doesn't mean it not detected, I agree with starting from the basic hook and then if no crash(after 10+ minutes) add one function at time until you get a crash, then it's more than likely the last function added back into the hack that is being detected. Once you found the function giving you the detection then modify it, for example split the function into a couple of mini functions to avoid detection of the original function.

Example(Delphi) but same princiable applys

Function iOwnAcea( szInPut: String): Boolean;
var
isAsshole: Boolean;
begin
Result:= False;
if szInPut = 'Acea' then
isAsshole:= True;

Result:= isAsshole;
end;

you could modify the function like this

Function iOwnAcea( szInPut: String): Boolean;
var
isAsshole: Boolean;
begin
Result:= True;
if Not szInPut = 'Acea' then
isAsshole:= False;

Result:= isAsshole;
end;

Or split the function into mini functions....

Function SetFalse(): Boolean;
begin
Result:= False;
end;

Function SetTrue(): Boolean;
begin
Result:= True;
end;

Function iOwnAcea( szInPut: String): Boolean;
var
isAsshole: Boolean;
begin
Result:= SetFalse;
if szInPut = 'Acea' then
isAsshole:= SetTrue;

Result:= isAsshole;
end;

Originally Posted by Departure

some detections are not crashing you straight away, meaning you might get a successful hook going but doesn't mean it not detected, I agree with starting from the basic hook and then if no crash(after 10+ minutes) add one function at time until you get a crash, then it's more than likely the last function added back into the hack that is being detected. Once you found the function giving you the detection then modify it, for example split the function into a couple of mini functions to avoid detection of the original function.

Example(Delphi) but same princiable applys

Function iOwnAcea( szInPut: String): Boolean;
var
isAsshole: Boolean;
begin
Result:= False;
if szInPut = 'Acea' then
isAsshole:= True;

Result:= isAsshole;
end;

you could modify the function like this

Function iOwnAcea( szInPut: String): Boolean;
var
isAsshole: Boolean;
begin
Result:= True;
if Not szInPut = 'Acea' then
isAsshole:= False;

Result:= isAsshole;
end;

Or split the function into mini functions....

Function SetFalse(): Boolean;
begin
Result:= False;
end;

Function SetTrue(): Boolean;
begin
Result:= True;
end;

Function iOwnAcea( szInPut: String): Boolean;
var
isAsshole: Boolean;
begin
Result:= SetFalse;
if szInPut = 'Acea' then
isAsshole:= SetTrue;

Result:= isAsshole;
end;

Aww :3 He loves me. Ima make this boy my bitch ^=^

Anyways, As all of you stated above its not the detours, and as departure the know it all stated that's one way of looking at it, but a more correct way of stopping this is to not use public hooks. I don't care what you're functions are, if you have ASM and C++ knowledge you can create a simple hook that will remain undetected for a numerous amount of time.

To everyone who said look at the detours:
Detours simple create a jump allowing you to 'attach' in a sense to the game. If you can stay in game without crashing before login then its not the detours its the hook.

here's some more correct code for ya

Code:

char* BitchArray[4] = {"You", "Are", "My", "Bitch"}
for(int DepartureIsAceasBitch = 0; DepartureIsAceasBitch < 3; DepartureIsAceasBitch++)
{
     cout << BitchArray[DepartureIsAceasBitch] << endl;
}

cin.get()

Your move big boy ;3

CreateJmp is detected if u dont modify it or unless u do something on it ..

But if i were wrong ya i would disable all my hacks or do as @Departure said spread functions

and u both seriously love eatch other as i see lmfao

Originally Posted by R3d_L1n3

CreateJmp is detected if u dont modify it or unless u do something on it ..

But if i were wrong ya i would disable all my hacks or do as @Departure said spread functions

and u both seriously love eatch other as i see lmfao

Well, creating a jmp in asm is not detected as long as you jmp back when your function finishes. So trust me it's not the detours, and doing what he said was stupid when any function can be detected at anytime, i can guarantee the function that has the highest likely hood of being in his hack and crashing it is getmodulehandle.

---------- Post added at 10:57 AM ---------- Previous post was at 10:51 AM ----------

For example lets take this code here, a simple detour that has been surviving great even though any detour works really.
We can modify the memory all we like but that the end we jmp back to the original to prevent detection and crash.

The detours you posted is a hotpatch which only works on function start and there must also be MINIMAL 5 nops or other useless bytes before.

@Acea thats why i said u got to modify it

Please Closes

HelpHelp

Similar Threads

Tags for this Thread