(R2.FB4) MSSB-R02 Federation YF-71 - The YF-71 Blackbird Fighter-Bomber is not listed from SFT14, pg 6. - Ken Kazinski, 25 Jun 2017.

(R2.FB5) MSSB-R02 Federation SR-75 - The SR-75 Aurora Reconnaissance Fighter-Bomber is not listed from SFT14, pg 7. - Ken Kazinski, 25 Jun 2017.

(R2.FB6) MSSB-R02 Federation AC-130 - The AC-130 Hercules Gunship is not listed from SFT14, pg 7. - Ken Kazinski, 25 Jun 2017.

(R2.FB6) MSSB-R02 Federation C-5 - The C-5 Galaxy is not listed from SFT14, pg 7. Note, this probably should have been FB7 as FB6 is already taken. - Ken Kazinski, 25 Jun 2017.

By Ken Kazinski (Kjkazinski) on Monday, June 26, 2017 - 02:42 am: Edit

(R1.PF8) MSSB-R02 Federation Thunderbolt-Q - The graphics for the Thunderbolt-Q and Thunderbolt-R look to be switched. - Ken Kazinski, 26 Jun 2017.

(R1.PF93-R2) MSSB-R02 Federation Int-W = The Mustang-W Workboat is not listed from CL50 Supplemental. - Ken Kazinski, 26 Jun 2017.

By Steve Petrick (Petrick) on Monday, June 26, 2017 - 02:10 pm: Edit

(R1.PF8) MSSB-R02 Federation Thunderbolt-Q - The graphics for the Thunderbolt-Q and Thunderbolt-R look to be switched. - Ken Kazinski, 26 Jun 2017. REPLY: Previously reported and on the list for correction in a future update.

(R1.PF93-R2) MSSB-R02 Federation Int-W - The Mustang-W Workboat is not listed from the Captain’s Log #50 Supplemental File. - Ken Kazinski, 26 Jun 2017. REPLY: As has been noted elsewhere, it is kind of difficult to include something that was created AFTER the Master Starship Book of a given Empire is printed. The Federation Master Star Ship Book was published in 2014, and Captain’s Log #50 appeared in 2015.

(R2.125) MSSB-R02 Federation DLX - "technlogy" should be "technology." - Ken Kazinski, 25 June 2017. REPLY: Previously reported and on the list for correction in a future update.

(R2.F) MSSB-R02 Federation F-122 - The F-122 is not listed from Star Fleet Times #22, page #7. - Ken Kazinski, 25 Jun 2017. REPLY: As has been previously noted, we do not include in the Master Star Ship Books things in Star Fleet Times that have not been published either in a Captain’s Log or formally published in a product.

(R2.F) MSSB-R02 Federation F-22 - The F-22 is not listed from Star Fleet Times #22, page #7. - Ken Kazinski, 25 Jun 2017. REPLY: As has been previously noted, we do not include in the Master Star Ship Books things in Star Fleet Times that have not been published either in a Captain’s Log or formally published in a product.

(R2.F20) MSSB-R02 Federation F-101 - Nick Samaras asked on March 23, 2015, the line about no SSD available is incorrect. Captain’s Log #39 had SSDs for these fighters, and they look different then what is in this book. it was given reference number F20 in Captain’s Log #35. There was not an answer. - Ken Kazinski, 25 Jun 2017. REPLY: It is on the list for correction in a future update.

(R2.FA4) MSSB-R02 Federation B-24 - Should not "KIT BOMBERS" be in a box? - Ken Kazinski, 25 Jun 2017. REPLY: The decision was taken that the Kit Bombers are simply a subset of "Bombers in Captain’s Log" and the title was not placed in a box.

(R2.FB4) MSSB-R02 Federation YF-71 - The YF-71 Blackbird Fighter-Bomber is not listed from Star Fleet Times #14, page #6. - Ken Kazinski, 25 Jun 2017. REPLY: As has been previously noted, we do not include in the Master Star Ship Books things in Star Fleet Times that have not been published either in a Captain’s Log or formally published in a product.

