I think there are some @@@ on those 38 pages. Not sure.

By Tom Lusco (Tlusco) on Saturday, December 06, 2025 - 10:44 am: Edit

ANSWERED On the 549 revisions:

549.1212 refers to OOB production notes for the active war production of aux pod slots. Is that noted somewhere, or is it intended to be updated? The current OOBs don't mention aux pod slots as you note, so I'm wondering if its in another file I haven't managed to find.

521.23 and the OOBs mention that each empire can produce one large and two small troop ships per turn in addition to other auxiliary construction. Is this still true, or is 549 intended to supplant that rule too?

The revised rule would allow the large races to produce one large or two small aux/turn, which feels healthy. Small races only one small aux/year though, which feels stingy. Those are peacetime rates though, so really can't judge without seeing the wartime production update.

By Steve Cole (Stevecole) on Saturday, December 06, 2025 - 10:52 am: Edit

THE ANSWER They are in the updates later in the book.

549 codifies large/small as using slots to buy whatever you want.

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

DONE CW book 1-38 Line Items:

(634.112) BATTLE ROUND #2: should have entire title block bolded as Battle round 0&1 are. Rationale: consistency L.Bergen 6 DEC 2025

(634.113) BATTLE ROUND #3: should have entire title block bolded as Battle round 0&1 are. Rationale: consistency L.Bergen 6 DEC 2025

By Lawrence Bergen (Lar) on Saturday, December 06, 2025 - 03:11 pm: Edit

NOTED, BTW I queried the (@@@) at this moment there are four; one is in the table of contents, three are in the whirlpool scenario.

Three of them are part of documents that are either in progress or have yet to be written such as that new “by year: what to they have” WYN order of battle.

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

PROPOSAL ROBOT CONTROLLED - COMBAT PROCEDURES _ WORKING COPY 03 DEC
CHUCK EDITS ARE INCLUDED


(331.0) ROBOT-CONTROLLED UNITS IN COMBAT

Robot-controlled units (RCUs) are used to send certain slow units through the WYN barrier. Even though RCUs cannot intentionally move into a hex with opposing forces they might sometimes find themselves in combat. As they have no crew on board, they do not arrive in any condition to fight. When this happens RCUs in the combat hex affect the normal combat procedure due to their many limitations and restrictions.
(331.1) ROBOT-CONTROLLED UNIT COMBAT

RCUs are subject to the following:
(331.11) ALWAYS SLOW: Units that are declared as RCUs or have used robot-controlled movement during the turn are considered slow-units for combat.

(331.12) ABANDONMENT: Robot controlled units are considered ‘abandoned’ when there are no other non-RCUs in the hex. Even if they began combat alone in a hex they would still be considered abandoned. They can become abandoned when their fleet withdraws before combat or retreats and leaves the unit behind. Abandonment can also occur if the last remaining friendly non-robot-controlled unit is destroyed in combat leaving them alone in the battle hex.

(331.13) NO WITHDRAWAL: RCUs cannot withdraw before combat and would not count in the calculation for either (302.131) Option 1 or (302.132) Option 2 of an opposed withdrawal. Robot controlled units would be considered abandoned if their fleet is allowed to withdraw from combat unopposed and they choose to leave with all non-RCUs under (302.12). The robot-controlled units would remain in the hex, and the opposing force would have an opportunity to engage them under (331.72).

(331.14) NO CLOAK CAPABILITY: RCUs cannot use cloaks or any of the cloaking device benefits nor can it deploy a cloak decoy even if the unit is so equipped. Robot controlled units may not attempt cloaked evasion (306.1).

