James – User talk

I removed your note, unless you could provide some reproduction of your issue. I tested the command in the development and stable branches, and it worked as expected in both. What do you expect the result to be? --Strangepete (talk) 21:47, 23 November 2014 (CET)

You are right...testing it now in the editor with a plain group on utes results in correct change of behaviour when setBehaviour "SAFE" is used. However, the problem arose in the situation, when a group is engaged or in an attack and you want them to go on to the next waypoint, e.g. waypoint before was "SAFE AND DESTROY" and you want them to stop fighting and go on with the next waypoint. In this scenario, setBehaviour "SAFE" showed no result at all. You can proof this quite easily by placing a friendly squad and a few enemies on utes and checking behaviour settings for your group. As soon as they are in "COMBAT", setBehaviour "SAFE" has no effect. That's what I was addressing to. You can force them to stop fighting and go on with the next waypoint by using setBehaviour "Careless", which inspite of "SAFE" has some effect even in combat. Hope you understand my point. And I hope thats the right way to answer to your request cause I'm totally new in this wiki stuff. As I try atm it seems that "CARELESS" is the only command working during a combat, beside "SAFE", "AWARE" etc. are also failing. Maybe you cannot call this a bug or missfunction of the original intended use, but I would add this as a comment to the command however. EDIT: "Careless" and "stealth" are the only two options that show an effect while a group is in behaviour "Combat". That at least I would add to the command description.