bluedog_Ablestar_Tank incorrectly being defined as an engine not a tank

[Fiddoodle]

bluedog_Ablestar_Tank is defined as an engine on line 419 of chemical-propulsion-Bluedog_DB.cfg, when it should be defined as a bipropellant tank on line 63.

This is causing it to show up in VAB Organizer as a rocket fuel tank and making its RCSFX property require hydrazine and IWFNA instead of the expected result of hydrazine or HTP.

[CharleRoger]

There is no bug in the configuration, it's working as I intended, but the way I have configured it could be improved. I wasn't able to find any information on the RCS system of the Ablestar, if it even did actually have any, so I just assumed it would have used hypergolic propellants, which restricts the possible subtypes in the fuel and oxidizer switches. It probably makes more gameplay sense to just make this an ordinary bipropellant tank and have a separate monopropellant RCS, as you described.

[Fiddoodle]

According to this blog, the Ablestar used nitrogen jets for attitude control in vacuum, although it has no source for the claim. Edit* no citation in text, the sources seem pretty thorough at the bibliography.

Limiting the tank to only holding hypergolic fuels would be a neat nod to its lineage as the first vacuum restart capable upperstage, although it is probably more hassle than it is worth for a single tank.

[CharleRoger]

I default to assigning monopropellant in this case, though cold gas thrusters have been on my mind as a possible modlet ever since I replaced EVA propellant with nitrogen. For now I will configure it as described above for the next version.