Moorland Reach launched into the worst possible reception: not hostility, which at least generates conversation, but a fortnight of reviews describing it as promising and then near-total silence. Sixty-eight hours on the shipped build told us why. The world is genuinely excellent and almost everything you do inside it is obstructed by something that does not work.
Ninety-one hours later, on a load order of forty-one mods that the community treats as standard, it is one of the best open-world games of its generation. Both of those sentences are true about the same product, which is the reason this publication exists.
What shipped, and what was wrong with it
The moorland itself is the achievement. Eleven square kilometres of ruined settlements, drystone walls, peat cuttings and standing water, lit by a weather system that produces genuinely different afternoons. Nobody has ever complained about the terrain.
Three things obstructed it. The climbing system attached to surfaces unpredictably, so traversing the crags — which the map layout constantly asks you to do — failed perhaps one attempt in five for no legible reason. The quest log listed objectives without locations, ordering or completion state. And the northern third of the map, roughly the size of the starting region, contained four points of interest and no quests at all.
The traversal fix, and how long it took
The climbing problem was diagnosed publicly eleven days after launch by someone reading the game's own movement parameters, which are stored in plain configuration files. The surface detection radius was smaller than the character's reach animation, so the game refused holds the animation had visibly grabbed.
A three-line configuration change fixed it. That change was published in the second week and has been in every recommended load order since. The studio has never shipped it, and the shipped build we re-tested this year still fails one climb in five.
| Problem | Fixed by | Time to fix | In official build |
|---|---|---|---|
| Climbing surface detection | Community, 3-line config | 11 days | No |
| Quest log unusable | Community, full replacement | 4 months | No |
| Empty northern region | Community, 6 modders | 29 months | No |
| Save corruption on fast travel | Studio patch | 6 weeks | Yes |
| Shader stutter on load | Studio patch | 3 months | Yes |
The last two rows matter. The studio did fix things, and both fixes were real. It fixed the problems that generated crash reports and left the ones that merely made the game tedious, which is a resource-allocation decision that looks entirely rational from inside a company and disastrous from outside it.
The quest log replacement is better than most shipped ones
Four months after launch a single modder replaced the quest interface completely: objectives grouped by region, distances shown, completion state visible, and a filter for quests whose prerequisites are already met. It reads like something from a studio with a dedicated interface team.
We spent thirty of our ninety-one modded hours with it and did not once open the map to work out where something was. On the shipped build we did that constantly, and the difference in how the game feels to play is out of all proportion to the size of the change.
A three-line configuration edit and a rewritten menu account for most of the two-and-a-half point gap. Neither is a technical achievement. Both are just work somebody decided to do.
The northern region is a different scale of thing
Six modders over twenty-nine months built out the empty third: eleven settlements, a quest chain of about fourteen hours, and — the part that impressed us most — new landmarks that respect the original art direction closely enough that we twice had to check which content we were looking at.
It is not flawless. Voice work is absent, so the new quests are text-only against a game that is otherwise fully voiced, and the seam is obvious. Two of the settlements reuse building sets in ways the original never does. But it is fourteen hours of content in a region that shipped with four hours, and it is free.
Why the modding grade is A and not A+
The game earns an A because its data formats are plain, its configuration is text, and the studio has never once shipped an update that broke the load order — five updates in three years, all of them additive.
It falls short of A+ because there is no official loader and no documentation whatever. Everything the community knows about the file formats was worked out by reading them, and the ordering rules for the standard load order are folk knowledge maintained on a forum rather than anything the game explains. Compare the space simulation elsewhere in this ledger, where the developer published the schema.
The two verdicts
As shipped, 6.2. A superb landscape wrapped in three systems that do not work and one third of a map that is empty. Recommended only to somebody who intends to mod it, which is not a recommendation.
As modded, 8.7. With forty-one mods, most of them small, it becomes the game the terrain always deserved. Setting it up takes about ninety minutes of reading, which is ninety minutes nobody should have to spend and which we would spend again.
Two scores
Shipped 6.2 — an excellent world obstructed by broken traversal, an unreadable quest log and an empty northern third.
Modded 8.7 — forty-one mods, ninety minutes of setup, and one of the best open worlds of its generation.