VPN recommendations and game QoS

Most “gaming VPN” advice is marketing. BRUTAL takes the opposite, honest approach: it only suggests testing a relay when a real route trace proves a fixable bottleneck on your path, and otherwise tells you plainly that a relay would just add latency. Separately, when you apply a game profile, BRUTAL tags your game's traffic with a QoS priority marking so Windows treats those packets as high-priority. This article covers both.

Why BRUTAL doesn't blindly recommend a VPN

A generic VPN adds an extra hop between you and the game server. In most cases that raises your ping, not lowers it — the “VPN made my game faster” claim is usually wishful thinking. BRUTAL used to estimate a VPN benefit from a direct ping, which was baseless, so that approach was removed. The current tool is an evidence-gated GPN verdict (gaming-VPN verdict) that earns its recommendation from real measurements.

How the GPN verdict works

The verdict appears after you run a Trace Route in the Route Analyzer (it also needs an Analyze run first, so it has your jitter and loss numbers for context). BRUTAL suggests testing a relay only if both of these are true:

• The trace found a fixable bottleneck — the worst latency jump is out in the ISP backbone or Internet transit segment and adds at least ~25 ms. (A bottleneck on your own local network or at the destination cannot be routed around by a relay.)
• Your connection is genuinely unstable — more than ~1.5% packet loss, or more than ~12 ms jitter, or median ping above ~120 ms.

If both hold, BRUTAL shows an orange card explaining exactly what it found — how many milliseconds the bad segment adds and which hop — with a Measure it in Smart Route (free) button. Smart Route, built into the app, measures your direct path against relay paths to the live game server and engages a relay only if it measurably wins; measuring is free, and only engaging a relay needs Ultra. If your route is already clean, BRUTAL shows a green card that says, in plain words, your route is already good — a GPN would only add latency. Save your money.

How to get the verdict

1. Open the Route Analyzer and click Analyze (this captures your latency, jitter and loss).
2. Click Trace Route and let it finish (or cancel a long one with a second click).
3. Read the GPN card that appears. Green means don't bother; orange means it might genuinely help — with the evidence shown.
4. If it's orange, press Measure it in Smart Route (free) and let Smart Route compare the paths with your game running. Trust the numbers, not the marketing.

Game QoS: priority tagging for your game's traffic

This is a different, PC-side feature that lives in the game profile system (applied automatically by the Guardian when it detects a supported game, or when you apply a profile). When a profile is applied, BRUTAL creates Policy-based QoS rules in Windows for that game's known TCP and UDP ports.

Each rule marks the game's packets with DSCP value 46 — the standard Expedited Forwarding (EF) class, the same priority class used for real-time voice and video. In plain terms, it asks Windows (and any network gear that honors DSCP) to treat your game's packets as high-priority. The rules are scoped to the actual emulator/game executables and the specific port ranges each game uses, so only the right traffic is tagged.

How game QoS is applied and removed

• Applied when you apply a matching game profile, or automatically when the Guardian detects a supported game running. The Route Analyzer's log notes the TCP/UDP ports that were tagged.
• Removed when you remove the profile — BRUTAL cleans up the QoS registry policies it created (they are clearly named with a _brutal suffix so nothing stray is left behind).

Best practice

• Diagnose before you spend. Run Analyze + Trace Route and let the GPN verdict tell you whether a relay is even worth testing for your specific route.
• Whatever you try, measure both ways — the GPN verdict exists precisely so you can prove it helps instead of guessing.
• QoS tagging is most effective when paired with router-side SQM; if your bufferbloat grade is poor, fix that first (see the Bufferbloat test).

Common issues and troubleshooting

• No GPN verdict appears: you need to run Analyze first (for jitter/loss context) and then Trace Route. The verdict needs both.
• The verdict says don't bother but I still lag: a relay can only fix a routing problem out on the backbone/transit. If the trace shows no such bottleneck, your lag is likely distance, Wi-Fi, or bufferbloat — a relay won't help those.
• QoS doesn't seem to change anything: DSCP priority only takes effect if your router/ISP honors it. Many home setups don't. It is a best-effort request, applied safely, and removed cleanly with the profile.