Steam downloads that crawl, Epic Games Launcher connection errors, and unstable matches on overseas servers can look like the same “Clash problem,” but they are different network tests. A game download is a high-volume transfer from a content delivery network. A match is a stream of small, time-sensitive packets, often using UDP. A launcher may use HTTPS for sign-in and updates, while the game itself connects to a separate set of hosts and ports.

That difference matters when choosing a node or writing rules. A node that transfers a large file quickly is not automatically the best choice for a game server, and a low ping shown in a node test does not prove that the game uses the same route. This guide separates those tasks and shows how to test them without sending every PC connection through a proxy.

Clash for PC Gamers: Tune Steam, Epic Downloads and Online Play

Separate download speed from game latency

Before changing the configuration, identify what is actually failing. Note whether the issue affects Steam downloads, Epic downloads, launcher sign-in, matchmaking, or an active match. Close other large downloads and repeat one test at a time. If Steam is downloading at 2 MB/s while the game has stable ping, the problem is probably throughput, download-region selection, or the route to the content server—not real-time game latency.

Record a baseline before editing anything: the game server or region, in-game ping, whether voice chat works, the launcher’s download rate, and the node selected in Clash. Repeat the same test after each change. If you change the node, DNS mode, rule set, and TUN setting all at once, you will not know which change helped—or caused a new problem.

Check the Clash client and traffic mode

Clash Verge, Clash Verge Rev, and other desktop clients provide a control interface; the active core performs routing. Confirm that the client is running, the configuration is loaded, and the selected proxy group is using the node you intend to test. The names and menu locations vary by client version, but the same checks apply: inspect the current profile, the system proxy state, the TUN state if used, and the connection log.

System proxy mode affects applications that honor the operating system’s HTTP or SOCKS proxy settings. It is useful for launchers and browsers that follow those settings, but it does not capture every game process. Some games open direct sockets, use UDP, or start a separate executable that ignores the system proxy. In that situation, the launcher may appear in Clash’s connection list while the game traffic does not.

TUN mode creates a virtual network interface and can capture traffic beyond applications that explicitly use the system proxy. It is often more suitable when a game does not respect the system proxy, but it requires the client and core to support TUN, and may require administrator permission on Windows. TUN is not a guarantee that every connection will be proxied: routing rules, DNS handling, process metadata support, and exclusions still matter.

Enable only one deliberate path while testing. If another VPN, proxy client, network filter, or security product is active, temporarily disable it to avoid competing routes. Check the Clash connection log while launching the game or starting a download. Look for the destination, matched rule, selected policy, and connection result. If no related entry appears, the traffic may be bypassing Clash, or the client may not be capturing that protocol.

Choose a node for each task

Do not select a node from one number alone. A client’s latency test may probe a particular address using a particular method; that is useful for comparing candidates, but the result may not match the route to a Steam CDN or a game server. Test at least two or three nodes that are geographically and operationally plausible, then compare them under the same conditions.

For a clean comparison, keep the game region fixed, close background downloads, and switch only the node. Some services select a CDN based on the client’s apparent location, so changing nodes may also change the download server. That can make one node faster for a particular file without making it a better general-purpose node. Conversely, a node with a slightly slower download can still provide a more stable route to a game server.

Use the client’s delay test as a preliminary filter, then validate with the application that matters. For online play, enter a real match or use the game’s own network diagnostic. A ping to the proxy server measures the path to the proxy, not the complete path from the PC through that proxy to the game server.

Route Steam and Epic traffic carefully

In rule mode, Clash evaluates rules from top to bottom. A rule can send matching traffic to a proxy group, a direct connection, or another policy. The group name in a rule must exist in proxy-groups, and the rules must appear before any catch-all rule such as MATCH. If an earlier broad rule matches the destination, a later Steam or game-specific rule will never be reached.

Steam and Epic use multiple services for store pages, authentication, updates, and content delivery. Download hosts can vary by region and session, and a game may use domains and IP addresses that are unrelated to the launcher. A short list of domain suffixes is therefore only a starting point, not a complete catalog of all traffic. Use the connection log during a real download or game session to identify which destinations are actually being matched.

The following example shows the structure of explicit routing rules. It assumes that Game-Proxy and Download-Proxy are already defined as proxy groups in the configuration. The example domains are not a universal coverage list; verify the destinations generated by your own client and games before relying on it.

proxy-groups:
  - name: Game-Proxy
    type: select
    proxies:
      - "Choose a node"
      - DIRECT

  - name: Download-Proxy
    type: select
    proxies:
      - "Choose a node"
      - DIRECT

