Mordhau Guides 1.0.0 is here — the guides are stable, and corrections are always welcome.

Skip to content

What Still Needs Writing

An honest list of the gaps, so anyone looking for something useful to do can pick one instead of guessing.

Most of what is left is not writing. It is measurement: numbers that have to be tested in game by someone who has the game open, because they change with patches and nobody should be inventing them. If you can run the test, you are the person who can close the gap.

TIP

Before you start, the accuracy rules cover the one thing that matters most here: mark anything you could not verify rather than rounding it into a confident number.

Player guides

Weapon numbers. Weapons and Loadouts covers how to choose a weapon and deliberately carries no stat table. Damage by type, windup and release timings, and point costs are all missing. This is the single largest gap on the site.

Armour. What each tier costs, what it weighs, and how it behaves against each damage type. Currently one paragraph inside the weapons page.

Perks. There is no reference at all. What each one does, what it costs, and whether it is worth the armour you give up for it.

Maps. Nothing beyond the names in the server guide's rotation list. Layout, objectives and callouts, per map and per mode.

Progression. Levels, gold, and what unlocks when.

Server guides

Admin commands. The RCON guide covers the commands it needs for the tasks it walks through. A full reference of what is available, and what each one actually does, does not exist yet.

Hosting mods. How to run a modded server, and what breaks when you do.

Performance. The server guide touches tick rate. Everything else about running a server that stays smooth with a full player count is undocumented.

Modding

The SDK guide says plainly that it is unfinished, and it is the thinnest section on the site. Publishing to mod.io and the basics of building a custom map would both be worth having.

Translations

Arabic, French, Japanese, Russian and Chinese each carry a handful of pages against the English section's two dozen. A translated page needs no technical knowledge beyond speaking the language, and contribution methods covers how the language folders work.

Please do not machine translate. A rough page from someone who speaks the language is worth more than a fluent one that gets the terminology wrong.

What finished looks like

A page is done when someone who has never done the thing can follow it start to finish without opening anything else, and when every number on it either came from a test or is marked as untested.

That is a higher bar than most of what already exists here. Pages get better by being corrected, so a first draft that is honest about its gaps is worth far more than nothing at all.