Would we be able to have a list of the CI reasons IDs and the meanings please?

http://www.unknowncheats.me/forum/call- ... earch.html

It would be nice if they kept posting their progress like that, so that we could patch the aCI before the hacks get even finished

It would be nice if they kept posting their progress like that, so that we could patch the aCI before the hacks get even finished

hehe indeed.

I lol at this post

 

 

Like tekno really have aCI.

I lol at this post

 

 

Like tekno really have aCI.

 

Why does everyone seem to refer to any CI system as aCI...

Would we be able to have a list of the CI reasons IDs and the meanings please?

 

This. NTAuthority should delivar!!!11!!1

inb4 "everything means cheats"

Just me guessing, but from what I understood of the workings back in aIW, the different IDs mean different methods, not specific cheats. So perhaps different places of injection or so? If so, a list would be pretty useless..

Just me guessing, but from what I understood of the workings back in aIW, the different IDs mean different methods, not specific cheats. So perhaps different places of injection or so? If so, a list would be pretty useless..

false, detections aren't only for methods, they are also specific

Lol it's funny how they think that we're incapable of spying on their dirty little deeds so we can immediately patch everything. Hackers gonna hack I guess, just not for long before we patch em' out xD

oh, but of course

Immature stupid people are gunna be stupid

already had a more advanced aCI finished locally, but hesitating to upload as it might cause issues

already had a more advanced aCI finished locally, but hesitating to upload as it might cause issues

Well you can try to test it with staff people first, and check if it causes any issues ?

Well you can try to test it with staff people first, and check if it causes any issues ?

The only way to test it with staff only is if staff is running a different client build.

But by what I've seen with IW5M, the staff isn't a sufficient sample to spot all the problems. Problems usually show up on messed up environments (such as nab users operating systems)

While testing on public, we can never know when a false detection happened, or when they're being good liars.

Well you can try to test it with staff people first, and check if it causes any issues ?

The only way to test it with staff only is if staff is running a different client build.

But by what I've seen with IW5M, the staff isn't a sufficient sample to spot all the problems. Problems usually show up on messed up environments (such as nab users operating systems)

While testing on public, we can never know when a false detection happened, or when they're being good liars.

 

or something like Connecting.... problem. All of staff didnt have that problem

Well you can try to test it with staff people first, and check if it causes any issues ?

The only way to test it with staff only is if staff is running a different client build.

But by what I've seen with IW5M, the staff isn't a sufficient sample to spot all the problems. Problems usually show up on messed up environments (such as nab users operating systems)

While testing on public, we can never know when a false detection happened, or when they're being good liars.

Hmm yeah I do agree on that system part, people just don't know how to install things properly.