Radical Aimbot Solution

[Nux]

Ban Hammer.

Seriously though, this is a bad idea.. unless I change O/S, in which case it's a completely sensible solution.

[player1]

@ the last four or five posters: Thanks, I really needed that. LOL!

When they banned Poland, I said nothing because I was not from Poland.
When they banned Windows, I said nothing, because I am not using Windows.
When they banned Linux, I still said nothing, because I am not using Linux.
And now there are only us Mac players left.
All 3 of us.

[temple]

Make Unix/Linnux less bitchy about drivers and I'll listen.

[Patriotpie]

addIP 1.*.*.*
addIP 2.*.*.*
addIP 3.*.*.*
addIP 4.*.*.*
addIP 5.*.*.*
addIP 6.*.*.*
addIP 7.*.*.*
addIP 8.*.*.*
addIP 9.*.*.*
addIP 10.*.*.*
addIP 11.*.*.*
addIP 12.*.*.*
addIP 13.*.*.*
addIP 14.*.*.*
addIP 15.*.*.*
addIP 16.*.*.*
addIP 17.*.*.*
addIP 18.*.*.*
addIP 19.*.*.*
addIP 20.*.*.*
addIP 21.*.*.*
addIP 22.*.*.*
addIP 23.*.*.*
addIP 24.*.*.*
addIP 25.*.*.*
addIP 26.*.*.*
addIP 27.*.*.*
addIP 28.*.*.*
addIP 29.*.*.*
addIP 30.*.*.*
addIP 31.*.*.*
addIP 32.*.*.*
addIP 33.*.*.*
addIP 34.*.*.*
addIP 35.*.*.*
addIP 36.*.*.*
addIP 37.*.*.*
addIP 38.*.*.*
addIP 39.*.*.*
addIP 40.*.*.*
addIP 41.*.*.*
addIP 42.*.*.*
addIP 43.*.*.*
addIP 44.*.*.*
addIP 45.*.*.*
addIP 46.*.*.*
addIP 47.*.*.*
addIP 48.*.*.*
addIP 49.*.*.*
addIP 50.*.*.*
addIP 51.*.*.*
addIP 52.*.*.*
addIP 53.*.*.*
addIP 54.*.*.*
addIP 55.*.*.*
addIP 56.*.*.*
addIP 57.*.*.*
addIP 58.*.*.*
addIP 59.*.*.*
addIP 60.*.*.*
addIP 61.*.*.*
addIP 62.*.*.*
addIP 63.*.*.*
addIP 64.*.*.*
addIP 65.*.*.*
addIP 66.*.*.*
addIP 67.*.*.*
addIP 68.*.*.*
addIP 69.*.*.*
addIP 70.*.*.*
addIP 71.*.*.*
addIP 72.*.*.*
addIP 73.*.*.*
addIP 74.*.*.*
addIP 75.*.*.*
addIP 76.*.*.*
addIP 77.*.*.*
addIP 78.*.*.*
addIP 79.*.*.*
addIP 80.*.*.*
addIP 81.*.*.*
addIP 82.*.*.*
addIP 83.*.*.*
addIP 84.*.*.*
addIP 85.*.*.*
addIP 86.*.*.*
addIP 87.*.*.*
addIP 88.*.*.*
addIP 89.*.*.*
addIP 90.*.*.*
addIP 91.*.*.*
addIP 92.*.*.*
addIP 93.*.*.*
addIP 94.*.*.*
addIP 95.*.*.*
addIP 96.*.*.*
addIP 97.*.*.*
addIP 98.*.*.*
addIP 99.*.*.*
addIP 101.*.*.*
addIP 102.*.*.*
addIP 103.*.*.*
addIP 104.*.*.*
addIP 105.*.*.*
addIP 105.*.*.*
addIP 106.*.*.*
addIP 107.*.*.*
addIP 108.*.*.*
addIP 109.*.*.*
addIP 110.*.*.*
addIP 111.*.*.*
addIP 112.*.*.*
addIP 113.*.*.*
addIP 114.*.*.*
addIP 115.*.*.*
addIP 116.*.*.*
addIP 117.*.*.*
addIP 118.*.*.*
addIP 119.*.*.*
addIP 120.*.*.*
addIP 121.*.*.*
addIP 122.*.*.*
addIP 123.*.*.*
addIP 124.*.*.*
addIP 125.*.*.*
addIP 126.*.*.*
addIP 127.*.*.*
addIP 128.*.*.*
addIP 129.*.*.*
addIP 130.*.*.*
addIP 131.*.*.*
addIP 132.*.*.*
addIP 133.*.*.*
addIP 134.*.*.*
addIP 135.*.*.*
addIP 136.*.*.*
addIP 137.*.*.*
addIP 138.*.*.*
addIP 139.*.*.*
addIP 140.*.*.*
addIP 141.*.*.*
addIP 142.*.*.*
addIP 143.*.*.*
addIP 144.*.*.*
addIP 145.*.*.*
addIP 146.*.*.*
addIP 147.*.*.*
addIP 148.*.*.*
addIP 149.*.*.*
addIP 150.*.*.*
addIP 151.*.*.*
addIP 152.*.*.*
addIP 153.*.*.*
addIP 154.*.*.*
addIP 155.*.*.*
addIP 156.*.*.*
addIP 157.*.*.*
addIP 158.*.*.*
addIP 159.*.*.*
addIP 160.*.*.*
addIP 161.*.*.*
addIP 162.*.*.*
addIP 163.*.*.*
addIP 164.*.*.*
addIP 165.*.*.*
addIP 166.*.*.*
addIP 167.*.*.*
addIP 168.*.*.*
addIP 169.*.*.*
addIP 170.*.*.*
addIP 171.*.*.*
addIP 172.*.*.*
addIP 173.*.*.*
addIP 174.*.*.*
addIP 175.*.*.*
addIP 176.*.*.*
addIP 177.*.*.*
addIP 178.*.*.*
addIP 179.*.*.*
addIP 180.*.*.*
addIP 181.*.*.*
addIP 182.*.*.*
addIP 183.*.*.*
addIP 184.*.*.*
addIP 185.*.*.*
addIP 186.*.*.*
addIP 187.*.*.*
addIP 188.*.*.*
addIP 189.*.*.*
addIP 190.*.*.*
addIP 191.*.*.*
addIP 192.*.*.*
addIP 193.*.*.*
addIP 194.*.*.*
addIP 195.*.*.*
addIP 196.*.*.*
addIP 197.*.*.*
addIP 198.*.*.*
addIP 199.*.*.*
addIP 200.*.*.*
addIP 201.*.*.*
addIP 202.*.*.*
addIP 203.*.*.*
addIP 204.*.*.*
addIP 205.*.*.*
addIP 206.*.*.*
addIP 207.*.*.*
addIP 208.*.*.*
addIP 209.*.*.*
addIP 210.*.*.*
addIP 211.*.*.*
addIP 212.*.*.*
addIP 213.*.*.*
addIP 214.*.*.*
addIP 215.*.*.*
addIP 216.*.*.*
addIP 217.*.*.*
addIP 218.*.*.*
addIP 219.*.*.*
addIP 220.*.*.*
addIP 221.*.*.*
addIP 222.*.*.*
addIP 223.*.*.*
addIP 224.*.*.*
addIP 225.*.*.*
addIP 226.*.*.*
addIP 227.*.*.*
addIP 228.*.*.*
addIP 229.*.*.*
addIP 230.*.*.*
addIP 231.*.*.*
addIP 232.*.*.*
addIP 233.*.*.*
addIP 234.*.*.*
addIP 235.*.*.*
addIP 236.*.*.*
addIP 237.*.*.*
addIP 238.*.*.*
addIP 239.*.*.*
addIP 240.*.*.*
addIP 241.*.*.*
addIP 242.*.*.*
addIP 243.*.*.*
addIP 244.*.*.*
addIP 245.*.*.*
addIP 246.*.*.*
addIP 247.*.*.*
addIP 248.*.*.*
addIP 249.*.*.*
addIP 250.*.*.*
addIP 251.*.*.*
addIP 252.*.*.*
addIP 253.*.*.*
addIP 254.*.*.*

