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








Config.xml
generated file contains block combat score values and basic settings (only nexus sync at this point)
Conquests.xml
generated file contains basic information about the availability of conquest system + blocks. Keep in mind that rewards are assigned every 3 minutes.
AssemblyDefinition.xml
generated file contains some default settings and one dummy blueprint
PS: combat assembler can hold only 40 blueprints, and it needs an unique definition per instance, meaning if you are running nexus server and wan't to have multiple of those with different settings, you have to place one per instance. It is also not public by default, so you need to create your combat assembler installation, export it as a prefab or local blueprint and alter the vanilla assembler and connection point (connector) to these subtypes: LargeAssembler -> CombatAssembler and Connector -> CombatConnector. These blocks have no computers in them and therefore players can always connect and use the combat assembler no matter the grid ownership. Demo Combat Assembler grid blueprint is linked on the bottom.
Store.xml
PS: players are always using their own combat score points, they can't use combat score of other faction members. If run on nexus server and combat score is used, they can use combat score from server A on server B, since it is synchronised.
Zone.xml
ResourceZone.xml