Actual build power of t1 engies

[samoja]

i was curious so i conducted a series of tests to see exactly how much t1 engies are needed to replace one t3 fact, i started out with 3 UEF t3 facts, 1 supported by 20 t1 engies, i put supported fact to produce 2 Percis, and 2 unsupported facts to produce 1 Percy each, then i removed engies until i got roughly the same build times for them, and my results were: t3 fact supported by 13 t1 engies can produce as fast as 2 unsupported t3 facts, then i tried to add increasing number of engies to all 3 facts, 20, 40 and 60 respectively, and added corresponding number of Percis to each, namely 2, 4 and 6, and fact with 20 engies finished first, followed by the one with 40 and one with 60 ended up last, so my results were, yes engies do speed up production a lot but their cumulative effect seems to drop as they amass. I am attaching the replay so you can judge on your own.

[Ze_PilOt]

And that is the source of the problem.

Two T3 factories : 8380 mass.
One T3 factories + 13 engies : 4866 mass.

Yes, the efficiency decrease with the numbers of engies due to roll-foff time, but never to a point where the mass difference worth it.

[dstojkov]

Two T3 factories : 8380 mass.
One T3 factories + 13 engies : 4866 mass.

We played like this until now, well it seems to be broken ... but actually not that much. You get in other trouble while assisting a factory with engies first your build power is vulnerable mean you have to invest for t1 pds or t2 ( t3 if you can ) land and air for shields for TMDs not to mention that you can not spam as several fab because engies prevent the unit to comes out.

The best is to have more that one fab that is assisted with a certain amount of engies and when you get the eco build further fab. Like it is now is ok I would not change this. The real pb for me is the the buildrate from t2 and t3 fab for their cost.

We could adapt the cost for the fab to fit a better cost/buildrate again it will be only a little adjust that make the hole unchanged and working. I will also in my next patch adjust this