安装 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(越南语)
Українська(乌克兰语)
报告翻译问题



The only job it has these days is deleting itself so that you can't have two versions installed. That's initialised at io_scene_valvesource\__init__.py line 38. Is that script not running?
Thanks for the clarification. I have been keeping a copy stored in addons_extern[github.com], so I just removed that file entirely with a commit note.
I also wouldn't have the script save user prefs without consent. It should be entirely in the user's control, and that script took that away. I believe a changelog note would be best, considering it's in bold on the website.
It's a fair point about saving user prefs. I want to save the old add-on being disabled, but of course any other changes are saved too. I'll just remove the save call; in most cases the user will do it themselves anyway. The worst that will happen is a "missing add-on" warning on the prefs screen.