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
Script is this (use your own user name)
for /f "usebackq delims=|" %%f in (`dir /b "override\*"`) do mklink /h "C:\Users\YOURUSERNAME\Documents\Neverwinter Nights\override\%%f" "%cd%\override\%%f"
you only need to subscribe. There is alternative way of copying the files directly to override folder. I will write exactly how, if you are interested. Also I will be releasing nwnvaultversion, but don't know when yet.
Well, the collision can be the problem, but only of things in conflict. I know only of amethyst dragon icons, where the collision is understandable.
But when I was testing my packages I sometimes experienced strange thing. All worked, then I restarted game, something worked, then restarted computer, everything worked. With the same files at same place, without changes. I blame workshop for this misbehaviour.
@Satorial: Pity, the transarency brings all together, as the icons are mainly made with some degree of transparency also (you cannot see it with the black background).