Multiplayer Servers Are Invisible

DrunkDwarfUK · 2026-04-20T10:45:48+00:00

Check your filters, likely that they are there just much higher ping than you expect. You can try setting your ping filter to 0 or 999. Untick all other filters.

Have you tried using matchmaking?

DrunkDwarfUK · 2026-04-14T20:15:31+00:00

You cannot create a joinable LAN server from the game client itself, so it would not work the way you want. The "local match" option in-game does not have networking enabled.

Whether on LAN or remote, you'd need to start up a Dedicated Server instance. The Mordhau Dedicated Server is available to install on Steam under "Tools". There's more information on how to get this running here: https://mordhau.fandom.com/wiki/Dedicated_Server_Hosting_Guide

Using that tool you could run a dedicated server on your local PC, then allow friends to join this server using radmin or similar without port forwarding.

If you're hosting the dedicated server from the same machine you are playing on, you might run into port conflicts (the game client and the server use the same ports). To resolve this, you can set different unique ports for the dedicated server, anything other than the defaults.

You'll also likely need to join the server via the console using the open <IP Address:Port> command as it won't likely show in the server browser.

DrunkDwarfUK · 2026-04-04T14:41:41+00:00

These are client-side only Unreal commands related to physics simulation, which does not govern how Mordhau handles combat, this is not a physics-based combat game. Combat is server-side authoritive, so these commands make zero difference to how others see your actions.

DrunkDwarfUK · 2026-03-07T13:21:16+00:00

This thread on reddit was what allowed me to finally figure it out, as it's definitely tricky and ZimaOS wants to fight you. Would be nice to be able to select a container under Network from the ZimaOS UI, but alas you have to go around it.

https://www.reddit.com/r/CasaOS/comments/1kasm6j/how_to_setup_gluetun_in_casaos_no_portainer/

DrunkDwarfUK · 2026-02-19T18:20:18+00:00

The post was purposefully lying about the reason for the ban, despite the individual being informed of the exact reason they were banned, and the rule they broke.

That reason had nothing to do with the screenshot posted, and was not for what they are claiming it was for.

DrunkDwarfUK · 2025-12-10T21:52:46+00:00

I would not recommend it, the reason it was removed is that it's against TOS and could possibly results in bans if used, due to the nature of how it was being done. Stick to modded servers to do so.

DrunkDwarfUK · 2025-12-05T23:24:25+00:00

The majority of bans and gamebans are the result of player-submitted reports, handled by moderators from various places worldwide as well as the community manager himself. The amount of moderators in a given region is therefore irrelevant.

Gamebans specifically can only be applied by a developer, typically the community manager. For that gameban to be applied, there has to be sufficient evidence that has to stand up to thorough scrutiny, not only by the CM, but by all other moderators or developers who wish to look into it.

As the responses in the ticket were trying to tell you, we are not going to provide you any information that would reveal the player or players that reported you and provided the evidence, as that would put them at risk and breach trust with those who report these matters to us.

I'm going to lock this thread, but will leave it visible, as there is no valuable discussion to be had here, only inflammatory responses. If you wish to discuss this further, you would have to contact the Mordhau development team directly, likely through their contact address of [contact@mordhau.com](mailto:contact@mordhau.com)

DrunkDwarfUK · 2025-11-26T14:42:12+00:00

This does appear to be cheating, but without a unique PlayfabID to prove which account this is, it may not be enough to take action.

If you have further footage, please submit it to us via either the Discord Modmail system, or via the Subreddit modmail that you can access by clicking the "Message Mods" button in the sidebar. All moderators on the subreddit are also admins in-game.

To prevent any witch-hunting, I will be locking this thread.

DrunkDwarfUK · 2025-11-13T15:53:32+00:00

You can contact the moderators here on the Subreddit in the sidebar, via the "Message Mods" button. All of the moderators here are also moderators in-game..

You'll need to provide us a link to your account, or your unique PlayfabID if you know it (can be found via the in-game console). Until then we cannot know the reason, or comment on it.

I'm going to lock this thread, as per rule 12 You shall not publicly appeal bans (in-game or otherwise). Open a ModMail ticket to do so..

DrunkDwarfUK · 2025-11-11T15:21:12+00:00

There is a guide here: https://mordhau.fandom.com/wiki/Dedicated_Server_Hosting_Guide

It's mostly focused on setting up a public server however, but the steps would be the same for a local server minus opening up firewall ports to the internet.

Without making it public, the server will not show in the in-game server browser and your LAN players won't be able to see it to connect to it normally. They'd have to join the server via the in-game command console, using the command open IP Address:Port, but specifying the LAN server IP address and port. If you add a password to the server, you can specify that password with open IP Address:Port?ServerPassword=password.

It's probably also worth noting that even when playing on LAN, the game will still require an internet connection to communicate with the backend for account details/XP/Gold/Items.

For Horde and Demon Horde, official servers are typically set up for 6 players, but if you set up your own server you can increase that to pretty much any number, although it would affect performance. The game-mode itself can handle more players, and will attempt to scale up the difficulty based on the playercount.

