Updating A Script In Your Trainer

private: System::Void checkBox1_CheckedChanged(System::Object^  sender, System::EventArgs^  e) {
		 }
};
}

private: System::Void checkBox1_CheckedChanged(System::Object^  sender, System::EventArgs^  e);
		 
};
}

//Name Of Hack <---- This is optional good for organizations and prevent being mixed up with hacks.

DWORD "THIS SPOT IS FOR A SUB NAME" = THIS SPOT IS FOR YOUR ADDY;
BYTE SUB NAME GOES HERE[] = {DOUBLE BYTES GO HERE};
BYTE SUBNAMEGOESHERE[] = {DOUBLE BYTES GO HERE};


void Form1::checkBox1_CheckedChanged(System::Object^  sender, System::EventArgs^  e)
 { 
 
if(this->checkBox1->Checked)
{ 
		WriteMemory(SUB NAME,THIS SPACE IS FOR NUMBER OF BYTES,BYTES GO HERE); <--- Event if it is checked it uses the enable bytes.
}
else
 { 
		WriteMemory(SUB NAME,THIS SPACE IS FOR NUMBER OF BYTES,BYTES); <--- If unchecked it sends  disable bytes.
        } 
 }

//Full Godmode <-- Name of hack
DWORD FGM = 0x0043BD42;  <--- "FGM" is full godmode which is my subname for this tut. 0x009FF50C is the adress. 
Note: Always add 0x before the adress so It declares it as a byte.

BYTE enableFGM[] = {0x0F, 0x84}; <---enableFGM pretty much explains it self. And besides are the double bytes from the script.

BYTE disableFGM[] = {0x0F, 0x84};


void Form1::checkBox1_CheckedChanged(System::Object^  sender, System::EventArgs^  e)
 { 
 
if(this->checkBox1->Checked)
{ 
		WriteMemory(FGM,2,0x0F, 0x84);
}
else
 { 
		WriteMemory(FGM,2,0x0F, 0x85); <-- Number "2" in between the sub name and bytes are number of bytes. Very important. Lets say you have 4 bytes then it would be 4 and so on. 
        } 
 }