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










This mod doesn't interact with Tac Armory UI in any way, but Tac Armory UI itself is known to cause crashes for many people and not recommended for use.
I tried informing TeslaRage through the mod posting and putting in a github pull request. I haven't seen any activity from them since fall of last year so I don't know how long it might take them to see it and it's a noticeable bug.
Honestly I tried to write it as a patch that overwrites his class instead of reposting the entire project but nothing I did would let it load the config files.
It's just slightly annoying; in our modmaking community it's customary to give the courtesy of asking for permission when you intend to copy someone's work, even if you make substantial modifications.
For example, your reupload of the TeslaRage's loot mod with a bug fix; you could probably just inform TeslaRage of the bug and they'd fix it for everyone.
I invite you to come by the modmaking discord at some point, it's a friendly place.
https://discord.gg/ZytsZ93
It's meant to function wildly different than yours, just my own personal taste.
Instead of manually creating a list of loadouts for it to choose from randomly I build a randomized loadout from lists of items. If you have too many item options it would expand exponentially and, for some reason, the engine didn't like parsons millions of lines of an ini file.