(331.15) SMALL SCALE COMBAT: Forces containing RCUs can qualify for small scale combat under (310.11).
(331.151) Resolving Casualties: Casualties may be assigned to RCUs. As a modification to (310.31), each unit taken as a casualty is destroyed outright and counts as one casualty, regardless of whether it began the battle crippled or at full status.
(331.152) Retreat: Forces with RCUs may assign “retreat” as a casualty, but any RCUs that survive combat may not retreat (331.7) and would be abandoned in the hex setting up another round of combat resolved by procedures in (331.75). If both forces retreated, the remaining RCUs are destroyed for no benefit.
(331.153) Abandoned: Abandoned RCUs (331.12) would not use small scale combat, even if they qualify, and combat would instead be resolved by (331.72).

(331.2) BASE COMBAT

Robot controlled units are considered a “base-like” units (756.3) for purposes of (302.2) would require an approach battle.

(331.21) ACTION WITH BASES: If a friendly base is present, then RCUs are assumed to have been programmed to be near it, see (302.2122). If there is more than one base the player announces at which base the RCUs are located. If there are both a base and base-like unit in the hex, then RCUs are always considered to be at the base. If there are only other base-like units present, then the RCU owner will disclose in advance the location of the RCUs in relation to these other base-like units. Robot controlled units themselves may not create multi-system hexes and would all be considered to be in one location. They may be designated at different locations if their target hex was already considered a multi-system hex.

(331.22) APPROACH BATTLE: Robot controlled units would not participate in an approach battle when at another base or base-like unit as they cannot move (209.22) to intercept an enemy force. Robot controlled units are considered a base-like unit would require an approach battle.

(331.23) BASE BATTLE: Robot controlled units must be included in a base battle.

(331.3) BATTLE FORCE DETERMINATION

(331.31) ASSIGNMENTS: Robot-controlled units must be assigned to the Battle Force in every combat round. Exception: see (331.23). After selecting a flagship, the player fills the command slots normally. One RCU is selected as the main focus and placed into the base location on the battle chart. Any remaining open command slots must then be filled with RCUs, up to the flagship’s command rating. Once all command slots are filled, any remaining RCUs are placed in the force as excess units co-located with the base (302.231). Excess robot-controlled units do not contribute to combat potential but can be damaged.
(331.311) Disarmed: Robot-controlled units lose all offensive combat potential and cannot deploy any assigned attrition units.
(331.312) Groups: RCUs lose all capability to be part of a battle group, gunline group, tactical auxiliary group, carrier group, or flagship escort group, nor can they be escorted in any way. RCUs cannot act as a consort or escort another unit.
(331.313) Formations: RCUs cannot occupy any formation positions.
(331.314) Personnel: Personnel such as ADM, MMG, DIP, prime teams, or marine units cannot operate from a robot-controlled unit.
(331.315) Support Echelon: RCUs cannot occupy the rear support echelon. The RCUs exceeding the command rating of the flagship (331.311) are not considered to be in the support echelon.
(331.316) Flagship Requirements: RCUs cannot serve as flagships as they have an effective command rating of “null” and do not take part in flagship selection. This effect lasts until the conclusion of the Final Activity Actions phase, see (209.23).


(331.32) SYSTEM RESTRICTIONS
(331.321) Scout Functions: Robot controlled units cannot operate as scouts and do not provide electronic warfare points, nor do they have the self-defense capability of (308.52) when resolving damage.
(331.322) Ion Pulse Generators: Vudar RCUs cannot operate their ion pulse generators (328.0) and gain no protection from them.

(331.4) COMBAT DAMAGE DETERMINATION

Resolve RCU combat normally with these additional stipulations.

(331.41) PENAL SHIPS: Robot controlled units cannot be the target of a penal ship Honor Duel mission (528.432).

(331.42) STASIS: A robot-controlled unit could be targeted by a stasis ship. While there is no added benefit to directed damage, as the units were already stopped in place, it would allow the unit to be included in a collective attack with other frozen ships per (312.212). A robot-controlled unit could be targeted by a defending stasis ship per (312.28).

(331.5) DIRECTED DAMAGE

