安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题










Thank you for your message. I don't have a clear answer, but I can share a few tips based on my experience.
I know that NPC factions or towns cannot acquire PC buildings if the buildings' "is feature" setting is set to "true."→ Image
The vanilla Campfire is one of the buildings that is "is feature = true," and I have never encountered a player-built Campfire stolen.
However, most beak thing statues are "is feature = false." So, the next relevant setting is the "create player town."
Most beak thing statues (and most of my mod's furniture) do not create a town, and they often belong to "nowhere" if built far from the player's outpost.
And that is all I know at the moment. This info can be of help to you.
Have noticed that sometimes when the error looks as if it might occur, statues are designated to 'nowhere' rather than the nearby non-player site.
Really enjoying the mod, and thinking about re-using whatever framework is used on my end for some duplicate buildings which don't switch over as easily.
This is obviously great, and I'd be interested to know why. Has anyone else noticed this, and if so, does anyone know why this behaviour occurs?
much like, even though I kill them every play through
Thumbs up
hahaha,
I like your "a beakhead statue holding a lamp" idea. So, I made a quick mockup.
→ Image1
→ Image2
Is my understanding correct?