TODD BLEUER
Home | MUSIC | Message Boards & Romance Center | PHEASANTS | SPORTS FISHING,FOOTBALL ECT | PETS & LINKS | GENEALOGY | WEB RINGS | Favorite Links | FREE URL SUBMISSIONS | Contact Me | GAMES PLUS | FREE STUFF | MIRANDA'S PAGE | ZACK'S MEGA PAGE | It's All American

-=[BIA]=- ADMINS PAGE

Ok guys here is a list of all the stuff you will need.

Here is the double bind tool

dbinds click here to download file

HERE IS ALL THE AASA BANS

all are the files condenced down.

click here to download file

click here to download file

click here to download file

Here is  the welcome 3 scriped

click here to download file

BAD NAME LIST

click here to download file

Here is the biamd5 file

click here to download file

Here is the md5 file

click here to download file

click here to download file

CVAR CHECKS

click here to download file

Here is the catch all tool

catchall click here to download file

Here is the admin forceclass folder zipped

click here to download file

Here are the admin commands to download

admincommands click here to download file

admincommands1click here to download file

Here are the Admin commands
 
 
 
22. Admin Commands
open xxx.xxx.xxx.xxx?password=adminpassword - Join a server as admin. Replace the x's with the I.P.
Admin a_switchteam <playername> | <playerID> - Switches the team of the specified player (either from Assault to Defense, or vice-versa.) The team switch happens at the beginning of the next round. This is merely a request to change the team of the named player. Other mitigating factors may prevent this player’s team from actually changing the next round.
Admin a_open <mapname> OR Admin a_map <mapname> OR Admin switch <mapname> - Opens a new map. These commands can all be used interchangeably. mapname: the name of the map to open.
Admin restartmap - Restarts the current map.
Admin forceclass (<playername> | <playerID>) <class> - Immediately changes the class of the specified player. The class is specified using one of the following abbreviations:
r - M16A2
m - Modded M4 without M4 Mods
m4m - Modded M4 with m4 Mods
m4a1auto - Ranger M4A1
ma - Ranger M4A1
ar - M249
g - M16A2/M203
s - M82
s24 - M24
sf - Modded M4A1 (or AK74SU)
ak - AK47
ak74su - AK74
gp -AK w/ launcher
rpk - RPK Light Machine Gun
svd - Dragunov sniper rifle
mos - Mosin-nagant sniper rifle
sl - Squad Leader
ft - Fireteam Leader
rct - recruit (no weapons)
Admin ban [ <playername>] [<time(w|h|d|m)>] [ <IP> | <MAC> ] - Bans the specified player from the server for the amount of time specified, w=weeks, m=minutes, h=hours, d=days
Admin kickban [ <playername> | <playerID> ] - Kicks the specified player from the server, and then adds his IP address to the banlist file.
Admin kick [ <playername> | <playerID> ] - Kicks the specified player from the server.
Admin say <message> - Uses the chat to message players.
Admin message <message> - This is similar to admin say, except that the message is delivered in big text to the middle of the screen. Everyone receives the message.
Admin mute [ <playername> | <player ID> | all ] - Mutes the chat specified player. This is a server mute and no players can see what he types. This doesn't affect other Admins or SuperUsers. playername | player ID: mutes the specified player. all: mutes everyone on the server. Using it again unmutes the specified player or all.
Admin deathmessages [ 1 | on | 0 | off ] - Turns death and damage messages off for all players. 1/on: Turns messages on. 0/off: Turns messages off. When changing this setting via the console, your preference is automatically saved in your ArmyOps.ini file. However, if you wish to change the ArmyOps.ini file directly, the variable to look for is bDeathMessages.
Admin score [ 1 | on | 0 | off | round | match ] - Turns the scoreboard on and off. Scoreboard can be displayed at the end of a round, end of a match, or never. Note that certain UI changes mean that even with the scoreboard disabled, players can still (currently) switch to the scoreboard from the weapon selection screen. 1/on: Turns the scoreboard on. 0/off: Turns the scoreboard off. round: Shows scoreboard at end of round only. match: Shows scoreboard at end of match only. When score mode ‘round’ or ‘match’ are specified, the score will be displayed at the appropriate time. The client can then hit ESC to close the score screen, or can wait until the beginning of the next round at which time the score screen will automatically be closed. When changing this setting via the console, your preference is automatically saved in your ArmyOps.ini file. However, if you wish to change the ArmyOps.ini file directly, the variable to look for is ScoreMode and the possible values are: SSM_On, SSM_Off, SSM_Round, and SSM_Match.
Admin motd [ self | all | <text> ] - Sets or displays the message of the day. self: displays message of the day to admin only. all: Displays message of the day to all players. text: The text string to set as the message of the day. We currently have 4 MOTD lines that can be set in ArmyOps.ini. These lines are displayed when a client logs into a server (if they are not blank.) Using the admin motd command to set the MOTD only sets the first line of the MOTD (in the ini file, it’s called MOTDLine1). Similarly, when the self or all parameters are specified, only MOTDLine1 will be displayed. All four lines will still be displayed when a client logs into a server for the first time (provided they aren’t blank.)
Admin roekicktimer [ 1 | on | 0 | off ] - Turns on or off the ROE kick timer at the beginning of the round. 1/on: Turns the ROE kick timer on. 0/off: Turns the ROE kick timer off. Note that entering this command has an immediate effect (i.e. the server doesn’t wait until the start of the next round to use the new value). When changing this setting via the console, your preference is automatically saved in your ArmyOps.ini file. However, if you wish to change the ArmyOps.ini file directly, the variable to look for is bEnableROEKickTimer.
Admin roekick [ 1 | on | 0 | off ] - Turns on or off the ROE kick functionality for players exceeding max ROE. 1/on: Turns on ROE kick. 0/off: Turns off ROE kick. The effect of this command is immediate. When changing this setting via the console, your preference is automatically saved in your ArmyOps.ini file. However, if you wish to change the ArmyOps.ini file directly, the variable to look for is bEnableROEKick.
Admin roekickdead [ 1 | on | 0 | off] - If enabled, instead of a player being kicked for an ROE penalty, they will be killed. 1/on: Turns ROE kick dead feature on. 0/off: Turns ROE kick dead feature off. The damage type used to kill the offending player is suicide, so to other players it may seem like the culprit killed himself. However, the player gaining the ROE sees a specific message telling him he is being killed due to ROE. When changing this setting via the console, your preference is automatically saved in your ArmyOps.ini file. However, if you wish to change the ArmyOps.ini file directly, the variable to look for is bEnableROEKickDeath.
Admin pb_sv_ [ enable | disable ] - Enable enables punkbuster for the server, disable disables punkbuster for the server.
Admin pb_sv_gameauth [ 0 | 1 ] - Enables or disables authorization for a server. 0 stops pb from kicking even with auth off.
Admin quit - Disconnects you from the server and also shuts down the server you are currently admining.
Admin pb_sv_specname <playername> - Spectates the specified player (this really is a PB command but the regular spectate one no longer works).

