Point clientcommand: Difference between revisions
m (-kept only relevant stuff) |
(-added class hierarchy, cleanup) |
||
Line 1: | Line 1: | ||
{{ | __NOTOC__ | ||
{{CD|CPointClientCommand|file1=client.cpp}} | |||
{{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. | ||
Line 7: | Line 7: | ||
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. | ||
== Keyvalues == | == Keyvalues == | ||
Line 14: | Line 12: | ||
== Inputs == | == Inputs == | ||
{{IO|Command|Command to execute.|param=string}} | {{IO|Command|Command to execute.{{Bugfix|In Hammer, using " symbol in parameter field will corrupt the [[VMF]] file's structure, making the file unviewable for the next Hammer session.|Remove the string argument manually with a text editor.}}|param=string}} | ||
== See also == | == See also == |
Revision as of 08:14, 22 November 2022
![]() |
---|
CPointClientCommand |
![]() |
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.
Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
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.
Fix:Remove the string argument manually with a text editor.