vora.tools

Merge CS2 configs

Two configs into one, section by section. Keep the binds from the machine you play on and the crosshair from somewhere else.

Config A

Or paste a crosshair share code

Codes from before the September 2026 update are converted — CS2 does not take them any more. A current code keeps its pixel settings and ignores the picker.

Config B

Or paste a crosshair share code

Codes from before the September 2026 update are converted — CS2 does not take them any more. A current code keeps its pixel settings and ignores the picker.

Two configs and you can start choosing what comes from where.

How the merge decides

Nothing is dropped for being in only one file.
Choosing a source settles disagreements. A setting the other config has never heard of comes along either way, because losing a real setting is worse than inheriting one you did not think about.
A key bound in one file and unbound in the other clashes.
bind and unbind on the same key are the same decision made two ways, so they are counted as one conflict rather than both being written out.
Aliases and unrecognised commands survive.
alias, exec and anything else we did not model are carried through as written. Only a line that could not be re-emitted safely is left out.