Hello, I have been wanting to make a topic that really analyses Aurora C# Ground Combat, as in what interesting effects emerge despite its simple foundations (as it always happens), and what possible conclusions could be drawn from it.
I had been very active in a similar thread in the old forum some years ago when I coincidentally had just been playing as GDI and came out of it finding that even in otherwise complete defeat encounters with moderate 1.5TL disadvantages on near equal tonnage deployments, a single ground unit class just kept standing and winning all the battles. (more to that later) Since I learned some new things while writing and thinking about it back in the forum, I fear the ultimate point of it all went a bit under in some confusion.
That is why, -this time-, I wanted to place a neutral, large calibre thesis alpha-strike that really aligns all the mathematics right from the start, so that all that remains doing is uncovering implications thereafter.
Before start, just also a motivational disclaimer:
Expand
My own gameplay philosophy in Aurora is actually 95+% RP based, which means in ground combat too I will simply build all kinds of thematic designs, APCs, guard towers, “medics” infantry, -you name it-, no matter their objective efficiency.
However, I am also a person that likes to understand systems. I can throw the conclusions away for artistic purpose, but I am still curious about the truth.
This was merely an exercise to figure out how everything really works itself out to be.
Formulas
I am starting with the basics, but derive from there to two full design efficiency formulas, - one for duels, one for battlefields.
The most foundational Aurora equation is this kill chance for a shot that had already hit:
(1) Kill_wpnX_pShot

(“T” always stands for the stats of the Target/Enemy)
Right away I want to foreshadow a result by drawing attention to that AP and DMG, as well as Armor and HP originate from the same two source TL-numbers, especially in cases of even stat units and weapons. Seeing that, the formula could be effectually simplified to either close to or even literally:

Next we include the hit chance from Aurora basics in completion:
(2) Hit+Kill_wpnX_pShot

However, note that 0.2 is merely a stretch factor to scale encounter length that applies to both sides, and thus cancels out. Then, since this is about comparing design efficiency, design independent factors like morale don’t matter, and environmental factors are unnecessary complexity, -mostly applying to both sides again anyway-, that can be left outside the scope of this argument. The Hit+Kill formula in effect therefore simplifies to:

Next we need to include all the shots a weapon can fire. For this it is necessary to realize there are two possible situations to compare. One is the battlefield with a target rich environment, in which case the kill performance can simply be multiplied by the shot amount:
Kills_wpnX

Should this result in more than 100%, it simply means the weapon kills more than one of the enemy design ‘per turn’ on average.
However, on a direct unit vs unit comparison, only one “kill” can ever be had, which makes the equation slightly more involved if you want to understand the designs in this “duel” environment:
Kill_wpnX_Duel

Then you do this nearly identically in a second layer when including all weapons X a design has, finalizing the two ultimate kill chance equations vs their opponent:
(3A) Kills

And for duels:
(3B) Kill_Duel

Now, to get the actual design efficiency vs the opponent, you can primitively ask the question “how many of them do I kill before they kill me?”:
(4A) Efficiency

And though that gives some very interesting results, it also isn’t exactly fair, because an Oliphant doesn’t actually count as one. In most cases the real efficiency comes rather from the principle to inflict as much cost as possible on as low a budget as possible. Cases like this one may arise:
The yellow numbers below designate the Efficiency per unit first, -looking terrible for the Infantry against the tank-, but after factoring in build cost in the second yellow line, suddenly the infantry is on top as it is so vastly cheaper.
To take into account cost, there is an asterix for later (here:*), but on the simpler end and by principle, you can append the equation with this:
(4B) Efficiency (size or cost)
Interestingly in Aurora, only mass and Armor thickness determine cost of ground units, not the tech level, so you can easily convert the numbers into each other using the official rule:
(4C) Cost-Size Conversion
![]()
Sometimes you might even want to draw up a mixed metric where you optimize the cost-damage inflicted for a certain tonnage of ground troops you can drop at once, so cost/m would also be a very legal consideration. (Pulverizing a mountain by the lowest bidder in m/cost… may be not that useful however :P)
Finally it would be great to judge a whole design’s performance against multiple types of threats to get an overall assessment of validity. This is a topic about analyzing unit types against all others after all, so there must be some objective numerical condense to make that visible.
Naively it is just the average efficiency against all enemy types:
(5A) Summary Efficiency

