For more information see here Bug Report Template Build: 4016 Mode: Survival Mode: Single Player/Multiplayer SERVER NAME:N/A SEED-ID:N/A If applicable: MODIFIED PLAYFIELDS: Yes Reproducibility: Always Severity: Minor Type: PDA Logic Summary: SpawnOPV Formatting doesn't support certain names Description: I've been able to constantly reproduce this issue based on the naming convention of the PDA yaml format and the spawn names of given ships. This will occur for both the OPVSpawn property as well as the OPVAttackTargetName, but the latter is more at issue. This is because OPVAttackTargetName *must* define a spawn name instead of a group name, this prohibits scenario creators from using a '-' anywhere in their POI/OPV's spawn name. Steps to Reproduce: 1) Create a OPV of any kind with the spawn name including a dash 2) create a PDA chapter and 2 tasks, with a playfieldOp in each task spawning an OPV 3) For the first task, spawn the OPV ship with the dashed spawn name, you can use the group name as expected 4) For the second task, spawn any OPV, with the OPVBehavior AttackTarget, and the attack name being the ship made in step one, using it's dashed spawn name 5) Test PDA design and logic, notice that the OPV for the 2nd task default to attacking the player instead of designated OPV Screenshots, Crash Logs, any other Relevant Information or Download links:
Was inaccurate here, was an issue with how the PDA file was made. This works if you ensure the entry is covered in 'myOPVship'