Pastebin launched a little side project called HostCabi.net, check it out ;-)Don't like ads? PRO users don't see any ads ;-)
Guest

BF3- Admin Commands.

By: a guest on Aug 25th, 2013  |  syntax: None  |  size: 6.83 KB  |  hits: 29  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. Here are the ingame admin commands!
  2.  
  3.  
  4.  
  5. Description
  6.  
  7. Exposes some basic text based commands to players with accounts and necessary privileges
  8.  
  9.  
  10.  
  11. Command Response Scopes (default)
  12.  
  13. ! Responses will be displayed to everyone in the server. Everyone will see "Phogue has been kicked for team killing".
  14.  
  15. @ Responses will only be displayed to the account holder that issued the command. The command issuer will see "Phogue has been kicked for team killing" but no one else will.
  16.  
  17. # Responses will be displayed to all players that hold an account ("display to admins only"). Only account holders will see "Phogue has been kicked for team killing".
  18.  
  19. All error messages are privately sent to the command issuer
  20.  
  21.  
  22.  
  23. Settings
  24.  
  25. Banning
  26.  
  27. Ban Type
  28.  
  29. Frostbite - Name (default): Bans on the players name alone. This is the weakest type of ban.
  30.  
  31. Frostbite - EA GUID: Bans on the players EA GUID which is tied to their login account.
  32.  
  33. Punkbuster - GUID: Bans a player on their punkbuster GUID.
  34.  
  35. History
  36.  
  37. 3.3.0.0
  38.  
  39. Updated to support BF3
  40.  
  41. Commands (default)
  42.  
  43.  
  44.  
  45. Kicking / Banning
  46.  
  47. @kick [playername] [optional: reason]
  48.  
  49. Kicks a player from your server
  50.  
  51. The reason will appear in the response and is used to display to the player on the games menu
  52.  
  53. Requirements: Minimum of kick privileges
  54.  
  55. @tban [playername] [time in minutes] [optional: reason]
  56.  
  57. Temporarily bans a player from your server for a set time in minutes
  58.  
  59. The reason will appear in the response and is used to display to the player on the games menu
  60.  
  61. By default procon will not allow users with only temporary ban privileges to ban for longer than an hour
  62.  
  63. Requirements: Minimum of temporary ban privileges
  64.  
  65. @ban [playername] [optional: reason]
  66.  
  67. Permanently bans a player from your server
  68.  
  69. The reason will appear in the response and is used to display to the player on the games menu
  70.  
  71. Requirements: Permanent ban privileges
  72.  
  73. Killing
  74.  
  75. @kill [playername] [optional: reason]
  76.  
  77. Kills a player
  78.  
  79. The reason will appear in the response and message sent to the player
  80.  
  81. Requirements: Minimum of kill privileges
  82.  
  83. @nuke [optional: team]
  84.  
  85. Kills every player in the server, or if a team is specified will kill every player on that team
  86.  
  87. Has a 10 seconds countdown that can be canceled with the @cancel command
  88.  
  89. Requirements: Minimum of kill privileges
  90.  
  91.  
  92.  
  93.  
  94.  
  95. Communication
  96.  
  97. @say [text]
  98.  
  99. Says [text] for everyone to see from the Server
  100.  
  101. Requirements: Must hold an account with procon
  102.  
  103. @psay [playername] [text]
  104.  
  105. Says [text] to a specific player from the Server
  106.  
  107. Requirements: Must hold an account with procon
  108.  
  109. @yell [text]
  110.  
  111. BFBC2 & BF3 only
  112.  
  113. Yells [text] for everyone to see in the middle of their screen
  114.  
  115. Requirements: Must hold an account with procon
  116.  
  117. @pyell [playername] [text]
  118.  
  119. BFBC2 & BF3 only
  120.  
  121. Yells [text] to a specific player in the middle of their screen
  122.  
  123. Requirements: Must hold an account with procon
  124.  
  125.  
  126.  
  127. Map controls
  128.  
  129. @restart [optional: timer]
  130.  
  131. Restarts the current map
  132.  
  133. If specified will display a countdown timer than can be canceled with the @cancel command
  134.  
  135. Requirements: Must have "Use Map Functions" privileges
  136.  
  137. @nextlevel [optional: timer]
  138.  
  139. Forwards to the next level
  140.  
  141. If specified will display a countdown timer than can be canceled with the @cancel command
  142.  
  143. Requirements: Must have "Use Map Functions" privileges
  144.  
  145.  
  146.  
  147. Player control
  148.  
  149. @move [playername]
  150.  
  151. Moves a player to another team. Swaps them in Rush, Conquest, Squad Rush and will cycle through the 4 teams in Squad Deathmatch
  152.  
  153. Queues the player and will move them when the next die
  154.  
  155. Requirements: Must be able to move players between teams and squads privileges
  156.  
  157. @move [playername] [squad]
  158.  
  159. BFBC2 & BF3 only
  160.  
  161. Moves a player into a squad on their same team
  162.  
  163. Queues the player and will move them when the next die
  164.  
  165. Requirements: Must be able to move players between teams and squads privileges
  166.  
  167. @move [playername] [team]
  168.  
  169. Moves a player onto another team in no squad
  170.  
  171. Queues the player and will move them when the next die
  172.  
  173. Requirements: Must be able to move players between teams and squads privileges
  174.  
  175. @move [playername] [team] [squad]
  176.  
  177. BFBC2 & BF3 only
  178.  
  179. Moves a player onto another team and into a specific squad
  180.  
  181. Queues the player and will move them when the next die
  182.  
  183. Requirements: Must be able to move players between teams and squads privileges
  184.  
  185. @fmove
  186.  
  187. fmove functions exactly like all of the @move commands except forces the move immediately by killing the player
  188.  
  189. Requirements: Must be able to move players between teams and squads privileges
  190.  
  191.  
  192.  
  193. Countdowns
  194.  
  195. @cancel
  196.  
  197. Cancels all countdowns initiated by the account holder
  198.  
  199. You cannot cancel other account holders countdowns
  200.  
  201. Requirements: Must hold an account with procon
  202.  
  203. Custom Configs (basic in game command addons)
  204.  
  205. @exec
  206.  
  207. Displays a list of configs available in the /Configs/CInGameAdmin/*.cfg directory
  208.  
  209. This command replaces the "@exec -l" command of 1.6 and prior versions of the in game admin
  210.  
  211. Requirements: Must hold an account with procon (the configs validate privileges themselves)
  212.  
  213. @exec [configname]
  214.  
  215. Executes a config in the /Configs/CInGameAdmin/*.cfg directory
  216.  
  217. The config author is responsible for insuring the executing account holder has sufficient privileges
  218.  
  219. No pre-made configs are provided with procon, but you can visit the forums to download configs to extend the in game admin
  220.  
  221. You can make/edit/copy/whatever any more configs, essentially allowing you to make your own basic in game commands =)
  222.  
  223. Requirements: Must hold an account with procon (the configs validate privileges themselves)
  224.  
  225. If procon needs confirmation of your intentions it will ask "Did you mean [command]?", you can then answer !yes which will execute your confirmed command.
  226.  
  227.  
  228.  
  229. Argument Matching
  230.  
  231. Procon will match your command against a dictionary of possible arguments, then order the possibilities by those containing subsets of what you said.
  232.  
  233.  
  234.  
  235. Possibilities: "Phogue", "1349", "Sunder", "Zangen", "Sinex"
  236.  
  237.  
  238.  
  239. "Sangen" will match "Zangen" because only one letter is different and no possibilities have a subset of "Sangen"
  240.  
  241. "sin" will match "Sinex" because even though it is lexicographically closer to "1349", Sinex contains a subset of "sin"
  242.  
  243. Additional Information
  244.  
  245. This plugin is compatible with Basic In-Game Info's @help command
  246.  
  247. In game admin will use Vanilla bfbc2 data if available, then use punkbuster data if available.
  248.  
  249. The in game admin uses a combination of a spell checker with an auto-completer. As of 1.5 the spell checker will favour names/maps/etc that have a subset of what you typed exactly. Play around with it and let me know your horror stories with this feature on the forums =)
  250.  
  251. No one will see you issuing the commands (even you) if you prefix it with a '/'
  252.  
  253. /@kick Phogue (this text won't be displayed in the game)
  254.  
  255.  
  256.  
  257. Greetings
  258.  
  259. NL_Henkenator68