Supporting continuing development for Empyrean Challenge / Cluster Wars
You are not logged in.
My point was that 100 ANM-10 is the same mass as 1000 ANM-1 and 100 MSL-10 is the same mass as 1000 MSL-1. Therefore the effectiveness of your ANM is always just proportional to the mass of assembled launchers. Every other element in the game where mass increases linearly with TL has its ability increase by TL^2. I think you should get that bonus with better TL ANM. Otherwise, if you chose to not increase MSS-TL any mass of MSL-1/ANM-1 would be just as effective at blocking MSS as the same mass of higher TL ANM.
I can add FUEL usage to the calculator. In defense, will also need to note that FUEL usage may be less than 100% if not all the ESH have to be used to block the attack.
SHP damage was always random but I do remember you could specifically target specific areas of COL like ASM, FCT, MIL, etc. - will start another thread to address the "Black Box" of combat damage.
Would probably still keep the old orders to run as inputs to the game engine, but they would be entered into a database and checked for accuracy - i.e. making sure (and giving you the choices to) PME, PMM, etc only on S/Cs in your orbit. LOD/UNL commands would maybe automatically add a DOC command or give error message if you already have a DOC command to another S/C. Some "deep" error checking might not be possible because when validating requires reading all the orders the program may become less responsive. However, being able to run Test Turns at will immediately (which assume that combat doesn't mess with your plan) will help tremendously.
Was thinking along those lines in the sense that when you looked at the detail of one of your S/Cs you would also see the orders associated with it. Most orders have an S/C that gives the order but also another S/C, system or orbit which is a target of that order. This way on the detail view of another s/c, system or orbit you will see orders where it is the target of an order as well. For example, a detail view on an orbit might show the RPVs targeting it for probing from which S/C. Could also allow navigation between system views, orbit views and S/C views with hyperlinks.
The rulebook stated ANM intercept ANM-TL / MSS-TL * 0.9 MSS.
However, say you have 100 ANM-10 against 100 MSS-10, 90% intercepted 10 MSS-10 get through.
If you had ANM-1, an equivalent mass of ANM would be 1000 ANM-1, which if 9% effective still shoot down 90 MSS-10.
I think formula should be ANM-TL ^2 / MSS-TL ^2 * 0.9, otherwise no incentive to ever upgrade from ANM-1.
This is reflected in the MSS damage calculator utility.
The goal is to develop a web based interface to the game. EWP and MSS Damage Calculators are up and an S/C Design Program is next. Plan is to proceed with web-based order entry and validation as well as automated running of test turns through the web interface. Turn results and all the functionality of Central Command will be available in web format. Optionally, a PDF of all systems and S/Cs could be generated for off-line viewing.
Please comment on algorithms and if they seem correct