CF Shuts down

Is anyone having the same problem that can help me? When i inject my hack crossfire just shuts down without warning. It's annoying. Does anyone know why it's doing that, is it normal?

Hmm Maybe its a Failer in the base ?
did you code the hack?

Originally Posted by Royku

Hmm Maybe its a Failer in the base ?
did you code the hack?

ya, i coded the hack. I stripped it down to just auto on features to figure out where the problem is. It's very simple, so simple that here is the code:

Code:

#include<windows.h>
#define grenades  ((i==6)||(i==7)||(i==8)||(i==64)||(i==100)||(i==126)||(i==135)||(i==209)||(i==210)||(i==240)||(i==263)||(i==272)||(i==338)||(i==382)||(i==383)||(i==384))
#define Knifes    ((i==5)||(i==35)||(i==74)||(i==132)||(i==239)||(i==372)||(i==381))
#define Mutant    ((i==120)||(i==176)||(i==177)||(i==178)||(i==182)||(i==195)||(i==196)||(i==197)||(i==198)||(i==199)||(i==223)||(i==224)||(i==225)||(i==226)||(i==227)||(i==228)||(i==270)||(i==271)||(i==302)||(i==303)||(i==304)||(i==305)||(i==306)||(i==307))
#define CShell    (DWORD) GetModuleHandleA("CShell.dll")
void Hacks();
#define WeaponMgr		      0xA65EE8
#define MoveSpeedPenalty      0x2450
#define ohk  0x7F8




void Hacks()
{
	
	
	for(int i=0; i<533; i++)
       {
       
  
		   
       *(float*)((*(DWORD*)((*(DWORD*)(CShell+WeaponMgr))+(4*i))) + MoveSpeedPenalty) = -10.0f; // -10 is REAL fast, so i have mine set to -0.30// OR 0.0f for just no weight.
	   *(float*)((*(DWORD*)((*(DWORD*)(CShell+WeaponMgr))+(4*i))) + ohk) = 10000000000.0f;
	  
		
	   }
	   
     }
	   
	  
  


	
  



BOOL WINAPI DllMain ( HMODULE hDll, DWORD dwReason, LPVOID lpReserved )
{
	DisableThreadLibraryCalls(hDll);
	if ( dwReason == DLL_PROCESS_ATTACH ) 
	{
	    
 		CreateThread(0,0,(LPTHREAD_START_ROUTINE)Hacks,0,0,0);
       	}

	

   
	return true;
}

The hooking part is wrong i think

any info or advice?

Rename your hack to sxs and then start crossfire.

Also change your 10000000000.0f; to something lower. I lol'ed at this part....

Originally Posted by CrossRaiders

Rename your hack to sxs and then start crossfire.

Also change your 10000000000.0f; to something lower. I lol'ed at this part....

That's not the part that is causing issues, its how i own in zombie mode. And i don't need to rename it to sxs cuz the injector isn't the problem, yestarday my hack was working, but now it just shuts down crossfire. Now can somebody who knows how to code give me advice?

Why this:

Code:

for(int i=0; i<533; i++)

I think its:

Code:

for(int i=0; i<445; i++)

Its neither

Code:

for(int i=0; i<533; i++)

or

Code:

for(int i=0; i<445; i++)

its

Code:

for(int i=0; i<560; i++)

Originally Posted by Fly3r

Its neither

Code:

for(int i=0; i<533; i++)

or

Code:

for(int i=0; i<445; i++)

its

Code:

for(int i=0; i<560; i++)

It doesn't matter cuz i don't use the last 25 - 40 guns anyway, so it doesn't matter.

You need to change 10000000000.0f vale to something else. I know for a fact that x-trap detects large values such as this.

Originally Posted by CrossRaiders

You need to change 10000000000.0f vale to something else. I know for a fact that x-trap detects large values such as this.

Actually my zombie ohk is working and it is set HIGH also. Xtap not detecting

I found out the problem, it's just that you can't inject until you are actually in a game, then it'll work. Except you can inject weapon hack anywhere.

EDIT:_=====================

Upon further researching, i have come to the conclusion and it turns out pointer checking is freakin vital after all lol. So, you coders out there, do POINTER CHECKING before trying to write data into memory or else you might be writing to a place that's not there or writing gibberish to a place in memory that is there and you will end up crashing the game.

Originally Posted by 258456

I found out the problem, it's just that you can't inject until you are actually in a game, then it'll work. Except you can inject weapon hack anywhere.

EDIT:_=====================

Upon further researching, i have come to the conclusion and it turns out pointer checking is freakin vital after all lol. So, you coders out there, do POINTER CHECKING before trying to write data into memory or else you might be writing to a place that's not there or writing gibberish to a place in memory that is there and you will end up crashing the game.

I knew it was something to do with injector.

Originally Posted by CrossRaiders

I knew it was something to do with injector.

It had nothing to do with the injector. I just wasn't checking if the place in memory i was going to edit existed. That's why. It wasn't with the injector.

CF Shuts down

Post a Reply

Tags for this Thread