23. Punk Buster Commands
Tasks
pb_sv_task <start-seconds> <optional-run-every-seconds> - This allows server admins to set a task starting from a specified time in seconds and then running again every x seconds there after. If no re-run value is specified then the task is only run once. This feature is not limited to PB functions and can run in-game functions as well. You may use more than one task if you like. Example:
pb_sv_task 10 300 "say ^3Visit us at www.yourwebsite.com"
pb_sv_task 15 305 "say ^5Email server admins: admin@yoursite.com"
pb_sv_task 700 "pb_sv_bindsrch com_maxfps"
pb_sv_task 700 "pb_sv_bindsrch m_pitch"
This will spam your two messages on screen and re run them at the specified times. The last two will run a bind-cvar check once only.
pb_sv_tlist - Shows what tasks you have running and shows you what slot number each task is assigned to.
pb_sv_taskdel <slot#> - Deletes a task in your list of tasks by slot number. This is useful in keeping multiple tasks from piling up and repeating themselves. In your pbsv.cfg you should insert this command right before your list of tasks to make sure you start off clear. Example:
pb_sv_TaskDel 1
pb_sv_TaskDel 2
pb_sv_TaskDel 3
pb_sv_TaskDel 4
Name Management
pb_sv_badname <grace-seconds> <filter> - This command will allow you to filter out certain text in names, then give the player x seconds to change the name before being removed from the server. Here are some examples:
pb_sv_badname 30 www.
pb_sv_badname 30 .com
pb_sv_badname 30 UnnamedPlayer
pb_sv_badname 30 ogc
pb_sv_badname 30 noskill
pb_sv_badname 30 noname
The first two lines prevent people from using your severs to advertise web sites. The others are just suggested filters and can be adjusted to your preferences. They are all set to give the player 30 seconds of warnings before they are removed from the server.
pb_sv_badnamelist - Lists all the bad names in your check list and shows you each lines assigned slot number.
pb_sv_badnameDel <slot#> - Deletes a name in your list of bad names by slot number. This is useful in keeping multiple bad names from piling up and repeating themselves. In your pbsv.cfg you should insert this command right before your list of bad names to make sure you start off clear.
pb_sv_badnameDel 1
pb_sv_badnameDel 2
pb_sv_badnameDel 3
pb_sv_badnameDel 4
pb_sv_badnameDel 5
pb_sv_badnameDel 6
pb_sv_badname 30 www.
pb_sv_badname 30 .com
pb_sv_badname 30 UnnamedPlayer
pb_sv_badname 30 ogc
pb_sv_badname 30 noskill
pb_sv_badname 30 noname
pb_sv_changePeriod 10 - Amount of seconds allowed between name changes, prevents name spamming.
pb_sv_changeMax 5 - Number of total allowed name changes per session.
pb_sv_dupNameGrace 20 - Amount of time (in seconds) that a duplicate name has to be changed before that player is removed from the server. This ensures that all players on the server have a unique name.
pb_sv_extChar 0 - Control of extended characters in names (characters and symbols that can not be produced from a single key stroke.) 0 to disallow such names. 1 to allow these names.
pb_sv_emptyname 0 - Control the option of a an empty name (no name at all). 0 will not allow an empty string to be returned for a name value. 1 will allow an empty string.
pb_sv_minName 1 - Dictates the minimum amount of actual characters a players name must have to be allowed on the server. This will double check the above pb_sv_emptyname 0 to make sure a player doesn't enter ^7^7 as a name (which satisfies the pb_sv_emptyname 0 but still returns an empty string to the console.) Set this to one to make sure that a player has at least one standard character in their name.
Guid Settings
Pb_sv_noguidgrace 30 - Number of seconds that a player with no guid is kicked (0 - 300) We recommend giving players 30 seconds or so in case of slow communication rate with the master auth server.
pb_sv_updategrace 300 - Number of seconds that a player with a "no updated status" has to update before being kicked (300 - 600)
pb_sv_guidrelax 7 - This setting was added to server version 1.011 to set options for the locked-down guid system. This setting is cumulative based on adding the values for the conditions desired: 1=UNKN Guid, 2=WRONGIP Guid, 4=DUPLICATE Guids. The current default for this setting is 7 (1+2+4) which means that PB will not kick (relax kicking) for any of the three cases. We recommend kicking for at least UNKN guids. Below are the possible combinations:
0= Kick for UNKN guid, wrong ip guid and duplicate guid.
1= Kick for wrong ip guid and duplicate guid.
2= Kick for UNKN guid, and duplicate guid.
3= Kick for duplicate guid.
4= Kick for UNKN guid and wrong ip guid.
5= Kick for wrong ip guid.
6= Kick for UNKN guid
7= Don't kick for UNKN guid, wrong ip guid and duplicate guid.
These values are bitmapped and work like the games FLAGS system, but since they are used to "relax" or disable instead of enable, they are reversed in the sense that you don't add up the numbers but rather subtract them.
Auto Kicking
pb_sv_CQC 1 - This allows admins to turn off / on the feature that shows players why they were kicked (bad name, cvar violation, hook, no guid, etc.) We recommend leaving this ON, so people can see why they were kicked. 1 is ON and 0 is OFF.
pb_sv_KickLen 10 - When kicked from the server for a violation (bad name, cvar violation, hook, no guid, etc.) this is the time (in minutes) that person must wait before they can re-join the server.
Manual Screen Shots
To manually take a screen shot, in game from your console of all players, the command is:
pb_sv_getss
To manually take a screen shot of a specific player, get all the players slot numbers by doing a pb_sv_plist [enter] and when you get the slot number of the person you want to take a screen shot of ( lets say its player number 4 ) type:
pb_sv_getss 4
Automatic Screen Shots
To set up your server to take automatic screen shots, you will need to use and understand the following commands in your pbsv.cfg.
pb_sv_autoss 1 - This setting tells your PB enabled server whether it should retrieve screen shots automatically. Setting to 1 will turn the auto screen shot capture ON and setting it to 0 will turn it OFF. The default is OFF.
pb_sv_autossfrom 60 - This is the MINIMUM number ( in seconds ) that PB will wait after taking a screen shot from players, before attempting to take another one. The default is 60 seconds. Remember that taking screen shots from every player every 60 seconds will rack up a nice number of screen shots in your PB's screen shots folder and use plenty of system resources, sometimes resulting in lag. If there are 10 players on your server and the map lasts 10 minutes, you will be getting 100 screen shots per map. Be careful with this setting. Some recommended settings and samples will be presented at the end of this page.
pb_sv_autossto 1200 - This is the MAXIMUM number ( in seconds ) that PB will wait after taking a screen shot from players, before attempting to take another one. The default is 1200 ( 20 minutes. ) Some recommended settings and samples will be presented at the end of this page.
pb_sv_ssfloor 1 PB - screen shots are taken and then saved numerically. This is the "starting" number that PB will use to name screen shots. Default is 1.
pb_sv_ssceiling 100 - This is the highest number PB screen shots will be saved. After screen shot #100, PB will over write the screen shots starting at your pb_sv_ssfloor setting. Default is 100 but this could easily be reached in a few hours. Some recommended settings and samples will be presented at the end of this page.
pb_sv_ssdelay 0 - Each player will have to wait a random amount of seconds ( up to the number of this setting ) before actually sending the screen shot after the request has been made. This *may* help reduce lag, as all players don't have to send their shots and then get processed and written at the same time, rather they get done randomly within the time frame set. On the other hand, it may cause more lag ( lets say set to 5 ) from screen shots being sent and processed over a longer period of time ( processing 20 players over a 5 second period, rather than an instantaneous "glitch" from all 20 being done at the same time.) Default is 0 which means there is no delay and all shots are taken at the same time.
pb_sv_sspath "" - This is where PB will send the screen shots and the helper html files. The default is "" ( empty ) and need not be specified if you want to keep the shots stored in the default PB screen shots folder.
pb_sv_ssheight 240 - The height in pixels of the screen shot. 240 is the default and the recommended value to maintain a good size while keeping file size and cpu usage at an acceptable level.
pb_sv_sswidth 320 - The width in pixels of the screen shot. 320 is the default and the recommended value to maintain a good size while keeping file size and cpu usage at an acceptable level.
pb_sv_ssSrate 1 - The sample rate ( quality ) of the shot captured. If set to "2" then only every second pixel is taken ( both horizontally and vertically. ) If set to "4" then only every fourth pixel is taken. This reduces file size and cpu usage but significantly reduces the picture quality as well, making it hard to prove those "close calls." Default is 1 and is recommended.
pb_sv_ssxpct 50 - Percentage ACROSS the screen where the center of the screen shot should be captured from. Default is 50 and is recommended to keep the screen shots centered.
pb_sv_ssypct 50 - Percentage DOWN the screen where the center of the screen shot should be captured from. Default is 50 and is recommended to keep the screen shots centered.
Miscellaneous
pb_ver - tells the PunkBuster version
pb_load - load a script of PunkBuster commands (untested)
pb_plist - list of all players on the server and their "PunkBuster status" (Unsure of what this means)
pb_power - list of all players on the server and the different PB status' then pb_plist
pb_kick # - # is the number of a player. Use "pb_power" or "pb_plist" to find the number. It needs 10 people to kick (vote) the player off the server for about 2-5 mins. The votes only count for one round like the regular kick.
pb_myguid - the "unique identifier" PunkBuster has assigned you for this server.
pb_sslog - controls whether any ScreenShots taken of you are logged to the System/pb/scrnshot directory. Default is 1 (yes).
pb_sssave - controls whether additional information is saved (?) whenever you are investigated (? again). Default is 0 (no).
pb_msgprefix - The prefix before any punkbuster messages. Default is "PunkBuster Client". You could change it to "PB Client", for example. (On ET you can apparently change the color, but I don't know how to do this in AA.)
pb_syste - apparently you m can change this (from 0 to 1 or vice versa) if you are having lockup problems
pb_lan - setting defaults to 0; when set to 1, PB will behave as though it has no internet access
pb_webupdate - command adds the PBWEB functionality directly into the PB client; PBWEB should no longer be required to manually update PB clients; PunkBuster will automatically issue this command when necessary to auto-update during gameplay before going into distress mode
pb_sv_maxConUpdates - setting defaults to 12; PB Server will not send updates to more than this number of clients simultaneously in an effort to cut down on update timeouts after a recent PB update
pb_sv_homepath - command to display PB's home path
pb_sv_specname <playername> - Spectates the specified player
pb_sv_update - Attempts a PunkBuster server update.
pb_sv_rcon - If you have server admin on a specific server and want extra admin privalges, you can use PB Rcon.
This works with PB Power so you will need to know how to do that also. When under admin issue the command:
admin pb_sv_rcon [min PB power points needed] [Server command]
min PB power points needed is where when you give power, you needed that number they're min. to be able to run that command.
For server command you can put specific commands <pb_sv_badname, pb_sv_specname..> or if you trust your Power and Rcon people you can do pb_sv_ and they will be able to run all pb_sv_ commands on PB server from in the game. This does not execute regular in game commands.
pb_sv_kick [PB slot number] [minutes] [Displayed reason] || Optional: [Private Reason]
"Ex. admin pb_sv_kick 4 25 No adversing other clans please."
pb_sv_ban [PB slot number] [Displayed reason] || [Private Reason]
To empty that ban list, or any other time bans, etc. on the server type..
pb_sv_banempty
pb_sv_banmask [IP Mask]
Ban a whole mask..
Ex. admin pb_sv_banmask 152.65.
No asktrics go in for wildcards. just the dot and stop there.
pb_security 0/1 - Can be used to alleviate the *WARNING*: PunkBuster Reports PB Server Running Old Version error (use 0 if u are recieving that errror). pb_writecfg can be used 2 write a change the the punkbuster configuration so it is autoloaded.
pb_sleep 20-500 Can be used to set the number of milliseconds betweek pb scans. 500 to reduce lag caused by frequent scans. 20 to increase lag by more frequent scans, though I don't know why anyone would even use a higher number.
Cvar Checks
(Checking of .ini files for varibles)
pb_sv_cvar "[section] [Cvar_name]" [IN/OUT/INCLUDE/EXCLUDE] [P1] [OptionalP2]
To find the section go in Armyops.ini and User.ini and when you find a varable you want to add scroll up till you find something like [Engine.Something] or [<>.<>] That is what the section will be.
Now once you have that go back down the the specific line you want to check.. this is what Cvar_name will be.
Where you see IN/OUT/INCLUDE/EXCLUDE is what kind of varable it is.
If the varable is a number, you will most likely use IN or OUT.
If the varable is something like True/False, you will most likely use INCLUDE or EXCLUDE.
[P1] is what you will be looking for or not looking for.
If __ is specififed:
IN -- [P1] will be the number you want it to be equal to, or if [P2] is defined you want the number to be inside P1 to P2, if only P1 is specified, that number MUST equal P1.
OUT -- Basicly the opposite of IN. If only [P1] is specified, the number must NEVER equal P1, if P1 and P2 are specified, it can't be inside P1-P2.
INCLUDE -- [P1] Will be the only varable that needs to be specified. If P1 is ex. 'True' then that varable must be True to play on your server.
EXCLUDE -- Again the opposite of INCLUDE except [P1], you can't have that in it for you to play on that server.
Examples:
IN - pb_sv_cvar Engine.PlayerInput MouseSenitivity IN 1 4
IN - pb_sv_cvar Engine.Controller Handedness IN 1
OUT - pb_sv_cvar Engine.PlayerInput MouseSenitivity OUT 5 9
INCLUDE - pb_sv_cvar Engine.PlayerController bMessageBeep INCLUDE True
EXCLUDE - pb_sv_cvar Engine.PlayerController bMessageBeep EXCLUDE False
pb_sv_cvarempty - Gets rid of all cvar checks.
Anything that was admin pb_sv_ and list in it, and you expected something to come back will not work.. PB server commands will not echo anything.
Ex. pb_sv_badnamelist
pb_sv_tlist

24. PB Power Tips - Thanks to {WP}_Gedron for this
This is all about the PunkBuster Player Power System, a system similar to votekick. The only thing different about is certain people can have more weight to a votekick than others.
The cool thing is that certain players on their own server can be designated "Deputy" allowing them to remove players from their server (and ban them for 5 minutes[default]).
To do this:
1) Log in as admin
2) Type in the console pb_power and retrieve the player's slot number you wish to make a deputy.
3) Type in the console admin pb_sv_power XX 100 where XX=desired deputy player's slot number.
Nothing will come up in the console if done correctly.
It's good to do another pb_power to check that the right person got the correct votekick power.
Then, as that player (in the game), he can easily kick people without loging out and then re-loging in as admin.
To do this:
1) Open console
2) type pb_power and retrive desired player's slot number
3) type into console pb_kick XX where XX=kicked player's slot number
The player will be kicked from the server and will be banned for 5 minutes(default). This is usually good enough to keep the undesirables from ruining the game for your other players. They will typically get tired of waiting and go play somewhere else instead of waiting that long just to irritate you again.
The "deputy's" weighted kick will last until the server is rebooted.
The kick does not cause any honor loss to the player who is kicked. The message they get when being punted is a little missleading in that you might think he is loosing 100 experience points for being kicked, but actually that 100 refers to the 100 points of "deputy weight" that the kicker had.
The pb_sv_powerdef # setting is used to set the number of power points allocated to players who are not in the local PB Player Power database.
Use the pb_sv_powermin # setting to specify the number of power points required to be applied to a given player before that player is removed from
the game. The pb_sv_powerkicklen # setting holds the number of minutes that players must wait before being allowed to rejoin when removed via
this facility. To completely disable this facility, set pb_sv_powerkicklen to 0.
 