Of course, that doesn’t take into account the fact that some unit types like infantry or lighter vehicles would likely make up a much larger share of an actual battle force, so you could add some incidence factor to it:
(5B)

The problem with that however is that you never really have enough battlefield intelligence to know these incidence numbers, and thus can only make a close guess. I ended up using the general formula and simply adding more infantry types to the battlefield, so it should at least roughly be representative.
At this point we are capable of writing out a complete efficiency formula for duels:
(6) Duel/Unit Efficiency Complete

(the arrow notation on the right is half-bogus, but the Latex editor I was using had no other passable alternative)
It looks impressive through size, but is really simple as relations go, so this goes in all the Excel work for getting Unit vs Unit Efficiencies.
Formulas Round 2 - True Battlefields
Naturally, nobody will be shocked to find out that the huge Behemoth Obliteratrix Cannon ‘shell-shock, the new rock’ heavy tank will have an easy time rolling over a normal infantry man, - even if cost adjusted. By applying the 3A “Kills” formula, I got comparisons like these…:
…Where the tank has a maximum hitmod(0.6)*100% kill chance per shot, so 4x60% = 2.4 “kills per turn”, while the AMR infantry with its mere 1/45 chance can’t even get to to 1 once you factor in it is 43.5 times cheaper, thus ending with roughly a 2.5 cost efficient encounter for the ‘not even anti-infantry’ tank vs. ‘supposed anti-tank’ infantry.
However, to arrive at a real battlefield there is a part that is easily overlooked, -including by me at first in the old forum and also this revision once more-, which is that you need to set up a cost equivalent encounter beforehand.
The domination of the tank above is achieved because he can keep shooting at more targets after dispatching the first, but these additional targets somehow get no chance to fire back at him, which would have shifted the balance.
So in order to have an actual fair fight, you need to set up every unit against a cost equivalent number of enemies of the target’s design (seen in the screenshot through the “# Encountered” box on the right), which is done by satisfying this simple formula:
(7) Fair Force Balance
(With U_0 just being 1. T as the numerical count of Targets. Thus, T can be fractional and even smaller than 1 if more expensive, but that is fine since all formulas are continuous and apply just the same.)
What follows now is the derivation that takes this and leads to the full battlefield efficiency equations. Since they are long and not really useful by themselves, I just package them into a box for those interested:
To whom it may concern
In any encounter the winner will always be efficiency >1 and the loser <1.(unless exactly matched) Since we already normalized the two sides for cost, we should be able to figure out both sides’ efficiencies by simply looking at the percentage of forces the winner lost at the time the losers’ force reached 0.
For that end we start with the force change rates:
Force Change Rates per Turn
Note that we are using the “Kills”, not “Kill%” equations here. Similarly to the shot multiplication, we can just multiply by force count as we assume there are always targets left. Just think of it as an infinite line of tanks against an infinite line of infantry. Though they are infinite, we still know they both spent the same amount of resources, so there are cost/cost_T infantry for every tank. They will always be able to keep shooting and contributing if by chance they kill it early.
Now, having both number counts related to each other makes for easy setup for differential equations, so here is one side (you only need one):

Substitute:
![]()
Substitution Result:

This is a famous formula. Known equations that satisfy being themselves again after two derivations are hyperbolic functions, so a good general solution is:
Force Count - General Solution

At t=0, cosh will be 1 and sinh be 0, so we have trivial constants:

To get the non-trivial constants, one route can be to combine this known solution for t=0:
![]()
With what our general formula produces (also at t=0, but not yet inserted here):
![]()
Again with cosh(0)=1 and sinh(0)=0, you now get the non-trivial constants as:
And thus a non-nebulous, usable force count equation:
Force Count - Actual Solution
Interesting to analyze about this is that the cosh-Term basically designates the initial population count of each side, while the sinh-Term represents attrition stemming from the enemy.
The Kills geometric average appearing as a multiplier to time is also very interesting, as it simply signifies the encounter’s end state approaching faster the better either -or both- sides are at killing. It does counter-intuitively however not mean that more killing or attrition will be done to yourself if for example only your own unit gets better at killing. Because in such a case, the end time t_e itself would be smaller too, counter-balancing and even over-compensating the effect. (not to mention attrition would be reduced by inverse relation to your killing)
So from this we can now check which side reaches 0 first by setting U and T 0. Remember that tanh = sinh/cosh. Here is the example for U=0:

Zero Population Times
The tanh function is only defined between -1 and 1 and so an expression inside the tanh could resolve in error if it is bigger than 1. Most interestingly that happens exactly when that side is the winner, as once the other side is destroyed first, your own forces never reach “Zero Population”.
(There is also a rare edge case where both sides are exactly equally matched, thus both having ‘inner expression’=1. It means both sides only asymptotically approach 0, never actually reaching it.)
Now, that is interesting. We now have an isolated term that doesn’t even have to do with time anymore and seems to predict the outcome of a battle in itself. Squaring it for convenience, you can now try at defining an invariant, a numerical constant predictor of the matchup that doesn’t change over time:
Invariant Definition
![]()
(8) Invariant
![]()
(If you derivate this after t and plug in the U’ and T’ from the start of the bonus section, you can see these indeed cancel out.)
The right side of this equation is especially interesting as it holds values accessible without calculation at the start of a matchup. From this we can actually predict the winner of the battle before it even starts, and without need for any cumbersome tanh-calculations.
The rules stand as - "1) If [ Kills * U²_0 > Kills_T * T²_0 ], T gets destroyed. 2) Both are equal at equal (duh). 3) U gets destroyed if smaller.
Since the invariant term has now given us much more handy force count equations compared to the bonus section, we can now move to directly determining the remaining forces factor that we set out to get, as it directly represents final efficiency. Plugging in these times, depending on who we now know will win beforehand:

We get:
(9) Remaining Forces Factor
The final efficiency for the winner is thus determined by inserting the term of the winner into this:
(10B2) Efficiency - Battlefield (cost)

The inverse of this will then be the efficiency of the loser.
We had the cost necessarily baked into the formula, but it can now be extracted back out to arrive at primitive unit count elimination efficiency and from there mass efficiency (or any desired combination):
(10A) Efficiency - Battlefield

(10B1) Efficiency - Battlefield (size)

Lastly, finally, you can write the full battlefield efficiency formula out the same way it was done for duels in (6), in a despite the troubles getting there, surprisingly easier to compute form:
(11) Battlefield Efficiency Complete
The cost and unit efficiencies just determined in 10A and 10B1 can be re-applied in the same way to the inner part of of the sum as they had been in (6).
Another interesting thing to note here btw. is already a conclusion that I want to frame, stemming from the mere condition of winning here again:
C1: “An increase in cost of a design is only justified if it leads to at least a quadratic raise in killing efficiency against its enemies.”
Because, as you can see, cost itself has quadratic impact on performance due to the cheaper side not only being less costly when individually destroyed, but also appearing with more “individuals” to begin with at the same time. In effect, this is increasing defense on a secret route not caught by the classic defensive stats alone.(more “lives”, while a tank only ever has 1)
Thus, if a bigger weapon comes with *1.1 cost, it better at least provide *1.21 better killing chances.
That concludes the theoretical base. Now that all the tools exist to really look into what does what and how well it fares, I put it all into an Excel file to make it quicker to calculate. I will show you some findings in the next section, but everyone can play around with it if they want here: Aurora GC Analysis v1.1.xlsx
Analysis
To start out with, I found it would be interesting to maybe settle a question everybody could quickly stumble across and see if that reveals something in the process already.
“What is the best anti-infantry tank?”
Using this model
Against softest targets of same TL it dispatches 68 light PWI in duels and 48 in battlefields.
Against many types of infantry, with the exception of any LAV, we find a very efficient design:
However, increasing armor from light to medium reveals something profoundly interesting about Aurora GC rules:
All the anti-infantry performance stats remained exactly the same! Our tank model got 2 times as expensive from doubling its armor, but since even LAV could just barely penetrate the light armor, weapon efficiency against it went down by exactly (1/2)^2, as dictated by (1). Since this combines with C1 to cost(*2)^2 = efficiency(*2)^2, we arrive at exact parity.
However, notice that against the group of 3 vehicles to the right the extra armor actually decreases efficiency against them? That is because some of their weapons (the MAVs and MACs) actually overshot the armor in the beginning, so adding more actually put the anti-infantry tank more into their target focus, thus not being able to “harvest” the extra efficiency from more armor to offset the quadratic inefficiency loss from cost.
This reveals a tragic truth about Aurora GC mechanics (no criticism though), by applying the C1 to:
C2: “An increase in armor thickness is only ever barely justified if the original armor wasn’t (or was barely) penetrated to begin with.”
Or a more compact, final conclusion version:
C2B: “An increase in armor thickness is never worth it.”
Now if that sound sacrilegious to you, welcome to the show and the why I opened this topic.![]()
But think about it. Increasing the armor through thickness by a factor f can at best only decrease enemy killing chance by 1/f². At the same time, cost is directly linearly related to armor thickness (cost~f), thus our win efficiency determination (Kills_T*cost^2) becomes 1/f² * f² and cancels out exactly.
At the same time however, this cancellation does not occur at the same 1/f² yield for any weapon that overshot the previous armor, while still demanding f² battlefield efficiency on the negative side.
So we have 0 gains and sometimes loss. The only conclusion is to never do it.
Uncomfortable truths need to be spoken, but as my disclaimer reads, I will also ignore them, - just know them.
Just to make it clear, this rule only pertains to ‘armor thickness’. As by the cost formula (4C), any increase in base armor from TL comes free of charge and remains a huge boon.
Also, this is a cost consideration only. If you are looking for the highest performance for a certain drop size (mass limited deployment, not cost limited), then armored units are of course at least neutral if not better performing. A boarding shuttle crew in heavy armor will always be the better pick.
…But armor thickness is useless in an open battlefield where both sides can throw whatever is available.
Heavier in other ways
Okay, so making the thing heavier from skin is not a good idea. What if we also increase the motor and make it heavier as a HVeh anti-inf tank instead?
Yields in all regards are once again slightly lower than with the light MVeh. We increased size (thus cost) from 50 to 68 here. A 36% cost increase vs a 50% hp gain should at least in those cases where dmg wasn’t high enough yield a slight increase, or not? Ah, but the HVeh is also 33% easier to hit, thus the inefficiency rise is actually cost^2*Hitmod_increase, which comes out to virtual cost factor of 57%, - slightly worse than what we get from hp.
Exactly what shows up in the graph, and I checked, but this exact slight 7% inefficiency shows up throughout all tech level differences too. I will spare the armor thickness experiments as those are now foregone conclusions.
So you can’t make a better anti-infantry tank by going heavier, but can it be better by being lighter? Yes.
Performance increase in all regards, including LAV infantry! Its only counter in fact seems to be the lightest possible LAV with on the other side even anti-vehicle MAV tanks performing at a loss, what is going on?
The combination of square increase from saving about a third in cost and another third from better hit mod (~27/8 gain) has more than offset the loss of only half the kill shots from one weapon (50% inefficiency).
Now we have a design that performs well not just in an anti-infantry role, but shapes up as potential anti-all superior design. Can we improve by going even smaller and not using a vehicle at all? Well, not entirely as well. We have already seen HCAP infantry being outmatched by real anti-infantry tanks. However, CAP infantry still reveals something interesting:
Is this dramatic anti-vehicle efficiency from a supposed anti-infantry trooper? The only weakness shown here being the HCAP vehicle from just before?
Well, as infantry come with 0 base size, the weapons now follow the same direct application of C1 as the armor before, which is that lighter is always better except if efficiency increases by at least square that saving. HCAP is more than 50% more expensive for only potential 50% AP gain, and thus really inefficient in every single situation. I looked at the all TL comparisons, and HCAP is literally never an improvement over CAP for infantry against any unit at any TL, so a micro conclusion:
C3: “Infantry should never use HCAP over CAP.”
Again, this is for cost consideration only. Density of firepower is a perspective where HCAP is better unless your TL exceeds enemy TL so far that your CAPs can even shred tanks with guarantee.(but then you wouln’t care about efficiency anymore, so HCAP>CAP for mass, always)
You might also want to conclude the same for PWI vs PW, but here the 20% cost vs potential 25% offensive gain lead to more ambiguous outcomes.
Despite that small outlier, I think it is time to celebrate the previous findings by formulating a super summary conclusion so far:
C-Super: “Light designs are cost efficient. Heavy designs are size efficient.”
It might sound obvious if stated like that, but is by no means guaranteed from just some rules and seemingly random numbers for vehicle and weapon weights as they are. However, the balancing is so well done that Aurora C# simply blooms into this great position where both paths of design have their own clear benefits, thus leaving none obsolete, and even satisfying the RP-perspective.
Battlefield Hierarchy
With that foundation settled, there still remains the question and the lead from before that indicated possible existence of a ‘best unit’ (by cost) semi-allrounder with few specialized weaknesses.
We had an extremely well performing light vehicle, and an anti-infantry infantry that somehow was immensely efficient against vehicles as well. Hell, CAP infantry is actually so good, it performs favorably even one TL upwards against a somewhat balanced 55% infantry battlefield (own unit is TL3):
(Great average 1TL up mostly due to stellar performance against LAV infantry, which with 15% is most likely overrepresented here.)
To spare all the detailed individual investigations, it would be better to just take this entire theatre…:
…and see how it performs against itself in one go:
I marked our champions light CAP infantry as well as the two light vehicles, because they clearly stand out.
So things to note:
- All light infantry, save PWL -the greatest failure of all-, is actually performing stellar well, being only ever beaten by dedicated anti-infantry but literally no other vehicle class, and even then never to a truly disastrous degree like <0.1.
It appears the “light is most cost efficient” rule can be appended to include the unit classes themselves after already conquering armor and weapons. - In fact, the greatest winner here (and in other tests) is the LAV light infantry, though it also has glaring weaknesses that can be much more easily exploited compared to the all round fit other infantry types. Also, the numbers convey undue advantage from 45% vehicle content still being a rather too large share of true battlefield composition.
- You can clearly see the previously reported “armor thickness makes things worse, always” statement in action.
- Heavy vehicles really have no place in cost considerations.
The semi anti-infantry light variant (18) is barely performing against anti-infantry tanks, and otherwise infantry too armored to be in the field anyway.
The heavy HAV (20) at least works as HVeh and anti-infantry tank hunter, but those positions are also performed better by other designs.
Finally, my favorite, my original GDI Mammoth Tank template (MAV+MAC) HVehH, is the greatest loser of all, having no strengths other than anti-infantry tanks, against which he is also just 3rd place. - Tank destroyer MVehs with HAV, despite overshooting other MVeh, are actually -true to design- very effective against all medium or heavier vehicles, thus becoming the only non anti-infantry tank design to be viable.(though still outclassed by light LAV infantry)
- Finally the two most popular light vehicle designs, where the MAV version is the most efficient tank destroyer in the game (even above LAV infantry) but with a series of glaring weaknesses (also against said vindictive LAV infantry), while the HCAP version is shinning through and through as the king of the battlefield, only being beaten by both these grumpy envious louts.
For comparison to the last, its CAP version too:
![]()
As you can see, while average performance increases by notable further 25% and the LAV-inf is left beaten, it also comes with a reinstated allergy to the common main battle tank and other heavy vehicles. In my opinion the avoidance of straight counters is in summary more important to be crowned a battlefield king (otherwise a 1million one-unit specialist could claim it), but that might be taste.
Since lots of unit types seem to be made obsolete by others that are just simply better than they themselves in all matters and do more, a sort of core unit composition and hierarchy has now emerged, which I see mostly as this:
(Single LAV LVeh {0.15} or double LAV MVeh {0.21} are actually the most efficienct anti HCAP LVeh designs, but who really builds these?)
So all tanks are useless, except maybe the anti-infantry tanks, who can however all without exception be better represented in that role by the HCAP LVeh.
Seeing that and thus taking the tanks entirely out of the picture, we arrive at a classic paper-rock-scissor situation, where:
- AT infantry and AT walkers/skimmers --beat–> regular walkers/skimmers
- Walkers/Skimmers --beat-> all other infantry
- All other infantry --beat-> AT infantry and AT walkers/skimmers
- Everybody: Eats tanks for breakfast. (infantry sometimes scared)
Those are the conclusive rules for Aurora GC cost efficiency. Lay thine eyes upon them and despair. (or or you may like it, idk..)
Visuals Hinting at Model Weakness
The last section deals with perhaps a hook for further discussion, because I could myself not solve it in any definite way. Remember that I said in the very beginning that in my GDI ground battles there was only one unit that stood against all tides and even defeated enemies of higher tech levels?
That unit was no M60 armed Humvee LVeh. Those were in fact the first to go.
The winner was the Mammoth Tank. A unit the math says is the worst of the bunch. When all other units of the division had been eradicated to single digits or close to, the original 24 strong contingent of HVeh multi-purpose tanks ended the battle with still 18 of them left, mowing down hundreds of enemy PWI and even LAV.
The fourth power (Attack/Defense)^4 law had their armor deny even technologically advanced enemies, and their bigger cannons actually came into focus when classical AP weapons could not touch the enemy anymore.
“Shooting with cannons after sparrows?” Yes, but what if those sparrows suddenly developed shield generators? Then the cannons are the only calibre left still hurting, so you gotta do it.
Looking at it more naively, I actually found that a multi-purpose HVehH was usually only matched by any weight HAV designs and more anti-tank specialized medium HVehs:
However, that is not because getting weapons into focus was the entire story either. What really turned it around is the uncaptured effect of cover.
[Edit: A misconception and error had me thinking all units were target size=1. Corrected below, but I leave the original text bit.]
Wrong Original
In Aurora, units aren’t targeted by size, but by unit, so everyone is essentially just “size 1”. That curiously means that large and expensive units effectively apply a shrink factor when becoming part of a force group. The larger, the more they get hidden/overshadowed by friendly crowds in matters of cost calculations, and thus the more they benefit from cover.
A calculation example (also in the Excel file):
A tank of cost 12 might get targeted by 100x0.12 cost enemy infantry at once, being easily destroyed. However, if he appears with a cost equivalent contingent of 100 infantry himself, the enemy also receiving another 100, we have two equal cost forces again, ours with 101 units, the enemy with 200.
The chance that the tank gets targeted suddenly shrinks to 2/101 of what it was before, thus representing about 98% cover. Naively he now has 50 times as much time to deal with the enemy infantry that is only twice as large (though, of course, cover will deplete over time). Given that the tank could in some situations (like tech advanced aliens) be much better at guaranteeing kills than the infantries around him, this force composition suddenly is better than any of both units on their own.
In Aurora, units aren’t targeted by cost, but by size. Since larger vehicles expand in cost faster than in size, it curiously means that large and expensive units effectively apply a shrink factor when becoming part of a force group. The larger, the more they get hidden/overshadowed by friendly crowds in matters of cost calculations, and thus the more they benefit from cover.
A calculation example (also in the Excel file):
A tank of cost 12 might get targeted by 100x0.12 cost enemy infantry at once, being easily destroyed. However, if he appears with a cost equivalent contingent of 100 infantry himself, the enemy also receiving another 100, we have two equal cost forces again.
Though an infantry man comes at 1/100th the cost, they still weight 1/10th of a tanks weight. Thus the 100x infantry force of equal cost to the tank will get targeted 10 times more often due to their sprawling size.
The chance that the tank gets targeted suddenly shrinks to 2/11th of what it was before, thus representing about 82% cover. Naively he now has ~5 times as much time to deal with the enemy infantry that is only twice as large, - more than doubling his personal performance. (though, of course, cover will deplete over time) Given that the tank could in some situations (like tech advanced aliens) be much better at guaranteeing kills than the infantries around him, this force composition suddenly is better than any of both units on their own.
[/Edit]
Somewhere in the formulas section I wrote that cheaper units shine because their cheapness leads to quadratic increase in efficiency from also granting them a second line of defense upgrade from getting ‘extra lives’.
Well, it turns out other units can borrow that part, as simply by standing next to those ‘extra lives’, they kind of “rub off”. The effect essentially allows to merge large attack power of heavy units with large extralegal defense stemming from ‘many lives’ the tank doesn’t otherwise have access to.
Yes, it won’t work for too long, but longer the more you add, and every bit of time is more valuable to the ‘100% kill chance but too few shots’-tank as it is to the ‘low kill chance but many shots’-crowd.(rather, the later doesn’t even get as much cover due to ..being a crowd)
Cover benefits the large, singular units most. [Edit] Just 1 infantry man means a huge tank receives half damage for a time.
Just a few infantry men can mean a huge tank receives half damage for a time. [/Edit]
So while the Mammoth Tanks in that historic encounter might have nearly lost all cover, even the bit that was still left meant their mere 18 remaining units were so unlikely to be targeted that they could continue their devastating artillerist handiwork until no enemies were standing.
…In have failed to capture this effect in straight mathematics. It depends too much on real battleforce composition on both sides. I don’t think that outside of complete simulations of battles there can be a straightforward formulaic predictor as those demonstrated above. It really “depends”.
For now you can simply approach the reality of being integral to a working battle force by tweaking the cover option I added in the sheet, though remember that each unit type would need a different value. (maybe some standard for size-to-cover gain could actually be worked out? By looking at PW infantry as standard perhaps? Recommendations welcome)
Though it isn’t really any final conclusion this time, and even draws into question previous conclusions made, I think it is still time to celebrate this final revelation just emerging out of the Aurora basic rules setup:
C4: “Force composition actually matters”
Great for RP, great for keeping all game elements relevant. Not so great for calculation exactness. ![]()
So that might be potentially disappointing that all that could be read above in the end is thrown into disarray. Perhaps see it as a buddhist zen voyage, where you learn about all the complexities, only to after years realize it is all simple again, ..but now you know why just a bit better than before. ![]()
So until further GC enlightening might graze us, I will close the post as I did back in the old forum on similar topic:
“All hail the Mammoth Tank!”
///Edit 28.10.26: One of the final battlefield efficiency formulas was inaccurately calculating the side of the targets. I changed it to show only “our” side. The calculations had used the correct one already, so just a visual issue that is updated in the new excel file too.




























