CS2 matchmaking ping cap: mm_dedicated_search_maxping, the default value, and the queue tradeoff

[ice]

CS2 matchmaking ping cap: mm_dedicated_search_maxping, the default value, and the queue tradeoff

CS2 matchmaking picks a dedicated server for you, and one console command decides how far it is allowed to reach. mm_dedicated_search_maxping sets the longest preferred ping to dedicated servers for games.

What the command does

It takes one argument, a ping in milliseconds. Setting it to 60 tells the matchmaker to pass over any server you would reach at more than 60 ms. The description Valve ships with the command in the game's own convar list is "Longest preferred ping to dedicated servers for games".

Total CS lists the default as 150 ms and gives 60 as the example value for a lower latency queue. Valve's official update notes do not state a default for the command, so the 150 figure comes from a third party rather than from Valve's own wording.

The tradeoff

A lower cap usually buys a less laggy match and costs you queue time. The guide puts it plainly: the lower you set the value, the smaller the selection of servers you can queue for, and if a competitive game takes too long to find it suggests raising the value to something like 110.

The command is a filter, not a guarantee. On a quiet night in a low population region the matchmaker can still leave you waiting, because the cap narrows the pool instead of forcing a server inside it.

How to set it

1. Open Settings, then Game, and set Enable Developer Console to Yes.
2. Press the tilde key to open the console.
3. Type the command with your value, for example mm_dedicated_search_maxping 60.
4. Add the line to your autoexec config file if you want it to load on every launch. The CS2 autoexec config topic on this board covers that file.

Ping is not the whole connection

A low ping number does not tell you about packet loss or misdelivery. Those are separate measurements, and CS2 surfaces them in the telemetry HUD rather than inside the ping value.

FAQ

[*]Does the cap apply to Premier as well as Competitive? The command is a matchmaking setting, so it applies to the queues that run on dedicated matchmaking servers. Valve's update notes do not split it by mode.
[*]Will a low cap get me banned? No. It is a client side preference for which servers you join.
[*]Why am I still placed on an 80 ms server with the cap at 50? The matchmaker chooses from what it can find in your region and your party. When nothing inside the cap is available, the wait grows instead.
[*]Is there a region picker in CS2? Valve does not expose one in the settings. The ping cap is the closest control players have over which servers they are matched with.
[*]Does it work in a party? Yes, and the combined constraints of the party decide the final pool.
[*]Where does the command live? In the game's convar list, where it sits alongside the other mm_dedicated_* matchmaking commands.

Sources
CS2 convar list generated from Valve's DumpSource2 dump, build 11162119, 22 October 2026
Total CS: Max matchmaking ping command
Counter-Strike 2 official update notes
Total CS: How to enable the developer console