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
Nice guide! I just got one question.
So If I want to play a custom module with a graphics mod (e.g: Neverwinter Nights Facelift by Zwerkules) Should I just put it on "override" so I can play all the fan made campaings with that enabled?. In fact, wouldn't be better to put every mod on "override" ?
Turns out almost every mod you download from the workshop comes in an override folder that when you run the game seems to use the contents of all the override folders you have to a virtual one that works like "My Documents/NWN/override".
The problem comes when you have the same filename spread across multiple mods a.k.a your typical modding conflict. Since the game tries to loads multiple override folders conflicting each other it forms a ♥♥♥♥♥♥♥♥♥♥♥ and mods altogether stop working.
My solution was to merge every single override folder manually into the one in "My Documents/NWN/override" replacing files when asked and just using one tileset graphic overhaul, then later unsubscribing for every mod on the workshop.
That seemed to do the job for now and now every single mod I want works 100% of the time. Hope it helps.