安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
In vanilla, pawns can get inspirations in any skill for which they have a learned level of 3 or above, so you'll often get pawns with inspirations in skills they suck at. It's especially noticeable with a gene that reduces their skill level.
Turning off aspirations doesn't change the new inspiration descriptions from this mod, but it disables the mood hit from not fulfilling them.
Turning off the new inspirations won't fix pawns getting inspirations in poor skills, since that's a vanilla issue. It just disables the new inspirations from this mod, which reduces the pool of inspirations you can end up with (no more inspired cooking/planting hogging up your crafters' potential inspirations).
I don't want the pool of possible inspirations diluted with those new ones.
I've played with it like that for a day now and it's a big improvement.
will you be uploading it on the workshop? or github or something
Are their unadjusted skill levels 3 or above? If their base skill level is 3, they're eligible for an inspiration related to that skill in vanilla as well.
I guess it's to stop players from only getting inspired creativity by giving a crafter "awful" genes in everything else? but all it really does is waste time
I suggest using the Inspiration Tweaks mod now that it has been updated. It does the same thing that my patch did, and more. I only made the patch that I did because, at the time, Inspiration Tweaks needed an update to 1.5 yet.
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2117570018&searchtext=inspirations
It sure would be great if the mod authors fixed this issue, but in the meantime at least I have (finally) arrived at a workaround.