No more aimbotters! It's like magic!

[Odin]

What about *.*.*.*?

[kevlarman]

[snip]No more aimbotters! It's like magic!

joke's on you! g_banips can't hold that many bans.

[Iltama]

What about if we just fill every map with randomly moving *ghost* players, that no one can see. I really don't know if it would work, it's just an idea that I think would make using aimbot a lot harder, atleast with long range weapons, if it would snap into those ghost players.

[Odin]

Sounds like a great idea but that's just more load on the server.

[Nux]

You wouldn't need to fill the map with them. Just have one haunting each player. If you can only make your ghost an enemy to you, that would stop you from locking on to other peoples ghosts. If you can't do that, just make their ghosts move around alot more to make sure it isn't just like locking on to the person.

Is there some way of making a target that the aimbot would try to aim at, but could never do so? This might make them freeze-out or at least keep them spinning on the spot.

[Ivancool]

what we need is for someone to make a spec bot that detects insane kill whoring and then autospecs the suspect looking for things like 180 degree snaps and other aimbot clues (including the rediculous gretch lookup lock lol) and auto kicks aimbotters.

Good idea.
1. The specbot elaborate normal activity patterns utilizing normal players stats.
2. The specbot elaborate haxs activity patterns (fov_360, same hitbox location shots, fast aim with low sensitivity, perfect accuracy, etc).
3. The bot analize the stats of any player and compare them with normal activity patterns to detect possibles anomalies. If the diference is too big, or fits with the haxs patterns  = autokick/ban.
Very complex, very effective.
 
Cons: False positive

[Nux]

When I thought about this, I imagined just how funny it would be to have my aiming 'detected' as aimbotting ^^ ..well, it would be funny the first time at least.

[David]

Ban Vista users.  :wink:

Didn't the graphics card people already do that?

[beerbitch]

what we need is for someone to make a spec bot that detects insane kill whoring and then autospecs the suspect looking for things like 180 degree snaps and other aimbot clues (including the rediculous gretch lookup lock lol) and auto kicks aimbotters.

