Build a safe, testable CSS autoexec

SHORT ANSWER

A safe Counter-Strike: Source autoexec starts empty and adds only commands confirmed by the running build. Keep one setting per line, comment the reason, and test after each small batch instead of importing a large config from Counter-Strike 1.6.

Before you change anything

1. A legitimate Steam installation or dedicated-server installation for Counter-Strike: Source.
2. A backup of every file that will be changed.
3. Access to the local client console or the dedicated-server console, as appropriate.

Version-specific procedure

1. Back up the current user configuration and existing autoexec, if present.
2. Create a minimal autoexec in the location resolved from the live installation; begin with comments only.
3. Add one documented bind or preference, then execute the file from the console.
4. Treat any unknown, cheat-protected, or server-only response as a failed compatibility check and remove that line.
5. Add a final visible confirmation message only if the engine documents such a harmless console output command; otherwise verify by reading back a changed value.

Verify the result

1. The console reports no unknown commands while executing the file.
2. Each active line has a reason and an engine/version source or runtime verification record.

Rollback

1. Rename the new autoexec and restore the backed-up file; launch with defaults to confirm recovery.

Common pitfalls

1. A file that parses successfully can still contain bad values; parsing and performance are separate checks.