What you'll read in this post:
From wild animals roaming the map to tame mercenaries charging money; the known Manor Lords bug are a pain in the backside.
A big 'but' though: not everyone suffers these bugs. Yes, there are often posted, but some only occur in very specific situations. Others don't affect all games.
Today, Joe (from Manor Lords publisher Hooded Horse) posted an announcement that no further bug reports on some 13 issues are needed. Either because the cause is known or because devs are aware of their existence.
Known issues reported by Hooded Horse
The full list of known issues was posted on Friday morning in the Discord Channel. A new subthread Frequently reported issues was started just for this list of known issues in Manor Lords.
- Game crashing in October -- Some fields, usually triangular, may have base 0% fertility for all the crops. Assigning any crop to the field crashes the game.
- Wild Animals can move away from the marked area, forcing the hunters to cover larger distances and significantly decreasing their effectiveness.
- Mercenaries may keep charging monthly fee despite surrendering during battle.
- Manor's grid blocks access to the other buildings.
- People, animals in cities with big populations can clog in multiple ways, which can lead to performance issues.
- On the highest speed option big city inhabitants can stop their activities for a prolonged period of time.
- Homeless families left after a Manor is destroyed do not inhabit it again after it is rebuilt resulting in persistent freezing and homelessness icons.
- Game crashing related to vegetable gardens.
- The game can become unresponsive when "Royal tax increased" pop-up appears during the visit mode.
- Resource deposits may spawn on a steep terrain, thus may hinder or block ability to build a mining pit atop of it.
- Supplies from demolishing might lay on the ground for a long time.
- Heavy plow node is less efficient than human workers, due to the oxen plowing fields in illogical paths.
- After losing a battle over the last region, the game does not end, but becomes unplayable.
Bugs are annoying
Sure, some of these issues I've personally witnessed. I did wonder why I spotted a hunter having to walk across a whole region the other day. 🤔
I've also seen people freeze to death just because they wouldn't move back in to a rebuilt Manor - or just any house for that matter.
But to be fair, silly things like that are to be expected in Early Access.
Any of the other bugs, I can't attest to. I've never had to battle over the last region. I've also never lost a battle with mercenaries (knock on wood) and my fields always have some kind of fertility.
Maybe I don't play enough. I know for a fact I don't. But I still play enough to encounter more issues than I do.
And I don't, so that's good news for the state of the game if you ask me 😉
Don't report random crashes
Also, a request was made not to report any more crashes. At least: as long as you don't have at least an inkling of the cause.
With such a successful game as well as such an active community, you can count on the players to let you know exactly what pains them. And when something doesn't work, or worse, the game crashes, they'll be sure to rear their head.
The problem is, not everyone can post useful bug reports. "I randomly clicked somewhere and then boom black screen" is not going to be anything that a developer can work with.
On the other hand, a report detailing when, where and what happens, whether you've been able to reproduce it and solve it by doing something different, that is bound to draw attention.
Hence the final note by Joe:
Please try not to report crash bugs until you think you've identified a potential cause, and please don't report crash bugs with little to no information.
Hear hear, Joe. We've got your back.