Point clientcommand: Difference between revisions
UselessMouth (talk | contribs) No edit summary |
UselessMouth (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
{{base point|point_clientcommand}} It issues commands to the client console as if they were typed manually by the player. The client commands are sent as parameters of the ''Command'' [[input]]. One instance of the entity is ever needed in a map. | {{base point|point_clientcommand}} It issues commands to the client console as if they were typed manually by the player. The client commands are sent as parameters of the ''Command'' [[input]]. One instance of the entity is ever needed in a map. | ||
{{bug|{{csgo}} Doesn't work for any other player aside from the host.}} | {{bug|{{csgo}} Doesn't work for any other player aside from the host.}} | ||
In multiplayer games, the commands are only executed on the [[Activator]]'s client. If the activator was not a player, then it simply won't do anything (unless it's in commentary mode; then the command will be executed from the first player). If you require all players to execute the command, use the [[point_broadcastclientcommand]] entity instead. | In multiplayer games, the commands are only executed on the [[Activator]]'s client. If the activator was not a player, then it simply won't do anything (unless it's in commentary mode; then the command will be executed from the first player). If you require all players to execute the command, use the [[point_broadcastclientcommand]] entity instead. | ||
Revision as of 07:38, 19 March 2020
Template:Base point It issues commands to the client console as if they were typed manually by the player. The client commands are sent as parameters of the Command input. One instance of the entity is ever needed in a map.
Bug:
Doesn't work for any other player aside from the host. [todo tested in ?]
In multiplayer games, the commands are only executed on the Activator's client. If the activator was not a player, then it simply won't do anything (unless it's in commentary mode; then the command will be executed from the first player). If you require all players to execute the command, use the point_broadcastclientcommand entity instead.
This command (in conjunction with point_servercommand and the config (cfg) file) used to allow a client to cheat on multiplayer servers through changing player names, execute client commands, and other things. On multiplayer servers, any command that has the FCVAR_SERVER_CAN_EXECUTE flag set (this is the default for most of the available commands) cannot be executed by this entity; any attempt will be reported and blocked.
Warning:This entity can corrupt the vmf file if used improperly. If your map crashes when you open it, this could be the problem. Open the vmf file in notepad and press Ctrl+F. Search for command and remove that line.
One way in which this entity can become corrupted is by enclosing commands that contain spaces in quotation marks. In some other contexts this is necessary to make sure the computer does not interpret a space as the end of the command, but here it will cause an immediate map crash on attempting to save, compile, or open the map. The map can be repaired by removing the superfluous quotation marks in Notepad or with a tool such as PSPad. Attempting to open the map in Object Viewer may fail but yield a useful error message that gives the exact line of code to be edited, referred to as a "malformed expression."Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentnameortarget).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
Inputs
- Command <string>
- Command to execute.