安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
举报此帖
1. With the current Starbase mechanics, there are several things that happen due to the reduced size and engagement distances introduced by Real Space:
1a. Sending a fleet to an enemy system doesn't always trigger combat with the system's outpost. Due to the distances involved, it's possible for the fleet to position itself on top of the star without engaging.Two possible solutions, either increase range slightly at least for star bases, or change the navigation mechanic so that fleets told to navigate to a system are sent to the outpost instead of to the geographic center of the system.
1b. Prior to hyperjump blocking technology, it's trivially easy to bypass a defensive fortress since the engagement range is so small. While the player can recognize this and not build bastions until the technology is researched, the AI still wastes resources on them. This could be addressed by either increasing the range of starbases, or by making the hyperjump blocking technology on by default. I lean towards the latter.
2. It's much more difficult to intercept fleets. In some cases, when one fleet is told to attack another while both are moving, the intercepting fleet will miss by just enough that it has to loop around and then pursue the target fleet. If both fleets have the same speed, this is very frustrating and requires a lot of extra setup and attention to coordinate fleet combat. Increasing the range of engagement somewhat would help to solve this.