CT Only: Continuing down the LBB recreation rabbit hole.

[plazman30]

And a request for comments. I wanted to make sure that these books could easily get distinguished from an original LBB copy, if for some reason these PDFs made it out "into the wild" and some unscrupulous seller began making PODs and selling them. So, I added this to the book. What are people's opinions?

 

[Ildefonse]

I think that is a fine choice to distinguish from the originals.

 

[PVernon]

I think it looks good, but the line of numbers 6 to 16 are the print run numbers ( the one scand is from the 6th print run) and should probably be changed in some way. Also (I realise that this is aconcept test so not in any way final) in the line below that there is a typo, the period between the 1 and 2 should be a comma.

 

[plazman30]

I think it looks good, but the line of numbers 6 to 16 are the print run numbers ( the one scand is from the 6th print run) and should probably be changed in some way. Also (I realise that this is aconcept test so not in any way final) in the line below that there is a typo, the period between the 1 and 2 should be a comma.

That's a good point. I think it might be best to completely remove the Printer's Key from the book. In a world of PDF distribution and POD, I don't think Printer's Keys are relevant any more.

 

[Takei]

That's a good point. I think it might be best to completely remove the Printer's Key from the book. In a world of PDF distribution and POD, I don't think Printer's Keys are relevant any more.

Printer's Keys might not be relevant but some sort of pdf document revision would be a good idea. ISO 8601 being a good candidate (YYYY-MM-DD).

 

[plazman30]

That's a good idea. I could use ISO 8601 as the version number of the document. I have proofreaders which have done an amazing job of finding typos. But stuff always slips through the cracks.

 

[plazman30]

It's funny. This is a personal project, but I'm treating like something that's going to get distributed to the masses.

 

[Takei]

It's funny. This is a personal project, but I'm treating like something that's going to get distributed to the masses.

I’m hoping it does

 

[plazman30]

Matt and Marc both know how to reach me.

The thing is, this is something I am working on as a fun little side project. I dive into it when I have time. I walk away from it when I want to. As soon as someone pays me and I have a deadline, this stops being fun and becomes work. Right now I am converting books 1 and 3 from Scribus to Affinity. Once that's done, I was going to take a crack at Book 0.

I just wish I could post this somewhere for people to see. But I understand how copyright law works.

 

[Enoki]

One thing I really want to update is the tables to make them easier to read.

Original LBB vs my "remaster":

View attachment 7130View attachment 7131

I have a question here.

I know you are reproducing the original tables, but it seems to me these are not all that consistent. For example, at 2G, moving 10,000 km is 23.6 minutes. Why list it in seconds? What is the measurement used in the game for moving these distances in terms of turns? Wouldn't a consistent unit of measure compatible with turns in space combat or whatever be more useful here? This issue seems to permeate the whole table.

 

[whartung]

I know you are reproducing the original tables, but it seems to me these are not all that consistent. For example, at 2G, moving 10,000 km is 23.6 minutes. Why list it in seconds? What is the measurement used in the game for moving these distances in terms of turns? Wouldn't a consistent unit of measure compatible with turns in space combat or whatever be more useful here? This issue seems to permeate the whole table.

He's not rewriting the rules, just reformatting them.

 

[plazman30]

I don't know the rules well enough to make them "consistent." But now they're in an editable form, so we could potentially make them consistent if someone wanted to.

 

[Badenov]

I have a question here.

I know you are reproducing the original tables, but it seems to me these are not all that consistent. For example, at 2G, moving 10,000 km is 23.6 minutes. Why list it in seconds? What is the measurement used in the game for moving these distances in terms of turns? Wouldn't a consistent unit of measure compatible with turns in space combat or whatever be more useful here? This issue seems to permeate the whole table.

I reproduced these tables in Excel for my own readability (and because there's an annoying copy-paste error in MgT1, my main source), and I had the same issue with inconsistent units. I wound up using the format "dd:hh:mm:ss" and just leaving the leading zeroes in. Then you can see at a glance how much time it takes in whatever units make sense for that number.

 

[Enoki]

He's not rewriting the rules, just reformatting them.

I said as much. I was just wondering why it was done that way to begin with. Making the numbers a consistent measure or turn based makes far more sense.

 

[plazman30]

I'm actually using an LLM to convert the tables into editable tables in Google Sheets/LibreOffice Calc. Might be useful to include a spreadsheet with all the tables in any final product.

 

[plazman30]

Here is what I did with Book 3, pages 10 and 11

Original LBB

 

[kilemall]

I have a question here.

I know you are reproducing the original tables, but it seems to me these are not all that consistent. For example, at 2G, moving 10,000 km is 23.6 minutes. Why list it in seconds? What is the measurement used in the game for moving these distances in terms of turns? Wouldn't a consistent unit of measure compatible with turns in space combat or whatever be more useful here? This issue seems to permeate the whole table.

Are you referring to the travel times chart?

If so, the time standard you seek is 1V is 10000 km per 1000s or 10km/s.

V for vee or retained velocity is not explicitly defined that way but it’s the shorthand I use since the vector maneuver figures so highly in my version of combat.

The travel times are based on the rocket formula that probably gives that space sim vibe CT is famous for. So in your example the craft reaches 1G in 500s of accel, flips metaphorically or actually and applies acceleration the opposite direction to come to a stop.

The system fudges actual distance/time travelled during accel for convenience, except when one uses the formula.

 

[kilemall]

A couple addendums-

Combat time for maneuver battle in CT is 1000 seconds with abstracted phasing.

So I read the chart as being tactical time for the typical play area of 1 million kilometers for battle, and calendar adventure time for long trips.

Matching course/vee or figuring out tactically optimal firing passes of course can happen much faster- most set piece battles are going to occur around a fixed point, a planet, shipyard or other facility.

 

[aramis]

I'm in the box every 3 rows and 3 columns camp. too lazy tonight to actually demo it.