#95 AI scripts don't treat "Sabotage" and "Hunt" commands properly

[Dmitri Fatkin]

When "Sabotage" or "Hunt" command is assigned to a unit in scenario properties, it's always executed upon the start of the mission in the original game. Unlike that, Legacy tends to ignore one or both, depending on chosen AI behavior.

Here's the exact list of which script ignores what:
qBotVeryEasy: both "Hunt" and "Sabotage" tasks aren't upheld by footed units.
qBotEasy, qBotMedium, qBotHard and qBotBrutal AI scripts ignore both "Hunt" and "Sabotage" orders issued in mission scenarios to footed units.
SmartBot: "Sabotage" order is not accepted by all types of soldiers.
AI Player (easy): the script ignores "Sabotage" order for infantry-type of units.
AI Player (medium): "Sabotage" order is not carried out by infantry-type of units.
AI Player (hard): in this one, the problem is similar to the above 2 scripts.

[josbuttler]

I’ve noticed the same issue with Legacy not properly handling "Hunt" or "Sabotage" commands depending on the AI behavior. It's frustrating when footed units don’t follow these orders, especially when it works perfectly in the original game. It's a bit like how I feel when experimenting with creative tools—sometimes things just don’t click, like when I tried out Novelai, and not all the features worked as expected. Hopefully, the devs can fix this AI behavior issue soon!

[carson reed]