Recent content by AnotherDilbert

If we change the basic setting to "-1" (Budget ship) and refresh the filter, we get budget hull and drives: Saving about MCr 10. Leading to a potentially profitable tramp trader:

To get an estimated economic projection, select if the ship is a Custom or Standard design in cell C200: Not great... You'll find a CT-style description of the ship on the "Description" tab:

Use the filter in cell A9 to hide rows that are not needed: Resulting in:

Specify some passenger capacity: And we are essentially done...

Specify a 200 Dt hull: Specify Jump 1 and Man 1:

Let's build a simple tramp trader, something like a Free Trader: Start with TL and basic setting, TL 12 seems reasonable: The basic setting controls a lot of default values. Specify "0" for a standard ship. Collapse all the grouped cells with the "1" button top-left, they are generally...

How to use this spreadsheet: https://forum.mongoosepublishing.com/threads/high-guard-2022-ship-design-spreadsheet.126250/

Take a standard Free Trader: Not profitable. Add Decreased Fuel to the Jump drive: Even less profitable... Change to a Budget Jump drive: Still not profitable, but less unprofitable. Budget drives are more profitable, unless the ship is tightly packed with large drives. Essentially...

Sorry, even worse... I must have been thinking about T5.10, completely unrelated to Mongoose:

Oops, I was still in HG'16 mode... Thanks for the correction.

Yes, quite. Note the cost is the same. You cannot reduce the drive to less than 10 Dt. For a small tramp trader, a Budget drive is probably better for the bottom line. Here, the cost isn't the same... The smaller base tonnage of the Power Efficient plant is cheaper (and uses less fuel).

I give up... We are obviously not going to even remotely agree.

OK, "None". Then why are we discussing detection or sensor rolls at Very Distant? There can't be any. This would be a direct contradiction: "However, it is possible for sensors to reach further in order to detect incoming threats." So, you get the same information at Very Distant, despite...

I wouldn't read too much into that. In MgT2'16 Distributed Arrays were specifically to get Minimal sensor info at Distant range for Radar (even if we already had it for Visual and Thermal), just as the text still says. Core'16, p150: That was then given for free in Core'20, making Arrays...

So, you have abandoned your assertion that is sensor detail is "None" at Very Distant? You are now maintaining that there is some intermediate state of sensor detail between "None" and "Minimal" that isn't defined, discussed, or even vaguely alluded to in the rules? Why would that rule limit...