descriptions.plist
in my AddOns/Config
folder - if I remove it, the errors disappear. I'll have a tinker.Moderators: winston, another_commander, Getafix
descriptions.plist
in my AddOns/Config
folder - if I remove it, the errors disappear. I'll have a tinker.A favor: Can you please upload the offending plist somewhere? We are investigating issue #228 and it might prove useful.
Not using autolock here, so I am not sure what the expected behaciour is. Can you please elaborate a bit and provide a reproducible way to replicate the issue? Is this happening also without any other OXPs installed?
Code: Select all
PS.awardEquipment("EQ_TARGET_MEMORY");
PS.awardEquipment("EQ_SCANNER_SHOW_MISSILE_TARGET");
PS.awardEquipment("EQ_TARGET_AUTOLOCK");
TAP needs an unlocked missile armed/available to work - always has done, as far as I know. That is its disadvantage in a firefight.
mission_targetAutolock
when the equipment is bought and the script checks throughout that this variable is defined before doing anything. This is why the console method does not produce results. If you set the Lave tech level to 12 (i.e. 13 in-game), and give the commander a bunch of credits, then you can buy the required equipment and the TA itself and then you should find that it works.