Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
2. set the blocked path as forbidden land, they should've move
3. exit game and play again, this one works well for me
I kind of fixed it by moving a few parts here and there.
Its just weird because the things that seem to somehow not work anymore are there since basically the start of the game and didnt have any issues.
But suddenly they had.
Which is weird. They constantly wanted to access the storage of the lumberyard, which they dont need as i had a full storehouse filled with like 300 lumber.
But my builders somehow insisted they had to access the dedicated lumberyard storage, couldnt and thus were stuck inside their builders hut.
I later moved the lumberyard storage addition a tiny bit. It was perfectly accessable before for all others, but somehow builders couldnt.
This fixed it and my builders got unblocked.
I assume theres some coding issue in the AI logic (as i have now seen plenty of such issues existing in my few hours of playing 1.0).
The builders somehow were stuck in some logical loop where they wanted to build something with lumber, but their logic told them to get it from the lumberyard, as the construction site was close to it, while the storage house with my 300 lumber was a bit further away (we talk like 10 ingame metres here, but still).
And thus their logic insisted to get the lumber from the closest point, but they somehow couldnt.
I have a similar issue with a fishing hut.
It seems the devs forgot to code their villager Ai properly, so it gets stuck.
What they seemed to have forgotten was adding a failsafe logic.
Like "Move to closest resource point. Closest resource point is blocked/cant be reached, target next accessible resource point instead".
They forgot the latter part of that, so the AI villagers ever want to only get to the closest resource point (including stored resources) and if they cant, their action gets interupted.
They really need to fix that AI loophole.
I checked it all through and ANY other villager was able to interact fine.
ALl my lumberjacks had no issue working with the destined object (a wood storage).
Only my builders had issues with it.
Again, i assume the devs missed the mark with the AI behaviour code and didnt bother to implement a pathfinding failsave.
The Villager AI targets a resource destination it somehow cant reach and then doesnt default to the next destination it can reach, but instead loops the attempts that obviously have the same result: cant be reached.
They need to fix those loops and honestly, the entire games "problem" handling is bothersome and underdeveloped.
I constantly have messages of "too few houses", "houses cant be reached" and many more.
I see no obvious problem, theres enough space, materials, beautification and so on.
They could do things, but dont.
Also stuff like "no access to basic food" could mean like a dozen different things.
My market is stocked with berries and fish.
Cant they buy it?
Or cant they reach the market stands?
Is it too less?
I dont know.
The game needs a much much better way to tell you whats wrong. Especially for bigger settlements.
The game wants to promote its free-build feature, but then it should provide the quality to handle that and it currently doesnt.
Its a total mess.
I really do like the game but yea, I agree with you 100%. I get those errors too but I completely ignore them and refuse to do anything with them. They definitely do need to do some revamping on the code.