• If you are not the person that was banned/muted, you are only allowed to post evidence. Trash talk is unnecessary.
Haters-Gonna-Hate.jpg
 
Putting that software on your server is like putting asbestos in your house, by the time you realize it's killing you it's to late. I wonder how long you have until every one gets band from skial.
 
Putting that software on your server is like putting asbestos in your house, by the time you realize it's killing you it's to late. I wonder how long you have until every one gets band from skial.

That's not how asbestos works... If you break it up and breathe in the particles then you're at a higher risk for cancer. It's not some secret killer that attacks you in your sleep.

#HighHorseFail
 
  • Like
Reactions: Doki
Two false positives in the span of a week. I'd say that is evidence of faulty software.


I've read all of the posts here but I'm still having a hard time understanding your argument. I apologize in advance if this is a stupid question. Does the server "reject" bullets fired from a gun if they're fired faster than the set rate or is the client simply unable send commands faster than the set rate? If it's a client-side "limitation" then this seems like an area which hackers could exploit - no?
 
  • Like
Reactions: Doki
Auto-Fire - Player holds down +attack and fires semi-auto weapons as if they were full-auto.

http://forums.alliedmods.net/showpost.php?p=1586521&postcount=16

Discussion in this thread clearly outlined he was banned for +attack as listed in the autotrigger detection (thanks for the link to the maker Oaky) and Semi automatic weapons in TF2 now have a capped fire rate so you can't fire them full auto anymore no matter how fast you click or how cleverly you macro the button. The mod is pointless in regards for TF2, but is outlined as working for all source games; both 'positives' were detected on TF2 servers; where it's impossible to do what the detector implies. Just remove the auto fire thing from your TF2 servers before it causes more problems.
 
how about you just un-ban the guy. If he's still using a hack the anti-cheat plugin will pick it up and re-ban him.

PROBLEM FUCKING SOLVED
 
Auto-Fire - Player holds down +attack and fires semi-auto weapons as if they were full-auto.

http://forums.alliedmods.net/showpost.php?p=1586521&postcount=16

Discussion in this thread clearly outlined he was banned for +attack as listed in the autotrigger detection (thanks for the link to the maker Oaky) and Semi automatic weapons in TF2 now have a capped fire rate so you can't fire them full auto anymore no matter how fast you click or how cleverly you macro the button. The mod is pointless in regards for TF2, but is outlined as working for all source games; both 'positives' were detected on TF2 servers; where it's impossible to do what the detector implies. Just remove the auto fire thing from your TF2 servers before it causes more problems.


I have no idea why it is so hard for you guys to read. I already fired several hundred bullets with +attack and did not even trigger 1 out of the 20 detections needed to get banned.

If you want proof, go to kc1.skial.com and try it for yourself. If you get 1 detection, it will tell you in chat, and will not ban you.
 
  • Like
Reactions: Doki
how about you just un-ban the guy. If he's still using a hack the anti-cheat plugin will pick it up and re-ban him.

PROBLEM FUCKING SOLVED

Not really, if we unban people all the time, people will think they're entitled to a second chance for everything. Why don't we just unban people for sv_cheats detections and aimbot detections while we're at it?
 
how about you just un-ban the guy. If he's still using a hack the anti-cheat plugin will pick it up and re-ban him.

PROBLEM FUCKING SOLVED
Not really, if we unban people all the time, people will think they're entitled to a second chance for everything. Why don't we just unban people for sv_cheats detections and aimbot detections while we're at it?

He's already been unbanned for having a normal K/D. Check SourceBans.