安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









So fun news, I tested this with "Player as Knight" and guess what? It worked. Meaning that players under lieges can get called up as knights (or commanders) and means you can level up both sides of the traits at the same time.
Unless you have massive amounts of errors re: other mods, the bloat from this won't impact you. I didn't even notice because I play via cloudgaming and don't see the useless errorlog.
But I've just fixed that file. Thanks for your report!
Whereas I have a mod in my workshop from like 4 years ago that still works today, on Elder Kings - despite me making it years ago.
Battle → script increments battle count → Check threshold → Upgrade trait tier
With tracked traits, it becomes:
Battle → script sets a flag/increments XP → UI tracked system records XP → Check threshold → Engine upgrades trait tier
This mod could be a beast of a performance hog, instead it's nearly undetectable. In addition, you have no idea how complicated localization + bug tracking gets with tracked leveled traits. Even doing just 5-10 traits in my initial run was frustrating when things went awry.