(R2.FB5) MSSB-R02 Federation SR-75 - The SR-75 Aurora Reconnaissance Fighter-Bomber is not listed from Star Fleet Times #14, page #7. - Ken Kazinski, 25 Jun 2017. REPLY: As has been previously noted, we do not include in the Master Star Ship Books things in Star Fleet Times that have not been published either in a Captain’s Log or formally published in a product.

(R2.FB6) MSSB-R02 Federation AC-130 - The AC-130 Hercules Gunship is not listed from Star Fleet Times #14, page #7. - Ken Kazinski, 25 Jun 2017. REPLY: As has been previously noted, we do not include in the Master Star Ship Books things in Star Fleet Times that have not been published either in a Captain’s Log or formally published in a product.

(R2.FB6) MSSB-R02 Federation C-5 - The C-5 Galaxy is not listed from Star Fleet Times #14, page #7. Note, this probably should have been FB7 as FB6 is already taken. - Ken Kazinski, 25 Jun 2017. REPLY: As has been previously noted, we do not include in the Master Star Ship Books things in Star Fleet Times that have not been published either in a Captain’s Log or formally published in a product.

(YR2.CA1) MSSB-R02 Federation YCA/Cygnan - The rule in MSSB-02 is shown as (Y2.CA1) but the SSD shows (YR2.CA1). - Ken Kazinski, 25 Jun 2017. REPLY: After publication in Captain’s Log it was reported that the ship is not technically an "early years" ship, entering service in Y130, and therefore should not have had a "Y" prefix on its rule reference number. An error in updating that resulted in the "R" being deleted instead of the "Y," and that error got carried forward. When the SSD is reprinted, and when an update to the Federation Master Star Ship Book appears the rule number will be changed to (R2.CA1).

(YR2.CA2) MSSB-R02 Federation/Cygnan YDD - The rule in MSSB-02 is shown as (Y2.CA2) but the SSD shows (YR2.CA2). - Ken Kazinski, 25 Jun 2017. REPLY: After publication in Captain’s Log it was reported that the ship is not technically an "early years" ship, entering service in Y130, and therefore should not have had a "Y" prefix on its rule reference number. An error in updating that resulted in the "R" being deleted instead of the "Y," and that error got carried forward. When the SSD is reprinted, and when an update to the Federation Master Star Ship Book appears the rule number will be changed to (R2.CA2).

By Ken Kazinski (Kjkazinski) on Tuesday, June 27, 2017 - 10:32 pm: Edit

(R1.28J-R2) MSSB-R02 Federation GPF - Should not "superceded" in "use heavy fighters has been superceded by" be "superseded"? - Ken Kazinski, 26 Jun 2017.

(R1.41-2) MSSB-R02 Federation FTR - The rule for the FTR is (R1.43). - Ken Kazinski, 26 Jun 2017.

By Steve Petrick (Petrick) on Wednesday, June 28, 2017 - 01:04 pm: Edit

Ken Kazinski:

Currently, either spelling is basically considered to be correct although some dictionaries insists that "superseded" is incorrect and "superceded" is correct. (The auto-spell checker on this board takes the opposite view). I have more than a few books where superceded is used, seems to be an ongoing war. So for the nonce, I am going to leave it alone.

The Federation FTR was previously reported:

By Steve Petrick (Petrick) on Monday, November 24, 2014 - 03:52 pm: Edit

(R1.24-2) This ship can control a number of seeking weapons equal to half its sensor rating (F3.211).

(R1.28C-2) This base is missing the "-2" in its rule number.

(R1.28C2-2) This base is missing the "-2" in its rule number.

(R1.41-2) This unit should have been numbered (R1.43-2).

(R1.42-2) This unit should have had the engine refit defined in (R1.67).

(R1.43-2) [Corrected number for the unit currently numbered (R1.41-2)] This unit should have had the engine refit defined in (R1.67).

(R1.55-2) CanNOT disengage by acceleration or use emergency deceleration.

(R1.56-2) CanNOT disengage by acceleration or use emergency deceleration.

(R1.57-2) CanNOT disengage by acceleration or use emergency deceleration.

(R1.60-2) CanNOT disengage by acceleration or use emergency deceleration.

(R1.74-2) CanNOT disengage by acceleration or use emergency deceleration.

(R1.89-2) Add that the unit can control seeking weapons equal to double its sensor rating (XF3.2).