Explanation of the command is on the right. The | symbol means or. Commands with the [] symbols means what's inside those brackets are replaced. Don't keep the [] symbols there when using the command.
There are other commands, but most of them do not work with the GOAA servers. I felt these were the most critical to know.

playerlist - number on the left is the players id number
admin kick playername|playerid - kicks player from server/player can return
admin kickban playername|playerid - bans player from server until server reset
admin message <message> - displays a message in a box in the middle of the screen
admin mute playername|player id | all - can mute the text of one player or all the players on the server.
Type it in again to unmute.
admin a_switchteam playername|player id - handy to get clan members all on the same team
admin PB_SV_BadName [grace_seconds] [text_filter] - Adds a bad name to the list of bad names for the server to disallow in player names
admin PB_SV_BanGuid [guid] [player_name] [IP_Address] [reason] - Adds a guid directly to PB's permanent ban list
admin PB_SV_BanMask [IP Address / Subnet Mask] - Permanently bans players from joining the server from the specified IP Address / Subnet Mask; for example: issuing PB_SV_BanMask "12.34." will cause PB to deny access to all players trying to join from an IP Address that begins with "12.34."; These bans are written to the pbbans.dat file just like bans issued with the PB_SV_Ban command
admin PB_SV_Cvar "[section] [Cvar_name]" [IN/OUT/INCLUDE/EXCLUDE] [Param1] [optional_Param2] - Adds an automatic cvar check to the list of cvars for the server to check for during gameplay
admin PB_SV_CvarEmpty - Empties the list of Cvar range checks in memory (sometimes this works, sometimes it doesn't)
PB_SV_CvarList - Displays the allowed cvar ranges for all cvars that the Game Server is monitoring (can be done as a player too)
admin PB_SV_File [filename] [o/s] [game_version] [filesize] [md5] ... [md5] - This command is used to add checks for other *.u / *.dll files,. The [o/s] parameter can be w (for win32), l (for linux), m (for mac), or a (for all). Multiple md5 hashes can be specified separated by spaces to signify multiple "official" releases for a given file / game version combination.
Example: pb_sv_file agp.u a 1.9.0 900422 e1e6ac94a9c953098bd56a1ad7cfd8f0
admin PB_SV_Power [slot #] [power rating] - Adds player in specified slot # to the locally stored PB Player Power database with the specified power rating (this is your deputy admin command)
admin PB_SV_ProtectTag [Unique ID] [Registered Tag] - Protects the specified PunkBuster Registered Tag on the local server so that players who wear the protected tag without having the correct Registration Credentials will be removed from the server (costs $24 a year for a tag)
admin PB_SV_Task [X] [Y] [command] - Adds a task to PB's Task List; The Task will be executed X seconds after entry and every Y seconds thereafter; use -1 for Y if a one-time task is desired; this can be used to execute game server commands as well as PB commands (this is your message spam command)
admin PB_SV_TaskEmpty - Empties the list of Tasks in memory (sometimes it works, sometimes not)
admin PB_SV_Update - Forces the PB Server to attempt a PB software update even if no players are currently connected
admin PB_SV_KickLen [Minutes] - The number of minutes (default is 2) a player will be kept from being able to rejoin after getting kicked by PunkBuster (You can add this in your txt file so it's already set)
admin pb_sv_md5toolempty - empties the list of md5 checks running on the server
admin pb_sv_md5toolfreq - sets how often each md5 check is ran.
admin pb_sv_md5tool w "" v system/[file to check for] NOT_FOUND - checks for unauthorized folders in the game.