How to Change Tickrate on a Mordhau Server

Tickrate is one of the most important performance variables on a Mordhau server. It directly affects combat responsiveness, hit registration, animation smoothness, and overall server feel. Increasing tickrate can dramatically improve gameplay—but only if your server’s CPU can handle it.

This guide explains how to change the Mordhau server tickrate, what the safe and optimal values are, and how to find the sweet spot based on your CPU, player count, and mods.

---

What Is Tickrate in Mordhau? #

Tickrate is the number of times per second the server updates the game state.

• 60 tickrate = 60 updates per second (default)
• 120 tickrate = 120 updates per second (high-performance)

Higher tickrates result in:

• More responsive melee combat
• Better hit detection
• Smoother movement and animations
• Reduced desync in competitive fights

However, higher tickrate also increases CPU load significantly, especially on the server’s primary game thread.

---

Default Mordhau Server Tickrate #

By default, Mordhau servers run at:

• 60 tickrate (Internet servers)
• 60 tickrate (LAN servers)

This default is chosen for compatibility and stability, not peak performance.

---

How to Increase Mordhau Server Tickrate to 120 #

To increase the tickrate, you must modify the Engine.ini file on your server.

File Location #

Mordhau/Saved/Config/WindowsServer/Engine.ini

Required Configuration (Copy Exactly) #

[/Script/OnlineSubsystemUtils.IpNetDriver]
NetServerMaxTickRate=120
LanServerMaxTickRate=60

[IpDrv.TcpNetDriver]
NetServerMaxTickRate=120
LanServerMaxTickRate=60

Apply the Changes #

1. Stop your Mordhau server
2. Edit Engine.ini
3. Paste the configuration at the bottom of the file
4. Save the file
5. Restart the server

Once restarted, your server will attempt to run at 120 tickrate.

---

Important: Not All Servers Can Handle 120 Tickrate #

Increasing tickrate does not guarantee better performance.

Tickrate stability depends on:

• CPU single-thread performance
• Active player count
• Mods and server scripts
• Background CPU load

If the CPU cannot keep up, you will see:

• Tickrate drops
• Rubberbanding
• Combat desync
• Server hitches under load

---

CPU Performance: The #1 Factor #

Mordhau is extremely single-threaded.

This means:

• One fast CPU core matters more than many slow cores
• Clock speed and IPC are more important than total cores

Ideal CPU Characteristics #

• High single-core boost clocks
• Modern architecture (Zen 3+, Raptor Lake, etc.)
• Low contention with other services

A high-core but low-clock CPU will struggle at 120 tickrate.

---

Recommended Tickrate by Server Size #

Small Servers (Up to 16 Players) #

• 120 tickrate is usually safe
• Minimal CPU strain
• Excellent combat responsiveness

Medium Servers (16–30 Players) #

• 90–120 tickrate, depending on CPU
• Monitor CPU usage closely
• Mods can push this lower

Large Servers (32+ Players) #

• 30-60 tickrate recommended
• 120 tickrate often unstable
• CPU spikes during large fights

Modded Servers #

• Reduce tickrate by 10–30%
• Mods increase server-side processing
• Start conservative and scale upward
• Custom Horde maps are even more intense on tickrate

---

How to Find the Tickrate Sweet Spot #

The best approach is incremental testing.

Step-by-Step Testing Method #

1. Start at 60 tickrate
2. Increase to 90
3. Monitor:
   • CPU usage
   • Server hitches
   • Player reports
4. Increase to 120 if stable
5. Roll back if instability appears

Warning Signs of Too-High Tickrate #

• CPU usage pinned at 90–100%
• Stutters during combat
• Desync complaints from players
• Server failing to maintain target tickrate

If you see these, lower the tickrate immediately.

---

Tickrate vs Player Experience #

Higher tickrate improves:

• Parry timing accuracy
• Swing manipulation consistency
• Hitbox precision

But unstable tickrate is worse than a lower stable tickrate.

A consistent 90 tick server feels better than a fluctuating 120 tick server.

---

Does Higher Tickrate Increase Bandwidth Usage? #

Yes, slightly.

Higher tickrate:

• Sends more updates per second
• Increases outbound network traffic
• Can expose weak network routing

This is rarely the limiting factor, but it matters on low-quality networks.

---

Common Tickrate Issues and Fixes #

Server Won’t Hold 120 Tick #

• CPU is insufficient
• Lower tickrate to 90 or 75

Good CPU but Still Lagging #

• Mods consuming CPU time
• Other servers on same node
• Background processes interfering

Players Experiencing Desync #

• Tickrate unstable
• CPU thread saturation
• Reduce player cap or tickrate

---

Should You Increase Tickrate on Your Mordhau Server? #

You should increase tickrate if:

• You have a strong single-core CPU
• You run a competitive or duel-focused server
• Player count is controlled
• Mods are minimal or optimized

You should not if:

• You are CPU-limited
• Running large modded servers
• Hosting high player counts
• Sharing resources with other servers

---

Raising tickrate can significantly improve Mordhau’s combat feel, but only when done responsibly.

The goal is not the highest number, but the most stable performance for your hardware. Finding the right tickrate based on your CPU and server load will always outperform blindly forcing 120 tickrate.

If you’re serious about Mordhau performance, CPU quality matters more than anything else, and choosing the right hosting environment makes all the difference.