Aulex wrote:Anyone want to help me figure out how the chicken bot storm was able to travel so far from the chicken's death and also how the ai was able to assist it. It occurs at around minute 35-40 where grey is constructing a chicken and yellow kills it with a strat, then the storm spawns and then grey takes a sniper bot, othuum and flak piece to assist the storm. I looked through the storm's files and found this list
RULEUCC_Attack = false,
RULEUCC_CallTransport = false,
RULEUCC_Capture = false,
RULEUCC_Guard = false,
RULEUCC_Move = true,
RULEUCC_Nuke = false,
RULEUCC_Patrol = true,
RULEUCC_Pause = false,
RULEUCC_Reclaim = false,
RULEUCC_Repair = false,
RULEUCC_RetaliateToggle = false,
RULEUCC_Sacrifice = false,
RULEUCC_Stop = true,
RULEUCC_Transport = false,
and you can see the guard command is false so i'm very confused unless i understood part of that code wrong. Also isn't the chicken bot storm only supposed to spawn if it's half built or greater? You can see later in the replay that it was built with greater progress then destroyed being finished but the storm didn't spawn.
That list only means which commands can be given to the storm. For example, the AI can tell it to stop, move and patrol. This list basically tells the UI which commands it lets you use for a certain unit. In the storm's case, this doesn't really matter as the player can't select it anyway., but anything that CAN select it (in whatever other way neccesary to do so), can then also issue those orders to the unit. The AI can probably still select it as its selection, afaik, does not abide by the UNSELECTABLE category, which the ion storm has.
In theory, I would guess (I can't check this as I have no PC capable of running FA at the moment) that setting everything there to false would disable any form of commands being issuable to the storm, even for AI, but again, this is just a theory. If someone were to test this, that'd be great.
*Looks at Aulex*EDIT: I would guess the storm was originally meant to be controllable, but they probably (for balance reasons) decided against that. That's probably why it still has a name and all those other things, and the commands that you can issue to it could have been left over from that, or, were not all removed (slight mistakes like this often happen), and since the player can't select it anyway with the simple addition of the UNSELECTABLE category effectively prevents the player from selecting it in any way (normally) possible, they probably didn't look into it much anyway.