Point clientcommand: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
(reworded the warning because it was quite long and a bit hard to understand.)
Line 2: Line 2:


{{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.


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.
Line 7: Line 8:
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 DOES NOT HAVE the ''FCVAR_SERVER_CAN_EXECUTE'' flag set cannot be executed by this entity; any attempt will be reported and blocked.
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 DOES NOT HAVE the ''FCVAR_SERVER_CAN_EXECUTE'' flag set 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.
{{warning|'''This entity can corrupt the map.[[vmf]] file if used improperly.''' Inputs using quotation marks '''"''' in the parameter field will cause the vmf to be broken in such a way that hammer refuses to open and compile it. This is because the vmf uses the same quotation marks to determine the end of a string. It will read the quotation mark or your input, assume that to be the end of the string and then realise that the subsequently written words are nonsensical. {{fix|Either remove the quotation marks while hammer is still running, or open the vmf in a text editor, search for this entity and manually remove the unnecessary quotation marks.}} }}
 
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 ==
== Keyvalues ==

Revision as of 16:50, 19 August 2022

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.


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 DOES NOT HAVE the FCVAR_SERVER_CAN_EXECUTE flag set cannot be executed by this entity; any attempt will be reported and blocked.

Warning.pngWarning:This entity can corrupt the map.vmf file if used improperly. Inputs using quotation marks " in the parameter field will cause the vmf to be broken in such a way that hammer refuses to open and compile it. This is because the vmf uses the same quotation marks to determine the end of a string. It will read the quotation mark or your input, assume that to be the end of the string and then realise that the subsequently written words are nonsensical.
Note.pngFix:Either remove the quotation marks while hammer is still running, or open the vmf in a text editor, search for this entity and manually remove the unnecessary quotation marks.

Keyvalues

Name (targetname) <string>[ Edit ]
The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentname or target).
Also displayed in Hammer's 2D views and Entity Report.
See also:  Generic Keyvalues, Inputs and Outputs available to all entities

Inputs

Command <stringRedirectInput/string>
Command to execute.


Outputs

See also

Retrieved from "https://developer.valvesoftware.com/w/index.php?title=Point_clientcommand&oldid=264079"