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






Definitely respect how you work though, makes your stuff very easy to use n ♥♥♥♥
I'm opposed to XML as it is an exterior modification to the game, that is: you can't use XML without editing a file directly. XML can be used to break the boundaries of the game (like insane missiles) or create vehicles with poor meshes (like Z fighting) which mess up hit detection and player interaction. Working within the boundaries of the game's intended design adds a challenge, plus it makes the resulting vehicle more impressive. That's why my Challenger is my favourite vehicle thus far, all it's systems and design use absolutely no XML
Just curious, why are you so opposed to using xml pieces?