b) when i modified the name, i'd prefer aurora to keep the name even if i modify the specs afterwards; maybe an additional button "autogenerate" which gets enabled/disabled by the same flag storing the "customized name" state could be added for that
c) for autogenerating names, i'd love to be able to modify the naming convention; for example, i didn't much care for the power need on energy weapons, but the recharge time instead.
d) when designing ships (and at many other places relevant to combat), the component names column was too small, and the relevant information wasn't visible (especially when it came to fire controls and sensors, it got tricky to distinguish between the point defense systems and the anti-ship/long range systems produced by the same company)
^ This, so much this.
I'd kill for formatting tokens that can be used in the name which pull details from the design specifications, both selected tech and calculated results.
Given the quantity of useful information, perhaps enumerate alphabetically with a-z as tokens or the actual variable names wrapped in angle brackets(<var_name>)? Something of the sort. Anyways, I'll assume a-z tokens for now.
Then, for engines, perhaps something like what I buried in the OT tag for brevity.
token variable
a Engine Technology
b Power/Efficiency Modifier
c Fuel Consumption Technology
d Fuel Use Per Hour
#e Fuel Use Per Hour - Rounded
f Fuel Consumption per Engine Power Hour
#g Fuel Consumption per Engine Power Hour - Rounded
h Thermal Reduction Technology
i Thermal Signature
#j Thermal Signature - rounded
k Engine Size (HS)
#l Engine Size (HS) - Padded
m Engine Size (tons)
#n Engine Size (tons) - Padded
o EP
#p EP - Rounded
q Engine Technology
Possibly using % as the token identifier? %% to escape and get a % in the name. Rounding tokens taking an integer as total digits precision from left most digit. Padded tokens taking an integer for inserting leading zeroes if necessary to keep them that many digits so they both text align and sort correctly.
Assuming the following tech input for an engine, Magnetic Confinement Fusion, 1.15 Power/Efficiency, 0.3 Fuel Consumption, 0.35 Thermal reduction, 19 hull size.
I could then enter a name such as:
HS:%k P:%b F:%c T:h EP:%o
and I'd get something like :
HS:19 P:1.15 F:0.3 T:0.35 EP:546.25
or
Assuming the following tech input for an engine, Magnetic Confinement Fusion, 0.85 Power/Efficiency, 0.3 Fuel Consumption, 0.35 Thermal reduction, 7 hull size.
I could then enter a name such as:
Vega Mk2 %#2lHS %3eFPH %2pEP Engine
to get:
Vega Mk2 07HS 27.6FPH 150EP Engine
where un-rounded, FPH is 27.64, and EP is 148.75
Or the aforementioned energy weapons, say, laser:
token variable
a Focal Size
b Focal Size - Final
c Wavelength
d Capacitor Recharge Rate
e Reduced Size
f Energy Weapon Mount
g Damage Output
h Rate of Fire
i Rate of Fire - 5s Increments
j Range Modifier
k Max Range
l Max Range - 10k km
m Max Range - Practical
n Max Range - Practical - 10k km
o Effective Range
#p Effective Range - 10k km
q Size (HS)
r Size (Tons)
s Power Requirement
t Power Recharge
Where the practical range is the game restricted maximum range rather than the weapon range, end effective range takes an integer specifying damage to yield range for.
then, assuming the following tech input:
40cm, X-ray, Capacitor 8, Reduced Size 0.75, Spinal
and a name such as the default is:
%bcm C%u %c Laser
or:
50cm C2 X-Ray Laser
alternatively, this name might be used:
%bcm Laser (Spinal %a) ROF-%j D64-16-4=%20p-%10p-%5p k km %rt
50cm Laser (Spinal 40) ROF-32 D64-16-4=7-28-112 k km 600t
Indicating that its a 40cm focal size, uprated to 50cm via spinal, takes 32 increments to recharge, and puts out 64 damage to 70,000km, 16 damage to 280,000km, and 4 damage to 1,120,000km, and masses 600t.
15cm, X-ray, Capacitor 12, Reduced Size 1.0
%bcm Laser ROF-%j D64-16-4=%64p-%16p-%4p k km
15cm Laser ROF-2 D64-16-4=0-2-10 k km
The obvious insertion of flavour is as simple as its ever been under this system, just place raw text as you see fit, and use as few or many tokens as desired.
If we had that, naming schemes other than stock which involve one or more criteria from the design become painless to utilise, rather than an effort to remain consistent with theme/past designs due to having to manually edit the name for every design you ever make, patterned or not.
