[help] hack is detected
[help] hack is detected
i dont know why but everytime i use this hack i get banned in 1min i thought c++ was better then vb6 heres my code
my function is
Code:
void CWarrockHackILP21Dlg::OnTimer(UINT nIDEvent)
{
switch(nIDEvent)
{
case FastAsFamasTimer:
{
iMemoryiX188291();
BYTE iByteVariableiX299131[ ] = {///-.-};
WriteProcessMemory(ihProcessiX381992, (LPVOID*)(DWORD) 0x523F53, &iByteVariableiX299131, sizeof(iByteVariableiX299131), NULL);
}
break;
case HeadShotTimer:
{
iMemoryiX188291();
BYTE iByteVariableiX299131[ ] = {0x31, 0xC0};
WriteProcessMemory(ihProcessiX381992, (LPVOID*)(DWORD) 0x4a38a4, &iByteVariableiX299131, sizeof(iByteVariableiX299131), NULL);
}
break;
}
CDialog::OnTimer(nIDEvent);
}
void CWarrockHackILP21Dlg::OnFastAsFamas()
{
{
int State = m_FastAsFamas.GetCheck();
if(State)
{
SetTimer(FastAsFamasTimer, 1, NULL);
}else{
KillTimer(FastAsFamasTimer);
}
}
}
void CWarrockHackILP21Dlg::OnHeadShot()
{
{
int State = m_HeadShot.GetCheck();
if(State)
{
SetTimer(HeadShotTimer, 1, NULL);
}else{
KillTimer(HeadShotTimer);
BYTE iByteVariableiX299131[ ] = {0x85, 0xC0};
WriteProcessMemory(ihProcessiX381992, (LPVOID*)(DWORD) 0x4a38a4, &iByteVariableiX299131, sizeof(iByteVariableiX299131), NULL);
}
}
}
Code:
DWORD iprocidiX299193;
HANDLE ihProcessiX381992;
void iMemoryiX188291()
{
HWND ihWndiX293811 = FindWindow(0, "WarRock");
GetWindowThreadProcessId(ihWndiX293811, &iprocidiX299193);
ihProcessiX381992 = OpenProcess(PROCESS_ALL_ACCESS|PROCESS_VM_OPERATION|PROCESS_VM_READ|PROCESS_VM_WRITE|PROCESS_QUERY_INFORMATION, FALSE, iprocidiX299193);
}
well it looks ok recheck all your codes.....vb6 is easier to code in than c++ but c++ works better. and besides vb6 is dected so no ponit in even using it. i know i did not say the problem i don't know but everything looks good
i knew someone was gonna post something completly useless
Change hProcess and Memory to something else but i should detour your hack so PB won't detect it
masterboy is right but you would have to put up a bypass code i can give to you to but its not detour but go straight through hidden. idk hard to explain but all my c++ hacks have never been detected except for a public one... so ya
i have the same problem have replace and change the stings, banne d after 10 mins play pnkbstr is coming hard i need bypass
Originally Posted by ilovepie21
i dont know why but everytime i use this hack i get banned in 1min i thought c++ was better then vb6 heres my code
my function is
Code:
void CWarrockHackILP21Dlg::OnTimer(UINT nIDEvent)
{
switch(nIDEvent)
{
case FastAsFamasTimer:
{
iMemoryiX188291();
BYTE iByteVariableiX299131[ ] = {///-.-};
WriteProcessMemory(ihProcessiX381992, (LPVOID*)(DWORD) 0x523F53, &iByteVariableiX299131, sizeof(iByteVariableiX299131), NULL);
}
break;
case HeadShotTimer:
{
iMemoryiX188291();
BYTE iByteVariableiX299131[ ] = {0x31, 0xC0};
WriteProcessMemory(ihProcessiX381992, (LPVOID*)(DWORD) 0x4a38a4, &iByteVariableiX299131, sizeof(iByteVariableiX299131), NULL);
}
break;
}
CDialog::OnTimer(nIDEvent);
}
void CWarrockHackILP21Dlg::OnFastAsFamas()
{
{
int State = m_FastAsFamas.GetCheck();
if(State)
{
SetTimer(FastAsFamasTimer, 1, NULL);
}else{
KillTimer(FastAsFamasTimer);
}
}
}
void CWarrockHackILP21Dlg::OnHeadShot()
{
{
int State = m_HeadShot.GetCheck();
if(State)
{
SetTimer(HeadShotTimer, 1, NULL);
}else{
KillTimer(HeadShotTimer);
BYTE iByteVariableiX299131[ ] = {0x85, 0xC0};
WriteProcessMemory(ihProcessiX381992, (LPVOID*)(DWORD) 0x4a38a4, &iByteVariableiX299131, sizeof(iByteVariableiX299131), NULL);
}
}
}
Code:
DWORD iprocidiX299193;
HANDLE ihProcessiX381992;
void iMemoryiX188291()
{
HWND ihWndiX293811 = FindWindow(0, "WarRock");
GetWindowThreadProcessId(ihWndiX293811, &iprocidiX299193);
ihProcessiX381992 = OpenProcess(PROCESS_ALL_ACCESS|PROCESS_VM_OPERATION|PROCESS_VM_READ|PROCESS_VM_WRITE|PROCESS_QUERY_INFORMATION, FALSE, iprocidiX299193);
}
u act like its easy to make one -.-
Obviously you're gonna get banned you're changing memory addresses, I'm pretty sure memory addresses get checked.... To make sure no one over writes it. C++ and VB doesn't matter you are just changing a memory address, they both do the same thing. A tip you can use is, not all addresses are protected very likely, so find a value that isn't checked and that will indirectly affect the value you want to change. Not easy ,but life aint very easy. Another thing you should do is change names of the variables I doubt this will help ,but do it none the less.
Its useless to put fastas famas and headshot in a timer.
You modify the asmcode and you do it once.
If you modify asmcode, punkbuster will detect it unless you have a bypass.
You modify the asmcode and you do it once.
If you modify asmcode, punkbuster will detect it unless you have a bypass.
This thread is closed for replies.
