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






But in my opinion, I have already made the code as lightweight and optimized as possible to the best of my abilities. If you run the game with just this mutator, there is no perceivable performance impact.
I will see if I can get category detection implemented. The thing is that for each weapon I have to compare each tag that they have (because a weapon can be in multiple categories as you know) with each element inputted in the blacklist/burst fire fields. It’s definitely possible, I just don’t feel like writing nested for loops.
Still though, using this with HavenM on my heavily modded configs while running on a potato laptop did not produce an unusually low FPS for me. And RF itself is not the most well optimized. For now I think the performance is acceptable, but if I get too many complaints about serious performance drops I'll consider trying to fix it.
In fact, HavenM is active in the demo video.