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











"[...]\steamapps\common\DarkestDungeon\campaign\quest\quest.restriction.json"
and copy it, then place it where the file you deleted was within my mod. If that does not work, a new game may be required. If you were trying this with a new game, then I have no idea how it could mess up, given that the entire quest restrictions removal mod is editing only that one file. From there it would be a mod conflict of some sort instead, which would require extra effort.
"steamapps\workshop\content\262060\2640714729\campaign\quest\quest.restriction.json"
...or something very similar. Given it is the only file in the campaign\quest folder, you could also just remove the entire quest folder and get the same effect.
However, when I clicked on the link you referenced, When you press down a mod and enter the game, it appears that the mod can be used.
If you do figure that out, I will add that I personally put it high enough in my mod list to not be overwritten by other UI mods. The visual ones sometimes change things they shouldn't.