When the Abyssal Trident, which is a complex device as a power, is added to an Array, it seems to come up as a zero cost item when calculating the cost of the array. If there are cheaper items in the array, the most expensive of those will be used to determine the "Base Power" cost. If the Abyssal Trident is the only item, it is free. I suspect this may happen for other complex powers that contain other powers, but I have not found another case as of yet.

It's worth noting that the Wide Array correctly calculates the cost for determining whether the Abyssal Trident can be "turned on" for the array (which means it can't be legally turned on if any power has fewer than 34 pp).

Portfolio with Array and Wide Array examples at https://www.dropbox.com/s/pirzg3sem0zkx2v/Abyssal%20Trident%20Array%20Miscalculation.por?dl=0

Thank you for reporting this. I'll add it to our to-do list.
--
Hollis McCray
Lone Wolf Development Support - support@wolflair.com
http://www.wolflair.com

Tip: Is Hero Lab / Army Builder regularly going into demo mode? Make sure each of your computers is using a *different* license number. Each computer needs its own license number to run properly - you can activate your free secondary license from the License menu, then use your new license number on your second computer to get up and running.

Just following up on this, someone else ran into the same issue, I think,
at http://www.echoesofthemultiverse.com/viewtopic.php?f=22&t=1777. I'm
going to take a closer look at the scripting to see if I can suss out why
this is happening, but the pattern seems to be that items with Auto-Adds of
Devices don't count their value into determining the cost of an array slot.
Add a Cutting Torch and it counts as 0 points. Add the equivalent Linked
Damage/Weaken and it counts for the correct amount of points. I don't know
if this is at all related to that it is currently impossible to directly
add a " -- Device --" to an Array (although you can add powers with
Removable Flaws).

Using an alternative Array construct with debugging statements, this bug
results from the PPCost field indeed being 0 at the time when the Container
Cost Array is calculated. I have not figured out why that is happening.