❗ PushToConsol dont work ô_Ô

Posts 1–13 of 13 · Page 1 of 1
❗ PushToConsol dont work ô_Ô
Code:
#define Engine 0x485F90 
void __cdecl RunConsoleCommand( const char* cCommand)
{
	void* address = ( void* ) Engine;

	__asm
	{
		Push cCommand
		call address
		add esp, 0x4
	}
}
RunConsoleCommand("ShowFPS 1");

What is wrong, i get a crash..
I think its patched :/
Oh really?
How make now PushToConsol -.-
Or how make Dip full ud
Code:
void PTC( const char* mycmd )
{
	_asm
	{
		PUSH mycmd; Push mycmd onto the stack 
		MOV EAX, 0x00485F90; Move address to the EAX register
		CALL EAX; Call the address with the parameter of the mycmd
		ADD ESP, 0x4; fix the stack pointer due to the cdecl calling convention
	}
}
you must push in present. ( i think)
There are two (virtualized) checks to determine if the console commands will execute called in Engine.exe.

The first one compares the calling thread ID with a stored thread ID.

The second one compares if the entrypoint of the calling thread is in the range of Engine code section.

They can be bypassed, there is no need to call the console function from present etc. Your choice.
Quote Originally Posted by HellSpider View Post
There are two (virtualized) checks to determine if the console commands will execute called in Engine.exe.

The first one compares the calling thread ID with a stored thread ID.

The second one compares if the entrypoint of the calling thread is in the range of Engine code section.

They can be bypassed, there is no need to call the console function from present etc. Your choice.
Calling the function from Present is the easiest way, but laggiest.
Quote Originally Posted by flameswor10 View Post
Calling the function from Present is the easiest way, but laggiest.
wrong. L2callWhenNeeded.
Quote Originally Posted by [POWER] View Post
wrong. L2callWhenNeeded.
I meant laggiest if you have 2304983209 commands without any 'anti lag' methods
Quote Originally Posted by flameswor10 View Post
Calling the function from Present is the easiest way, but laggiest.
Bypassing is easy too and wont cause any lag at all.
variables must be 'global' when you are working with assembly
Quote Originally Posted by kibbles18 View Post
bypassing is hard...
Nah, I've explained how the check works somewhere in an older thread. It's just some lines ASM, nothing significant. Well, the explanation is more like evading the check.
Posts 1–13 of 13 · Page 1 of 1

Post a Reply

Similar Threads

Tags for this Thread

None

Talk with us