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










Possibly the biggest difference is that I decided to not make a mod. Instead each mod using ModCheck should add ModCheck.dll itself. This means you will never get errors due to using a patch file without having the assembly loaded. Your mod will add your mod as requirement to every single mod using it.
The big question now is what should we do? It seems getting mod creators to use even one of these is a struggle. Having two competing systems will most certainly not make it any easier.
Naturally this made me look closely at the code and surprisingly despite the same goal and being based on PatchOperation, our codes have nothing in common. Even more surprisingly we both made a project on GitHub on the very same day, which is before I released anything.
ModCheck:
Forum post [ludeon.com]
GitHub [github.com]
As long as the coding behind the PatchOperation and the mod loading haven't changed it should work. Though you might want to see if works just with the testpatch that should show up in the debug.