Jump to content
Sign in to follow this  

How to use BF2CC in-game admin commands

Recommended Posts

The following describes how to use bf2cc in game admin commands

(Please note that admins do not need to install bf2cc in order use the admin controls while in-game, bf2cc is typically for main admin use only. Admins can still have full control of players just by using in-game admin commands.)

The .NET Framework MUST be installed on your machine to run the Client or Daemon. Go to WindowsUpdate.Microsoft.com to install it. We recommend that you install ALL recommended updates and service packs from Windows Update.
The .NET Framework 2.0 Beta will NOT work. You can install either the normal 2.0 version or the 1.1 version with the 1.1 Service Pack.

BF2CC Daemon In-Game Administration

The BF2CC Daemon uses a system of in-game chat filtering to look for commands sent by registered Players (admins). If the daemon sees a command sent by a registered Player (admin) it will execute the specified command. The normal permission system still applies, so only admins (players) with the appropriate permissions will be able to perform the appropriate functions.

Quick Setup Guide:

1. Log in to Bf2CC in daemon mode using a top level Administrator account. Note: Only top level Administrator accounts will have the menu choice to register admins for In-Game administration.
2. Make sure you have an admin account created in BF2CC for the player you wish to register for In-Game administration.
3. Have the player join the BF2 server.
4. In the BF2CC player list, right-click on the player and choose "Register Hash for In-Game Admin".
5. Select the admin account you want to register this player (hash) to.
6. Save the changes to the admin accounts by clicking OK.


All commands begin with an exclamation point. !
Users do NOT need to be logged in to the Daemon (with the BF2CC client) once their hash is registered to their admin account.

NOTE: You type commands into the actual in-game chat (like you are sending a chat message to the server), NOT the console that you can pull down with the tilde key.


You can edit the warn/kick/ban shortcuts and the reason they represent using the client. The shortcuts and reasons are in the Options Form, under In-Game Admin. Only users with top level "Administrator" user accounts can edit these reasons and shortcuts.

Alias Usage Function
(!help Displays All w/k/b reasons and Aliases)
Warns a player for the specified reason.

!k .

Kicks a Player with the specified reason.
You can use partial strings for the name. You can also use shortcuts for your reasons. See examples below.

Bans a Player with the specified reason.
You can use partial strings for the name. You can also use shortcuts for your reasons. See examples below.

Shows AutoBalance Status

!ab on
!ab 1
!ab off
!ab 0
Turns AutoBalance On or Off

Changes to the specified Map. The map MUST already be in the Map List.

Sets the specified map as the Next map in the rotation. The map MUST already be in the Map List.

Runs the next map in the rotation.

!shownext !shownext Shows the next map in the rotation.
!restart !restart Restarts the current map round.
!pause !pause Pauses the game.

Warn/Kick/Ban Examples: (The quotes only surround the command for this example, do NOT use quotes when sending your commands)

"!w did tk" - This example would warn the player named "did" or a player with "did" in their name, like "ParaDiddle". In this case, we are using the default shortcut for the Teamkilling reason. This would output to the server like "WARNING!!! ParaDiddle for Team Killing!"

"!k .35 tk" - This example would kick player with ID 35. Notice that when specifying an ID, you must precede the ID with a period. This way, BF2CC won't look for a player with the numbers "35" in their name. To see player ID's in game, you must bring up the score screen and then select the manage tab.

"!w did Stop Being a NOOB!" This example would warn the same player from the example above, but this time we have specified our own custom reason. This would output to the server like "WARNING ParaDiddle!!! Stop Being a NOOB!"

"!k *[ClanABC]* padding" In this example, we are using wildcards, specified by asterisks, to kick multiple players. In this case we are kicking ANY player with the clan tag "[ClanABC]". We are kicking them by using the default Stats Padding shortcut. BF2CC won't spam the server with a reason for everyone. BF2CC will show the reason only for 1 player, but ALL players will see the reason in a dialogue box once they are kicked from the server (assuming PB is enabled).

"!b did tk" This example will permanently ban the player for teamkilling.

"!b did tk day" This example will ban the player for 1 day for teamkilling.

"!b did tk 5000" This example will ban the player for 5000 minutes for teamkilling.

Ban Times can be specified as follows:

