安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Could not resolve cross-reference: No Verse.SoundDef named BulletImpactMetal found to give to Verse.ThingDef AJO_BookRack (using undefined sound instead)
and
Could not resolve cross-reference: No Verse.ThingDef named BuildingRubble found to give to Verse.ThingDef AJO_Dartboard
Full log is here: https://gist.github.com/HugsLibRecordKeeper/10b0949a0dff72b97c86524d5e78005f (sorry it's long, I have a lot of mods but just ctrl+f either of the above errors to find yours)
Config error in AJO_PlayArcadePS: jobDef AJO_PlayArcadePS has joyKind Gaming_Cerebral which does not match our joyKind Gaming_Dexterity (https://imgur.com/a/b8OFrmz)
any idea on that?
Config error in AJO_Dartboard: has null thingClass.
Config error in AJO_Dartboard: has components but it's thingClass is not a ThingWithComps
There are a couple items from other mods with the same errors, so it could be some other mod patching a parent def or something, but I can't figure out what might be causing it. ANy ideas of things I can look for?
If you want me to help, post your plaintext modlist here. You can copy it from a save loaded with the load order causing the error. It'll take several people posting, but I should be able to narrow it down eventually.
If your defs are loaded before any that overwrite the parent def and any that apply the patches, would that insulate the AJO objects, or are the patches applied to objects directly rather than the defs themselves?
I did a pretty thorough search within my mod folders for any files that overwrite or apply patches to anything in the hierarchy of the affected items and that was the only one I found. Since the errors continue after disabling, it's either not the cause or something funky is going.