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.