rate is a network data-rate setting expressed in bytes per second. It is not your ping, rendering FPS or a switch that changes an official server’s tick rate.
Enter rate without a replacement value in the developer console and inspect the value reported by your game. Also review the supported game-traffic bandwidth option in the current settings menu. Save the starting configuration before experimenting.
Internet plans are commonly advertised in bits per second, while this command reference uses bytes per second. Eight bits make one byte, but that conversion alone is not a complete recommendation: other traffic, connection stability and server limits also matter.
Values labelled “default” or “maximum” in an old guide may describe another game version. Use the current build’s accepted range and menu choices. Increasing a limit does not automatically force constant traffic at that rate or remove route latency.
For high ping, compare regions and connection conditions. For packet delivery problems, inspect network telemetry. For low FPS, investigate rendering and PC workload. Do not change several unrelated network variables at once.
See the ping guide and packet-loss guide. Command units checked on 6 November 2026: rate reference.
It is a network data-rate setting, expressed in bytes per second in the command reference.
No. Ping measures round-trip delay, not a bandwidth limit.
It is a network setting, not a rendering frame-rate control.
No. A client bandwidth setting does not change official server tick rate.
No. Eight bits equal one byte; prefixes and units must also be handled consistently.
Check the current build’s accepted values and supported menu options instead.
No. Routing, distance and congestion are separate factors.
Save the starting value, change one factor and compare the same network conditions.