Good idea.
1. The specbot elaborate normal activity patterns utilizing normal players stats.
2. The specbot elaborate haxs activity patterns (fov_360, same hitbox location shots, fast aim with low sensitivity, perfect accuracy, etc).
3. The bot analize the stats of any player and compare them with normal activity patterns to detect possibles anomalies. If the diference is too big, or fits with the haxs patterns  = autokick/ban.
Very complex, very effective.
 
Cons: False positive

Ok, thats easy to code, I'll get right on that.[/sarcasm]

Actually, what we need is a global BAN list maintained by server admins who sign up for it. When we do catch a real hacker we can put them on this list. The server would read the file from a remote server and use it AND its own ban list to ban these players. We could have it use a combination of subnet/ip guid and nickname.

[Neckhole]

Actually, what we need is a global BAN list maintained by server admins who sign up for it. When we do catch a real hacker we can put them on this list. The server would read the file from a remote server and use it AND its own ban list to ban these players. We could have it use a combination of subnet/ip guid and nickname.

This is possibly the best idea within the thread, both in terms of practicality and probably in development.

[Ranger]

dual booting linux and windows ftw

[Thorn]

Ban Solaris

[DHRUVINATOR]

Not a Very Good solution.
Maybe a global website for registering you GUID with your name etc..
Once 1 is spotted we can report to moderators of the site  and they can check they ban the GUID. Yes aimbotter will get another GUID but thats life..

[David]

Actually, what we need is a global BAN list maintained by server admins who sign up for it. When we do catch a real hacker we can put them on this list. The server would read the file from a remote server and use it AND its own ban list to ban these players. We could have it use a combination of subnet/ip guid and nickname.

This is possibly the best idea within the thread, both in terms of practicality and probably in development.

I've thought about this before.
It should be quite doable with out needing to go near the tremulous source.

What you would need is a script on each server that every half an hour reads the admin.dat file, and sends all changes to the server, and then downloads new changes from the server.  gpg could be easily used to prevent evildoers from sending in fake bans, and each server could be configured to use the data from the master as it wishes, only trusting bans that are on X many servers, while having a white list of server and admins to trust, and a black list of server and admins to ignore.

It should be quite doable if a few people with the skills and resources put there minds to it.

[NiTRoX]

Not a Very Good solution.
Maybe a global website for registering you GUID with your name etc..
Once 1 is spotted we can report to moderators of the site  and they can check they ban the GUID. Yes aimbotter will get another GUID but thats life..

You have a fucking awesome sugnature.

[Dracone]

...CRUSADES AND REVOLUTIONS...

O YA!!!!!!!!!!!!!!!!!!!!

[beerbitch]

Not a Very Good solution.
Maybe a global website for registering you GUID with your name etc..
Once 1 is spotted we can report to moderators of the site  and they can check they ban the GUID. Yes aimbotter will get another GUID but thats life..

Include ip or subnet in this list. Subnet can be shared with other players that aren't cheating so instead of auto-banning that subnet maybe the trem patch for the server would send a PM to the admins saying this player "might" be the guy on the master list.

[rdizzle]

my other solution included a biometric/force feedback qkey that electrocutes cheaters and anyone who is issued a perm ban...

[tehOen]

my other solution included a biometric/force feedback qkey that electrocutes cheaters and anyone who is issued a perm ban...

IDEA STEALER!

[Mispeled]

And now there are only us Mac players left.
All 3 of us.

When did we get a third one?

[daenyth]

This idea is fucking moronic.

How do we know that the client is windows? The client sends us that information. Oh wait, the client is open source. I guess they can just modify the client to say they're on linux.

Doing this would actually increase the percentage of aimbots among players by getting rid of legit ones and not the cheaters.


tl;dr version: you're fucking stupid

[beerbitch]

This idea is fucking moronic.

How do we know that the client is windows? The client sends us that information. Oh wait, the client is open source. I guess they can just modify the client to say they're on linux.

Doing this would actually increase the percentage of aimbots among players by getting rid of legit ones and not the cheaters.


tl;dr version: you're fucking stupid

Did you even read the 1st post ? Its the TCPIP stack that would determine which operating system you're running, not some code in the client. Just how do you code a trem client to spoof a whole network stack ?

Why did I even respond to you, its obvious you're just a dumb troll.

This idea is rather ridiculous, hence the word "Radical" in the title. I wanted a productive discussion of how we can fix the hacker problem.

I like the idea of a master hacker ban list, and David's suggestion of using scripts to pull it into an admin.dat file is good. I'm not sure I like being able to push data back to the list though. I think a forum where admin server members could go to decide bans (using demo as proof etc) would be a better idea.

[Ryanw4390]

I say you guys figure out something to have Linux only servers or something, then you won't be playing with aimbots. Don't ruin the game for all windows users though.

[NiTRoX]

lets just ban the fucking linux users

[beerbitch]

lets just ban the fucking linux users

Oh hi NiTRoX

[PwNz!]

Hey, it was just an idea. You guys have a better one ?

Yes, Let the server people run an easy script kiddy app that will ban anyone that uses n_ commands. :/