No, the surface unit doesn't even have any sensors that it can detect or track the target with.
But doesn't the "enter solution for..." script command give the AI unit the same data as regular sensors would, in terms of target position and identity?
I'm not an advanced programmer by a long shot, but I can write simple C++ code and I've successfully created simple plugins for a flight simulator, so I doubt the doctrine language would faze me. But if the only commands available are the ones I can see and access from the Mission Editor interface, then I don't understand how writing separate code would help.
Are there any decent examples of mission-specific doctrines somewhere that I can take a look at?
|