Robot-controlled units on the line as well as those units in excess of the command rating (331.31) may be targeted with a 1:1 directed-damage attack. One robot-controlled unit may be targeted by a 1:1 directed damage attack without counting against the limit in (302.51). A second robot-controlled unit could be targeted using the direct damage attack, but this would count against (302.51)

(331.6) DAMAGE ALLOCATION

(331.61) DAMAGE: RCUs may only be voluntarily damaged by the owner to resolve damage when they are included on the battle line. Only one robot-controlled unit per combat round may be voluntarily crippled/destroyed by the owner to resolve damage. If no other unit is available to be damaged, then all remaining RCUs, even those in excess of the command rating, must be damaged.

(331.62) RECLAMATION: Destroyed RCUs do not generate salvage and are not eligible for depot repair.

(331.63) RESCUE: Transports in the support echelon assigned Mission W: Rescue can rescue RCUs eligible to be rescued. See (537.2) for procedure and restrictions.

(331.7) RETREAT AND CAPTURE

Robot-controlled units cannot retreat from combat but do follow the slow unit retreat (302.742) procedures to enable a capture attempt by opposing forces; see (331.731) below.

(331.71) CAPTURE ELIGIBLE: Most units that require robot-controlled movement to cross the WYN Radiation Barrier are not eligible for capture. However, monitors (519.23), overloaded transports (517.4), and warships operating under robot control are capture-eligible. If any such eligible robot-controlled unit is destroyed, it may be captured under the standard capture rules (305.1) or the modified combat rules (331.721).

(331.72) RETREAT AND ABANDONMENT: If a fleet containing robot-controlled slow units retreats and is pursued, those RCUs use the slow-unit retreat procedure (302.742), subject to the modifications below. If the fleet contains no other slow units, the robot-controlled slow units are treated as ‘abandoned’ under (331.12) but still use this modified slow-unit retreat procedure to allow capture attempts. Rule (304.41) regarding battle intensity would apply in both situations.
(331.721) Modified Combat Options: During this modified slow unit retreat round, the attacking player has two options:
(331.7211) Option 1 – Standard Combat: The attacking player can choose to follow normal combat damage procedures. Under this option the player who elects to roll damage would also follow normal capture rules in (305.12). Any capture eligible RCUs that were destroyed as part of the damage procedure would be included in this normal capture roll.
(331.7212) Option 2 – Forego Damage: The attacking player can choose to skip the damage roll under (302.42), ignoring the non-RCUs, instead having their attacking force simply make a capture attempt die roll upon each capture-eligible robot-controlled unit during the Troop Action Interphase. A capture succeeds on a die roll result of 2–7, modifiers (331.723) may apply. A failed roll means the robot-controlled unit is destroyed.
(331.722) Capture Requirement: RCUs not eligible for capture (331.73) would be automatically destroyed for no benefit at the end of the combat phase.
(331.723) Capture Support: Troop units (521.5) or prime teams (522.43) in the battle force follow their rules to improve the chance of capture on one die roll only. Under option 2 the attacking player chooses which die roll to modify before the die roll is made. Prime teams used in this way are still at risk and could be wounded or destroyed under (522.43).

(331.73) DEMISE: Any abandoned RCUs that survive the slow unit retreat battle self-destruct and destroyed for no benefit. Any mobile slow units that survive the battle get away normally under (302.742-C).

(331.8) WYN UNCONVENTIONAL AUXILIARIES

Unconventional WYN auxiliaries (555.1) that declared as RCUs or have used robot-controlled movement during the turn would adhere to all above combat rules.

***END OF (331.0) PROPOSED RULE***

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

last chunk of reports

Final report 638+.pdf final_report_638.pdf (53 k)

By Lawrence Bergen (Lar) on Monday, December 08, 2025 - 04:46 pm: Edit

ALL DONE
634 LINE ITEM REPORT L. Bergen 12/7/25

