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






it does absolutely nothing useful for the addon. its made because of the addon image jpeg inside the addon.
you can safely ignore it
Also here's the spray for the people who wonder about it
https://www.deviantart.com/lui-ra/art/Un-arbol-370842965
also, cool vac ban bro.
And what the absolute christ of all mighty is that spray in the screenshot?
The game will load whatever content is more recent. Meaning that it will load the new HUD Script edits over this one, but only the script.
If the model does not show up either, then you either downloaded the mod while playing the game, or you have another mod overwriting this one.
I, and many others, use an addonimage file. That is a jpg file, wich bill be used as icon in the addon menu.
BUT. Windows likes to add a file called "Thumbs.db" (wich is basically a thumbnail cache file) into the addon after you created it. There's no way of removing it after you made the addon, and there's not really a fix for that issue either.
Now, the game realises that several addons have that Thumbs.db file and marks them as conflicting. The game doesn't even care if the conflicting files are being used.
Open the Dev console right after you visited the addon menu. It creates a list of all the addons that conflict with more information about wich file conflicts.
If that file is "thumbs.db" you can savely ignore the conflict message and re-enable your mods again.