?#### (Any Number, specifying the minutes to ban the player for)
A note about using asterisks. Using an asterisk will tell BF2CC to look for ALL matches and kick ANY players (meaning more than 1) who's name matches the search string. For example, "!k [ClanABC]* tk", will kick ALL players whose names begin with the clan tag "[ClanABC]" for teamkilling. If you do NOT use an asterisk and your search string returns more than 1 player, no players will be warned/kicked/banned. You will see an error and it will ask you to be more specific.

Map Command Examples:

"!change kub" This will change the map to "Kubra Dam"
"!change 2" This will change to the 2nd map in rotation.



Available commands

I?ve divided all the commands into ?categories?, makes life easier.

Map commands

Show the next map

Set the next map
!setnext [mapID]
!setnext [partial mapname] [partial gamemode] [mapsize] (mapsize is inf, alt or std, this used to be 16, 32 and 64)

Run the next map

Save the maplist

Remove a map from the maplist
!remove [mapID]

Change the next map and run it
!change [mapID]
!change [partial mapname] [partial gamemode] [mapsize] (mapsize is inf, alt or std, this used to be 16, 32 and 64)

Restart the map (this restarts the round)

Reload the map (this reloads the entire map)

Player management

Resign a player from command or squad position
!resign [partial playername] [reason]

Kill a player
!kill [partial playername] [reason]

Kick a player off the server
!k [partial playername] [reason]

Warn a player
!w [partial playername] [reason]

Ban a player
!b [partial playername] [reason]

Tempban a player
!tb [partial playername] [reason]

Screenshot a player through Punkbuster
!ss [partial playername]

Fling a player (max altitude is 1000 meters)
!fly [partial playername] [altitude]

Switch a player to the other team
!switch [partial playername]
!switch [partial playername] [now]

Displaying text

!s [text]

Team announcement
!st [us/them] [text]

Display the current time (of the server)

Display help information (shows all available commands)

Other commands

Turn on/off map- and kickvotes
!vote [on/off]

Stop the server from running

Configurable settings

Turn on/off debugging
debugging = True/False

Turn on/off logging of admin commands
logging = True/False

Use punkbuster
usePunkbuster = True/False

Time in minutes a player is kicked
kickTime = [minutes]

Time in minutes a player is tempbanned
banTime = [minutes]

Set the admin command symbol (default ?!?)
admCmdSymbol = ?!?

Set the max altitude for ?fly?
maxAltitude = [height in BF2 meters]

Set the height and width of screenshots taken by Punkbuster
pbSsWidth = [width]
pbSsHeight = [height]

Set up admins through their hashes and give them a powerlevel. Look at the dummy hashes to see how to add hashes
adminHashes = [dictionary]

Set up powerlevels for your admins. You can set up a powerlevel for each available command.
adminPowerLevels = [dictionary]

Keep the following in mind when setting up powerlevels: If the admin?s powerlevel is equal or smaller than the admincommand?s powerlevel, the admin can execute the command. Or in other words, if the admin?s powerlevel is greater than the admincomman?s powerlevel, he cannot execute the command.

Set up predefined reasons/messages. For example, ?!k playername tk? results in ?KICKING playername, stop teamkilling!? You can use these predefined reasons/messages when using !k, !b, !tb, !w, !s and !st.
predefinedReasons = [dictionary]

All available maps in PR, this is NOT your server?s maplist
mapListAll = [dictionary]


Custom commands

You are allowed to create your own custom commands. With this, you can extend the admin module with your own custom commands. The ?ad_admin_settings.py? file explains how you can do this.



By default, all the commands that are entered in chat (and are succesful) are stored in /admin/ad_scripts/logs/ad_admin.log. It looks similar to this (it?s a bit messed up here, but you get the idea):

09-04-11 23:05:33: S performed by admin (AfterDune): yes!
09-04-12 00:11:32: FLY performed by admin (AfterDune) on player (AfterDune): 100
09-04-12 00:15:49: S performed by admin (AfterDune): sdfsd
09-04-14 15:49:13: W performed by admin (AfterDune) on player (AfterDune): test
09-04-14 15:55:46: HELP performed by admin (AfterDune):
09-04-14 16:08:14: ST performed by admin (AfterDune): yea!

Share this post

Link to post
Share on other sites
This topic is now closed to further replies.
Sign in to follow this