Tweet
This is going to be a work in progress thread.......so bear with me...........if it looks incomplee (will remove this when done)
1. Make sure you are streaming your servers (server admins)
Ok first thing is first you suspect someone on your server is cheating, what do you do as an admin?
Record a demo.
While you are following your suspect, open your console and type "/record" (to stop recording, enter "/stoprecord"). A good demo is at least five minutes long, but many streaming services require a longer demo for certain bans (for example, PBBans generally requires a ten minute demo for wallhacks). This will serve as evidence if somebody wants to appeal your ban.
Take PunkBuster Screenshots (PBSS).
This is most helpful if you suspect somebody is using wallhacks or chams. To take a PBSS, open your console, log into RCON (/rconpassword <password>), and type "/rcon pb_sv_plist". You'll then see a list of all the players connected to your server. Take note of the player's slot number (the leftmost number). Then type "/rcon pb_sv_getss <slot>. To review your PBSSes, go to the /game/pb/svss folder in your server using FTP. Taking good PBSSes will be discussed in the next section.
Know what hacks look like.
Below is a great example of a multihack that contains all of the most common hacks:
http://www.youtube.com/watch?v=aG9uw3jF ... re=related
Here's a brief description of the various hacks seen in this video:
Aimbot. An aimbot "snaps" the player's aim from player to player automatically. The aimbot in this video would be referred to as "full snap" because it moves from head to head instantly. A "humanized" bot will move between targets more slowly and inaccurately.
Wallhack. A wallhack allows the player to see nearby players through walls. The server doesn't return the position of players on the whole map, so the effectiveness of a wallhack is limited to nearby players.
Chams. Chams are any kind of visual that could not be produced by the unchanged game itself. These include player information, enemy spawn timers, and rocket cameras
Check the PBBans Master Player and Master Ban indexes.
Use the pb_sv_plist command and write down the last eight characters of the player's GUID. Go to the PBBans homepage and click on the MPi (if you have a PBBans account) or the MBi. Enter the GUID in the text entry field, then select "GUID", "Exact Match," and the game name from the drop down menus. Check "Show Linked GUIDs" and "Alias Tracker." It is up to the server owner what criteria constitutes a ban. The most common criteria are an exact IP match and a common alias between two GUIDs. PBBans also has a similar tool.
Now that you have your demo and screenshots, you will need to submit them to pbbans/Punksbusted
PBBANS FORMAT
http://www.pbbans.com/forums/index.php?showtopic=63301
PUNKSBUSTED FORMAT
http://www.punksbusted.com/wiki/index.p ... creenshots
thanks to the follwoing places for content for this thread
www.wikihow.com/Catch-a-Cheater-in-Quake-3-Based-Games
www.pbbans.com
www.punksbusted.com
1. Make sure you are streaming your servers (server admins)
Ok first thing is first you suspect someone on your server is cheating, what do you do as an admin?
Record a demo.
While you are following your suspect, open your console and type "/record" (to stop recording, enter "/stoprecord"). A good demo is at least five minutes long, but many streaming services require a longer demo for certain bans (for example, PBBans generally requires a ten minute demo for wallhacks). This will serve as evidence if somebody wants to appeal your ban.
Take PunkBuster Screenshots (PBSS).
This is most helpful if you suspect somebody is using wallhacks or chams. To take a PBSS, open your console, log into RCON (/rconpassword <password>), and type "/rcon pb_sv_plist". You'll then see a list of all the players connected to your server. Take note of the player's slot number (the leftmost number). Then type "/rcon pb_sv_getss <slot>. To review your PBSSes, go to the /game/pb/svss folder in your server using FTP. Taking good PBSSes will be discussed in the next section.
Know what hacks look like.
Below is a great example of a multihack that contains all of the most common hacks:
http://www.youtube.com/watch?v=aG9uw3jF ... re=related
Here's a brief description of the various hacks seen in this video:
Aimbot. An aimbot "snaps" the player's aim from player to player automatically. The aimbot in this video would be referred to as "full snap" because it moves from head to head instantly. A "humanized" bot will move between targets more slowly and inaccurately.
Wallhack. A wallhack allows the player to see nearby players through walls. The server doesn't return the position of players on the whole map, so the effectiveness of a wallhack is limited to nearby players.
Chams. Chams are any kind of visual that could not be produced by the unchanged game itself. These include player information, enemy spawn timers, and rocket cameras
Check the PBBans Master Player and Master Ban indexes.
Use the pb_sv_plist command and write down the last eight characters of the player's GUID. Go to the PBBans homepage and click on the MPi (if you have a PBBans account) or the MBi. Enter the GUID in the text entry field, then select "GUID", "Exact Match," and the game name from the drop down menus. Check "Show Linked GUIDs" and "Alias Tracker." It is up to the server owner what criteria constitutes a ban. The most common criteria are an exact IP match and a common alias between two GUIDs. PBBans also has a similar tool.
Now that you have your demo and screenshots, you will need to submit them to pbbans/Punksbusted
PBBANS FORMAT
http://www.pbbans.com/forums/index.php?showtopic=63301
PUNKSBUSTED FORMAT
http://www.punksbusted.com/wiki/index.p ... creenshots
thanks to the follwoing places for content for this thread
www.wikihow.com/Catch-a-Cheater-in-Quake-3-Based-Games
www.pbbans.com
www.punksbusted.com