Check a CS2 config

Counter-Strike says nothing when a line in your config does nothing. It does not warn, it does not log — the setting simply never applies. This finds those lines.

Drop CS2 files to check or inspect, or click to choose

Current configs are checked; cs2_video.txt is read into a settings overview. Nothing is uploaded.

What it looks for

Commands CS2 removed: Configs get handed down — copied out of a video, carried between installs, merged with a teammate’s. Anything from CS:GO that Counter-Strike 2 dropped is still sitting there doing nothing. We name 24 of them and say what replaced each one.
Keys bound twice: Only the last bind on a key survives. The earlier ones look right in the file and have not worked for months.
Aliases nothing defines: A bind calling +jumpthrow when no line creates it. The key does nothing at all, silently.
Values outside their range: The game clamps them, so the number in your file is not the number you are playing with.

What it will not tell you

That a command is dead just because we have not heard of it. Counter-Strike has thousands of console commands and our reference covers the ones that turn up in real configs, so an unfamiliar name is reported as no notes on this and nothing stronger. Every line called broken is either provable from the file itself — a key really is bound twice — or backed by a written entry saying what replaced it.

A config straight out of the game reports nothing wrong, which is the point. A checker that cries wolf is one you stop reading.