There is no news, my actual source had some test cpp added.
Last one are this one (update 2):
https://mega.co.nz/#!psFxnDBB!MK03E0...boKbBt8kw6x2HQ
- - - Updated - - -
Anti-kill configuration:
Turn ON and OFF EVERYTHING you will use on your antihack, including minimizer.
ANY modification after anti-kill configuration will cause Exitprocess.
Set
START.cpp:
Code:
carrega.Detecta_Inject_by_Thread = 1;
carrega.DInject_Thread_occours = 10000; // Scan occour every 10 seconds <forgot that for now
carrega.Detecta_Kill_by_Thread = 1;
carrega.Dont_kill_yet = 0; // (0) PAUSE Exitprocess, (1) activate exitprocess
carrega.Minimum_thread = 12; // <forgot that for now
When game starts this warning message are displayed:
AK-Scan - WARNING! [Dont_kill_yet] TURNED ON!
Anti-Kill / Anti-Inject by thread are PAUSED!
Thread counting process allowed!
==================================================
If you use minimizer: start game, and minimize game window.
Open: CODEX ANTIHACK V3\Utilitários\TreadCounter (for antikill)\
ThreadCounter (main.exe)
Your game main name need be
main.exe, obviously. Becouse
ThreadCounter (main.exe) search for GetProcessInfo(
"main.exe");
Monitore thread amount count until that changes, after some minutes, and if it dont change anymore, that is the
number you need to add on
carrega.Minimum_thread = number;
Detail, if your main.exe threads takes, for example: 50 seconds to stabilize thread counter, you need configure that dalay to all detectors. For my main.exe, 20 seconds are good enought.
==================================================
So, Set
START.cpp:
Code:
carrega.Detecta_Inject_by_Thread = 1;
carrega.DInject_Thread_occours = 10000;
carrega.Detecta_Kill_by_Thread = 1;
carrega.Dont_kill_yet = 1; // (0) PAUSE Exitprocess, (1) ACTIVATE exitprocess
carrega.Minimum_thread = 12; // < Thread counter number you need to add
Monitore thread count until that not change. about 5 minutes
==================================================
If you don't use minimizer:
Open: CODEX ANTIHACK V3\Utilitários\TreadCounter (for antikill)\
ThreadCounter (main.exe)
Open: main.exe (game)
Wait some minutes, close game and take
ThreadCounter (main.exe) results.
==================================================
Make everything again, how many times you think are necessary to make sure are no mistakes.
For example:
If [carrega.Minimum_thread] are = 12;
Less than that >
Threads killed > Exitprocess
More than that >
External thread added, inject! > Exitprocess
- - - Updated - - -
[Trusthme!! My configs are ok]
I thrust you, lets try to understand situation.
- Any external like: Mu window, Minimizer, Klick0r, etc. = Exitprocess.
(Inject)
Is that your problem?
- If thread counts change, just one number, more or less, for any reason, or, if main .exe count are not stable for any reason = Exitprocess
Try to undertand thread counts better, make sure main.exe count threads are stable for a long time.
- If thread count takes more than 17 seconds to be stable = Exitprocess
void A1(){
Sleep (
15000);
again:
Sleep (
2000);
k1();
goto again;
}
In this case, increase the first sleep time for all six Anti-kill detectors on
Detecta_AntiKill.cpp, start adding 10 seconds for everyone and add more later if you think that was necessary.
For my mxmain.exe (1.01e), 17 seconds are enought for threads number count be stable. Maybe your main.exe threads takes much more time to be stable. I dont know...
- - - Updated - - -
[ because the rest are good things, but have a much delay]
Delay, realy? My idea are make a more light anti-hack system as possible. Think about, if Someone get an disconnect every one minute, this guy just cannot play... Another thing, if detector are made to detect some hack running on computer memory, it will detect this hack anyway.
Think about, run a Dump scann with five hundred memory dumps every milisecond are necessary or make something more secure? I dont think so.
But if you want to make detectors running REALY, REALY faster.
On START.cpp
carrega.DVerifica_occours = 41000; //Occours every X miliseconds
carrega.DLauncher_Occours = 42000; //Occours every X miliseconds
carrega.DHide_occours = 14000; //Occours every X miliseconds
carrega.DDump_occours = 31000; //Occours every X miliseconds
carrega.DWindow_occours = 11000; //Occours every X miliseconds
carrega.DClassName_occours = 9000; //Occours every X miliseconds
carrega.DInject_occours = 30000; //Occours every X miliseconds
carrega.DPID_occours = 13000; //Occours every X miliseconds
carrega.DSpeed_occours = 12000; //Occours every X miliseconds
carrega.DHeuristica_occours = 1010; //Occours every X miliseconds
carrega.DHeuristica_NC_occours = 1050; //Occours every X miliseconds
carrega.DInject_Thread_occours = 10000; //Occours every X miliseconds
If you turn all this values to = 1; after that, people can use your client to make processor benchmarks or maybe some frittatas. Rsrs
[EDIT 3: high cpu ?]
So... if changing anti-kill speed occour time your CPU goes almost 100%... Imagine greater.
Thust me! Delay are our friend.
você pode criar uma chamada rest, e disparar ela um metodo POST.