General Document Line Item: Use of “WYNs” vs “the WYN” Both appear throughout; WYN seems it could be plural or singular like ‘deer’, saying WYNs sounds a little awkward, I know it is likely a style thing but recommend choose one term and apply consistently. L. Bergen 12/7/25 EITHER ONE IS PERFECTLY FINE. THE LEVANT. LEVANTIANS.

General Document Line Item: Review when referencing locations like ‘capital core prefecture’ should it be capitalized, Capital Core Prefecture. What about just the standalone ‘prefecture’? Deferment to Jean's expertise is likely. L. Bergen 12/7/25 THREE FOUND.

(634.110) BATTLE ROUND #0:; 1st and 2nd line, replace text with: “The invading fleet enters one of the border prefectures, defined by geography, and fights a barrier recovery round battle, see (332.3-332.4). The WYN can use:” Rationale: fixes 3 typos, 2 missing commas, 2 rule reference format changes. L. Bergen 12/7/25 DONE

(634.112) third bullet: “Any allied ships within the WYN Cluster (@@@).” Possible fixes: Not sure what we were looking for here. The WYN can have allied forces inside the cluster hex but since this scenario allows variations as to whom these allies would be maybe delete the reference. They would have previously had to arrive by Operational (209.113) or Retrograde (209.151) movement. Or possibly looking to reference the rule for Reserve movement of allied forces into the WYN cluster hex this would be (209.132). L. Bergen 12/7/25 DELETED BULLET POINT, IT'S IN THE FOURTH ROUND.

(634.12) CAPITAL DEFENSES: Recommend a review against the WYN OOB. Specifically, regarding what bases are allowed by history. Not sure the WYN can have the Starbase at Vanonia. Also the number of PDUs on planets might need to be adjusted at various points in the history. For reference: (433.424) Minor planets are limited to 6xPDU, Majors can have up to 10xPDUs. A mention of Early Warning Networks (537.3) quite possibly should go here in the initial paragraph. Since this was originally a non-historical or general scenario it may be fine (with the SB) as it is but historically it does not align. L. Bergen 12/7/25 REVIEW TO YOUR HEART'S CONTENT BUT REPORT TOMORROW OR DROP THE ISSUE.

(634.2) SCENARIO FORCES; 1st line edit: replacement.
1st line, replace text with: “Players may attempt the invasion of the WYN Cluster during any scenario and would use whatever released forces they have available.” Reason: Style change, cleaner format. L. Bergen 12/7/25 ALL GREAT REASON FOR NOT MAKING ANY CHANGES.

(634.2) SCENARIO FORCES; 3rd line edit: replacement.
3rd line, replace text with: “Players wishing to play a short scenario consisting entirely of invading the WYN Cluster, would use the forces below.” Reason: Style change, cleaner format. L. Bergen 12/7/25 GREAT REASONS TO MAKE NO CHANGE AT ALL.

(634.21) WYN FORCES: replace line “Obtain these WYN counters from Civil Wars and add them: 9xFF, 2xDW.” with “Add 2xDW, 9xFF from Civil War Counters.” Reason: This is now a Civil War scenario. NOTE: This one may want to consider “another way” since this scenario was originally published in TO, we have updated the 712 WYN OOB, as well as we are working on several chronological snapshot OOBs (per your request). We also created sheet Zulu (including the ships added to the OOB this fall) so there are additional counters and possibilities that could be added here. Maybe a review and rewrite is needed for this one? L. Bergen 12/7/25 REVIEW ALL YOU WANT BUT REPORT TOMORROW OR FOREVER HOLD YOUR PEAC.E I AM TIRED OF CONSTANTLY FIDDLING.

(634.22) INVADING FORCES: add comma after General War “of the General War, and use…” L. Bergen 12/7/25 REVISED.

