安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
奖励
reason they do that is because the game literally says:
"Mods that failed to load: KitchenLib. Press any key to continue"
and then it force closes the game.
if you could make it so your code blames the actual problematic mod instead of your own, you would probably be seeing a lot less people blaming you. then again, they could put in a little more work then injecting whatever code sounds good without doing any testing
it doesnt. this mod allows other mods to exist, and THOSE break. i had the mod "Mystery Meat" out itself as the only mod on my list that causes the error code to pop up through this mod.
"Mystery Meat" is the problem.
These are vague reports, how am I supposed to debug and try to solve issues based on that?
I forward users to the Discord Server to open a PRIVATE ticket so I can collect and read their logs. These logs contain PRIVATE information about the user’s computer. 1) You can’t send these logs and file over Steam, 2) Unless you want your PRIVATE information public on Steam, then by all means put it up.
Additionally, going back and fourth via Steam comments is incredibly ineffective. If you have a better solution, by all means feel free to suggest it, but unless there is an easier reporting method on Steam, I will continue to forward users to Discord.
I'm pretty sure this wasn't the cause of the module conflict, because when I found out, I uninstalled all the modules and reinstalled the whole game. With only Kitchenlib and its two associated modules subscribed to, the game still appears with the following screen, unable to launch.