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








After your last fix, I was finally able to get into the mod settings, change them, and exit with a save. Why did I do that? Because before I reconfigured the mod, the generation error persisted, but after that, it disappeared. I still don't quite understand why I couldn't get into the mod settings all day yesterday, but after that, the error that caused the world generation problem disappeared. I haven't tried this mod in a save, but something tells me that if no red errors popped up in the developer console during world generation, then everything went well.
If any errors occur later, I'll write back, of course, but again, logically, they shouldn't. It's an honor for me to see that you're interested in solving my problem, and I really hope that I can thank you somehow.
Exception ticking Corpse_Human37461 (at (133, 0, 197)): System.DivideByZeroException: Attempted to divide by zero.
[Ref D27014E1] Duplicate stacktrace, see ref for original
UnityEngine.StackTraceUtility:ExtractStackTrace ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Log.Error_Patch1 (string)
Verse.TickList:Tick ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.TickManager.DoSingleTick_Patch2 (Verse.TickManager)
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.TickManager.TickManagerUpdate_Patch2 (Verse.TickManager)
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Game.UpdatePlay_Patch1 (Verse.Game)
Verse.Root_Play:Update ()
Also, I was wondering what would happen if I reinstalled the mod and reset all its settings to default. Well, I encountered my previous world generation error, and again, it also fixed itself when I changed the settings.