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


I recently discovered something horrible. In overdrive mode, not only the repairs on mechs AREN'T DONE, but any workshop project is also not done either!
What the hell were you guys thinking?!
Overdrive speed should not affect that! A lot of time, overdrive is used just to move faster from one theater of operation to the next, making use of the excess of energy the base has, and even more so as for some reason beating missions tend to always net batteries.
Speed change should NOT affect repairs or workshop projects. It's completely ludicrous! It just needlessly slow down the game for no reason, while adding an extra hassle for, again, no reason. You're simply encouraging players to sandbag until the projects and repairs are done instead of doing that on the move. And please, don't give me some reasons such as realism... Tech crews are litterally spraying magical gel on the mechs to fix them, so it's not like you can use excuses like "vibrations from high speed is making maintenance dangerous".
I also want to point that you give the players absolutely no informations about this quirk of overdrive speed. Having a bad system is one thing. Having a bad system and not telling the players about some important parts of it is unforgiveable. Ideally remove the limitations on repairs depending of speed. If for some unthinkable reason you think this limitation must stay(and I will fight you at every corner for it to go, because come on), at the very least put into descriptions that it interrupts repairs.
-When plotting a course on a moving target(convoy, patrol), the patrol is plotted not on the objective, but on the spot under it. The result is you need to constantly click on the target because otherwise the mobile base will move to its location when you first plotted the course. Your system should be able to recognise that the player want to go to the location of the escort/patrol, and follow it instead of dumbly going on the map location under it.
-There are some extremely weird reactions with the terrain that don't appear on the timeline like mechs taking damage just running around when there is a small elevation, or downright crashing when moving down a step despite, again having no indication it should happen.
-I have written about it already, but the situation about buildings and their destruction needs to be addressed. Them not having a fixed lifebar or not being targettable is bad enough, but they seem to also not take damage when targetted, or when projectiles should go through them(or at least collide with them and inflict damage). To further add to the problem, using ctrl to target a building can lead to a mech shooting over the building into an empty piece of sky above it, instead of on the building. There is something very very wrong at work here.