(634.5) NOTES ON WYN DEFENSE THEORIES; replace 2nd line: “They are only one single hex surrounded by three viscous and heavily-armed empires.” with; “They are only one single hex surrounded by three vicious and heavily armed empires.” Reason: Typo and eliminated hyphen: I laughed when my spellcheck reminded me that viscous is a thick syrup-like liquid, while some Kzintis, Lyrans, and Klingons are indeed thick others are quite intelligent, none are syrup. L. Bergen 12/7/25 FIXED.

(634.5) NOTES ON WYN DEFENSE THEORIES; Typo strategy is missing an ‘r’: “It’s an axiom of stategy that everyone…” should be “It’s an axiom of strategy that everyone…” L. Bergen 12/7/25 STRATEGERY, GOT IT.

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

ALL REPORTS DONE TO THIS POINT.

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

I finished the rulebook but cannot get it to PDF. I will try to get that done tomorrow but we're having technology issues caused by the technicians who rerouted our network and internet service earlier today and my patience is at an end.

By Lawrence Bergen (Lar) on Monday, December 08, 2025 - 05:57 pm: Edit

ALL DONE
(637.0) Romulan civil war introduction has my last name incorrectly. L Bergen 8 DEC 2025 FIXED

(637.0) Romulan civil war introduction last line typo “aat” should be “at”. L Bergen 8 DEC 2025 FIXED

(637.14) SETUP ORDER missing comma between “first” and “followed”; should be “…sets up first, followed by…” L Bergen 8 DEC 2025 DONE

(637.15) MODULES USED; Remove duplicate “of“…assumes the use of of the following modules…” Edited; “…assumes the use of the following modules…” L Bergen 8 DEC 2025 DONE

(637.15) MODULES USED; Original: has extra space before comma“Tactical Operations , and ISC Wars (IW) .” Edited: “Tactical Operations, and ISC Wars (IW).” L Bergen 8 DEC 2025 NOT FOUND

(637.233) Republican Headquarters; remove the space between home and world “The home world of Romulus…” Edited as “The homeworld of Romulus…”. Rationale: “homeworld” is standard in F&E) L Bergen 8 DEC 2025 DONE

(637.242) Unaligned Infrastructure: “5318: A colony base is collocated with the SB.” Please correct “collocated” in line 5318 should be co-located. L Bergen 8 DEC 2025 FIXED

By Lawrence Bergen (Lar) on Monday, December 08, 2025 - 06:19 pm: Edit

DONE
(637.285) No Economic impact. Capitalization: “impact” should be capitalized for header consistency. L Bergen 8 DEC 2025. FIXED

(637.41) ROMULAN REPUBLICIAN FORCES; Typo: “REPUBLICIAN” should be “REPUBLICAN”. L Bergen 8 DEC 2025. FIXED

(637.552) Raids Actions; Heading should be “Raid Actions”. reason: Typo. L Bergen 8 DEC 2025 FIXED

(637.553) Capturing Units; Original: “Romulan Civil war.”
Should be capitalized: “Romulan Civil War.” L Bergen 8 DEC 2025 DONE

(637.421) Imperial Fleet (Rolandus); remove duplicate “in” in line; Deploy in in hex 4318:“ L Bergen 8 DEC 2025 OUT OF NUMERICAL ORDER. DONE.

(637.513) Provincial Income:; “Only factional provinces generate income. They are subject to disrupte or capture…” fix typo: “disrupte” should be “disruption”. L Bergen 8 DEC 2025 CHANGED TO "DISREPUTE".

By Lawrence Bergen (Lar) on Monday, December 08, 2025 - 06:35 pm: Edit

DONE
(637.61) IMPERIAL VICTORY: Determine victory by evaluating the the following conditions.; remove extra “the”. L. Bergen 8 DEC 2035 DONE

(637.623) Condition #3: “the Republican faction controls all Romulan colonies and planets colonies east…” remove 2nd ‘colonies’ as a duplication error. L. Bergen 8 DEC 2025 DONE

By Lawrence Bergen (Lar) on Monday, December 08, 2025 - 06:54 pm: Edit

