Okay update: The conflict between WOTC-Extended Information & [WOTC] Tactical HUD Lag Fixes ironically lags the game. I found the answer to Tactical HUD Lag's description, just putting that info here if anyone has the same problem as mine.

Weird, the Season 9 Tweaks mod should address that issue internally. You're definitely not the first to report that, though... Wonder what's up there.

引用自 XpanD：

Weird, the Season 9 Tweaks mod should address that issue internally. You're definitely not the first to report that, though... Wonder what's up there.

My best guess is that the S9 Tweaks only affects the Mod Configs, like in-game stats or settings from different mods.

The solution to my problem was to delete a single line from [WOTC] Tactical HUD, something I kinda doubt the Season 9 Tweaks Mod could do.

Well whatever, the [WOTC] Tactical HUD Dev was kind enough to explain the conflict and put the solution on it's description page. Better than no solution at all.

Nah, that shouldn't be it -- mod class overrides are exposed to config as well, and the S9 Tweaks mod makes the same change you applied manually.

From what I understand of it, the game merges together each instance of a config (for example, all XComEngine files) on startup. Newer mods (higher Workshop IDs) get their configs merged later, so a newer mod /should/ be able to reliably overwrite config values set by older mods.

(this is likely also why new Odd seasons usually get a brand new Tweaks mod, as getting a new ID lets it modify mods that the old one wouldn't be able to)

My guess is that something is scrambling the load order for those affected by this issue, though I have no clue what could actually cause that to happen. S9 Tweaks' mitigation gets overwritten, and the conflict returns.

Good to know that the manual workaround helps!

引用自 XpanD：

Nah, that shouldn't be it -- mod class overrides are exposed to config as well, and the S9 Tweaks mod makes the same change you applied manually.

From what I understand of it, the game merges together each instance of a config (for example, all XComEngine files) on startup. Newer mods (higher Workshop IDs) get their configs merged later, so a newer mod /should/ be able to reliably overwrite config values set by older mods.

(this is likely also why new Odd seasons usually get a brand new Tweaks mod, as getting a new ID lets it modify mods that the old one wouldn't be able to)

My guess is that something is scrambling the load order for those affected by this issue, though I have no clue what could actually cause that to happen. S9 Tweaks' mitigation gets overwritten, and the conflict returns.

Good to know that the manual workaround helps!

I have to clarify one part in my case, I tend to add more mods after using a collection. It's definitely because of that.