(R1.88-2) This unit is not in service prior to Y160 and so does not need the Y140 transporter and tractor refits.

By Ken Kazinski (Kjkazinski) on Saturday, June 02, 2018 - 10:25 am: Edit

(R2.4) Federation CA - The Kongo is missing from the known names paragraph. See AM, SH7.0. - Ken Kazinski, 2 June 2018.

By Steve Petrick (Petrick) on Saturday, June 02, 2018 - 11:58 am: Edit

Kongo was converted to a command cruiser and listed there.

By Ken Kazinski (Kjkazinski) on Saturday, June 30, 2018 - 07:08 pm: Edit

(R2.62) MSSB-R02 Federation DER - Captain's Log #31, the designation of Halsey is missing from the known names paragraph. - Ken Kazinski, 30 Jun 2018.

By Steve Petrick (Petrick) on Monday, July 02, 2018 - 01:16 pm: Edit

The Official ship registry has Halsey listed as a DE (and is shows up in the list of names of DE's in the DE entry (R2.14), it is listed as a DE in the scenario where it appears (SH96.0), even though the other escorts of Nimitz are FFRs. Name is not missing.

By Ken Kazinski (Kjkazinski) on Wednesday, July 11, 2018 - 10:19 pm: Edit

So the DER is a DE, correct?

By Mike Dowd (Mike_Dowd) on Wednesday, July 11, 2018 - 10:50 pm: Edit

IIRC, the DER is a DE optimized for use on the Romulan front.

By Steve Zamboni (Szamboni) on Wednesday, July 11, 2018 - 11:36 pm: Edit

More phasers, fewer drones.

By Eddie Crutchfield (Librarian101) on Thursday, July 12, 2018 - 12:03 pm: Edit

Keeps 2 extra P1 instead of 2 additional drone racks

By Jeffrey Coutu (Jtc) on Thursday, November 14, 2019 - 12:32 pm: Edit

The following report is based on the 21 October 2014 Federation Master Starship Book.

(R2.10) In the “Seeking weapons:” paragraph, change “(F2.311)” to “(F3.211)”.- Jeff Coutu 14 November 2019

(R2.29A) In the “Y179-Y183” row of the carrier data chart, before “6xF-101C” add “or”.- Jeff Coutu 14 November 2019

(R2.32) In the image, the middle warp engine is missing the end portion.- Jeff Coutu 14 November 2019

(R2.39) At the end of the “Seeking weapons:” paragraph, change “(F2.213)” to “(F3.213)”.- Jeff Coutu 14 November 2019

(R2.53) In the “Landing force” paragraph, immediately after “four ground combat vehicles” change “(D15.81)” to “(D15.82)”.- Jeff Coutu 14 November 2019

(R2.60) In the carrier data chart for “Y180-Y183”, in the Escorts column after “FRA” add “(Rom)”.- Jeff Coutu 14 November 2019

(R2.86) In the “Shuttles:” paragraph, change “(M8.12)” to “(M8.312)”.- Jeff Coutu 14 November 2019

(R2.95) In the carrier data chart for “Y177-Y179” and later, in the Escorts column, after “None” add “(Raid)” (five locations total); this is based on the units description and also how it is done in (R2.96).- Jeff Coutu 14 November 2019

(R2.95) In the "Seeking weapons:" paragraph change “(R2.212)” to “(F3.212)”. - Jeff Coutu 14 November 2019

(R2.98) In the carrier data chart for “Y180-Y183”, in the Escorts column after “FBE” add “or”.- Jeff Coutu 14 November 2019

(R2.99) In the carrier data chart for “Y179-Y180” and “Y180-Y183”, in the Escorts column after “FFA” add “or” (two locations total).- Jeff Coutu 14 November 2019

(R2.102) In the “Seeking weapons:” paragraph, change “(F3.22)” to “(F3.21)”.- Jeff Coutu 14 November 2019

(R2.104) In the first paragraph change “(R2.27B)” to “(R1.27B)”.- Jeff Coutu 14 November 2019

(R2.130) In the “Seeking weapons:” paragraph, change “(F2.213)” to “(F3.213)”.- Jeff Coutu 14 November 2019

(R2.132) In the “Seeking weapons:” paragraph, change “(S3.212)” to “(F3.212)”.- Jeff Coutu 14 November 2019

(R2.137) In the second paragraph, in the text “SAR shuttles (R1.F25)”, I suggest changing “SAR” to “rescue”.- Jeff Coutu 14 November 2019

(R2.A23) In the header I suggest changing “(DDM)” to “[DD(M)]” since “DD(M)” is what is used in the Master Ship Chart on Captain's Log #33 page 105 and Module G3 page 28; and on the SSDs from Captain's Log #33 page 108 and in Basic Set SSD Book on page 15.- Jeff Coutu 14 November 2019

(R2.A23) In the second to last paragraph it should also mention that the SSD is combined with the destroyer in the current Basic Set.- Jeff Coutu 14 November 2019

(R2.A24A) The carrier data chart lists F-8 and F-4 fighters for Y170-Y173 but the “Escort ready racks:” paragraph does not mention configuring escort ready racks for those fighters.- Jeff Coutu 14 November 2019

(R2.A25A) The carrier data chart lists F-4 and F-8 fighters for Y169-Y174 but the “Escort ready racks:” paragraph does not mention configuring escort ready racks for those fighters.- Jeff Coutu 14 November 2019

(R2.F8) In the “F-20CE” paragraph, after “(J4.241” add “)”.- Jeff Coutu 14 November 2019

(R2.F10) In the “F-15E” paragraph, after “(J4.241” add “)”.- Jeff Coutu 14 November 2019

(R2.F12) In the “A-6D” paragraph, change “(J1.F9)” to “(R1.F9)”.- Jeff Coutu 14 November 2019

(R2.FA1) In the first paragraph change “(R1.F15)” to “(R1.F13)”.- Jeff Coutu 14 November 2019

(R2.FA7) The second from last paragraph it indicates that chaff was installed in “Y168” but in the paragraph beginning with “A chaff pack (D11.0)” it indicates chaff might have been added in “Y169”.- Jeff Coutu 14 November 2019

(R2.FA13) Based on the Master fighter Chart in Module G3 (which indicates the F-104G has 4xVI for drones and the F-104J has 2xI and 4xVI for drones), at the end of the “F-104S” paragraph, change “two remaining type-rails. For the F-104J delete one shaded box and there are four type-VI rails and two type-VI rails” to “two remaining type-I rails. For the F-104J delete one shaded box and there are four type-VI rails and two type-I rails”. [Specifically change “type-rails” to “type-I rails” and change the final “type-VI” to “type-I”].- Jeff Coutu 14 November 2019

(R2.208) Based on the ships description, the carrier data chart should have “or None” added to the Escorts.- Jeff Coutu 14 November 2019

(R2.212) Based on the ships description, the carrier data chart should have “or None” added to the Escorts.- Jeff Coutu 14 November 2019

(R2.213) In the first paragraph after the carrier data chart, change “(R2.F20)” to “(R2.FA14)”.- Jeff Coutu 14 November 2019

(YR2.8) Near the end of the first paragraph change “(see next page)” to “(see at right)” or something to that effect.- Jeff Coutu 14 November 2019

(YR2.29) In the first paragraph, change “(Y2.16)” to “(YR2.16)” by adding the “R”.- Jeff Coutu 14 November 2019

(R1.R-2) In the “Y181 DOCKING BAY HANGAR REFIT” paragraph, change “(R1.80A)” to “(R1.89A)”.- Jeff Coutu 14 November 2019

(R1.1-2) The first fighter table indicates that A-10 and A-20 are available in Y180, however, in the paragraph above the fighter table indicates the #4 docking module was installed in Y181.- Jeff Coutu 14 November 2019

(R1.68W-2) Recommend adding the Ship Type “(FTRS)” to the end of the header (that is the Ship Type for this unit in Master Ship Chart Module G3 on page 17).- Jeff Coutu 14 November 2019

(R1.75-2) In the paragraph below the fighter table, change “(R2.102)” to “(R2.104)”.- Jeff Coutu 14 November 2019

(R1.81-2) In the first fighter table, change “Y183-Y189” to “Y183+” since it is the last row.- Jeff Coutu 14 November 2019

(R1.89-2) The first fighter table indicates that A-10 and A-20 are available in Y180, however, in the paragraph above the fighter table indicates the #4 docking module was installed in Y181.- Jeff Coutu 14 November 2019

(R1.A31-2) the header has “(FTJ)” but that is also the Ship Type used for (R1.A28-2). I believe this this rule should use “(FTJB)” instead of “(FTJ)”.- Jeff Coutu 14 November 2019

(R1.201-2) In the last fighter table, for “Y195+” in the text “and or” remove “or”.- Jeff Coutu 14 November 2019


Minor Types (extra spaces, miss spelled words, missing comma, etc):

(R2.14) In the second paragraph, end of the first sentence, remove the space from “war ship”.- Jeff Coutu 14 November 2019

(R2.20A) In the second to last paragraph, at the end of the first sentence, remove the space before the period in “cruiser in Advanced Missions .”- Jeff Coutu 14 November 2019

(R2.28) In the second paragraph, in the first sentence, remove the space from “con verted”.- Jeff Coutu 14 November 2019

(R2.39A) In the paragraph before the carrier data chart, remove the space from “oper ating”.- Jeff Coutu 14 November 2019

(R2.45) In the “Seeking weapons:” paragraph, remove the space from “co ntrol”.- Jeff Coutu 14 November 2019

(R2.50) In the fourth paragraph, after “(R2.147)” add a comma.- Jeff Coutu 14 November 2019

(R2.60) In the first sentence in the text “that that” remove a “that”.- Jeff Coutu 14 November 2019

(R2.64) In the “Shock:” paragraph, in the first sentence, remove the space from “torpe does”.- Jeff Coutu 14 November 2019

(R2.68) The ship names in the “Known names” paragraph should be made italic.- Jeff Coutu 14 November 2019

(R2.70) In the first sentence, remove the space from “addi tional”.- Jeff Coutu 14 November 2019

(R2.105) In the first paragraph, remove the space from “(R1.31 )”.- Jeff Coutu 14 November 2019

(R2.105) For the carrier data chart, for the year “Y183+”, add a comma after “6xF-101C”.- Jeff Coutu 14 November 2019

(R2.110) At the end of the paragraph above the carrier data chart add a final period.- Jeff Coutu 14 November 2019

(R2.125) In the first sentence, change “technlogy” to “technology” by adding an “o”.- Jeff Coutu 14 November 2019

(R2.138) In the paragraph beginning with “The Vespucci was fitted”, it has a starting bracket in the text “[these are not included” but the ending bracket is missing.- Jeff Coutu 14 November 2019

CYGNAN NATIONAL GUARD MODULAR SHIPS OF Y136 [page 69]: In the second paragraph, change “obselecence” to “obsolescence”.- Jeff Coutu 14 November 2019

(R2.A22) In the second from last paragraph remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A23) In the second from last paragraph remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A24) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A24A) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A24B) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A25) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A25A) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A25B) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A25C) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A25D) In the third from last paragraph, remove the space from “#33 .”- Jeff Coutu 14 November 2019