rules:
  - DOMAIN-SUFFIX,steamcommunity.com,Download-Proxy
  - DOMAIN-SUFFIX,steampowered.com,Download-Proxy
  - DOMAIN-SUFFIX,steamcontent.com,Download-Proxy
  - DOMAIN-SUFFIX,epicgames.com,Download-Proxy
  - DOMAIN-SUFFIX,epicgames.dev,Download-Proxy
  - MATCH,DIRECT

Replace "Choose a node" with a proxy name that exists in the active configuration, or use a compatible group already supplied by the profile. Do not paste the example over a subscription-generated configuration without checking how the client handles custom rules. Some clients provide an override or rule editor; direct edits to a generated file may be overwritten when the subscription updates.

To route one game rather than every launcher-related domain, first check whether the installed Mihomo core and client can match process names in the traffic-capture mode you use. A process rule can be useful when supported, but it is not equivalent to a domain rule and may not work for traffic that the core cannot associate with a process. Do not assume that a process-name rule will capture UDP when only the system proxy is enabled. If a process rule is unavailable or unreliable, use TUN where appropriate and confirm the resulting connections in the log.

Troubleshoot Steam and Epic downloads

Start with the download client’s own settings. In Steam, open Settings → Downloads and try another download region, then pause and resume the same download to compare. In Epic Games Launcher, check its download throttling or rate-limit setting if available in the installed version, and confirm that no other application is saturating the connection. Menu labels can change between releases, so look for the current download or bandwidth controls rather than relying on an old screenshot.

Then compare the same download with Clash routing changed in one step at a time:

  1. Test direct access with Clash’s relevant rule set to DIRECT, if direct access is available and appropriate on your network.
  2. Test a candidate node with the download domains routed through the intended proxy group.
  3. Try a second node while keeping the download region and file unchanged.
  4. Compare a sustained interval, such as several minutes, and note whether the rate is steady, fluctuating, or repeatedly dropping to zero.

If the download becomes slower through the proxy, the node may have less available capacity than your direct route, or the content service may be assigning a less suitable CDN endpoint. Proxying adds another network leg: the PC connects to the proxy, and the proxy connects onward to the service. That can improve access when the direct route is poor, but it can also add congestion and reduce throughput.

If the launcher shows an error rather than a slow rate, inspect the Clash log for failed DNS lookups, rejected connections, or a rule that sends the request to an unintended policy. Confirm the Windows firewall allows the launcher and game binaries, and check that the system date and time are correct for sign-in and certificate validation. Avoid adding a wide rule for an entire CDN provider based only on one observed address; shared CDN IPs may serve unrelated services.

Do not use a large download as the only latency test. A download can fill the available bandwidth and increase queueing delay, making a simultaneous game feel worse. For a fair game test, pause Steam and Epic downloads, wait for other updates to finish, and then compare in-game network statistics.

Verify UDP and in-game connections

Many online games use UDP for real-time traffic because it avoids waiting for retransmission of every lost packet. Some also use TCP or HTTPS for login, matchmaking, voice, telemetry, or patch services. A successful login therefore does not confirm that the game’s UDP path works. Likewise, a game may appear in the Clash log through its web requests even though its match traffic is going direct or failing elsewhere.

Check the selected node’s protocol capabilities and the active core’s support for the protocol features configured in the profile. The client’s node label alone may not indicate whether UDP is enabled end to end. The network between the PC, proxy server, and game service must also permit the required traffic. If the provider or proxy protocol does not carry UDP, routing a UDP-dependent game through that node may fail or fall back in a way that does not provide stable play.

Use this sequence to narrow down the issue:

Do not expose Clash’s controller or proxy ports to the public internet to make a game work. Keep local-only services bound to the local machine unless there is a specific, secured LAN requirement. Also avoid enabling broad LAN access as a troubleshooting shortcut: it does not fix a missing game rule, and it can make a local proxy reachable by other devices on the network.

Common gaming proxy questions

Does a faster node always lower game ping?

No. Download throughput and game latency measure different properties. A node may have enough capacity for a fast download but take a longer or less stable route to the game server. Compare the game’s in-match ping and packet loss with downloads paused.

Why does Steam work but the game does not?

The Steam client and the game may use different processes, domains, ports, and transport protocols. The launcher may honor the system proxy while the game connects directly or uses UDP. Check the game’s connections in Clash’s log and confirm whether your capture mode and node support the traffic it needs.

Should all game traffic use the proxy?

Not necessarily. If direct access gives better stability, route the game directly and proxy only the destinations that need it. If an overseas server is reachable only through a proxy, route the relevant game traffic to a tested node. Keep rules specific and confirm their order so unrelated traffic is not affected.

Why does download speed change after switching nodes?

The node changes the route to the service and can change the apparent region used for CDN selection. The new endpoint may have more or less capacity, and the node itself may be congested. Compare the same file, download region, and time window before deciding which route is better.

Download Clash