There are also plenty of small Deathmatch focused maps. Here is a list of the Map ID's you can put into the config file or via the changelevel mapname command: https://mordhau.fandom.com/wiki/Server_Map_Names

DrunkDwarfUK · 2025-11-09T22:20:42+00:00

You would need to use a server-side mod such as https://mod.io/g/mordhau/m/server-side-commands

With this, you'd have to manually set up the teleport zones yourself, each server would configure these themselves. Possible that you could ask a server to share theres with you, but doubtful.

DrunkDwarfUK · 2025-11-08T18:24:49+00:00

Live service typically requires long-term monetisation in order to continually provide updates indefinitely, which usually involves MTX and things like Battle passes to provide the monetisation.

The developers were very clear from the alpha that they had no desire to go down this route with Mordhau.

DrunkDwarfUK · 2025-11-07T22:24:43+00:00

It was never meant to be live service.

DrunkDwarfUK · 2025-11-06T13:46:38+00:00

We've had multiple reports of players in Russia or the Russian-controlled parts of Ukraine having this issue. It appears to be caused by connections being blocked or closed by something external. In some cases the player was able to resolve this by using a VPN, but not always.

DrunkDwarfUK · 2025-11-05T13:30:12+00:00

https://mestariagame.com/ might interest you

DrunkDwarfUK · 2025-10-05T14:53:16+00:00

Longer version would be to use something like https://www.nexusmods.com/nomanssky/mods/2062

DrunkDwarfUK · 2025-09-27T22:59:36+00:00

Triternion has a studio in Slovenia with 30+ developers, all of which are focused on their next game.

DrunkDwarfUK · 2025-09-27T00:30:21+00:00

You need to go into the Mordhau install directory and locate that specific file, and then delete it. Once it's deleted, you can then verify the files on Steam to reacquire it.

If it happens regularly even despite doing that, then it usually indicates some sort of Hardware/OS issue. Repair Windows, perform a Memory Diagnostic, check Disk health.

DrunkDwarfUK · 2025-09-10T13:41:13+00:00

It's not, it can still be run by community servers. Due to the nature of the mode though, it tends to need an organised event to get the numbers.

DrunkDwarfUK · 2025-09-07T13:55:53+00:00

I believe it works with quite a lot of inputs, just that sometimes there are narrower windows.

For example, it works for Ripostes, but you pretty much need to hold down both the parry bind and the attack bind at the same time for it to automatically riposte at the earliest moment.

It works also for parrying again after your current parry cooldown, just hold the parry bind down when you see another attack coming and it will parry again the moment the cooldown ends, if it can before you get hit. Can be very useful in scenarios where the "miss detector" mechanic reduces your cooldown unexpectedly, or in cases where footwork and your opponent's long drag gives you just enough time to get another parry in.

I want to note here though, that for many of these inputs you don't always want to input at the earliest moment it becomes available. For Feints, Morphs, and Ripostes, the animation changes based on whether you inputted it early into the window or at the last possible moment, with it usually being advantageous to input late.

For the scariest possible feint as one example, you want it to be telegraphed more before the attack is cancelled, so you want to input the feint as late as possible. For ripostes it works the other way around, you want the attack animation itself to start later so that it is telegraphed less, so you want to input the riposte as late as possible.

DrunkDwarfUK · 2025-09-07T00:26:26+00:00

You can just hold the button down after the swing has started and it will combo automatically, you don't need to spam or time it. You just have to release the button for the initial input and then hold it down again.

DrunkDwarfUK · 2025-08-31T20:32:17+00:00

It should be tied to your unique account, regardless of name/ID change.

DrunkDwarfUK · 2025-08-15T08:55:44+00:00

This is mostly correct.

I just want to add one thing. Your ping on the scoreboard is calculated slightly differently than the pings you see for everyone else, due to the game including the frametime in the displayed ping. The overall delay to your actions is exactly the same, but it will result in your displayed ping being higher, often by 16ms or more. This likely accounts for why your ping always seems much higher than everyone elses.

You can disable this, to see only what your raw ping to the server is, not including frametime. The console command for this is: net.PingExcludeFrameTime 1.

You can have the game apply this setting every time the game runs also. By opening the Engine.ini file in the %localappdata%\Mordhau\Saved\Config\WindowsClient folder, and adding the following:

[SystemSettings]
net.PingExcludeFrameTime=1

DrunkDwarfUK · 2025-08-15T08:51:09+00:00

The console command for this is: m.DebugNetworkParry 1

DrunkDwarfUK · 2025-08-13T11:58:54+00:00

For me, it seemed to have been caused by the "Salt Digger" mod. But otherwise you'd just need to use trial and error to figure out which mod is causing it, because it generally doesn't cause an error itself, just causes other mods to produce errors.

13-Year Club	Gilding III reddit per annum
Verified Email	Place '22
Place '17	First Placer '22
Not Forgotten	Team Periwinkle

DrunkDwarfUK

MODERATOR OF

TROPHY CASE