Aurora 4x
New Players => The Academy => Topic started by: vorpal+5 on May 13, 2020, 10:51:01 PM
-
How they differ in properties? What does it means exactly to be static, as no unit move on the surface of a planet?
-
Think of it like towed artillery. They do not evade, can be fortified as well as infantry and can be very armoured.
-
They can be anything from dug-in bunkers/shelters/pillboxes to towed artillery to horse-drawn cannons to fortified laagers and so on.
-
So they seem to be very interesting for most if not all units? Would you declare infantry static, and if not, why?
-
Infantry isn't static because of a combination of things:
a) there has to be a unit class that perform boarding combat between ships
b) terrain affects different types in a different manner
c) infantry can self-fortify and dodge in a manner that is different from other classes
d) infantry cannot armour itself in the manner that static can
-
Sorry, I mixed concepts here, somehow a part of my brain thought that 'static' was a property you could attach to any unit type ...
Let me rephrase ... Why would you want to use anything but the static template, except for specialized tasks, like boarding? A Static unit can entrench well and can be quite armored, so why not using it for all units templates?
-
Why would you want to use anything but the static template, except for specialized tasks, like boarding? A Static unit can entrench well and can be quite armored, so why not using it for all units templates?
I think (I'm having some problems getting my head around the systems too) that the downside of static elements is they have no evasion (The Hit Mod column for the base unit type). And fortification bonuses don't count when a unit is on attack. So if you want to put units onto an attack field position, you want units that can evade, so you don't want static units.
-
Static units can NEVER make any breakthroughs... infantry can do that.
Static units also are susceptible to losses more than infantry from some types of weapons.
Both static and infantry serves a purpose for different reasons.
-
what is a good design for a static unit? can you put some example?
-
Some examples of static units (armour and weapon tech levels set to 1 for easy comparison):
Pillbox-HAV
Transport Size (tons) 60 Cost 1.2 Armour 1 Hit Points 3
Annual Maintenance Cost 0.15 Resupply Cost 36
Heavy Anti-Vehicle: Shots 1 Penetration 6 Damage 6
Purpose: Support garrison infantry with a heavy anti-vehicle weapon, and do so cost-effectively. Is most useful on worlds without mountains or jungles.
Battalion HQ, static
Transport Size (tons) 62 Cost 4.24 Armour 1 Hit Points 3
Annual Maintenance Cost 0.53 Resupply Cost 0
Headquarters: Capacity 10,000
Non-Combat Class
Purpose: Be an HQ for a garrison battalion of 10k size. Is somewhat harder to kill, for the price, than a garrison infantry HQ.
15cm Railgun STO-Point Defence
Transport Size (tons) 417 Cost 52.24 Armour 1 Hit Points 3
Annual Maintenance Cost 6.5 Resupply Cost 0
15cm Railgun I
Range 60,000 km Tracking 12,000 km/s Damage 3 / 1 Shots 4 Rate of Fire 15
Maximum Fire Control Range 60,000km Chance to Hit at Max Range 0%
Maximum Sensor Range 1,261,564km Max Range vs Missile 113,541 km
Purpose: Provide anti-missile protection for a planet (plus light gunfire). Essential if you suspect the enemy might swoop in and nuke your precious homeworld!