安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
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).