Fleet Power Network Array - Over scaling Aux Problem

Originally we at STOBetter were against its use for several reasons, one of these being what I want to talk about here, however in all the drama around its June 2025 'nerf' and then July 2025 refix, I don't think a single voice made any mention of this particular problem. This was something I brought up privately to some Cryptic QA people however I don't think it ever got looked at. So lets talk about this a bit:

With patch notes released on July 1st, 2025, The Fleet Power Network Array console was amended with this statement: 

[...] that players have made their statements clear that despite this console potentially being targeted as an Overperformer, the actual scope of its impact is not that far-reaching, and fixing the behavior to match our original intentions could be seen as having a disproportionate impact on a very niche form of gameplay that its current state facilitates. As a result of both of these factors, we've decided to revert last week's changes, and hold off on further efforts to modify its behavior and performance. 

This to me is official notice that this is how the console will remain for the time being so I'm comfortable using it now (I know, a thing I bought on an online game and didn't use for almost 18 months)...but as a veteran player I do want to bring attention to the fact that this console is still over performing because it is broken; this console does not have an upper bound.

Lets start with something easy: The tooltip. I'm a big proponent of "the tooltip should describe itself", there shouldn't be anything vague. Targets, values, ranges, times, all things it should have. If another system is to be called, it should be easy to tell what its calling for and how it should interact. For example here, this console very specifically calls "50% to 125%", as in it should give no more than 125% haste.

We can see here the side by sides when activating at 125 Aux and what happens

We can here expect that a 125% haste to apply:

1s / (1 + (125 / 100))

= 1s / (1 + 1.25)

  = 1s / 2.25

= 0.44s

But we get 0.39s....which would mean were getting more haste. When we work backwards we get:

1s / (1 + (x / 100)) = 0.39s

x = 156.41 (Theory calls for 156.25, rounding error due to the tooltip truncating to 2 digits)

Hmm....ok...so its clearly giving more than 125% haste. Lets try at 100 Power

Alright....so clearly this 125% haste is what you get at 100 Aux power, but it doesnt stop at 125%, and can scale upwards. What it we use EPS Power Transfer 3 and grant ourselves a bunch of power