(R2.A29) In the carrier data chart, for Y179-Y182 add a comma after the second “12xF-14A”.- Jeff Coutu 14 November 2019

(R2.A29) In the carrier data chart, for Y183-Y189 remove the comma in “6xA-20F,”.- Jeff Coutu 14 November 2019

(R2.A29) In the carrier data chart, for Y190-Y194 add a comma after the second “12xF-14C”- Jeff Coutu 14 November 2019

(R2.A29) In the carrier data chart, for Y190-Y194 remove the space in “6xF-101 C”.- Jeff Coutu 14 November 2019

(R2.A29) In the second from last paragraph, remove the space from “#38 .”- Jeff Coutu 14 November 2019

(R2.A31) In the third from last paragraph, remove the space from “#38 .”- Jeff Coutu 14 November 2019

(R2.A42) In the second from last paragraph, remove the space from “#48 .”- Jeff Coutu 14 November 2019

(R2.F15) In the “Standard:” paragraph (i.e., third paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.F18) In the paragraph beginning with “Items in the bay” (i.e., the paragraph before the “B-2p” paragraph), in the first sentence, remove the space from “dr opped”.- Jeff Coutu 14 November 2019

(R2.FA1) In the “Standard:” paragraph (i.e., second paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA2) In the “Standard:” paragraph (i.e., second paragraph), remove space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA3) In the “Standard:” paragraph (i.e., second paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA5) In the “Standard:” paragraph (i.e., second paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA6) In the first paragraph, change “100%of” to “100% of” by adding a space.- Jeff Coutu 14 November 2019

