Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.