:arrow: Maybe it is time to consider adding the battle queue interface.
The basic implementation would be to list the forces in conflict, and give the player the choice between "auto-resolve combat" and "attempt retreat".
This would deal with the problem of getting destroyed by an unknown enemy-- at least you have a chance to identify the foe and a chance to retreat. Eventually this queue would have more options including the option to personally lead your fleet in glorious 3D battle.
Geoff the Medio wrote:
If i'm reading it properly "speed" is on a scale 10 times smaller than detection radii. I.E. A ship with a speed of 50 will travel from a detector with the power of 5 to the edge of it's detection in one turn. It would be nice if these numbers were on the same scale-- at least as presented to the player. And there's really no need for the speed numbers to be so large. The difference between a speed of 30 and 31 is hardly noticable.
Historically, and as I think of it, and more or less as implemented in code, it's the other way around:
detect_range = 10.0*(detection - stealth);
The x10 factor can be removed, if you'd like... The reason for having it was to keep the stealth and detection meters in a 0 - 100 range. If things are going to be in consistent units between speed, stealth, and detection, then I'd rather it also be consistent with distances in uu on the map as well (as opposed to keeping the x10 for detect range, and adding an x10 for actual ship speed from ship speed meters).
Keeping the numbers in the 0-100 range is generally a good thing. It's also a good thing to avoid putting useless zeros on the end of numbers. Smaller numbers are easier to deal with and understand -- you don't measure a road-trip in meters or yards, but in kilometers or miles. Since the ship speed and UU numbers show roughly 10x the granularity than the player actually cares about i'd like to see the other associated measures match how detection is currently displayed.
Detection of 100 will encompass a 500 star galaxy if the detector is roughly in the middle, so the high end of that scale works out pretty good.
If 1 detection AND 1 speed are both going to be 10 uu... then why not change the UU?
what was 10 is now 1... that way no multiplications would be required.