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
Most mods for bg that involve anything other than assets do this by hooking into other dlls and making calls to their own code as part of a "detour". It's a really clever way of customizing any executable (also, dangerous) but it relies on keeping those "modified" dlls intact.
For example, my wasd and camera mods require modified a modified SDL2.dll and bink2w64.dll. If you had those "fixed" by, say, the Larian launcher at some point, then none of your native mods will work.
If you're relying on something like vortex and it suddenly seems to stop working, I'm afraid you'll have to dig deeper. Try manually installing the mods (follow the readme!) if you want to be sure everything is as it should be.
Found this post after searching for a hot minute, so going to hope this bumps it up.