Search the Community
Showing results for tags 'commands'.
Found 6 results
-
Hey there, Is there any commands/orders that players can give to bots ? I remember in Quake 3, the players could give simple commands to fellow bots to improve support: follow, defend, kill [username], etc. (check here for more) albeit only the team leader can issue such orders (the team leader could be given to another player at anytime). If i'm not mistaken, this function was input in the game core from the original release, whereas in ET F-A servers we are using Omnibot (right ?) Example: I was just playing on Jay1, the map was baserace, each team has 3 players, rest was filled with bots to reach 12-13 slots in each team. NB: Baserace is basically a CTF map with more complex/interesting game mechanics. All axis bots were on defense. They were standing a position inside their base and not making any move until an enemy was in the nearby. All allies bots were on offense: they were following routes with waypoints, i.e. they were running to the flags. It seemed pretty obvious their behaviors were specifically different. A direct consequence is that the game balance is altered. It reminds me we should be able to issue some basics orders to the bots, can we? I've googled this topic and found plenty of pages for the server side commands (setup of the server), but nothing for client side, in-game orders. Any input appreciated. As usual, in case i haven't post at the right place, please feel free to moderate appropriately.
-
Hello there, its me once again after long time heh, I have a problem and its a command based on my server's enh_command.db and its called !rules command which created it by myself, So this !rules will show rules of the server on the left side of the screen(echo section) whenever u execute but it is shown Public, everyone can see it when u execute the command but how am i supposed to make it appropriately private? Take a look on the texts i made for it:- [command] command = rules desc = Displays the rules of the server exec = echo "^E{^71^E} ^1Cheats/Hacks ^7Are Not Allowed ^e.";echo "^e{^72^e} ^7Be ^1Respectful ^7and Have ^1Discipline ^7Towards Others ^e.";echo "^e{^73^e} ^7Dont ^1Abuse ^7Your Admin Commands ^e.";echo "^e{^73^e} ^7Only ^1English ^7In Main Chat ^e.";echo "^e{^74^e} ^7Walljumping ^7is ^1NOT ^7Allowed on Objective/Campaign Maps ^e.";echo "^e{^75^e} ^1SelfKilling ^7is ^1NOT ^7Allowed ^e.";echo "^e{^76^e} ^1TrickPlanting ^7is ^1NOT ^7Allowed in Objective/Campaign Maps ^e.";echo "^e{^77^e} ^7SpawnKilling ^7is ^2Allowed ^e.";echo "^e{^78^e} ^7XP Whoring is ^2Allowed ^e.";echo "^e{^79^e} ^7Smoke & Arty Spamming is ^1NOT ^7Allowed ^e.";echo "^e{^710^e} ^7Level Hungers/Hunters Are ^1NOT ^7Welcome ^1!";echo "^e{^711^e} ^1MultiSatchel ^7is ^1NOT ALLOWED ^e.";echo "^e*** ^7Thank You !, Enjoy Playing on Our Server and Have Fun ^e ! ***" levels = 0 1 2 3 4 5 6 7 8 9 10 40 60 100 999 ------------------------------------------------------------- Before instead of Echo, "cpm" was used but i erased cpm and instead of it i wrote echo so that it should be private but im not sure about it if it works.. after changing everything to echo, a problem occured This :- step 2 rule went down out of no where and first letter starts with cpm, i was like dafuq cuz theres not even a cpm letter written on this rule's config, ================= Answers n solutions will be appreciated !
-
Well, finally I got encouraged and made a topic to try to fix my lag. I got some infos, hope someone can help me. It gets worst than the screenshots I made, my lagometer always crazy as my fps. velocidade internet.txt
-
Here it is all the /commands with explenation! >>>http://wolfensteinet.com/code-lists/cvar-list-2/
-
I can't remember if it was jay 3 or 4 I was on and I saw another admin use !mycmd. It brought up an entirely different set of commands including !rushing, !recruit, etc. I was wondering why we don't have this on jay 2??? Granted, I supposed we could just make a bind that says rules, or website and recruiting info. But why are the 2 servers different?
-
In-Game Admin - 3.3.0.0 Description Exposes some basic text based commands to players with accounts and necessary privileges Command Response Scopes (default) ! Responses will be displayed to everyone in the server. Everyone will see "Phogue has been kicked for team killing". @ 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 # 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". All error messages are privately sent to the command issuer Settings Banning Ban Type Frostbite - Name (default): Bans on the players name alone. This is the weakest type of ban. Frostbite - EA GUID: Bans on the players EA GUID which is tied to their login account. Punkbuster - GUID: Bans a player on their punkbuster GUID. History 3.3.0.0 Updated to support BF3 Commands (default) Kicking / Banning @kick [playername] [optional: reason] Kicks a player from your server The reason will appear in the response and is used to display to the player on the games menu Requirements: Minimum of kick privileges @tban [playername] [time in minutes] [optional: reason] Temporarily bans a player from your server for a set time in minutes The reason will appear in the response and is used to display to the player on the games menu By default procon will not allow users with only temporary ban privileges to ban for longer than an hour Requirements: Minimum of temporary ban privileges @ban [playername] [optional: reason] Permanently bans a player from your server The reason will appear in the response and is used to display to the player on the games menu Requirements: Permanent ban privileges Killing @kill [playername] [optional: reason] Kills a player The reason will appear in the response and message sent to the player Requirements: Minimum of kill privileges @nuke [optional: team] Kills every player in the server, or if a team is specified will kill every player on that team Has a 10 seconds countdown that can be canceled with the @cancel command Requirements: Minimum of kill privileges Communication @say [text] Says [text] for everyone to see from the Server Requirements: Must hold an account with procon @psay [playername] [text] Says [text] to a specific player from the Server Requirements: Must hold an account with procon @yell [text] BFBC2 only Yells [text] for everyone to see in the middle of their screen Requirements: Must hold an account with procon @pyell [playername] [text] BFBC2 only Yells [text] to a specific player in the middle of their screen Requirements: Must hold an account with procon Map controls @restart [optional: timer] Restarts the current map If specified will display a countdown timer than can be canceled with the @cancel command Requirements: Must have "Use Map Functions" privileges @nextlevel [optional: timer] Forwards to the next level If specified will display a countdown timer than can be canceled with the @cancel command Requirements: Must have "Use Map Functions" privileges Player control @move [playername] Moves a player to another team. Swaps them in Rush, Conquest, Squad Rush and will cycle through the 4 teams in Squad Deathmatch Queues the player and will move them when the next die Requirements: Must be able to move players between teams and squads privileges @move [playername] [squad] BFBC2 only Moves a player into a squad on their same team Queues the player and will move them when the next die Requirements: Must be able to move players between teams and squads privileges @move [playername] [team] Moves a player onto another team in no squad Queues the player and will move them when the next die Requirements: Must be able to move players between teams and squads privileges @move [playername] [team] [squad] BFBC2 only Moves a player onto another team and into a specific squad Queues the player and will move them when the next die Requirements: Must be able to move players between teams and squads privileges @fmove fmove functions exactly like all of the @move commands except forces the move immediately by killing the player Requirements: Must be able to move players between teams and squads privileges Countdowns @cancel Cancels all countdowns initiated by the account holder You cannot cancel other account holders countdowns Requirements: Must hold an account with procon Custom Configs (basic in game command addons) @exec Displays a list of configs available in the /Configs/CInGameAdmin/*.cfg directory This command replaces the "@exec -l" command of 1.6 and prior versions of the in game admin Requirements: Must hold an account with procon (the configs validate privileges themselves) @exec [configname] Executes a config in the /Configs/CInGameAdmin/*.cfg directory The config author is responsible for insuring the executing account holder has sufficient privileges No pre-made configs are provided with procon, but you can visit the forums to download configs to extend the in game admin You can make/edit/copy/whatever any more configs, essentially allowing you to make your own basic in game commands =) Requirements: Must hold an account with procon (the configs validate privileges themselves) 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. Argument Matching Procon will match your command against a dictionary of possible arguments, then order the possibilities by those containing subsets of what you said. Possibilities: "Phogue", "1349", "Sunder", "Zangen", "Sinex" "Sangen" will match "Zangen" because only one letter is different and no possibilities have a subset of "Sangen" "sin" will match "Sinex" because even though it is lexicographically closer to "1349", Sinex contains a subset of "sin" Additional Information This plugin is compatible with Basic In-Game Info's @help command In game admin will use Vanilla bfbc2 data if available, then use punkbuster data if available. 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 =) No one will see you issuing the commands (even you) if you prefix it with a '/'/@kick Phogue (this text won't be displayed in the game) Credits: ProCon. Please post your ingame username on our BF3 server so we can give you admin commands and you can use those to moderate our server when needed. ServerIP :216.155.140.211:25200 Fearless Assassins BF3 Platoon: http://battlelog.battlefield.com/bf3/gate/?returnUrl=|bf3|platoon|2832655241005703849|