DONE
(636.0) Lyran Civil War Introduction; correction “take the matters into their own paws,”.: Should be “take matters…” (no “the”) L Bergen 8 DEC 2025 DONE

(636.15) Error: “T actical Operations (TO)”: remove space within word “T actical” L Bergen 8 DEC 2025.NOT FOUND

(636.15). “…required .” Extra spacing before period, remove space. L Bergen 8 DEC 2025. NOT FOUND

(636.15) line: “If you do not have a product replace…”; recommend “If you do not have a product, replace…” Add missing comma. L Bergen 8 DEC 2025. THAT COMMA IS ALREAD THERE.

(636.161) last rule reference is in error; (635.13) should be (636.13). L Bergen 8 DEC 2025. DONE

(636.17): “…required . These rules…” Extra spacing before period, remove space. L Bergen 8 DEC 2025. NOT FOUND

By Lawrence Bergen (Lar) on Monday, December 08, 2025 - 07:30 pm: Edit

DONE
(636.563) Lend-Lease: last paragraph; “…the Duke may release up to three ship under his control.” Plural “three ship” should be “three ships.” L. Bergen 8 DEC 2025 done

(636.57) PRODUCTION NOTES; “One size-class-4 scout may be produced by per turn by any means.”; remove first “by”. Should be “produced per turn by any means”. L. Bergen 8 Dec 2025. ACTUALLY IN 572, TWO DEMERITS AND TEN PUSH UP.

(636.618) Instant Victory “…maintaining control its own HQ starbases.” Add missing preposition: “…control of its own HQ starbases.” L. Bergen 8 Dec 2025. DONE

(636.63) Victory Mitigation “At the end of the game each side counts”; add Missing comma after intro clause: “At the end of the game, each side counts…” L. Bergen 8 Dec 2025. DONE

(636.63) Victory Mitigation. Change "wanton" to "won ton" as the Lyrans are really in the soup here. L. Bergen 8 Dec 2025. DONE, BUT ONLY BECAUSE YOU SAID SO.

By Lawrence Bergen (Lar) on Monday, December 08, 2025 - 07:55 pm: Edit

DONE
(636.628) Instant Victory: Last Paragraph first line; "The Centrists achieve an instant an ASTONISHING victory if..."; 2nd "an" should be "and", recommended as, "...an instant and ASTONISHING..." L Bergen 8 DEC 2025. DONE

(636.15) BTW Ignore the line item for (636.15) as that extra space in 'Tactical' was my own review file error, sorry. SEVERAL OF THOSE.

That's all I have time for today. Mainly looking for small edits now. Fine tuning. WOULD BUT THAT THIS WERE TRUE. SIGH.

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

Thanks for everything, Lar, even if I makes me crazy.

By Steve Cole (Stevecole) on Tuesday, December 09, 2025 - 12:12 pm: Edit

There had better be a box of miilk chocolate on the way to Jean or I cannot guarantee your lives or health.

By Steve Cole (Stevecole) on Tuesday, December 09, 2025 - 12:37 pm: Edit

GARY CARNEY: If you want to be useful, use your incredible research skills to find the "date of acquisition" for the various foreign ships. This information is not in the readily-accessible files but scattered all across many products.

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

DONE
I have eaten my demerited won ton soup and done my pushups. Here are a few more I found in today’s file. ALL OF THIS WAS DONE

(331.152) Retreat:; rule reference (331.75) should be (331.72). Typo on my part. L.Bergen 9 DEC 2025.

(331.41) PENAL SHIPS: Recommend changing text to “Robot Controlled units could be the target of a penal ship Honor Duel mission unless restricted by (528.432).” Rationale: Actually Turtle pointed out they can be and the Klingons might want to take a key unit out in this way. I pointed out there may not be much honor in it and the robot AI has no ego to accept such a duel but yeah I suppose it must be allowed unless the unit is restricted by the type of unit. L.Bergen 9 DEC 2025.

