cl_phys_stop_at_collision<0 / 1>

Controls whether physics-driven entities should halt when colliding with something; primarily a debugging feature that needs cheats enabled.

GameCS2 Only
ScopeLocal
CheatsRequired

Arguments

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

<0 / 1>

BoolRequired

Set to 1 to make physics entities stop at collisions or 0 to allow them to continue.

Default: 0

Command Builder

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

All required arguments filled!

Output Command

cl_phys_stop_at_collision 0

Related Commands

Browse More

Explore other commands related to cl_phys_stop_at_collision.

cl_allow_animated_avatars<0 / 1>

Determines whether animated avatars are permitted in the game.

CS2 Only LocalCheats Not Required
View

cl_ent_showonlyattachment<0 / 1>

Used as a cheat, this command shows only entity attachments, assisting developers in debugging attachment problems.

CS2 Only LocalCheats Required
View

cl_ent_vcollide_wireframe<0 / 1>

Toggles an entity's interpolated vcollide wireframe visibility, useful for map debugging or inspecting collision calculation; requires a cheat-enabled server.

CS2 Only LocalCheats Required
View

Command Information

Learn more about how to use the cl_phys_stop_at_collision 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.