Separate activateTrigger's solved it. Set up an always false condition, so the property modifiers dont launch independently. Issue closed.
FYI, Made new units and recolored with drop shadows. Testing game play and balance. Hope to post a beta for others to kick around in a couple weeks.
Thanks for all the help.

SSDs have read and write limits based on their endurance, which is typically measured in Terabytes Written (TBW) or Drive Writes Per Day (DWPD). These limits indicate how much data can be written to the SSD before it may start to fail, with consumer-grade SSDs generally allowing between 500 to 3,000 write cycles depending on the type of NAND flash used.

It cant hurt to be confident the game is not going to crash with each movement. An option to limit drive activity for the next release would be helpful. Surfing the web is probably just as dangerous. I was concerned the battle calculator was making hundreds of saves with each invocation. On activation it prints a brief [coping data] message and there is drive activity.

I yield to your expertise.

@beelee GREAT IDEA

THANK YOU B