EDIT: The doctrine below isn't working right yet. Don't use it yet.
Thanks for the tips. Yeah, I've noticed that sometimes fighters engage surface ships with HARMS and sometimes they don't. Sometimes they actively engage a target and sometimes they loiter. Its all really aimless without any discernable logic to why and when.
Thanks for the doctrine tips. I'm not really a programmer. How about this then, per your suggestions
Code:
; $Header: FighterEvade.txt Wed Apr 23 16:04:39 EDT 2003 $
; $Revision: 1 $
; $Copyrt1: Copyright (c) 2003, Sonalysts, Inc. All rights reserved. $
;
; FighterEvade
; LoBlo attempted Edits,June 2006
; attempting to script better anti-air behavior from interceptors to make them better protectors
; currently untested
; Set Tactic
IF NEWTRACK THEN {
; AAM or SAM Missile?
IF TgtClass $= "MISSILE" AND ( TgtMissileClass "AAM" OR TgtMissileClass "SAM" ) THEN {
SETTACTIC "AirEvadeMissile"
} ENDIF
; SSM or ASM Missile?
IF TgtClass $= "MISSILE" AND ( TgtMissileClass "ASM" OR TgtMissileClass "SSM" ) THEN {
ATTACKBEST
} ENDIF
;What about enemy fighter response?
IF TgtClass $= "AIR" AND ( TgtID $= "HOSTILE" OR ( TgtID $= "UAE" ) OR ( TgtID $= "UPD" ) ) THEN {
Intercept
IF (tgtrng <= AttackRng) THEN {
ATTACKBEST
} ENDIF
} ENDIF
Also...
Quote:
PPS I'd also use the default platform doctrine to reference a target doctrine for these features, and create a priority structure for all the commands
|
Is that a better method then just creating all behavior in one .txt file without SETTATICS?
thx