
Originally Posted by
Lovroman
-snip
Wow, this response was very impressive. You go into so much detail, you deserve a cookie mister. And btw your English is great to.
Anyways, I see what you mean by "using some other function which VAC doesn't know yet". This makes a lot of sense now. Although how do you know what functions are checked by VAC and which are not?
Let's take Titanium for example. If I'm correct (based on the example) coding a hack for this requires that you have a method hooked at
Code:
private void onGUI(){
}
(You could use the others but let's use this as an example)
Let's say VAC has detected this method and if you modify anything in here it will auto-ban you.
If what your saying is correct that means that you have to find a new method to put all your hacks in, right? Something that preferably gets called frequently, like onGUI().
This raises my same question I stated earlier, how do you know what methods VAC has secured and what it hasn't? I'm guessing you'd need to look at previous hacks which have been detected and rule out those methods, right?
Thanks for responding, I am really trying to make a hack that will not get me VAC banned again. :P