Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuậ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.