The conclusion:
*No will give you an anti hack. You need to make it you self.
I prefer starting c# and use kill process.
That's an nice way to start.
Printable View
The conclusion:
*No will give you an anti hack. You need to make it you self.
I prefer starting c# and use kill process.
That's an nice way to start.
Ok, I'll try that but idk the code for it the antihack D:Quote:
Originally Posted by ZeroCold
User-mode blacklist with no obfuscation, code virtualization, or similar protection schemas is a terrible way to start.Quote:
Originally Posted by ZeroCold
Here's a little kick start, look through the whole thread.
http://forum.ragezone.com/f144/resol...or-exe-579575/
Now you're just expanding on the poor idea of a user-mode blacklist.Quote:
Originally Posted by Tman151
Atleast its something for the noobs in c++, Not everyone got the skills to make a pro antihack..Quote:
Originally Posted by gWX0
A blacklist can usually end up causing more problems than solving, especially if the blacklist finds a false-positive.Quote:
Originally Posted by Trilest
I would say otherwise.
So your saying I shouldn't use this? "http://forum.ragezone.com/f144/resolved-c-how-to-kill-processes-containing-word-like-injector-exe-579575/" ?O.OQuote:
Originally Posted by gWX0
Yes, that's what I'm saying.Quote:
Originally Posted by killerzx
oh ok... Then what else should I do? Since idk the codes or anything about making an AntiHack I guess I don't get one then :(.Quote:
Originally Posted by gWX0
lol my post :PQuote:
Originally Posted by Tman151
xD Blacklist is usefull in some cases.
Edit :-
just as an addon to ur anticheat is some wat better
Ofc its easy to bypass and it doesnt bring any harm in adding it
oh ok.. I'll be trying that out :D.Quote:
Originally Posted by katsumi
Unless the blacklist accidentally closes the wrong application, in which it does do harm in being there.Quote:
Originally Posted by katsumi