Known Lag Problems
These problems are reported by real players. If your region or ISP is listed, a network optimizer is likely to help.
Australia / Oceania
150-200ms- No dedicated Oceania server — players connect to SEA (Singapore), resulting in 150ms+ baseline ping
Middle East
45-120ms- No dedicated MENA server on the Steam/international client — players route to EU (Amsterdam) or SEA
- Pakistan players reported ~45ms to SEA server
What players commonly report
- Rubber-banding during large territory war battles with many simultaneous warlords
- Server consolidations reducing population per server (EU, Americas)
- Mail.ru Anti-Cheat privacy concerns — mracsvc.exe runs after game close
- No dedicated Oceania server — Australian players stuck at 150ms+ to Singapore
- Ping spikes correlating with territory war peak hours
How to Fix It
Try these first — they're free and solve the problem for most people.
01 Measure your ping to Conqueror's Blade servers externally
1. Open a command prompt (Win+R, type cmd, press Enter) 2. Run: ping conqblade.com -t (this pings the game's web server — not the game server directly, but gives a rough idea of routing to their infrastructure) 3. For a more accurate test, launch the game, connect to your region, then use Resource Monitor (resmon.exe) → Network → TCP Connections to find the IP your game connects to 4. Run: ping <server_ip> -t in a separate command prompt while playing 5. Watch for spikes above 100ms or packet loss — these confirm a network issue, not a hardware issue 6. Alternatively, enable Steam's in-game FPS overlay (Steam → Settings → In-Game → In-game FPS counter) which can show basic network info
Doesn't fix anything — but tells you whether your problem is network (ping spikes, packet loss) or hardware (stable connection, low FPS). No confirmed built-in ping display exists in Conqueror's Blade, so external measurement is the reliable method.
02 Select the server closest to your region at login
1. At the Conqueror's Blade server selection screen, choose the region closest to your physical location 2. NA players: choose Americas (Elysium Peak) 3. EU players: choose Crystal Sea or Sicania 4. SEA players: choose the Asia region (Singapore datacenter) 5. If you intentionally play a non-native server (for a guild), accept that your baseline ping will be higher
Choosing the wrong region adds 100-300ms of unnecessary latency. This is a free fix that makes a large difference for players who accidentally connect to the wrong server.
General network tips (not Conqueror's Blade-specific)
03 Enable IPv6 on your router
1. Log into your router admin panel (usually 192.168.1.1 or 192.168.0.1) 2. Find the IPv6 settings — usually under WAN, Internet, or Advanced settings 3. Enable IPv6 (auto or DHCP-PD mode, whichever your ISP supports) 4. Save and reboot the router 5. Restart Conqueror's Blade and check ping
Multiple community members reported ping dropping from 130ms to 22ms after enabling IPv6. The game's servers appear to have better IPv6 routing paths than IPv4 through some ISPs.
04 Use a wired Ethernet connection instead of WiFi
1. Connect your PC to the router with an Ethernet cable 2. Disable WiFi on your PC: right-click the network icon in the taskbar → Open Network & Internet settings → WiFi → toggle Off 3. Launch the game and check your ping
WiFi introduces jitter — random variations in latency that cause rubber-banding during warlord movement. A wired connection eliminates this. Most impactful during territory war battles with many simultaneous players.
Regions with good connectivity
Players in these regions likely won't benefit much from a network optimizer.
- Western Europe — Amsterdam datacenter — players in UK, France, Germany, Netherlands typically see sub-40ms ping
- Southeast Asia (Singapore proximity) — Singapore, Malaysia, Indonesia players see sub-20ms — community confirmed 4-25ms range
Still lagging? The problem is likely your ISP's routing to the game servers.
PingAim detects Conqueror's Blade automatically
No manual config. PingAim identifies Conqueror's Blade by process name and routes it through your fastest connection using a kernel-level WFP driver.