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
https://imgur.com/92X2RRa
In cases like this, when a mod needs a hotfix or similar within a certain timeframe, Steam has a really bad habit of not realizing that it has to update the mod again. There were cases of people running important mods like the VE Framework that were outdated for WEEKS because of that. The exact specifics of that behaviour are to my knowledge not fully understood - but it's likely that Steam just compares the date of the files between the updated mod and the ones on the users drive.
Because of that it is highly recommended to unsub from a mod that got 'hotfixed' - wait for Steam to delete it from your drive - and then just re-sub, to get the new files.
Because the mod is missing keys and the keys is actually invalid, the error "Error in patch.Apply(): System.Collections.Generic.KeyNotFoundException" is logged.
<LogAfterDefError.Settings.DefTraceEnabled>
<LogAfterDefError.Settings.PatchTraceEnabled>
And even though the two keys are enabled, they are not correctly recognized by "LogAfterDefError.dll". So, missing key settings on/off in the Mod options will not change anything. All patching operations are still logged.
Please check it. Thank you.