cl_player_proximity_debug<0 / 1>

When set to 1 this option enables player proximity debugging. Default is 0 (disabled).

CategoryGameplay
GameCS2 + CSGO
ScopeGlobal
CheatsRequired

Arguments

These are the parameters cl_player_proximity_debug uses when it is ran. Required arguments must be provided.

<0 / 1>

BoolRequired

Use 0 to disable player proximity debugging and 1 to enable player proximity debug information.

Default: 0

Command Builder

This interactive command builder generates a valid cl_player_proximity_debug command for in-game use. Fill all required fields.

All required arguments filled!

Output Command

cl_player_proximity_debug 0

Related Commands

Browse More

Explore other commands related to cl_player_proximity_debug.

cl_player_ragdolls_collide<0 / 1>

Specifies if player ragdolls are allowed to collide with one another when enabled.

Gameplay CS2 Only LocalCheats Required
View

cl_playerspray_auto_apply<0 / 1>

Determines whether graffiti is automatically applied when the graffiti menu is closed. Default is enabled (1).

Gameplay CS2 + CSGO GlobalCheats Not Required
View

cl_sanitize_player_names<0 / 1>

Replaces other players' names with inoffensive placeholder text within the game.

Gameplay CS2 + CSGO LocalCheats Not Required
View

Command Information

Learn more about how to use the cl_player_proximity_debug effectively.

Argument Data Types

Arguments can be of type String, Number, Bool, or Enum. Provide the correct type for the command to execute correctly.

Required Arguments

Arguments marked as Required must be provided for the command to work. Optional arguments can be left blank.

Command Scope

Commands can be Client-sided or Server-sided. Client-sided commands affect only your game client, while server-sided commands affect the entire server.

Cheats Required

Some commands require sv_cheats to be enabled. If a command has this requirement, it will not run on servers where cheats are disabled.