(R2.FA6) In the “Standard:” paragraph (i.e., second paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA7) In the “Standard:” paragraph (i.e., second paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA8) In the “Standard:” paragraph (i.e., second paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA9) In the “Standard:” paragraph (i.e., fourth paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA10) In the “Standard:” paragraph (i.e., second paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA11) In the “Standard:” paragraph (i.e., third paragraph), remove the space from “sys tems”.- Jeff Coutu 14 November 2019

(R2.FA13) In the header above this which has the text “FEDERATION FIGHTERS IN CAPTAIN’S LOG”, make “CAPTAIN’S LOG” italic.- Jeff Coutu 14 November 2019

(R2.201) In the fourth paragraph, third word, change “techology” to “technology” by adding the “n”.- Jeff Coutu 14 November 2019

(R2.203) In the second paragraph, third word, change “techology” to “technology” by adding an “n”.- Jeff Coutu 14 November 2019

(R2.203) In the second paragraph change “sufficently” to “sufficiently” by adding an “i”.- Jeff Coutu 14 November 2019

(R2.204) In the third paragraph, third word, change “techology” to “technology” by adding an “n”.- Jeff Coutu 14 November 2019

THE FIGHTING INSTRUCTIONS [page 113] In the text “2. The other ships [National Guard sh ips”, remove the space from “sh ips”.- Jeff Coutu 14 November 2019

(YR2.11) the first paragraph, last sentence, remove the space from “destroyer ,” (i.e., remove the space before the comma).- Jeff Coutu 14 November 2019

(YR2.25) In the “Landing:” paragraph, change “areodynamic” to “aerodynamic” by swapping the “r” and “e”.- Jeff Coutu 14 November 2019

(YR2.33) In the second paragraph, eighth word, remove the space from “K zintis”.- Jeff Coutu 14 November 2019

(YR2.45) In the “Tractors:” paragraph, change “(Range2)” to “(Range 2)” by adding a space.- Jeff Coutu 14 November 2019

(YR2.46) In the “Landing:” paragraph, change “areodynamic” to “aerodynamic” by swapping the “r” and “e”.- Jeff Coutu 14 November 2019

(YR2.46) In the “Tractors:” paragraph, change “(Range2)” to “(Range 2)” by adding a space.- Jeff Coutu 14 November 2019

(YR2.47) In the first paragraph, remove the space from “(YR2.32 )”.- Jeff Coutu 14 November 2019

(YR2.47) In the “Tractors:” paragraph, change “(Range2)” to “(Range 2)” by adding a space.- Jeff Coutu 14 November 2019

(YR2.48) In the “Tractors:” paragraph, change “(Range2)” to “(Range 2)” by adding a space.- Jeff Coutu 14 November 2019

(R1.R-2) In the “Y182 PF SHIELD REFITS” paragraph, change “conjectual” to “conjectural” by adding the “r”.- Jeff Coutu 14 November 2019

(R1.29-2) In the last fighter table, change “Y170-171” to “Y170-Y171” by adding the “Y”.- Jeff Coutu 14 November 2019

(R1.30-2) In the last fighter table, change “Y170-171” to “Y170-Y171” by adding the “Y”.- Jeff Coutu 14 November 2019

(R1.57-2) In the first paragraph, in the text “Weapon #4 is is”, remove the second “is”.- Jeff Coutu 14 November 2019

(R1.58-2) Remove the “=” at the start of the header.- Jeff Coutu 14 November 2019

(R1.74-2) At the end of the second to last paragraph, change the double period to a single period.- Jeff Coutu 14 November 2019

(R1.83-2) Add a period to the end of the last paragraph.- Jeff Coutu 14 November 2019

(R1.A26-2) In the first paragraph, in the text “Weapon #4 is is”, remove the second “is”.- Jeff Coutu 14 November 2019

(R1.A27-2) In the first paragraph, in the text “Weapon #4 is is”, remove the second “is”.- Jeff Coutu 14 November 2019

(YR1.12-2) At the end of the first paragraph remove the square.- Jeff Coutu 14 November 2019

(R1.201-2) Just after the header, change the rectangle to a space.- Jeff Coutu 14 November 2019

(R1.202-2) In the “Seeking weapons:” paragraph, in the text “See also (F3.213). See also (F3.213).”, remove the second “See also (F3.213).”- Jeff Coutu 14 November 2019

By Steve Cole (Stevecole) on Thursday, November 14, 2019 - 01:28 pm: Edit

The above is a REPORT (and an excellent one!). Only ADB can issue "errata" because "errata" is an official change and only Petrick can make those. No doubt much of the above is going to move from "report line item" to "errata" but it has not done so yet. I do not want others thinking that ADB empowered Jeff to issue official rules changes.

By Steve Petrick (Petrick) on Monday, October 05, 2020 - 07:05 pm: Edit

(R2.FA1) B-17: BOMBER: This was based on the Very Heavy Freight Shuttle (R1.F13) and not the VIP shuttle (R1.F15).

By Ken Kazinski (Kjkazinski) on Tuesday, April 20, 2021 - 10:20 pm: Edit

(R1.1-2) The R1 SSD (R1, pg 41), states the BPV is increased by 9 BPV for the Phaser-G refit. The text the first paragraph of (R1.1-2) states there is not change in the BPV. - Ken Kazinski, 20 Apr 2021.

By Ken Kazinski (Kjkazinski) on Thursday, December 23, 2021 - 08:25 am: Edit

(R2.108) Federation NCF - There was a note from R10 on 3/16/2011 - "(R2.108): Missing the “Ident” label on the shuttle track. We did the countersheet before I did the NCF hull outline and nobody thought of it. We did those counters MONTHS ago so we would not have any problems with the Origins deadline. R-section says first example in Y178, MSC says Y175. MSC should probably say Y178 with Y2 note. SVC decided to go with the first year the ships could have been built on the MSC for some reason that he has forgotten." The information that this ship could have been built in Y175 is missing from MSSB-R2.

By Ken Kazinski (Kjkazinski) on Friday, December 24, 2021 - 09:21 pm: Edit

(R2.31) Federation CMC - Posted on the web site on 2/13/2010 at 19:32:00, "Annex #03-02: CMC+ year in service should be Y170." but the MSSB-R2 states the plus refit was available beginning in Y165, does the MSSB supersede the post? - Ken Kazinski, 24 Dec 2021.

By Ken Kazinski (Kjkazinski) on Saturday, February 19, 2022 - 06:04 pm: Edit

(R2.F9) Federation A-20 - The colored graphic looks like there are six drones, but there should only be four. - Ken Kazinski, 29 Feb 2022.

By Stewart Frazier (Frazikar3) on Saturday, February 19, 2022 - 09:57 pm: Edit

Ken, I think that those are two type-IV-MW (or type-III-MW) being displayed...the other two are hidden under the wings ...

By Ken Kazinski (Kjkazinski) on Sunday, February 20, 2022 - 12:22 pm: Edit

Steward, I am not seeing it. The damage icon (top right in the rule) and Annex 4 both show 4xSpecial, which would be either 4 standard drones (Type-I) or 2 two-space drones. I am not seeing any Type-IV_MW (light drone rail) that would be listed in Annex 4 or the damage graphic. There are 6 red boxes which I assume are the ADDs.

By Jeff Anderson (Jga) on Sunday, February 20, 2022 - 12:49 pm: Edit

Can't special rails hold Type-IIIMW drones?

By Ken Kazinski (Kjkazinski) on Sunday, February 20, 2022 - 05:36 pm: Edit

The question is not about the types of drones/rails it is that the graphic shows 6 drones/rails and Annex 4 states there are only 4 drones/rails.

By Ken Kazinski (Kjkazinski) on Sunday, February 20, 2022 - 07:14 pm: Edit

(R2.F17) Federation B-1 - G3 Annex 4 (page 122) and Module J2 (page 63) have only 1 EW Pod, but text states "two built-in EW pods". Should not this be updated to "one built-in EW pod"? - Ken Kazinski, 20 Feb 2022.