安装 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'm currently working on a new system that adds a new AI Order that gets assigned to the bots, and all of the commands are added to this order as sub-objectives. The advantage is, since the bot no longer goes idle, I have a lot more control over everything it can do. I can make it not put away diving suits, for example.
I made the bots only follow orders from players if they are on the same team. It didn't make sense for you to be able to command an outpost manager to follow you, or command a security bot on the station to attack him. I can change this pretty easily, if there's a compelling reason... It just felt a little cheat-y.
You can turn on the Order Debug in Options and peak in the console how they are interpreting your instructions. Sometimes if you don't say it super clearly or they identify the wrong target for the command, it might mess them up. If there's an order that they consistently get wrong, you can add an example for it to the Orders Prompt.
Thanks for the feedback, I hope to make it more functional in the future.