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










Will take a look at it again. Probably wont add a selection to the settings since im sadly im rather limited on my modding time because of real life :(
I didnt spot any obvious mods that could be the source of the conflict. You could try having a pawn take luciferium the normal way.
If it throws an error it has nothing to do with this mod.
If it works then im afraid the next best thing is constantly halving your mod list and spawning raids with 100% luciferium infusion until you find the conflicting mod.
Or just leave it disabled.
https://gist.github.com/HugsLibRecordKeeper/554e2bdf3941a4bac98d7c3df8331917
https://gist.github.com/HugsLibRecordKeeper/3e37268cf378180261c96ae8f14c1bfd
@altay2510tr Please post a link to the error log with Hugslib or Log Publisher from HugsLib
Probably need to load MO after this so their patches can remove/overwrite mine.
Will put testing it on my todo list but no promise or ETA.