安装 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).