Let's hope Andro War doesn't take five years.

By Steve Cole (Stevecole) on Thursday, December 18, 2025 - 02:57 am: Edit

Meetings can be good or bad, but from my perspective bad is just bad. People can have a sense of accountability if someone emails them the report deadline and holds them to it, which works fine without a meeting. More than once in recent months, waiting for you guys to hold a meeting delayed the project when you could have each sent me your reports on time. When I said the deadline is X and you reply that the first time you can meet to discuss things is after the deadline, the meeting is just an excuse for delay. Real time meetings are good when discussing a problem everyone knows about and has studied; they are a horrible forum for a totally new idea no one has time to absorb. If that new idea had been emailed when it came up, there would have been time for everyone to absorb and process it. (You really need to send me lists of ideas to be considered so I can tell you which way I think it should go, as you might waste a lot of time developing a solution that Petrick or I reject on sight.) Consolidated staff reports are good (I don't get three reports of the same typo) and BAD if the guy doing the consolidation becomes the gatekeeper who never allows ideas the gatekeeper doesn't like to reach Steve Cole's desk. (The consolidated report must go to every staffer and any staffer must have the right and duty to contact me directly if he thinks his idea got left on the conference room floor.) For every meeting I have been to since 1971 that produced progress I was at nine meetings that delayed progress.

There is no substitute for being physically in the same room, although that does put all of the targets for Jean's whanger in range.

By Steve Cole (Stevecole) on Thursday, December 18, 2025 - 03:14 am: Edit

Condensed version of Gary's report (what I expected from the staff)...

Y136, change the note about the CR to be an LR as that was the historical ship. (Why doesn't Gary write a thrilling fiction story of this event?)

Y187 Add 2 SDDs and 3 SFFs, gifts from the Klingons.

Y188 and later: delete and leave for Andro War.

By Steve Cole (Stevecole) on Thursday, December 18, 2025 - 03:18 am: Edit

Something else I have said before.

When I go into the hospital for some dang fool thing, that doesn't mean the staff stops working. Have progress to show me when I get back.

When any one staffer cannot work on the current project, everyone else needs to continue working. Too many times in the last five years, the staff hit pause for weeks while someone was unavailable. Lots of progress was lost. If meetings mean that the staff continues even when one staffer cannot participate, so much the better.

Jean and Petrick must not delay starting their reviews because a few minor staff report changes will drift in. Waiting for the reports to stop is a futile exercise, as the staff never stops fiddling with things.

By Steve Cole (Stevecole) on Thursday, December 18, 2025 - 03:23 am: Edit

The current F&E Schedule is as follows:

Petrick and Jean are reading the current rules. I will continue to process reports as they dribble in. The PDF copy will be released ASAP, probably next week.

During January, reports on the PDF edition will be dealt with. There will be NO trivial rewrites for style, conciseness, or "clarity".

A hard copy edition will happen during February.

Then we'll start on the updated boxed set revision, which means the staff needs to send me lists of changes in line item format, each item one paragraph, not multiple paragraphs. Each item with a rule number first. Each item with a justification statement. Each item with a staff member name and date. We will pick a date for the release of this product (July? October?) and that date will not be pushed by late reports. Late reports will be held for the 2030 revision.

The staff must STOP their practice of saying "replace these 37 words with these other 37 words" when the point is to add one comma or correct one typo. Report "put a comma after "economy" not give me a long quote where I have to waste time figuring out that you just changed one comma.

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 11:47 am: Edit

659 Line items

(659.11) CONDITIONS; "...if one of the following conditions are met..." should be, "...if one of the following conditions is met..." Rationale: Correct typo. L Bergen 17 DEC 2025

(659.111) Occupation; "Planet and/or province occupied by only one faction…" missing 'is', "A planet and/or province is occupied by only one faction…" Rationale: Add missing word. L Bergen 17 DEC 2025

(659.111) Occupation; "...a successful “disruption” raid as defined under (314.27) can dispute a province (659.2)." recommend insert punctuation as: "...a successful “disruption” raid, as defined under (314.27), can dispute a province (659.2). Rationale: Corrected punctuation. L Bergen 17 DEC 2025

(659.12) DIMINISHED CONTROL; "...for economic terms during the owner’s next economic phase." should replace terms with purposes as follows, "...for economic purposes during the owner’s next economic phase." Rationale: clarity. L Bergen 17 DEC 2025.

(659.13) ECONOMICS; "On the subsequent turn of continuous control, ..." should be, "On the subsequent player turn of continuous control, ..." Rational: Clarity on 'which' turn we are talking about. L Bergen 17 DEC 2025

(659.15) SUPPLY; "A planet or base newly controlled during a given player turn could not supply units…" replace 'could not' with "cannot" as follows: "A planet or base newly controlled during a given player turn cannot supply units…" Rationale: tense consistency. L Bergen 17 DEC 2025

(659.21) CONDITIONS; "successful raids via ‘disruption’ under (314.27) results in ..." should be, "...successful raids via “disruption” under (314.27) result in ..." Rationale: subject–verb agreement & quote consistency. L Bergen 17 DEC 2025

(659.22) ECONOMICS; "EPs may by generated..." should be, "EPs may be generated...". Rationale: Correct typo. L Bergen 17 DEC 2025

(659.221) Time Period; "middle years period" capitalization change as, "Middle Years period". Rationale: capitalization consistency. L Bergen 17 DEC 2025

(659.24) DISRUPTIVE RAIDS; "...player-turn" Eliminate the hyphen, "player turn". Rationale: hyphen consistency. L Bergen 17 DEC 2025

(659.25) NO POLICE RESPONSE; "...a police ships..." not plural remove 's', "...a police ship...". Rationale: context typo, not plural. L Bergen 17 DEC 2025

(659.324) Factional Infrastructure; 1st line, "...within the neutral faction territory but such units..." Add comma between 'territory' and 'but', "...within neutral faction territory, but such units ..." Rationale: Comma splice. L Bergen 17 DEC 2025

(659.325) Internment; 1st line, "...as if it were neutral zone hex...", add missing article, "...as if it were a neutral zone hex..." Rationale: missing article. L Bergen 17 DEC 2025

(659.327) Co-hex; 1st line, "Units from a fighting and neutral factions..." should be, "Units from a fighting faction and a neutral faction ..." Rationale: article agreement. L Bergen 17 DEC 2025

(659.345) Condition E – Mobility Support; 1st line, "A controlled province neutral planet or base can..." add missing commas, "A controlled province, neutral planet, or base can...". Rationale: missing punctuation. L Bergen 17 DEC 2025

(659.41) POSSESSION; last line, "...at the end of that player gains control.", add missing word, "...at the end of that player turn gains control." Rationale: Clarity, add missing word. L Bergen 17 DEC 2025

(659.411) Disputed Claims; "Open provinces that has opposing factions..." word 'has' should be 'have'; "Open provinces that have opposing factions..." Rationale: correct subject–verb agreement. L Bergen 17 DEC 2025

(659.411) Disputed Claims; "is considered to be disputed..." word 'is' should be 'are'; "are considered to be disputed..." Rationale: correct plural agreement. L Bergen 17 DEC 2025

(659.42) UNCLAIMED; "...units remains ..." should be, "...units remain ..." Rationale: correct subject–verb agreement. L Bergen 17 DEC 2025

By Steve Cole (Stevecole) on Thursday, December 18, 2025 - 11:51 am: Edit

Thanks, Lar, I know how hard you guys have worked to make this a great product.

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 02:37 pm: Edit

660 line items (note there is one full line replacement toward the end...it was IMO the best option. Sorry.)

(660.0) CIVIL WARS ASSET NEUTRALITY; Introductory Paragraph; "...control of the government and not wars to wantonly destroy national military might..." Add word 'intended' after 'wars', "...control of the government and were not wars intended to wantonly destroy national military might..." Rationale: Structure and flow. L Bergen 18 DEC 2025

(660.1) PLANET-BASED ASSEST NEUTRALITY; title block typo, should instead be, (660.1) PLANET-BASED ASSET NEUTRALITY, Rationale: Correct typo. L Bergen 18 DEC 2025

(660.11) TEMPORARY ASSET NEUTRALITY; "...colonies and colony bases," add comma after colonies, "...colonies, and colony bases," Rationale: Add comma. L Bergen 18 DEC 2025

(660.13) NO COMBAT SUPPLY; "...its effect on supply." should be, "...their effect on supply." Rationale: plural agreement refers to “forces,” which is plural. L Bergen 18 DEC 2025

(660.15) KEY PERSONNEL; "...temporary interned..." should be, "...temporarily interned...". Rationale: correct verb form. L Bergen 18 DEC 2025

(660.15) KEY PERSONNEL; "...the conclusion of combat phase." should be, "...the conclusion of the combat phase. Rationale: add missing article. L Bergen 18 DEC 2025

(660.212) Prior Damage; "Factional controlled space bases..." would better be, "Faction-controlled space bases...", Rationale: Less awkward; hyphenation. L Bergen 18 DEC 2025

(660.23) ATTRITION UNITS; "...remains under the control...", should be, "...remain under the control...". Rationale: subject–verb agreement, subject is plural: “fighters, PFs, and SWACs.” L Bergen 18 DEC 2025

(660.231) Recoverable Units; last line, "...combat phase;" should be "...combat phase." Rationale: punctuation, semicolon unnecessary; replace with period.  L Bergen 18 DEC 2025

(660.24) KEY PERSONNEL; "temporary interned", should be, "temporarily interned", Rationale: Correct verb form. L Bergen 18 DEC 2025

(660.25) DEPOTS; Add comma for readability between 'faction' and 'but', "...controlling faction, but will..." Rationale: Add comma, Readability.  L Bergen 18 DEC 2025

(660.27) TRANSPORTABLE BASES; add comma for clarity between 'units' and "operate", should read, "Mobile Storm Stations (MSS), including any assigned attrition units, operate, fight, receive damage,..." Rationale: Add comma, clarity and readability.  L Bergen 18 DEC 2025

(660.3) POST ATTACK ACTIONS; "...the control of a given planet or colony or fixed base therein is..." add commas for clarity, should read, "...the control of a given planet, colony, or fixed base therein is..." Rationale: Add commas punctuation and readability.  L Bergen 18 DEC 2025

(660.31) INCUMBENT FACTION SUCCESS; "...start of current raid or combat phase." Add 'the', "...start of the current raid or combat phase." Rationale: Add missing article. L Bergen 18 DEC 2025

(660.313) Supply Restored; This is a tremendously long sentence and should be broken into two fixing two items at once. End the first sentence (add a period) after "... within the hex are immediately restored.", the remaining portion should be replaced with, "These assets may then be used as combat, retrograde, and as field-repair supply check sources, and as a supply point by the incumbent faction and its allies, if permitted by rule." The replacement adjusts for the line break, cleans up a missing comma and makes a slight adjustment in wording retaining content. L Bergen 18 DEC 2025

(660.32) CONQUERING FACTION SUCCESS; eliminate duplicate word "then", "...then all remaining planetary-based..." Rationale: TYPO duplicate. L Bergen 18 DEC 2025

END OF (660.0)

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 03:14 pm: Edit

(701.115) GENERAL UNITS; Introductory Paragraph, replace "...are are listed..." with "...and are listed..." Rationale: Correct typo + missing conjunction. L Bergen 18 DEC 2025

(701.115) GENERAL UNITS; "...available on line:" should be "...available online:" Rationale: Correct typo. NOTE: I thought I reported this previously but was looking at the whole section again not just the one that 'caught my eye' before. L Bergen 18 DEC 2025

(701.115) GENERAL UNITS; ASC; "...mainline battle force the enemy is going to destroy it right away as a few damage points takes a lot of firepower out of your fleet.", add commas and replace 'takes' with 'would take' as follows, "...mainline battle force, the enemy is going to destroy it right away, as a few damage points would take a lot of firepower out of your fleet. Rationale: grammar + clarity. L Bergen 18 DEC 2025

(701.115) GENERAL UNITS; LAC; add a comma between "rear areas" and "but" Rationale: grammar. L Bergen 18 DEC 2025

(701.115) GENERAL UNITS; LAS; add a comma between "units" and "and is" Rationale: grammar. L Bergen 18 DEC 2025

(701.115) GENERAL UNITS; LAP; add "to function" between "gunboats and" and "(marginally)" so it reads, "to operate gunboats and to function (marginally) as a scout." Rationale: Adds descriptive clarity. L Bergen 18 DEC 2025

(702.115) FEDERATION DNT; remove unnecessary comma between "tougher" and "ship". Rationale: correct typo. L Bergen 18 DEC 2025

(702.115) FEDERATION FFP:; add hyphen to "G factors" should be "G-factors on troop ships." Rationale: Hyphenation. L Bergen 18 DEC 2025

(702.115) FEDERATION FFP:; "The FFP can carry one pod; which can be double-weight; any pod..." Correct semicolon misuse, replace first semicolon with comma, "The FFP can carry one pod, which can be double-weight; any pod..." Rationale: correct typo. L Bergen 18 DEC 2025

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 04:09 pm: Edit

(704.IF) line items

(704.IF) CROWN FACTION is incorrect as a title block, correct to "(704.IF) IMPERIAL FACTION" Rationale: Avoids confusion with War of Returns OOB and also aligned with bottom corner page title blocks. L Bergen 18 DEC 2025

(704.IF0) Deployment Lines; Deploy in in hex 4318: Remove duplicate "in", Rationale: TYPO duplicate. L. Bergen 18 DEC 2025

(704.IF1) added fake number here for SVC alignment: (637.422) Sympathetic Forces (Patrol Detachment):; "...and serve as a firewall to the Seltorian war with...", replace the word to with "against" so reads, "...and serve as a firewall against the Seltorian war with..." Rationale: Adds descriptive clarity. L Bergen 18 DEC 2025

(704.IF131) Unit Production; "Counts about both the...", should be (704.IF131) Unit Production, Heavy War Destroyers; "Counts against both the..." Rationale: TYPO. L. Bergen 18 DEC 2025 CORRECTED BY REQUEST

(704.IF131) Unit Production; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read (704.IF131) Unit Production, Heavy War Destoryers; "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025 CORRECTED BY REQUEST ROPEL

(704.IF131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025

(704.IF132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025

(704.IF24) MANEUVER; add spacing of one line above. Rationale: Formatting. L Bergen 18 DEC 2025

(704.IF3) ECONOMICSC3) ECONOMICS typo (copy/paste) should be, "(704.IF3) ECONOMICS" also note a Format issue, title blocks need to be bold. L. Bergen 18 DEC 2025

(704.IF31) BASE ECONOMICS SOURCES: Format issue title blocks need to be bold. L. Bergen 18 DEC 2025

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 05:11 pm: Edit

DELETED PER AUTHOR REQUEST

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 05:18 pm: Edit

(704.RR) ROM REPUBLIC FACTION line items

(704.RR11) CONSTRUCTION SCHEDULE; 1st line, "Republican Forces Schedule:" should be bold. Rationale: Formatting. L Bergen 18 DEC 2025

(704.RR11) CONSTRUCTION SCHEDULE; 2nd Line, add comma after "war" and spell out '4', to read "At the start of the civil war, the Republican faction controlled four minor shipyards...". Rationale: comma + style, spelling out small numbers is consistent with most SFU rules text. L. Bergen 18 DEC 2025

(704.RR131) Unit Production; "Leaders: Includes CW and DW. One per year..." should say "Leaders: Includes CW and DW. May produce one per year..." Rationale: Parallel structure. L. Bergen 18 DEC 2025

(704.RR131) Unit Production; "Scouts: One substitution per year..." should say "Scouts: May conduct one substitution per year..." Rationale: Parallel structure, aligns with Imperial Section. L. Bergen 18 DEC 2025

(704.RR131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025

(704.RR132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025

(704.RR132) Personnel, Diplomats:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025

(704.RR132) Personnel, Independent Ground Combat Elements:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025

(704.RR22) LOGISTICS, Survey Operations:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025

(704.RR22) LOGISTICS, Command Points:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025

(704.RR25) AUGMENTATION; Format issue title blocks need to be bold. L. Bergen 18 DEC 2025

(704.RR25) AUGMENTATION, Auxiliaries:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025

(704.RR25) AUGMENTATION, Pod Deployment:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 05:28 pm: Edit

(705.P) CROWN FACTION line items

(705.P) "War of Return" should be ALL CAPS as well as bold. Rationale: Formatting matching Rom Civ War Scenario. L Bergen 18 DEC 2025

(705.P131) Unit Production, Heavy War Destroyers; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025

(705.P131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025

(705.P132) Personnel; Format issue title blocks need to be bold. L. Bergen 18 DEC 2025

(705.P132) Personnel, Admirals:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025

(705.P132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 05:31 pm: Edit

(705.C) COUNT FACTION line items

(705.C) "War of Return" should be ALL CAPS as well as bold. Rationale: Formatting matching Rom Civ War Scenario. L Bergen 18 DEC 2025

(705.C131) Unit Production, Heavy War Destroyers; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025

(705.C131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025

(705.C132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025

By Lawrence Bergen (Lar) on Thursday, December 18, 2025 - 05:37 pm: Edit

(712.0) WYN STAR CLUSTER Line items

(712.131) Unit Production, Heavy War Destroyers; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025

(712.133) Infrastructure, Bases:; "Bases:" should be bold. Rationale: Formatting L Bergen 18 DEC 2025.

By Lawrence Bergen (Lar) on Friday, December 19, 2025 - 10:11 am: Edit

Staff had its end of 2025 meeting and confirmed we had sent to ADB the maps and charts as requested. We also confirmed the two of the questionable line items in the many posted this week/yesterday were on point.

No more big reviews to be done. Only “one off” finds from here as SVC mentioned before. As customers we are ready to see this thing hit the digital market and hunt down the things our old eyes have missed and answer questions we haven't thought of yet.

Thank you to ADB for allowing us to get this right. For me personally it has been fun. And thank you to everyone who has provided research support and questions to help drive this product forward.

Hope you all have a safe and enjoyable holiday season.

By Steve Cole (Stevecole) on Monday, December 22, 2025 - 04:09 pm: Edit

(659.11) CONDITIONS; "...if one of the following conditions are met..." should be, "...if one of the following conditions is met..." Rationale: Correct typo. L Bergen 17 DEC 2025 DONE
=====
(659.111) Occupation; "Planet and/or province occupied by only one faction…" missing 'is', "A planet and/or province is occupied by only one faction…" Rationale: Add missing word. L Bergen 17 DEC 2025 DONE
=====
(659.111) Occupation; "...a successful "disruption" raid as defined under (314.27) can dispute a province (659.2)." recommend insert punctuation as: "...a successful "disruption" raid, as defined under (314.27), can dispute a province (659.2). Rationale: Corrected punctuation. L Bergen 17 DEC 2025 DONE
=====
(659.12) DIMINISHED CONTROL; "...for economic terms during the owner’s next economic phase." should replace terms with purposes as follows, "...for economic purposes during the owner’s next economic phase." Rationale: clarity. L Bergen 17 DEC 2025. This has been done.
=====
(659.13) ECONOMICS; "On the subsequent turn of continuous control, ..." should be, "On the subsequent player turn of continuous control, ..." Rational: Clarity on 'which' turn we are talking about. L Bergen 17 DEC 2025 this has been done.
=====
(659.15) SUPPLY; "A planet or base newly controlled during a given player turn could not supply units…" replace 'could not' with "cannot" as follows: "A planet or base newly controlled during a given player turn cannot supply units…" Rationale: tense consistency. L Bergen 17 DEC 2025 this has been done.
=====
(659.21) CONDITIONS; "successful raids via ‘disruption’ under (314.27) results in ..." should be, "...successful raids via "disruption" under (314.27) result in ..." Rationale: subject–verb agreement & quote consistency. L Bergen 17 DEC 2025 I cannot stop Chuck from using single quotes. Sigh.
=====
(659.22) ECONOMICS; "EPs may by generated..." should be, "EPs may be generated...". Rationale: Correct typo. L Bergen 17 DEC 2025 this has been done.
=====
(659.221) Time Period; "middle years period" capitalization change as, "Middle Years period". Rationale: capitalization consistency. L Bergen 17 DEC 2025 I’m not the guy who did it lower case.
=====
(659.24) DISRUPTIVE RAIDS; "...player-turn" Eliminate the hyphen, "player turn". Rationale: hyphen consistency. L Bergen 17 DEC 2025 this mistake, not done by me, has been corrected.
=====
(659.25) NO POLICE RESPONSE; "...a police ships..." not plural remove 's', "...a police ship...". Rationale: context typo, not plural. L Bergen 17 DEC 2025 this has been done. Ibid..
=====
(659.324) Factional Infrastructure; 1st line, "...within the neutral faction territory but such units..." Add comma between 'territory' and 'but', "...within neutral faction territory, but such units ..." Rationale: Comma splice. L Bergen 17 DEC 2025 I agree
=====
(659.325) Internment; 1st line, "...as if it were neutral zone hex...", add missing article, "...as if it were a neutral zone hex..." Rationale: missing article. L Bergen 17 DEC 2025 done
=====
(659.327) Co-hex; 1st line, "Units from a fighting and neutral factions..." should be, "Units from a fighting faction and a neutral faction ..." Rationale: article agreement. L Bergen 17 DEC 2025 done
=====
(659.345) Condition E – Mobility Support; 1st line, "A controlled province neutral planet or base can..." add missing commas, "A controlled province, neutral planet, or base can...". Rationale: missing punctuation. L Bergen 17 DEC 2025 added
=====
(659.41) POSSESSION; last line, "...at the end of that player gains control.", add missing word, "...at the end of that player turn gains control." Rationale: Clarity, add missing word. L Bergen 17 DEC 2025 concur
=====
(659.411) Disputed Claims; "Open provinces that has opposing factions..." word 'has' should be 'have'; "Open provinces that have opposing factions..." Rationale: correct subject–verb agreement. L Bergen 17 DEC 2025 concur
=====
(659.411) Disputed Claims; "is considered to be disputed..." word 'is' should be 'are'; "are considered to be disputed..." Rationale: correct plural agreement. L Bergen 17 DEC 2025 done
=====
(659.42) UNCLAIMED; "...units remains ..." should be, "...units remain ..." Rationale: correct subject–verb agreement. L Bergen 17 DEC 2025 this was done.
=====


(660.0) CIVIL WARS ASSET NEUTRALITY; Introductory Paragraph; "...control of the government and not wars to wantonly destroy national military might..." Add word 'intended' after 'wars', "...control of the government and were not wars intended to wantonly destroy national military might..." Rationale: Structure and flow. L Bergen 18 DEC 2025 concur
=====
(660.1) PLANET-BASED ASSEST NEUTRALITY; title block typo, should instead be, (660.1) PLANET-BASED ASSET NEUTRALITY, Rationale: Correct typo. L Bergen 18 DEC 2025 concur, done
=====
(660.11) TEMPORARY ASSET NEUTRALITY; "...colonies and colony bases," add comma after colonies, "...colonies, and colony bases," Rationale: Add comma. L Bergen 18 DEC 2025 concur, done
=====
(660.13) NO COMBAT SUPPLY; "...its effect on supply." should be, "...their effect on supply." Rationale: plural agreement refers to "forces," which is plural. L Bergen 18 DEC 2025 concur, done
=====
(660.15) KEY PERSONNEL; "...temporary interned..." should be, "...temporarily interned...". Rationale: correct verb form. L Bergen 18 DEC 2025 concur, done
=====
(660.15) KEY PERSONNEL; "...the conclusion of combat phase." should be, "...the conclusion of the combat phase. Rationale: add missing article. L Bergen 18 DEC 2025 concur, done
=====
(660.212) Prior Damage; "Factional controlled space bases..." would better be, "Faction-controlled space bases...", Rationale: Less awkward; hyphenation. L Bergen 18 DEC 2025 concur, done
=====
(660.23) ATTRITION UNITS; "...remains under the control...", should be, "...remain under the control...". Rationale: subject–verb agreement, subject is plural: "fighters, PFs, and SWACs." L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.231) Recoverable Units; last line, "...combat phase;" should be "...combat phase." Rationale: punctuation, semicolon unnecessary; replace with period. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.24) KEY PERSONNEL; "temporary interned", should be, "temporarily interned", Rationale: Correct verb form. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.25) DEPOTS; Add comma for readability between 'faction' and 'but', "...controlling faction, but will..." Rationale: Add comma, Readability. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.27) TRANSPORTABLE BASES; add comma for clarity between 'units' and "operate", should read, "Mobile Storm Stations (MSS), including any assigned attrition units, operate, fight, receive damage,..." Rationale: Add comma, clarity and readability. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.3) POST ATTACK ACTIONS; "...the control of a given planet or colony or fixed base therein is..." add commas for clarity, should read, "...the control of a given planet, colony, or fixed base therein is..." Rationale: Add commas punctuation and readability. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.31) INCUMBENT FACTION SUCCESS; "...start of current raid or combat phase." Add 'the', "...start of the current raid or combat phase." Rationale: Add missing article. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.313) Supply Restored; This is a tremendously long sentence and should be broken into two fixing two items at once. End the first sentence (add a period) after "... within the hex are immediately restored.", the remaining portion should be replaced with, "These assets may then be used as combat, retrograde, and as field-repair supply check sources, and as a supply point by the incumbent faction and its allies, if permitted by rule." The replacement adjusts for the line break, cleans up a missing comma and makes a slight adjustment in wording retaining content. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(660.32) CONQUERING FACTION SUCCESS; eliminate duplicate word "then", "...then all remaining planetary-based..." Rationale: TYPO duplicate. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(701.115) GENERAL UNITS; Introductory Paragraph, replace "...are are listed..." with "...and are listed..." Rationale: Correct typo + missing conjunction. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(701.115) GENERAL UNITS; "...available on line:" should be "...available online:" Rationale: Correct typo. NOTE: I thought I reported this previously but was looking at the whole section again not just the one that 'caught my eye' before. L Bergen 18 DEC 2025 CONCUR, DONE, JEAN CALLS THIS "ROCKS, SAND, DUST" IN THAT BIGGER MISTAKES HIDE SMALLER ONES.
=====
(701.115) GENERAL UNITS; ASC; "...mainline battle force the enemy is going to destroy it right away as a few damage points takes a lot of firepower out of your fleet.", add commas and replace 'takes' with 'would take' as follows, "...mainline battle force, the enemy is going to destroy it right away, as a few damage points would take a lot of firepower out of your fleet. Rationale: grammar + clarity. L Bergen 18 DEC 2025 done.
=====
(701.115) GENERAL UNITS; LAC; add a comma between "rear areas" and "but" Rationale: grammar. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(701.115) GENERAL UNITS; LAS; add a comma between "units" and "and is" Rationale: grammar. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(701.115) GENERAL UNITS; LAP; add "to function" between "gunboats and" and "(marginally)" so it reads, "to operate gunboats and to function (marginally) as a scout." Rationale: Adds descriptive clarity. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(702.115) FEDERATION DNT; remove unnecessary comma between "tougher" and "ship". Rationale: correct typo. L Bergen 18 DEC 2025 I DO NOT CONCUR, IT RIGHTS CORRECT AS IS TO ME, LEAVE IT TO JEAN.
=====
(702.115) FEDERATION FFP:; add hyphen to "G factors" should be "G-factors on troop ships." Rationale: Hyphenation. L Bergen 18 DEC 2025
=====
(702.115) FEDERATION FFP:; "The FFP can carry one pod; which can be double-weight; any pod..." Correct semicolon misuse, replace first semicolon with comma, "The FFP can carry one pod, which can be double-weight; any pod..." Rationale: correct typo. L Bergen 18 DEC 2025 ALSO CHANGED SECOND ONE TO PERIOD.
=====
(704.IF) CROWN FACTION is incorrect as a title block, correct to "(704.IF) IMPERIAL FACTION" Rationale: Avoids confusion with War of Returns OOB and also aligned with bottom corner page title blocks. L Bergen 18 DEC 2025 THIS WAS DONE EARLIER, IT HAPPENED WHEN I CLONED THE TITLE FORMAT.
=====
(704.IF0) Deployment Lines; Deploy in in hex 4318: Remove duplicate "in", Rationale: TYPO duplicate. L. Bergen 18 DEC 2025 DONE
=====


(704.IF1) added fake number here for SVC alignment: (637.422) Sympathetic Forces (Patrol Detachment):; "...and serve as a firewall to the Seltorian war with...", replace the word to with "against" so reads, "...and serve as a firewall against the Seltorian war with..." Rationale: Adds descriptive clarity. L Bergen 18 DEC 2025 CONCUR, NOTE CLEVER USE OF FAKE RULE NUMBER
=====
(704.IF131) Unit Production; "Counts about both the...", should be (704.IF131) Unit Production, Heavy War Destroyers; "Counts against both the..." Rationale: TYPO. L. Bergen 18 DEC 2025 CORRECTED, HARD TO FIND, NEEDED TO SPECIFY THE SUB-PARAGRAPH
=====
(704.IF131) Unit Production; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read (704.IF131) Unit Production, Heavy War Destoryers; "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025 CORRECTED BY REQUEST ROPEL ++ I CHANGED IT ANOTHER WAY, AVOID USING ALL=CAPS AS IT MAKES ME THINK YOU ARE QUOTING ME.
=====
(704.IF131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025 CONCUR, DONE
=====
(704.IF132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025 I THINK IT WAS AN EMPHATIC "ONE AND BY GOSH ONLY ONE"
=====
(704.IF24) MANEUVER; add spacing of one line above. Rationale: Formatting. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(704.IF3) ECONOMICSC3) ECONOMICS typo (copy/paste) should be, "(704.IF3) ECONOMICS" also note a Format issue, title blocks need to be bold. L. Bergen 18 DEC 2025 HAD TO FIND THIS, IT WAS IN THE REPUBLICAN FACTION
=====
(704.IF31) BASE ECONOMICS SOURCES: Format issue title blocks need to be bold. L. Bergen 18 DEC 2025 I THINK I FIXED IT EARLIER WHICH IS WHY I CAN’T FIND IT NOW.
=====
(704.RR) ROM REPUBLIC FACTION line items
=====
(704.RR11) CONSTRUCTION SCHEDULE; 1st line, "Republican Forces Schedule:" should be bold. Rationale: Formatting. L Bergen 18 DEC 2025 CONCUR, DONE
=====
(704.RR11) CONSTRUCTION SCHEDULE; 2nd Line, add comma after "war" and spell out '4', to read "At the start of the civil war, the Republican faction controlled four minor shipyards...". Rationale: comma + style, spelling out small numbers is consistent with most SFU rules text. L. Bergen 18 DEC 2025 CONCUR, DONE
=====
(704.RR131) Unit Production; "Leaders: Includes CW and DW. One per year..." should say "Leaders: Includes CW and DW. May produce one per year..." Rationale: Parallel structure. L. Bergen 18 DEC 2025 CONCUR, DONE
=====
(704.RR131) Unit Production; "Scouts: One substitution per year..." should say "Scouts: May conduct one substitution per year..." Rationale: Parallel structure, aligns with Imperial Section. L. Bergen 18 DEC 2025 CONCUR, DONE
=====
(704.RR131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025 done
=====
(704.RR132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025 IBID
=====
(704.RR132) Personnel, Diplomats:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025 CONCUR, DONE
=====
(704.RR132) Personnel, Independent Ground Combat Elements:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025 SUB BUT NOT SUB-SUB
=====
(704.RR22) LOGISTICS, Survey Operations:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025 DONE
=====
(704.RR22) LOGISTICS, Command Points:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025 DONE
=====
(704.RR25) AUGMENTATION; Format issue title blocks need to be bold. L. Bergen 18 DEC 2025 DONE
=====
(704.RR25) AUGMENTATION, Auxiliaries:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025 DONE
=====
(704.RR25) AUGMENTATION, Pod Deployment:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025 DONE
=====
(705.P) CROWN FACTION line items
=====
(705.P) "War of Return" should be ALL CAPS as well as bold. Rationale: Formatting matching Rom Civ War Scenario. L Bergen 18 DEC 2025 OK
=====
(705.P131) Unit Production, Heavy War Destroyers; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025 the WOULD BE ENOUGH
=====
(705.P131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025 DONE
=====
(705.P132) Personnel; Format issue title blocks need to be bold. L. Bergen 18 DEC 2025 DONE
=====
(705.P132) Personnel, Admirals:; Format issue sub-title blocks need to be bold. L. Bergen 18 DEC 2025 DONE
=====
(705.P132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025 IBID
=====
(705.C) COUNT FACTION line items
=====
(705.C) "War of Return" should be ALL CAPS as well as bold. Rationale: Formatting matching Rom Civ War Scenario. L Bergen 18 DEC 2025 HEY, I USED WHAT I GOT.
=====
(705.C131) Unit Production, Heavy War Destroyers; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025 DID IT MY WAY
=====
(705.C131) Unit Production; "Special Attack Forces: May produce one SAF (520.1) per year one turn." should say "Special Attack Forces: May produce one SAF (520.1) per year in either turn." Rationale: Corrected to match the rule referenced in (520.1). L. Bergen 18 DEC 2025 DONE
=====
(705.C132) Personnel; "Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81)." should drop the word 'only' and say "Extra Troops: May purchase one I-GCE per combat round for one EP (521.81)." Rationale: Unnecessary word, aligns with wording of troop transport drop entry. L. Bergen 18 DEC 2025
=====
(712.0) WYN STAR CLUSTER Line items
=====
(712.131) Unit Production, Heavy War Destroyers; recommend insertion of the word 'otherwise" between "replaces" and "allowed" to read "Can produce one HDW-FOP that replaces otherwise allowed FCR Production". Rationale: Minor clarity improvement. L. Bergen 18 DEC 2025 did my way
=====
(712.133) Infrastructure, Bases:; "Bases:" should be bold. Rationale: Formatting L Bergen 18 DEC 2025. It is, might have been fixed earlier.

END OF REPORTS
WELL DONE, STAFF.

By Steve Cole (Stevecole) on Monday, December 22, 2025 - 04:50 pm: Edit

STAFF ATTENTION: I have sent a note to Chuck with corrections needed to the charts. I need Chuck to fix them before we can release the product. I haven't seen printed maps yet.

ALL ABOVE REPORTS DONE TO THIS POINT

By Steve Cole (Stevecole) on Monday, December 22, 2025 - 05:28 pm: Edit

STAFF ATTENTION
I need answers to these items before it can go to Jean for proofreading.
======
(332.431) SSC Qualification: The qualifying limits on offensive and defensive points to use SSC (310.11) are based upon pre-adjusted combat potential. Nevertheless, fighter factors are ignored by the barrier-disabled player to qualify for SSC.
PETRICK ASKS what about PFs? You need to specifically include or exclude them. Also, do the fighters (and perhaps PFs) include those on ships or indepedent ones or both?
=====
(554.411) Deployment:
Spring Y165 - Initial fighter deployment;
Spring Y178 - Heavy fighters;
Spring Y179 - Mega fighters.
PETRICK ASSUMES YOU HAVE VERIFIED THESE DATES AS HE HAS NO DATA TO CHECK THEM AGAINST.
=======
(556.224) Refugees: If the Cluster is conquered and the remaining forces retreat out of the Cluster hex, those forces become homeless ships (556.8).
We cannot find a 556.8 in the text. what is the correct number.
======
(556.363) Moving On: Unless forced by (556.344) to retreat, the invading force may choose to continue to fight at the current prefecture or move to another prefecture.
We cannot find a rule number 556.344. what is the correct rule number?
======
(634.42) ISC INTRUSION: There are historical references to the ISC attempting to force their way into the Cluster in Y1??. This could be done using an ISC fleet consisting of: @@@
The staff never sent me this data. I think someone mentioned a cordon force in a different context. Let me know what to put here.
=====
I am out of time today but will have more questions from SPP tomnorrow.

By Gary Carney (Nerroth) on Tuesday, December 23, 2025 - 11:33 am: Edit

While incomplete, this might help with (634.42) somewhat:

-----

(634.42) ISC INTRUSION: In April Y187, the forces of the Inter-Stellar Concordium's Cordon Echo made an incursion into the WYN Cluster (625.E21).

This was done for two reasons:

Firstly - in response to an increase in Orion pirate activity in the region, as a result of the return of the Orion Cluster Crimelord to the "post-Usurper" WYN governing council in January Y187.

And secondly - the ISC had initially deemed the outbreak of civil war within the Kzinti Hegemony as an internal Kzinti matter. Eventually, they determined that the Usurper, by leading his forces out of the WYN Cluster into Kzinti space, had, through this act of aggression, triggered this latest round of violence in the area.

However, unlike the task forces assembled to intervene in the Romulan Civil War at Tibernia IV along Cordon Zulu (625.Z), or those directed to target the Seltorian Hive Ship Burning Torch of Vengeance along Cordon Charlie (625.C22), the forces available at Cordon Echo were successfully driven back by what remained of the WYN Navy.

Despite this failure, the intrusion led to certain unexpected consequences. Once news of this intrusion spread across Kzinti space, many of those WYN-Orion ships that had joined the Usurper to fight in the War of Return chose to abandon his cause and to head home: this was one of the motivators that historically led to the Usurper accepting the Crown Prince's offer of a space control ship "duel' to settle the War once and for all. As for these WYN-Orion ships: they would return home mere days before the one spectacular attempt by the Andromedan Invaders to seize control of the WYN Cluster.

In order to carry out this intrusion, the ISC player is permitted to create a task force from those ships assigned to Cordon Echo as listed in (625.E411) that have not been committed to the creation of the Pacification stations along this cordon - to include the PS to be placed in hex 0905, which is needed in order to act as Cordon Foxtrot's ROMP insertion node (625.F414) - minus any losses which might have been accrued through contact with local Klingon, Kzinti, and/or Lyran forces in the course of doing so. Historically, this task force was sent into the Cluster in Spring Y187.

As for the "spectacular" Andromedan attempt on the Cluster... that must wait until the future Andromedan War module is to be formally published.

-----

A few thoughts:

*Unlike the case with the ISC forces at Tibernia IV, or those which attacked the Hive Ship, no full "Echelon" of first-generation X-ships is assigned to Cordon Echo, as per ISC War. So there isn't quite the same operational strength available to the ISC forces in this region of the Alpha Octant, compared to what Cordons Zulu and Charlie had for their respective interventions.

Even so, the intrusion "worked" in the long run, as it did set off a chain of events that brought the War of Return to an end. So perhaps the ISC politicians chalked this one up as a de facto win for their peacekeeping mission?

Although, an interesting "what-if" might be to divert the Echelon of Justice from the Tibernia IV task force to this WYN incursion, and to see if that would be enough to turn the Cluster into an "ISC-WYN Protectorate"...

*I wasn't sure whether or not to formally place it in the suggestion above, but it might be worth specifying if the WYNs have those five WYN-Seltorian ships prior to April Y187 or not.

It would be an interesting irony to set things up so that, after having extinguished the Torch in Y186, the ISC find themselves shooting at five more "Seltorian" hulls a year later - albeit ones serving in the defence of the WYN Cluster.

As a further aside, the Klingons provide these five hulls after having launched "aggressive" probes of the Cluster in the last months of Y186, as per the R-section data in Module C3. A further instance of how the Empire's relationship with the WYNs can pivot like a D7 battlecruiser as and when required.

*And one final note, for now at least: historically speaking, victory in the War of Return proved to be a poisoned chalice. As per the Kzinti historical file in Away Team Log, the resulting "Patriarch of Triumph" only has a few years to sit on the throne before he is killed in battle with the Andromedans in Y190.

So, one might be careful what one wishes for...

By Steve Cole (Stevecole) on Tuesday, December 23, 2025 - 02:14 pm: Edit

Gary, is the above something you created/proposed or something you found in a published source?=

By Lawrence Bergen (Lar) on Tuesday, December 23, 2025 - 02:33 pm: Edit

DONE

For that first question:

(332.431) SSC Qualification: The qualifying limits on offensive and defensive points to use SSC (310.11) are based upon pre-adjusted combat potential. Nevertheless, fighter factors are ignored by the barrier-disabled player to qualify for SSC.
PETRICK ASKS what about PFs? You need to specifically include or exclude them. Also, do the fighters (and perhaps PFs) include those on ships or indepedent ones or both?

Under barrier disabled combat PFs may be used where fighters may not be. See reference rule:

(332.315) PF Tenders: They may launch, operate, and recover PFs (including CPFs) but each flotilla of 1-6 PFs is treated as an independent unit (using a command slot). PFTs cannot operate their scout systems. PFs carried through the zone by a host unit are themselves treated as barrier-disabled. If a barrier-disabled PFT is destroyed, then any of its undeployed PFs are also destroyed with no resulting minus points.

Suggest adding a reference back to this for PFs. L Bergen 23 DEC 2025

By Lawrence Bergen (Lar) on Tuesday, December 23, 2025 - 03:04 pm: Edit

DONE


(556.224) Refugees: If the Cluster is conquered and the remaining forces retreat out of the Cluster hex, those forces become homeless ships (556.8). 
We cannot find a 556.8 in the text. what is the correct number.

Suggest (554.314). Please find that there is a reference to homeless ships being adopted by friendly forces at (554.314). It references the homeless ship rule from basic set (410.5). L Bergen 23 DEC 2025

Related.

(634.3) SCENARIO VICTORY CONDITIONS; replace last rule reference of (554.8) with (554.314). Rationale: Incorrect reference to homeless ships needed correcting. L Bergen 23 DEC 2025

By Lawrence Bergen (Lar) on Tuesday, December 23, 2025 - 03:12 pm: Edit

DONE
(556.363) Moving On: Unless forced by (556.344) to retreat, the invading force may choose to continue to fight at the current prefecture or move to another prefecture.
We cannot find a rule number 556.344. what is the correct rule number?

The correct rule reference is: (556.334). L Bergen 23 DEC 2025

By Ryan Opel (Ryan) on Tuesday, December 23, 2025 - 03:53 pm: Edit

DONE
For the ISC Incursion I'd use either the 2nd or 6th Fleet elements from 626.E411.

Sorry can't cut and paste what they are from my phone.