(331.722) Capture Requirement:; format should be bold and aligned with (331.721) L.Bergen 9 DEC 2025.

(331.723) Capture Support: ; format should be bold and aligned with (331.721) L.Bergen 9 DEC 2025.

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

PENDING STAFF COMMENTS
(549.1213) Unused “aux pod slots” can be saved for up to two years and used on later turns. Add to line “Unless specified on the OOB …” Rationale: This is not the case for the Vudar in minor empires under OOB rule (717.2) Production. L.Bergen 9 DEC 2025.
I DID THAT, BUT WE MIGHT WANT TO REMOVE THIS AND CHANGE THE VUDAR OB NOTE.

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

DONE
(331.71) add a last line, “WYN unconventional auxiliaries are not capture eligible under (555.131).” L Bergen 9 DEC 2025. DONE

By Steve Cole (Stevecole) on Tuesday, December 09, 2025 - 05:19 pm: Edit

ALL DONE TO THIS POINT

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

Y116: Start with ADM and two “early frigates” which may not be defined in SFB or F&E.
Y136: Add Orion CR, the first functional WYN warship, apparently not converted to WYN overgunned design, might not have been taken over by WYNs. (Orions begin helping WYNs. Things like APTs and PTRs cannot have arrived prior to Y137. The WYNs received “hundreds of freighters” over a period of 50 years, some of which were converted. We need not keep track of freighters used for cargo, minining, etc.)
Add ZFF (dates of acquisition of the other 3 unknown?), KG2 (dates of acquisition of the other 2 unknown).
Y137:
Y138:
Y139: Add LDD, Resv
Y140: Add SUC, SUS
Y141: Add 2xSUC
Y142: Add 2xSUC
Y143: Add SUC, SUS
Y144: Add 2xSUC, the first ZFF. (Four others later: 146, 158, 169, 177.)
Y145: Add 2xSUC
Y146: Add 2xSUC, ZFF, 2xLYF.
Y147: Add SUS
Y148: Add SUG
Y149: Add SUG
Y150:
Y151:
Y152:
Y153:
Y154: Add KE4
Y155:
Y156:
Y157:
Y158: Add ZFF.
Y159: REPR
Y160: OCR and three unmodified LR.
Y161: Add one unmodified LR.
Y162: Add one unmodified LR.
Y163: Add one unmodified LRS.
Y164: Add one unmodified LR.
Y165: Add three Monitors recevied as gifts. Add one unmodified LR.
Y166: Add ENG. Add one unmodified LRS.
Y167: Add LAV
Y168:
Y169: Add ZFF.
Y170: Add SUV, OCR, JCL.
Y171: Add SUV
Y172: Add SUV
Y173: Add LUC
Y174: Add LUC (Conversion of the Nancy begins.)
Y175: Add LUC, OCR. The last LYF is destroyed.
Y176:
Y177: Add ZFF.
Y178:
Y179:
Y180: Add OCR; convert LDD into PBB. At this point 13 OLR hulls were in service including LRS. A double raider and battle raider had been purchased by this point.
Y181:
Y182: Add CW, ZDW. Major Kzinti incursion.
Y183: Add CW, CWV, DWE, HUB, SUX, ZDF. (There is a known list of 23 auxiliaries in service on this date, but it is also known that the list is neither complete nor accurate.) Convert one ZFF into ZFX.
Y184: Add CA, CW, CWE, DWE, SUX
Y185: Add CF, CWL
Y186: Add CA, PBC.
Y187: Add CA. ISC incursion fails, leaving two DDs in WYN hands.
Y188:
Y189: Add DN
Y190:
Y191:
Y192:
Y193:
Y194:
Y195:
Y196: PBB retired.

By Stewart Frazier (Frazikar3) on Tuesday, December 09, 2025 - 06:42 pm: Edit

Missing KF4 (R12.47) [Mod R8]