Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
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.