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

(712.0) WYN STAR CLUSTER

Located at a point where the Klingon, Lyran, and Kzinti borders meet, the WYN Star Cluster was surrounded by a dense cloud of highly radioactive dust and was long considered saturated with deadly radiation and thereby uninhabitable. Not until Y116, when a Kzinti noble fled into the Cluster after a failed bid to seize the Patriarchal throne was it discovered that the radioactive shell surrounding the cluster could be breached. Later, renegades and the disaffected of every empire in known space began to trickle into the Cluster. Common enemies and a common cause forced these groups to set aside past rivalries and form a rare multi-ethnic culture.

(712.0) FLEET DATA – WAR OF RETURN (Y186F)

FIRST DIVISION (Capital Prefecture):
F-Series: HCW, 2xDW, 6xFF
O-Series: OBRC, OCRC, OBR, 2xOCR, ODR, 2xOCRX, 2xOLRX.
E-Series: PBB, PBC, KE4, ZDW, 2xZFX, 2xZFF, ZDF, FPL, GFF, RSH.
Aux Ships: HUB, 2xJUV, 2xJUB, LAV, LAP, ASC, 2xSUX, 3xSUC, 2xSUG.

SECOND DIVISION (Kzinti Prefecture):
O-Series: 2xOLR, OLRS.
E-Series: ZFF, KG2.
Aux Ships: LUC, 3xSUC, SUS, SUV, SAP.
Support Unit: MON-S, APT.

THIRD DIVISION (Lyran Prefecture):
O-Series: 2xOLR, OLRS.
E-Series: ZFF, KG2.
Aux Ships: LUC, 3xSUC, SUS, SUV, SAP.
Support Unit: MON-S, APT.

FOURTH DIVISION (Klingon Prefecture):
O-Series: 2xOLR, OLRS.
E-Series: ZFF, KG2.
Aux Ships: LUC, 3xSUC, SUS, SUV, SAP.
Support Unit: MON-S, APT.

FIFTH DIVISION* (External Operations):
F-Series: 2xFF
O-Series: 2xOLRX.
Support Units: 3xPTR.

SIXTH DIVISION* (Internal Operations):
Aux Ships: FHL, REPR.
Support Units: CONVOY (414.6).

SEVENTH DIVISION* (Usurper Operations - Clandestine):
F-Series: CA, CWL, 3xCW, DWL, 2xDW, 6xFF.
X-Ships: CAX, 2xDWX.
Carrier Support: [CWV+2xDWE], FFE, FCR, MEGA.
Support: CWM, CWS, CWP, LTT, DWD, DWP, DWS, 2xFFG.


GENERAL HEADQUARTERS*:
Pods: KPT, DP, KRP.
Resources: ADM, MMG, ENG, 3xDIP, CPX, 2xCPF, RESV.

* These fleets were all based in the capital prefecture.

(712.1) PRODUCTION

(712.11) CONSTRUCTION SCHEDULE
Y168S-Y174S: (2xAuxPod)
Y168F-Y174F: (2xAuxPod)
Y175S-Y179S: FF, (2xAuxPod)
Y175F-Y179F: (3xAuxPod)
Y180S: DD, FF, (3xAuxPod)
Y180F: FF, (3xAuxPod)
Y181S: DD, FF, (3xAuxPod)
Y181F: DD, FF, (3xAuxPod)
Y182S-Y184S: CW, DW, FF, (3xAuxPod)
Y182F-Y184F: CW, DW, FF, (3xAuxPod)
Y185S-Y189S: CA, CW, DW, FF, (3xAuxPod)
Y185F-Y189F: CW, DW, FF, (3xAuxPod)

(712.12) SUBSTITUTIONS
(712.121) Allowable Substitutions
Any Small Auxiliary Ship for AuxPod.
Any Large Auxiliary Ship for 2xAuxPod.
Any Jumbo Auxiliary Ship for 3xAuxPod.
Any Heavy Auxiliary Ship for 4xAuxPod.
CWL or DWL once per year by any means.
HCW for CW once per year by any means.
HDW for DW once per year by any means.
See WYN SIT for complete list of substitutions.
(712.122) Downgrade Substitutions
CW for CA
DW for CW or CA
FF for DW or CW or CA

(712.13) RESTRICTIONS AND ALLOWANCES
(712.131) Unit Production
Carriers - Standard: Any one carrier of any per year plus one escort carrier per turn.
Carriers - Heavy Fighter: Production counts against either carrier or PFT built limits.
Escorts: May be substituted for their base hull without limit.
Fleet Carrier Resupply Ships: One per year by any means.
Commando Ships: One per turn by any means.
Drone Ships: One per year by any means
Fast Ships: One per year of any type.
Heavy War Destroyers:
One per year by any means.
Can produce one HDW-COG per year.
Can produce one HDW-HOG per year once available. Counts about both the heavy fighter limit and the HDW-COG or HDW-POG limit.
Can produce one HDW-POG per year.
Can produce one HDW-FOP that replaces allowed FCR production.
Leaders: Includes CW and DW. One per year of any one type by any means including free (551.12) production.
Maulers: Limit one in service at any time.
Police Ships: None; cannot build.
PF Tenders: One per turn by any means.
Scouts: One substitution per turn.
Transports: One TG or LTT per year by any means. Limit one APT and PTR each per turn.
Auxiliaries:
WYN and standard auxiliary unit production requires the use of auxiliary pod (AuxPod) capacity.
Small auxiliaries require one AuxPod.
Large auxiliaries require two AuxPods.
Jumbo auxiliaries require three AuxPods.
Heavy auxiliaries require four AuxPods.
Unused AuxPod production capacity from a given turn may be carried over to the next turn but if not used on that next turn, the unused capacity will be lost forever with no salvage or other compensation.
Free Auxiliary PFTs via (526.47) - receive at no cost (PFs and fighters included free): SAP, Y179F; LAP, Y180S; ASC*, Y181S.
Convoys (414.0) (526.1):
Limit one convoy in service to facilitate internal logistics under (414.6).
Campaign or Expedition: May produce one convoy or one military convoy per turn after declaring war; can only cross the WYN barrier under robot control (209.2).
Production: Convoys require the use 4xAuxPods; military convoys require 6xAuxPods.
Engineer Regiments:
Cannot operate in the central prefecture.
One free ENG when at war; may only replace if lost and requires the use 4xAuxPods.
Campaign or Expedition: Can only cross the WYN barrier under robot control (209.2).
Special Attack Forces (520.1):
May only be produced as part of a campaign or expedition. May produce one SAF per year one turn after declaring war; can only cross the WYN barrier under robot control (209.2).
Monitors: Prohibited from building (but may receive as gift).
Monitor Pallets: May produce for gifted monitors:
M-PAL-V, Y167; M-PAL-P, Y180S; M-PAL-S, Y179S.
Pods: One per turn (may receive as gifts).
Repair Units: Cannot build FRDs; may build one PRD per year when available.
(712.132) Personnel
Admirals: Only one ADM ever in service beginning Y167S.
Diplomats: Three DIPs at start; may start scenarios pre-deployed to the neighboring empires.
Independent Ground Combat Elements:
Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81).
Troop Transport Drop: May purchase I-GCEs during the Retrograde Phase for one EP each (521.831).
Raise Local Militia: May purchase I-GCEs during the Economic Phase; the cost is two EPs (521.838).
Marine Major Generals: One free MMG when at war; may only replace if lost.
Prime Teams: Receive one team per turn and may buy an additional one while at war; limit three in service.


(712.133) Infrastructure
Bases:
Cannot build any base larger than a BTX.
Can produce any number of PDUs per turn (431.2).
Can produce any number of PGBs per turn (441.11).
Can produce one MB per year, but only to replace internal, fixed base losses.
Campaign or Expedition: Can produce one MB/OPB per turn one turn after declaring war. Can only cross the WYN barrier under robot control (209.2).
Colonies: Prohibited from building inside the Cluster.
Minor Shipyards: May have no more than:
One FF slip for 10 EP;
One DW slip for 15 EP;
One CW slip for 20 EP;
One Minor Conversion Facility for 10EPs.
Alternative Conversion Facility: The WYN Cluster was unable to build starbases and so converted their capital shipyard to include a conversion capability. Beginning in Y140, the WYN shipyard has a conversion capacity of up to three points per turn [this is an exception to (433.11)]. Once per year, beginning in Y170, the WYN is permitted to make a single major conversion (433.12) (including any one X-conversion, when authorized). Flexible conversions (450.5) and authorized two-step conversions (437.0) are also permitted.
Minor Conversion Facility: The WYN built a facility at their capital planet Vanonia. Beginning in Y172, the WYN may make minor conversions using (450.123); this is in addition to the conversion capacity from their Special Conversion Facility (above).
Repair Depot: Tracks (424.11) at Hex 0804:
WYN-1: All F-Series “Fish” warships.
WYN-2: All O-Series Orion sourced warships.
WYN-3: All E-Series “external” empire sourced warships.
Attrition Unit Storage Depots:
Limit four fighter storage depots (FSD) in service.
Limit one PF storage depot (PFD) in service.

(712.2) FORCE DEPLOYMENTS

(712.21) TECHNOLOGY
(712.211) Fighter Deployment:
Initial, Y165S; Heavy, Y178S, Mega, Y179S.
Receive three free fighter factors per turn.
(712.212) PF Deployment:
Initial, 179F; PFTs; Y180S, CPFs, Y180F.
CPFs: One per turn; limit three in service.
CPF Carriage: All Fish ships, including purchased and captured ships can carry two casual PFs (exception: PBB can carry five casual PFs. All WYN auxiliary ships cannot carry casual PFs.
Free Flotillas (502.62): 2, Y179S; 4, Y179F; 2, Y180S.
(712.213) X-Technology Development:
Introduction: Y182S, may upgrade one base to X-technology per (523.413).
Eligible test-bed ships (553.0): FFX; OLRX.


(712.22) LOGISTICS
Survey Operations: Prohibited.
Command Points (308.9):
Two points at start - internal cluster use only.
One additional point upon Usurper excursion.
One free per turn while not exhausted (652.3) unless Admirals are used.
May purchase one per year.

(712.23) FORMATIONS
Battle Groups (315.0) (657.321):
Initial, Y146; Allied, Y164.
Tactical Auxiliary Groups (325.0): Y147.
Late War Combat Formations (318.4): Y181S
Tactical Reserve Forces (543.0):
Initial: Y193; Operational: Y194
(712.24) MANEUVER
Strategic Movement: Five free points per turn; may purchase up to five more. An external strategic movement node is required in any hex adjacent to the Cluster hex (0804) to move strategically into and out of the cluster (209.161).
Raid Pool (314.0):
Initial, 1; Y176S: 2; Commando, 1; Blockade, 1.
Special Raids: 1; Y168+ (320.122)
Espionage & Sabotage: Only one E&S mission (534.0) per turn.

(712.25) AUGMENTATION
Current Auxiliaries:
UNIT TYPE START MAX
FTS S Aux 0 4
SAS S Aux Used SUS -
SAV S Aux Used SUV -
SAP S Aux 3 4
SUC, SUS, SUG, SUV, SUX S Aux See OOB
∞
FHL L Aux 1 1
FTL L Aux 0 1
LAS L Aux 0 4
LAV L Aux 1 4
LAH L Aux Counts as LAV -
LAP L Aux 1
May sub for LAS 4
ASC L Aux 1
May Sub for LAV/LAP/LAS 1
LUC, LUX L Aux See OOB 8
JUV J Aux 2 4
JUB J Aux 2 4
HUC H Aux 1 1
HUB H Aux Counts as HUC -



Pod Deployment:
POD TYPE START MAX
KBP K-Type Battle Pod 0 2
KTP K-Type Troop Pod 0 2
KSP K-Type Scout Pod 0 2
KVP K-Type Carrier Pod 0 2
KVA K-Type Heavy Carrier Pod 0 2
KVH K-Type HF Carrier Pod 0 1
KHT K-Type HF Transport Pod 0 1
KPF K-Type PFT Pod 0 2
KPT K-Type PF Transport Pod 1 2
KRP K-Type Repair Pod 1 1
KDP K-Type Drone Pod 0 0
DP K-Type WYN Drone Pod 1 2
The WYN player can use the generic K-Type pod counters found in F&E Civil Wars.

(712.3) ECONOMICS

(712.31) BASE ECONOMICS SOURCES (Y168+):

WYN
36EP PROV
6EP/3EP MINORS
2EP/1EP MAJORS
4EP/2EP TRADE
6EP/0EP
0804 1 4 4 -

(712.32) CAPITAL SYSTEMS (Y186F+):

SYSTEM PLANETS TYPE FACILITIES
Capital
Sector
Prefecture Vanonia Major BTX, PRD,
12xPDU, FSD, PFD
Freeholm Minor BTS†, PRD,
6xPDU,
SHIPYARD
Early Warning Network (537.3) Remote Location Asteroid 2xFDU
Kzinti
Sector
Prefecture Zinfarst Major BTS
8xPDU, FSD
Belarus Minor BS
4xPDU
Lyran
Sector
Prefecture Plesetsk Major BTS
8xPDU, FSD, PRD
Hyperialis Minor BS
4xPDU
Klingon
Sector
Prefecture Kamchatki Major BTS
8xPDU, PRD, FSD
Kostromshya Minor BS
4xPDU

 “Capital Planet”
† Before Y182: Orion BTS (see Orion SIT for factors)

(702.33) EXHAUSTION EFFECTS: (652.31):
First fifteen turns on a wartime economy - 100%;
Next ten turns on a wartime economy - 75%;
Remaining turns on a wartime economy - 50%

end

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

(705.P) CROWN FACTION - WAR OF RETURN

FALL Y186
The Kzinti Crown Prince and Baran were able to provide the listed ships to oppose the Usurper and the Count during the War of Return. The forces do have additional ships that are assigned to other duties as listed in the ISC War Order of Battle. These ships are conducting operations against pirates, border incursions, or under long-term repair post-war.

(705.P0) FLEET DATA – WAR OF RETURN (Y186F)

KZINTI CROWN FORCES*

Crown Prince's Fleet: Set up in the following hexes:
0803: BC, CPX (with 2xPF).
0904: NCA, 2xCM, DW, 2xPOL, PTR.
1103: 2xFFK, FF, DF
1104: [NCV+MEC+DWE]
1202: CC, FLG
1401: BCX, HDW, MPF, DWL, MCG, MSC, DWS, [SCS+MEC+2xDWE], MEGA, 2xFCR, ADM (Crown Prince), MMG, 2xPRIME, MilCon, LAD, ASC, SAV, FRX+2xFTM; Crippled: BC, MCC, CM, DWL, 3xDW, FFK, CMX, 2xFKX, [CVL+MEC+FKE], CD, DWG, FFG, TGT, LTT, DWS, FFT.

(638.412) Baron's Fleet: Set up in the following hexes:
1100 (Barony): BC, HDW, DW, FFK, CD, MSC, TGT, [BCV+MEC+DWE], [CVP+MEC+DWE], FCR, MEGA, SAV, PTR, FRD+2xFTM, PRIME.
1400 (Barony): CMX; Crippled: BCH, 2xCM, DWL, DW, 2xFFK, 2xFKX, PFT, DF, SF.
1100 (Barony): FLG.
120Y (Barony): POL.
1700 (Barony): POL.

(638.413) Crown Forces GHQ: Assign as appropriate.
Pods: T-POD, PTP, 2xBP, 2xVAP.
Resources: COG, FOP, REPR, RESV

* Above Per (638.411).

NOTE: The Crown Prince and Barony Fleets have additional forces available but are tasked for other missions or are in long-term repair and maintenance.

(705.P1) PRODUCTION

(705.P11) CONSTRUCTION SCHEDULE

Crown Forces Schedule: Only a portion of the Kzinti schedule is available to the Crown forces which includes DW production at their capital SBX and the Barony SB using (442.53); schedule extract as follows:

Spring turns, Y187+: CM, HDW†, DW, FFK.
Fall Turns, Y186+: CM, 2xDW, FFK.
The HDW† listed is the one allowed substitution.

Minor Shipyards Usage: Barony minor shipyards under the control of Crown forces can be used for production, conversion, or repair of Kzinti-type ships (CM, DW, and 2xFF); see (638.543).


(705.P12) SUBSTITUTIONS
(705.P121) Allowable Substitutions
Any Small Auxiliary Ship for AuxPod.
Any Large Auxiliary Ship for 2xAuxPod.
Any Jumbo Auxiliary Ship for 3xAuxPod.
Any Heavy Auxiliary Ship for 4xAuxPod.
CWL or DWL once per year by any means.
HCW for CW once per year by any means.
HDW for DW once per year by any means.
(705.P122) Downgrade Substitutions
CL for any DN or BC
CL for any CM
DD for DN or BC or CM
FF for DN or BC or CM or DD †
CM for NCA †
DW for NCA or CM in Fall Y175+
BC or CC for any DN † BC for CC †
CVL or CVE for CV
CV or CVL or CVE for CVA*

(705.P13) RESTRICTIONS AND ALLOWANCES
(705.P131) Unit Production
Carriers - Standard: Any one carrier of any per year plus one escort carrier per year.
Carriers - Heavy Fighter: Production counts against either carrier or PFT built limits.
Escorts: May be substituted for their base hull without limit.
Fleet Carrier Resupply Ships: One per year by any means.
Commando Ships: One per year by any means.
Drone Ships: One per year by any means.
Fast Ships: One per year of any type.
Heavy War Destroyers:
One per year by any means.
Can produce one HDW-COG per year.
Can produce one HDW-HOG per year once available. Counts about both the heavy fighter limit and the HDW-COG or HDW-POG limit.
Can produce one HDW-POG per year.
Can produce one HDW-FOP that replaces allowed FCR production.
Leaders: Includes CW and DW. One per year of any one type by any means including free (551.12) production.
Police Ships: No call-ups permitted.
PF Tenders: One per year by any means.
Scouts: One substitution per year.
Transports: One TG or LTT per year by any means. Limit one APT and PTR each per turn.
Auxiliaries:
Auxiliary unit production requires the use of auxiliary pod (AuxPod) capacity.
Unused AuxPod production capacity from a given turn may be carried over to the next turn but if not used on that next turn, the unused capacity will be lost forever with no salvage or other compensation.
Convoys (414.0) (526.1):
May produce one convoy or military convoy per year.
Engineer Regiments:
None available.
Special Attack Forces (520.1):
May produce one SAF per year one turn.
Monitors: May produce one per year.
Monitor Pallets: May produce one per year.
Pods: One set per year.
Repair Units: May build one FRD or PRD per year when available.
(705.P132) Personnel
Admirals: Only one ADM ever in service (Crown Prince).
Diplomats: None.
Independent Ground Combat Elements:
Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81).
Troop Transport Drop: May purchase I-GCEs during the Retrograde Phase for one EP each (521.831).
Raise Local Militia: May purchase I-GCEs during the Economic Phase; the cost is two EPs (521.838).
Marine Major Generals: May replace if lost.
Prime Teams: Receive one team per year and may buy an additional one while at war; limit three in service.
(705.P133) Infrastructure
Bases:
Can produce any number of PDUs per turn (431.2).
Can produce any number of PGBs per turn (441.11).
Can produce one MB or OPB per year.
Colonies: Cannot build.
Minor Shipyards: Cannot build more.
Repair Depot: See (638.532):
Attrition Unit Storage Depots: May only replace if lost.

(705.P2) FORCE DEPLOYMENTS

(705.P21) TECHNOLOGY
(705.P211) Fighter Deployment:
Initial, Y165S; Heavy, Y178S, Mega, Y179S.
No free fighter factors.
(705.P212) PF Deployment:
Initial, 179F; PFTs; Y180S, CPFs, Y180F.
CPFs: One per year; limit one in service.

(705.P22) LOGISTICS
Survey Operations: Prohibited.
Command Points (308.9):
No points at start.
One free per year while not exhausted (652.3) unless Admirals are used.
May purchase one per year.

(705.P23) FORMATIONS
Battle Groups (315.0) (657.321):
Initial, Y146; Allied, Y164.
Tactical Auxiliary Groups (325.0): Y147.
Late War Combat Formations (318.4): Y181S
Tactical Reserve Forces (543.0):
Initial: Y193; Operational: Y194
(705.P24) MANEUVER
Strategic Movement: Two free points per turn; may purchase up to two more.
Raid Pool (314.0):
Initial: One.
Espionage & Sabotage: Only one E&S mission (534.0) per year.


(705.P25) AUGMENTATION
Auxiliaries: No additional auxiliaries are available to be built. Destroyed auxiliaries cannot be replaced.

Pod Deployment:
No additional pods can be built. Replacements for lost pods may be built.

(705.P3) ECONOMICS

(705.P31) BASE ECONOMICS SOURCES: Per (638.231)

(705.P32) EXHAUSTION EFFECTS: (652.31):
First fifteen turns on a wartime economy - 100%;
Next ten turns on a wartime economy - 75%;
Remaining turns on a wartime economy - 50%
Also see (638.516).


END

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

(705.C) COUNT FACTION - WAR OF RETURN

FALL Y186
The Kzinti Count was able to provide the listed ships to support the Usurper for the War of Return. The Count does have additional ships that are assigned to other duties as listed in the ISC War Order of Battle. These ships are conducting operations against pirates, border incursions, or under long-term repair post-war.

(705.C0) FLEET DATA – WAR OF RETURN (Y186F)

KZINTI COUNT FORCES*

Count’s Fleet: Set up in the following hexes:
1001: CCX, HDW, DW, [SCS+NEC+2xDWE], FCR, MDC,
NSC, LTT, DWG, DWS, FFT, 2xPRIME, OPB, LAV, LAP, FTS,
APT, FRD+FTM+PFM, ADM (Count)
0802: DW
0903: DW
Assign as appropriate:
Pods: 2xVP, T-POD, PTP, REP
Resources: POG, CPF, RESV

*Per (638.513).

NOTE: The Count Fleet has additional forces available but are tasked for other missions (i.e. Lyran border protection) or are in long-term repair and maintenance.

(705.C1) PRODUCTION

(705.C11) CONSTRUCTION SCHEDULE
Count Forces Schedule: The Count has no production capability in the scenario unless a minor shipyard is captured in the Barony.
Minor Shipyards Usage: Barony minor shipyards under the control of Count forces can be used for production, conversion, or repair of Kzinti-type ships (CM, DW, and 2xFF); see (638.543).

(705.C12) SUBSTITUTIONS
(705.C121) Allowable Substitutions
CWL or DWL once per year by any means.
HCW for CW once per year by any means.
HDW for DW once per year by any means.
(705.C122) Downgrade Substitutions
See (705.0)

(705.C13) RESTRICTIONS AND ALLOWANCES
(705.C131) Unit Production
Carriers - Standard: Any one carrier of any per year plus one escort carrier per year.
Carriers - Heavy Fighter: Production counts against either carrier or PFT built limits.
Escorts: May be substituted for their base hull without limit.
Fleet Carrier Resupply Ships: One per year by any means.
Commando Ships: One per year by any means.
Drone Ships: One per year by any means.
Fast Ships: One per year of any type.
Heavy War Destroyers:
One per year by any means.
Can produce one HDW-COG per year.
Can produce one HDW-HOG per year once available. Counts about both the heavy fighter limit and the HDW-COG or HDW-POG limit.
Can produce one HDW-POG per year.
Can produce one HDW-FOP that replaces allowed FCR production.
Leaders: Includes CW and DW. One per year of any one type by any means including free (551.12) production.
Police Ships: No call-ups permitted.
PF Tenders: One per year by any means.
Scouts: One substitution per year.
Transports: One TG or LTT per year by any means. Limit one APT and PTR each per turn.
Auxiliaries:
Auxiliary unit production requires the use of auxiliary pod (AuxPod) capacity.
Unused AuxPod production capacity from a given turn may be carried over to the next turn but if not used on that next turn, the unused capacity will be lost forever with no salvage or other compensation.
Convoys (414.0) (526.1):
May produce one convoy or military convoy per year.
Engineer Regiments:
None available.
Special Attack Forces (520.1):
May produce one SAF per year one turn.
Monitors: May produce one per year.
Monitor Pallets: May produce one per year.
Pods: One set per year.
Repair Units: May build one FRD or PRD per year when available.
(705.C132) Personnel
Admirals: Only one ADM ever in service (Count).
Diplomats: None.
Independent Ground Combat Elements:
Extra Troops: May purchase one I-GCE per combat round only for one EP (521.81).
Troop Transport Drop: May purchase I-GCEs during the Retrograde Phase for one EP each (521.831).
Raise Local Militia: May purchase I-GCEs during the Economic Phase; the cost is two EPs (521.838).
Marine Major Generals: May replace if lost.
Prime Teams: Receive one team per year and may buy an additional one while at war; limit three in service.
(705.C133) Infrastructure
Bases:
Can produce any number of PDUs per turn (431.2).
Can produce any number of PGBs per turn (441.11).
Can produce one MB or OPB per year.
Colonies: Cannot build.
Minor Shipyards: Cannot build more.
Repair Depot: See (638.532):
Attrition Unit Storage Depots: May only replace if lost.

(705.C2) FORCE DEPLOYMENTS

(705.C21) TECHNOLOGY
(705.C211) Fighter Deployment:
Initial, Y165S; Heavy, Y178S, Mega, Y179S.
No free fighter factors.
(705.C212) PF Deployment:
Initial, 179F; PFTs; Y180S, CPFs, Y180F.
CPFs: One per year; limit one in service.

(705.C22) LOGISTICS
Survey Operations: Prohibited.
Command Points (308.9):
No points at start.
One free per year while not exhausted (652.3) unless Admirals are used.
May purchase one per year.

(705.C23) FORMATIONS
Battle Groups (315.0) (657.321):
Initial, Y146; Allied, Y164.
Tactical Auxiliary Groups (325.0): Y147.
Late War Combat Formations (318.4): Y181S
Tactical Reserve Forces (543.0):
Initial: Y193; Operational: Y194
(705.C24) MANEUVER
Strategic Movement: Two free points per turn; may purchase up to two more.
Raid Pool (314.0):
Initial: One.
Espionage & Sabotage: Only one E&S mission (534.0) per year.

(705.C25) AUGMENTATION
Auxiliaries: No additional auxiliaries are available to be built. Destroyed auxiliaries cannot be replaced.
Pod Deployment: No additional pods can be built. Replacements for lost pods may be built.


(705.C3) ECONOMICSC3) ECONOMICS

(705.C31) BASE ECONOMICS SOURCES:
See: (638.223).

(702.C33) EXHAUSTION EFFECTS: (652.31):
First fifteen turns on a wartime economy - 100%;
Next ten turns on a wartime economy - 75%;
Remaining turns on a wartime economy - 50%
Also see (638.513).
END

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

WYN income seems off (36) as 4 Major + 4 Minor + Province equals 38 (4*6+4*2+6) [plus 4 trade = 42].

Also noted that the normal planetary income (5/3) produces the same starting WYN income but has WYN majors producing more EPs when captured [3 VS 2 (430.3)].

By Ryan Opel (Ryan) on Tuesday, December 02, 2025 - 11:31 pm: Edit

The WYN are short on population to fully exploit the major and minor planets.

Not an issue for an Empire with essentially unlimted populations but a problem for the WYN.

Think of it as a part of the road from colony to full planetary income. (NO WE ARE NOT WRITING A RULE FOR THAT.)

By Ryan Opel (Ryan) on Tuesday, December 02, 2025 - 11:34 pm: Edit

Gary,

When the Federation sent a gropup of diplomats to Tholia to open up negotiations after Operation Wedge they used a FFP escorted by a FFV, FFA. To anyone seeing from a distance it looked like any other 3 ship frigate squadron on a mission and not worth the effort.

By Ryan Opel (Ryan) on Tuesday, December 02, 2025 - 11:36 pm: Edit

705.P "The Kzinti Crown Prince and Baran..." correct spelling of Baron. R Opel 2 Dec 25 ALREADY DONE, I SAW IT WHEN FORMATTING

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 03:43 am: Edit

TUESDAY 2 Dec
I rounded up every scrap of paper in the office that was a page of the F&E civil wars rule book and processed the notes and corrections there on. I still have two emails report s not done yet. I got the last of the elements from the staff and. Put them into the book and started formatting them.

By Lawrence Bergen (Lar) on Wednesday, December 03, 2025 - 03:56 am: Edit

(712.131) Has a lot of discussion about Aux Pods and the use of them in producing units. Much of this was in the playtest rules published in Captains log 43 and maybe 44, they even made it into the SIT. But no complete rule has been published officially and there is no mention of using Aux Pods in 549.0. AuxPods do appear in the production schedules for the LDR and VUDAR on their OOBs and the there is a Vudar specific rule on the Vudar OOB.

This and since we included more LAC and SAC units on Zulu in Civil War colors could we write up an updated version of 549 to include Aux Pods rules in the production section and some Combatants rules. NOTE: These units were also Capt Log 43 and 44 and lightly included as part of the Minor Empires Production schedules and appear in the LDR (but with no mention of Aux Pods).

By Lawrence Bergen (Lar) on Wednesday, December 03, 2025 - 03:59 am: Edit

There will be another email sent shortly with the compiled list you asked for. Its why I am still up at this hour LOL

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 04:51 am: Edit

Compiled list? what compiled list? Compiled list of what?

I rewrote 549.12 to explain auxpods

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 04:53 am: Edit

By Lawrence Bergen (Lar) on Wednesday, December 03, 2025 - 05:56 am: Edit

I sent the Line Items regarding the 20 pages of rules we were sent. It should be in your inbox now. We should have addressed all of the rule numbers if you find one let us know.

I have to get up for work in 3 hours so I am going to bed LOL

By Gary Carney (Nerroth) on Wednesday, December 03, 2025 - 10:11 am: Edit

Should the WYN-Jindarian light cruiser be added to the above WYN Order of Battle, or is its uncertain historical status enough to warrant keeping it as an optional rule for the time being?

I recall a note in the Countersheet Zulu discussion to the effect that, if used, the JCL is to be restricted for use in the capital prefecture.

-----

Also, there is a note about the WYN shipyard gaining a special conversion capacity in Y140. Historically, however, my understanding is that this was the other way around; as per the R-section data in Module C1, the WYNs were limited to converting ships prior to Y160, when the Orion Cluster Cartel established their own yard.

FEDS - Memo for Record

REF SFB C1 pg1:

---

Quote:

The one thing the WYN lacked was a shipyard capable of actually building ships (rather than just converting them). In Y160, the Orions constructed one within the cluster on the condition that it remain under Orion control.

---

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 11:32 am: Edit

The Jindo CL deserves at least a note.

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 11:37 am: Edit

Looks like 549.12 needs a tune up, but it's really not necessary to even have an auxpod rule.

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:36 pm: Edit

(000.1) NOTE to SVC about section 209
(209.24) through (209.26) - Staff review of these three rules pointed out that these three rules need clarifications made. But more importantly they are in violation of the 200 Movement segment. These rules describe the Modified Combat Procedure for Robot Controlled ships which should be in the 300.0 Rule section. One Idea is to insert it as 331.0 to save SVC and the STAFF the hassle of renumbering 332.0 We welcome suggestions and have a draft in progress of the changes needed no matter what is decided.
(115.2) 332 Barrier Disabled Combat should read: 331.0 Barrier Disabled Combat.
Reason: (330.0) Flexible Command Points is the last combat rule published in Tactical Operations. Thomas Mathews 28 Nov 2025
(115.7) ‘Interned by the WYN: @@@’ should read: Interned by the WYN: 449.22 and 503.1
Reason: (449.22) covers the sale of a small number of ships to the WYN by the neighboring empires and how to handle anything outside of (449.22) when playing with Planetary Operations. If not playing with Planetary Ops then (503.1) covers those ships. Thomas Mathews 28 Nov 2025
(115.7) Asset neutrality rules: 660 should read: Asset Neutrality Rules 660.0
Reason: 660.0 covers all of the Asset neutrality rules. Thomas Mathews 28 Nov 2025
(115.7) Civil wars territory rules: 659 should read: Civil wars territory rules 659.0
Reason: 659.0 covers all of the Civil wars territory rules. Thomas Mathews 28 Nov 2025
(115.7) Influence points: 658 should read: Influence points: 658.0
Reason: 658.0 covers all of the Influence points rules. Thomas Mathews 28 Nov 2025
(115.7) Middle Years special rules: 657.0 should read "Middle Years Scenario Rules: 657.0"
Rationale: This is the actual title of the rule section and will help players find the entry. The rule number is correct. Lawrence Bergen 12/1/25
(115.7) Overloaded Tugs: @@@ should read: Overloaded Tugs: 517.4
Reason: (517.4) covers Overloaded Tugs. Thomas Mathews 28 Nov 2025
(115.7) Territory rules for civil wars: 659 should read: Territory rules for civil wars: 659.0 Reason: (659.0) covers all the territory rules for empires in civil wars. Thomas Mathews 28 Nov 2025
(115.7): Delete the open quotation mark in Influence points:”.
Rationale: correction of typo. TDF 12/1/25.
(209.112) Exiting Ships: Last line reads, See (332.0). but should read: See (331.0).
Rationale: Rule (332.0) was changed to (331.0) because (330.0) Flexible Command Points is the last combat rule published in Tactical Operations. Lawrence Bergen 12/1/25.
(209.122) External Units: 2nd paragraph last line rule reference of (332.21) should be: (331.21)
Rationale: Rule (332.0) was changed to (331.0) because (330.0) Flexible Command Points is the last combat rule published in Tactical Operations. Lawrence Bergen 12/1/25.
(209.134) Unavoidable Combat: Last line reads, See (332.21). but should read: See (331.21).
Rationale: Rule (332.0) was changed to (331.0) because (330.0) Flexible Command Points is the last combat rule published in Tactical Operations. Lawrence Bergen 12/1/25.
(209.142) Add at the end of “hex they retreated into.” “See (332.2).” STAFF 12/1/2025
(209.142) Change “by the second passage” to “by the third passage” and “@ @ @ this doesn’t match the published history, but...?” to “See (209.113).” STAFF 12/1/2025
(209.144) Suggested revision: Substitute the current sentence with, “The Barrier prevents pursuit combat of any kind.” Rationale: Confusing language. The sentence states, “No pursuit is possible across the Barrier.” However, someone is likely to argue that the pursuit happens before the pursued force leaves the barrier, likely triggering a BBS Q&A resolution. TDF 12/1/25.
(209.154) Suggested revision: replace “Any unit that has moved…” with “Any unit that moves…” Rationale: better syntax and grammar. TDF 12/1/25.
(209.161) Suggest replacing the first instance of SMN with “strategic movement node (SMN)”. Rationale: should not assume customer is familiar with F&E jargon. TDF 12/1/25.
(209.2) In the “Note,” replace “…be times that such movement in necessary” with “such movement is necessary.” Rationale: correct typo. TDF 12/1/25.
(209.2) In the very last sentence in this long rule, delete the one comma. Rationale: grammar. Use of the comma not appropriate there. TDF 12/1/25.
(209.241) Disarmed: Drop the last line which reads: Their defense factor is reduced by 50% (drop fractions); an original defense factor of “1” would remain “1”.
Rationale: November 14th Line item email to ADB was wrong! Used the very incorrect assumption that these robot-controlled units would be barrier-disabled when they, by rule, cannot be. See (209.21). Additionally play testing previously determined when in combat rule (209.242) allows all robot controlled units to be targeted at 1:1 instead of the normal 2:1 effectively reducing the defense factor by 50% over non-robot-controlled ships of the same type in combat. Lawrence Bergen 12/1/25.
(209.3) Change “scenrio" with “scenario”. And the cluster should be changed to “the Cluster” Rationale: Correct typos. TDF 12/1/25.
(331.252) Internal Cluster Battles: Combined with the effects of the radiation zone, units crossing the barrier enter the tight confines of the Cluster in a disorganized state. Because the WYN anticipated and planned for this, they are able to organize a second battle force. This additional force is used to exploit the barrier-disabled enemy, per (331.255).
Rationale: More clear and grammar correction of capitalization. L Bergen 12/1/25
(331.252) Replace rule text with the following;
(332.0) Barrier-Disabled Combat should read: (331.0) Barrier-Disabled Combat.
Reason: (330.0) Flexible Command Points is the last combat rule published in Tactical Operations.
All rules and subsequent rules within (332.x) should be renumbered as (331.x), additional rule references that should change are also called out in these line items by the staff. Thomas Mathews 28 Nov 2025
(332.12): BARRIER-DISABLED: Last Line beginning with "Because the recovery..." Drop the entire last line.
Rationale: It is not part of this definition, and this note appears first in (331.11) as a description of the action pause (last line) and again in (331.211) Combat Set up procedures. L Bergen 12//25
(332.21): BARRIER TRANSIT: change to (332.21) IMMEDIATE EFFECT:
Rationale: duplicate title block with the rule above. L Bergen 12/1/25
(332.212) Change “A barrier combat offer is then also required, see (332.23) below.” With ”A barrier disabled combat offer is also required. See (332.23), below.” Rationale: better syntax and grammar. TDF 12/1/25.
(332.213) second line, Insert the word "under" before the rule reference number.
Rationale: Clarity and consistent styling. L Bergen 12/1/25
(332.214) Mutual Entry: Clean up first line to read, "If two opposing forces simultaneously retreat through the barrier into the same unoccupied hex, no barrier combat occurs between them."
Rationale: Restructure to eliminate "and that is otherwise" as unnecessary language. L Bergen 12/1/25
(332.214) Mutual Entry: Clean up third line to read, "Follow the applicable procedures of (331.212) or (331.213) if other opposing forces are already in the hex."
Rationale: Restructure to add 'applicable' eliminate "from above...and" for clarity. L Bergen 12/1/25
(332.215) Use lower case for “Barrier Recovery Combat Round.” Rationale: grammar correction. TDF 12/1/25.
(332.222) Replace “…units from hostile force…” with “units from the hostile force.” Rationale: grammar correction. TDF 12/1/25.
(332.23) Use lower case for “Recovery Combat Round”. This correction is applied twice in this rule (line 2 and then again line 7). Rationale: grammar correction. TDF 12/1/25.
(332.231) Replace “(556.3)is” with (556.3) is” (i.e., add a space). Also, replace “then Sequence of Play” with “the Sequence of Play” Rationale: grammar correction. TDF 12/1/25.
(332.231) Use lower case for “Recovery Combat Round”. Rationale: grammar correction. TDF 12/1/25.
(332.232) Accepted Offer: drop the words 'form and' these are unnecessary to say players know they have to form a battle line to fight. L Bergen 12/1/25
(332.232) Use lower case for “Recovery Combat Round”. Rationale: grammar correction. Also, remove “see (634.111) for the forces that the WYNs can use in this special battle round.” This is extraneous and will be covered in a specific scenario. TDF 12/1/25.
(332.233) Withdrawal Restriction: the word 'force' should be 'forces' plural as it is more clearly referring to both sides. L Bergen 12/1/25
(332.24) DISABLED FLEET FORMATION: the words 'forces form' should be 'force forms' more clear and correct as it is only one disabled force at a time that can move through the barrier and would be involved in this combat. L Bergen 12/1/25
(332.24) Use lower case for “Recovery Combat Round”. Rationale: grammar correction. TDF 12/1/25.
(332.25) ADVANTAGE FLEET FORMATION: TYPO missing 'D' should be (331.25) ADVANTAGED FLEET FORMATION: L Bergen 12/1/25
(332.25) Use lower case for “Battle Force” (two instances). Rationale: grammar correction. TDF 12/1/25.
(332.251) Use lower case for “Battle Force”. Also do not use capitals for “Recovery Combat Round.” Rationale: grammar correction. TDF 12/1/25.
(332.253) Internal Cluster Battle Forces: The advantaged force first forms its primary battle force to engage the barrier-disabled battle force created under (332.24). After this is done, the advantaged force may choose to form a second, legal battle force called the bonus battle force. The bonus battle force may only attack barrier-disabled units that were not part of the original barrier-disabled battle force under (332.24) and were not crippled during the primary battle. The barrier-disabled force cannot form a battle force to oppose this attack, as they remain too sluggish and disorganized after crossing the radiation barrier to mount meaningful resistance. Both primary and bonus advantaged forces would benefit from any operational early warning networks present, see rule (537.3).
Rationale: The rule was wordy yet incomplete, we reformatted it and added the line about the EWN. Used lower case for “Battle Force” (8 instances) grammar correction. STAFF 12/1/25
(332.253) Replace rule text with the following;
(332.254) Primary Battle Force: Replace this text with the following: "The advantaged force’s primary battle force engages the barrier-disabled battle force formed under (332.24). Both sides resolve combat using modifications of (332.4) and resolve all damage according to the procedures in (332.5)."
Rationale: More direct writing and correction of rule reference. Notably the last rule reference was wrong as (332.4) and should be (332.5) reflected in the rewrite above, it correctly references damage procedures. Used lower case for “Battle Force” (2 instances). Rationale: grammar correction. TDF 12/1/25.
(332.255) Bonus Battle Force: Replace this text with: "Immediately after primary battle damage is resolved, the WYN bonus battle force determines and resolves its damage against any remaining barrier-disabled units not included in the original battle force under (332.22) and not crippled in the primary battle. The damage procedures of (332.5) apply."
Rationale: More direct writing and correction of rule reference. Notably the last rule reference was wrong as (332.4) and should be (332.5) reflected in the rewrite above, it correctly references damage procedures. Used lower case for “Battle Force” (3 instances). Rationale: grammar correction. Staff 12/1/25.
(332.256) WYN Internal Use Only: Only non-barrier-disabled WYN units may form a bonus battle force as they specifically plan and train to exploit their home field advantage inside the Cluster. No units allied to the WYN may be used in this bonus force. The bonus battle force is only used against forces entering the Cluster; it is not used against forces exiting the Cluster.
Rationale: Use lower case for “Battle Force”. Rationale: grammar correction. STAFF 12/1/25.
(332.256) WYN Internal Use Only: replace this text (intent and clarity) with:
(332.313) Drone Bombardment Units: fill in missing rule references as follows: "They cannot conduct drone bombardment (309.0) or transfer replacement drone bombardment points (509.1-U) during the Barrier-Disabled Combat Round." Lar Bergen 12/1/25
(332.318) Transport Units: missing rule reference is (537.2) Rescue Mission, text should be changed to "...nor can they perform any rescue missions (537.2). "
Rationale: missing rule references added clarity STAFF 12/1/25.
(332.319) X-Ships: replace text with:
(332.319) X-Ships: X-ships retain their EW reduction capability (523.38) however the attrition unit destruction capability (523.32) and mauler effect (523.31) cannot be used. All other restrictions (above) apply to X-ships.
Rationale: This version lets the players know what X-ships can do before laying out the restrictions (this is the pattern of the majority of rules in F&E). L Bergen 12/1/25
(332.33-K) Klingons: They have special restrictions. Replace the word "special" with the word 'several'. This indicates more than one restriction applies. STAFF 12/1/2025
(332.33-K1) example, fifth line: This item should indicate the Sacrifice mission will absorb ‘four’ rather than ‘three’ as we are now rounding up.
Reason correction based upon rule clarification STAFF 12/1/2025
(332.33-K1) fourth line, (rounded down): This item should be (rounded up).
Rationale: ADB (SVC) and staff determined that overall offensive and defensive combat values for everyone should be 50% (rounded up) in Barrier-Disabled Combat. This simulates a crippled unit effect without actually crippling the ship and destroying the balance of combat. As such the Penal ships should follow this structure as to not confuse the players when using the Klingon Penal ship Sacrifice mission. STAFF 12/1/2025
(332.33-K1) rule reference (@@@): This item should be (528.41) referencing the Sacrifice mission. Also Capitalize the Sacrifice mission. STAFF 12/1/2025
(332.33-O) Strike this as it is irrelevant. STAFF 12/1/2025
(332.33-R) Romulans: Cloaking devices (@@@) and cloaked decoys (@@@) are not functional. Add missing references cloaking devices (306.0) and cloaked decoys (538.0).
STAFF 12/1/2025
(332.33-T) Tholians: They have special restrictions. Replace the word "special" with the word 'several'. This indicates more than one restriction applies. STAFF 12/1/2025
(332.33-V) Vudar: Ion storm @@@ did you mean PULSE? generators (327.0) of any type may not be used. Yes! Text replaced as: "Ion Pulse Generators (IPGs) (328.0) of any type may not be used." STAFF 12/1/2025
(332.33-Z) Kzinti, rule reference, 1st line: This item should add a rule reference after the words ‘bombardment points’. The reference to be added is (309.41). STAFF 12/1/2025
(332.41) ADJUSTED COMBAT POTENTIAL: Barrier-disabled units have their individual attack and defense factors reduced by 50% (round fractions UP) before the total combat potential is calculated. All other conditions of (332.0) apply.
Rationale: This aligns with the way SVC designed the game in terms of the way crippled values are calculated. This also aligns the application for barrier-disabled combat 'temporarily crippled' concept without introducing other complications or balance issues. All was discussed, diagramed, heavily combat-tested (4 possible methods), and finally agreed upon 17 OCTOBER during STAFFCON in Amarillo. STAFF 12/1/2025
(332.41) COMBAT POTENTIAL: should be replaced with the corrected version as follows:
(332.42) Change “…a (+2) BIR die roll…” to “…a (+2) combat roll…” Also change “…a (-1) BIR die roll penalty.” With “a (-1) combat roll penalty.” Rationale: clearer effect, as technically the BIR is selected by the two sides and not rolled. TDF 12/1/25.
(332.43) SMALL SCALE COMBAT (SSC): drop words 'ships are "crippled" and their' so it reads as follows; "The barrier-disabled battle force is affected by (332.41)."
(332.431) SSC Qualification: first line change to "The qualifying limits on offensive and defensive points outlined in Small Scale Combat (310.11) are based upon pre-adjusted combat potential." This change offensive and defensive limits is confirmed in the referenced rule (310.11).
(332.432) Limited Casualty Options: The barrier-disabled player may not resolve casualties under (310.33) against fighter factors. They may resolve casualties against PFs if they have deployed them. Neither player may select a retreat option as a casualty under (310.32).
(332.432) No Retreat Option: replace text of rule with:
(332.5) DAMAGE PROCEDURES should be (332.5) MODIFIED DAMAGE PROCEDURES
This matches the writing in (332.4) setting the rule apart from normal combat and damage procedures except where called out in the rule itself.
(332.51) DAMAGE ALLOCATION and its sub-rules need to be moved down and renumbered to (332.52) swapped with the DIRECTED DAMAGE ATTACK PROCEDURES.
Rationale: The basic set (302.6) lays the groundwork and SOP step order for how damage is allocated and the rules as written are out of sequence. This is STEP 6.
(332.51) DAMAGE RESOLUTION needs to be renamed to (332.51) DAMAGE ALLOCATION. This aligns better with nomenclature of basic set rules and procedures.
(332.511) Directed Damage Restrictions: Corrected the rule number to (332.511) AND add rule reference (302.5) after the last word 'attack'.
(332.511) Use lower case for “Battle Force”. Rationale: grammar correction. TDF 12/1/25.
(332.512) Vulnerability Attack: The advantaged player may use a directed damage attack known as a vulnerability attack. This attack does not count as the player's one permitted directed attack. The advantaged player may use this extra attack to target any barrier-disabled unit in the hex, even if not included in the current Battle Force. If the target chosen is in the formation position, the attack is conducted at 2:1. If the chosen target is an escorted group or a breakable group, the escorted unit (carrier or other eligible unit) is protected at 2:1, but its escorts are attacked at 1:1. All other eligible targets are attacked at 1:1. Maulers gain no benefit in this attack, see (332.524).
Rationale: eliminated wordiness and added Mauler cross references L Bergen 12/1/25
(332.512), (332.513), (332.514) & (332.515): Use this revised language for clarity and better flow of how these four rules interact (added a new rule for dealing with the additional directed damage attacks already in the rules and added some clarity for mauler/X-mauler units.
(332.513) Follow-On Directed Damage Attack: The advantaged force may then immediately perform a follow-on attack using damage points that remain after the vulnerability attack. This attack does count as the player's one permitted directed damage attack. The advantaged player may use the follow-on attack to target one or more of the barrier-disabled units in the hex, even if not included in the current Battle Force. If the target chosen is in the formation position the attack is conducted at 3:1. If the target chosen is one escorted group or breakable group. The player may target the entire group attacked at 2:1, or may target the outer escorts of a group, plus any interior ad hoc escorts of that group, but not the carrier separately. All other eligible targets are attacked at 2:1. Maulers can be used in this attack, see (332.524).
Rationale: eliminated wordiness and added Mauler cross references L Bergen 12/1/25
(332.514) Attacking Maulers: No additional benefit is given to maulers attacking any barrier-disabled units at 1:1 during the vulnerability attack. However, maulers and X-ships using their mauler effect may gain their usual benefits when attacking any barrier-disabled unit during the follow-on attack. X-maulers have additional benefits, see (329.3). The limits on maulers using their directed-damage attacks on units in the formation position (308.45) still apply.
Rationale this rule was missing reference to X-Maulers added in TO. L Bergen 12/1/25
(332.515) Additional Directed-Damage Missions: The vulnerability attack does not count as a specific exception to the one allowed directed-damage attack under (302.51). As stated, the follow-on attack would count against this limit. Additional directed damage attacks may be performed depending on what units were included in the advantaged battle force. All additional directed damage attacks permitted by X-maulers (329.31) and against ships conducting commando assaults (521.373); penal units (528.0) included in a battle force; stasis ships that used their SFG (312.24); occur on a case-by-case basis as permitted by their rules.
Rationale: Added this rule because of the requirements in (329.3) TO for X-Maulers L Bergen 12/1/25
(332.61) Use lower case letters for “Recovery Combat Round”. Rationale: grammar fix. TDF 12/1/25.
(332.62) Use lower case letters for “Operational Movement”. Rationale: grammar fix. TDF 12/1/25.
(332.62) Use lower case letters for “Recovery Combat Round”. Rationale: grammar fix. TDF 12/1/25.
(506.0) OFF MAP : PAGE BLOCK Original: (506.0) OFF MAP should not have parenthesis or a decimal place in this PAGE BLOCK format.
Reason PAGE BLOCK at bottom is in incorrect format as compared to the rest of the book. L. Bergen 12/1/25.
(506.31) Resolve issue in red. SVC Asked [‡ = rules not in basic set, delete this mark?@@@]
Staff Answer: Yes, these marks can be removed as this is a Civil War page not a basic set page. STAFF 12/1/25.
(506.5) Line four. Original: “The Gorn player must play two EPs…” the word “play” should be “pay”. Suggested “The Gorn player must pay two EPs.”
Rationale: Typo Fix Lawrence Bergen 12/1/25.
(506.6) Replace “…off-map areas; other…” with “…off-map areas. Other…” Rationale: Correct run-on sentence. TDF 12/1/25.
(506.61) Original: “…expanded area map that includes all the notional off-map provinces…” suggested remove ‘the’ so it says “…expanded area map that includes all notional off-map provinces…”
Rationale: Clarity / Flow Improvement, “the notional” reads awkwardly. STAFF 12/1/25.
(506.62) Original: “Units are able to move freely within the expanded areas.” passive/wordy suggest replace with, “Units may move freely within the expanded areas.
Rationale: Simplicity and Flow Lawrence Bergen 12/1/25.
(506.621) Original: “the impassable zones of a civil wars map…” the issue is “civil wars map” should be “civil war map.”
Suggested “the impassable zones of a civil war map…”
Reason: Fix Typo / Pluralization. STAFF 12/1/25.
(506.621) Replace “…game; this…” with “…game. This…” Rationale: Correct run-on sentence. TDF 12/1/25.
(506.641) Original: “Thus, an expanded area is no longer treated as a ‘second main grid’ under (413.1) as there are no revenue-producing sources outside of the given map.” This needs a comma after the rule reference for readability. Suggested Fix: “Thus, an expanded area is no longer treated as a ‘second main grid’ under (413.1), as there are no revenue-producing sources outside the given map.”
Reason: Clarity and Flow
(506.66) Original: “This is not done during civil wars scenarios.” suggested fix: “This is not done during civil war scenarios.”
Rationale: “civil wars scenarios” is incorrect pluralization. Lawrence Bergen 12/1/25.
(506.66) Replace “…original F&E can…” with “…original F&E game can…”
Rationale: clarification. TDF 12/1/25.
(506.67) Replace “…in original F&E …” with “…in the original F&E game…” Rationale: clarification. TDF 12/1/25.
(554.0) Several times in this passage the word “barrier” is not capitalized. To be consistent with use in other rules, suggest replacing each instance of ‘the barrier’ with ‘the Barrier.” TDF 12/1/25.
(554.0) WYN SPECIFIC RULES, 2nd paragraph last line says correctly, 'just another cluster' and it should be lower case to reflect the idea that it was mundane. This is the exception to the rule of grammar where all instances referring to "the WYN Cluster", AKA "the Cluster" should be capitalized. No change needed but want to point out this is the one exception I found in the book. Lar Bergen 12/1/25
(554.117) Replace the first sentence with the following: “Inside of the Cluster, the WYN collect salvage according to (556.415).” Rationale: Salvage is not “normal” – WYN get both invader salvage and their own per indicated rule. TDF 12/1/25.
(554.231) Replace (@@@) with (556.11). Rationale: Rules reference. TDF 12/1/25.
(554.232) Replace “… May produce…” with “They may produce…” Correct lack of subject in sentence. TDF 12/1/25.
(554.323) Delete red text and rules reference. Rationale: Not needed. TDF 12/1/25.
(554.334) Do not capitalize “Alternative Conversion Facility). Rationale: Grammar fix. TDF 12/1/25.
(555.12) Replace the very last colon with a period. Rationale: Grammar fix. TDF 12/1/25.
(555.131) Delete the second sentence. Rationale: Unnecessarily redundant. TDF 12/1/25.
(555.133) Replace the semicolon with a period and then capitalize the next word “see”. Rationale: fix run-on sentence. TDF 12/1/25.
(555.142) Suggest deleting the entire rule. It is incomplete, as indicated by the red text, and not relevant to any of the Civil Wars scenarios. TDF 12/1/25.
(555.1511) Replace “They” with “The HUC/HUB”. Rationale: Referring to a ship, not a group. TDF 12/1/25.
(555.22) Replace colon with a period. Rationale: Grammar fix. TDF 12/1/25.
(555.23) Modify the last sentence with, ‘The WYNs could use their limited number of “combat” auxiliary pods (712.131) to build jumbo or heavy auxiliaries, see WYN OOB for limitations and WIYN SIT for cost. Players could use generic or borrowed counters available from the web store. Rationale: Missing Reference and updated rule text. Also suggest an update to rule 549.0 in Civil Wars for Aux Pod and building of LAC/SAC’s on Zulu. 12/1/25 L. Bergen 12/1/25.
(555.323) Suggest adding the following at the end of the sentence before the period: “…without the additional surcharge under (305.45).” Rationale: Conversion to a variant is already permitted by (305.45), so clarify the intent that it’s easy for the Orions to convert such a ship. TDF 12/1/25.
(555.442) Do not use italics for the word “not”. Rationale: Unnecessary emphasis should be avoided. TDF 12/1/25.
(555.443) Last line Replace “…status; this…” with “…status. This rule…” Rationale: fix run-on sentence and ambiguity created by indefinite pronoun. TDF 12/1/25.
(556.13) Delete the (@@@) – no immediately apparent reference to add. TDF 12/1/25.
(556.222) Replace “a ships” with “a battle force”. Rationale: correct grammar and clarify what is needed. TDF 12/1/25.
(556.223) Replace “…rules; i.e., auxiliaries…” with “rules. Auxiliaries…” Rationale: correct run-on sentence. TDF 12/1/25.
(556.233) Replace “…battle round; in that case,…” with “…battle round. In that case,…” Rationale: correct run-on sentence. TDF 12/1/25.
(556.3) In the last sentence, replace “… conquer one prefecture before attacking others.” With “…conquer prefectures in an order defined below.” Rationale: Prevent confusing interpretations of (556.30) et. seq. TDF 12/1/25.
(556.30) Do not capitalize “Movement Phase.” Do not capitalize “Combat Procedure.” Do not capitalize “Combat Phase.” Rationale: Grammar fix. TDF 12/1/25.
(556.305) Do not capitalize “Recovery Combat Round.” Rationale: Grammar fix. TDF 12/1/25.
(556.306) Replace the sentence with the following (underlines show changes). “If the invading force retreats through the Barrier, then the invading force goes to the same hex from which it entered the Cluster.” Rationale: capitalize “Barrier” for consistency throughout document. Remove indefinite pronoun “it” and replace with definite reference. TDF 12/1/25.
(556.31) Replace “…has by definition entered…” with “has, by definition, entered…” Rationale: clearly set forth dependent clause. TDF 12/1/25.
(556.311) Do not capitalize “Protecting Force.” Rationale: Grammar fix. TDF 12/1/25.
(556.316) Add the following to the last sentence in the second paragraph. “… to a battle, but such drone bombardment ships are in the support echelon and accordingly may be attacked using directed damage.” Rationale: The rule mentions they’re in another prefecture, but generally DB ships are in the support echelon and can be attacked at 3:1. TDF 12/1/25.
(556.316) Alternate strike of the portion of the rule "Drone bombardment ships from another prefecture could contribute to a battle. An invading force could use any drone bombardment unit he owns within the cluster hex to contribute to any one battle per combat round."
Reason: This violates the requirement for the ship to be in the support echelon, and the possibility that the opposing force can normally apply directed 3:1 damage against the drone ship. We already allow the ships to travel/transfer from prefecture to prefecture to the combat location (so these things can happen) so they could just do that. Lar Bergen 17 Oct 2025
(556.316) move the following sentence and create: (556.14) PROTECTING FORCES: The protecting force consists of the forces in that prefecture but can include ships and independent fighter/PF units from other prefectures.
Reason: This is a definition of Protecting Forces and should be moved to (554.13) a new definition. Lar Bergen 17 Oct 2025
(556.316) Strike the following "(This is a tactical decision. Most invaders would probably elect to attack the planets one at a time, but the invading force has enough ships to mount two attacks, nothing stops him from doing so.)"
Reason: This leads to a tactical note which is fun for players to write, let’s let them do so. Lar Bergen 17 Oct 2025
(556.316). Add the following sentence at the very end of the first paragraph. “Note the drone bombard limitations of (556.411) (i.e., the requirement of a drone bombardment tug (509.1-U)).” Rationale: Players may wrongly assume that DB ships work normally in the cluster – they do, but only if they have a supply of drones. TDF 12/1/25.
(556.317) Unresolved Damage Points: replace text with the following: “If there are plus or minus points from an approach battle, then these points are divided equally between any undevastated planets in the same prefecture as per (308.253). If there are no such planets, the plus or minus points remain in that prefecture until used in a later combat round or the Combat Phase ends (at which point they disappear). Points from all prefectures are added to the pursuit battle.”
Reason: more complete and added rules reference. Lar Bergen 17 Oct 2025
(556.32) "There are four prefectures. An invader enters the one that geography defines, and must conquer it (i.e., devastate both planets and destroy all bases/PDUs) before moving to another prefecture." Replace with: “There are four prefectures in the WYN Cluster, see map. An invader enters the border prefecture defined by (556.30). The invader must suppress that prefecture (i.e., devastate both planets and destroy all bases/PDUs) before moving to another prefecture.”
Reason more complete description, clarity Lar Bergen / TDF 17 Oct 2025
(556.32) Delete extra space between “will” and the comma, in the third-to-last line of the paragraph. Rationale: typo fix. TDF 12/1/25.
(556.321) Change the semicolon in the 1st sentence of the 2nd paragraph to a period and replace the immediately following “I.e.” with “Thus, ….” Rationale: Grammar fix. TDF 12/1/25.
(556.321) Do not capitalize “Combat Phase” (2 instances). Rationale: Grammar fix. TDF 12/1/25.
(556.321) Replace the last sentence with the following. “The invading force may leave some ships behind in the suppressed prefecture. The defending force may then send ships to fight such ships in the suppressed prefecture.” Rationale: The WYNs might not be stupid to do so. If the invaders were stupid (e.g., left cripples in the suppressed prefecture) then the WYN might have a reason to go there. Also new language is more clear. TDF 12/1/25.
(556.321) The first sentence is redundant with (556.32). Suggest deleting the first sentence and replacing the second sentence as follows: “The invading force, after suppressing the required initial prefecture, moves ships to the approach battle block(s) of one, two, or all three of the other prefectures.” Rationale: Replace redundant and confusing language with clear language. TDF 12/1/25.
(556.332) Delete “in any case.” Rationale: unnecessary wordiness. TDF 12/1/25.
(556.342) FINAL CLUSTER ENGAGEMENTS: When all bases and PDU/PGB/FDU units within the Cluster have been destroyed and all planets have been devastated, the invading force must either offer combat or retreat from the Cluster. The invader may direct their forces against one or more planets. The defender is required to fight at only one such planet and may choose which planet(s) to defend. If the defender declines to engage at any planet, they must retreat from the Cluster.
Rationale. Nowhere else in the rules are the requirement to retreat presented as conditions like this. L. Bergen 18 OCT 2025
(556.342), (556.3421), (556.3422) (556.3423) replace all four rules with:
(556.37) Add a comma after the word “hex.” Rationale: clarity. TDF 12/1/25.
(556.41) Do not capitalize “Movement Phase.” Rationale: grammar. TDF 12/1/25.
(556.416) After the sentence, add the following: “See (209.144).” Rationale: Ensure consistency of no-pursuit rule for any side (not just invaders). TDF 12/1/25.
(556.62) In the second paragraph, 1st sentence, replace the semicolon with a period and capitalize the next word (Remaining). Rationale: fix run-on sentence. TDF 12/1/25.
ZZZ End of STAFF review of Civil Wars, version sent by SVC on 11/26/25.

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:42 pm: Edit

(115.2) 332 Barrier Disabled Combat should read: 331.0 Barrier Disabled Combat. Reason: (330.0) Flexible Command Points is the last combat rule published in Tactical Operations. Thomas Mathews 28 Nov 2025

(115.7) Asset neutrality rules: 660 should read: Asset Neutrality Rules 660.0 Reason: 660.0 covers all of the Asset neutrality rules. Thomas Mathews 28 Nov 2025

(115.7) Civil wars territory rules: 659 should read: Civil wars territory rules 659.0 Reason: 659.0 covers all of the Civil wars territory rules. Thomas Mathews 28 Nov 2025

(115.7) Influence points: 658 should read: Influence points: 658.0 Reason: 658.0 covers all of the Influence points rules. Thomas Mathews 28 Nov 2025

(115.7) Interned by the WYN: @@@ should read: Interned by the WYN: 449.22 and 503.1 Reason: (449.22) covers the sale of a small number of ships to the WYN by the neighboring empires and how to handle anything outside of (449.22) when playing with Planetary Operations. If not playing with Planetary Operations then (503.1) covers those ships. Thomas Mathews 28 Nov 2025

(115.7) Overloaded Tugs: @@@ should read: Overloaded Tugs: 517.4 Reason: (517.4) covers Overloaded Tugs. Thomas Mathews 28 Nov 2025

(115.7) Territory rules for civil wars: 659 should read: Territory rules for civil wars: 659.0 Reason: (659.0) covers all the territory rules for empires in civil wars. Thomas Mathews 28 Nov 2025

(332.0) (332.0) Barrier-Disabled Combat should read: (331.0) Barrier-Disabled Combat. Reason: (330.0) Flexible Command Points is the last combat rule published in Tactical Operations. All subsequent rules with (332.x) should be renumbered as (331.x) Thomas Mathews 28 Nov 2025

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:43 pm: Edit

My apologies, one of my suggested edits still has a minor error. Please ignore the comment above in 637.533 (dealing with KR parts). "The Rolandus" is awkward. Instead, please use the following comment (which replaces "Rolandus" with "Imperial faction"):

(637.533): Replace “; more parts can be obtained under (442.8)” with “. The Imperial faction may use cargo transports (e.g., tugs, LTTs, TTs, APT, PTR) to obtain more parts from the Klingons under (442.8) though the Klingons do not send any KR parts on their own accord.
Reason: Confusing to say Klingons don’t obtain parts, but then say they can be obtained by a rule that permits the Klingons to send parts. Additionally, the semicolon should be replaced by a period and two sentences presented instead of one run-on sentence.

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:43 pm: Edit

(637.0) ADD to BY LINE: Lawrence Bergen
(637.0) Narrative Introduction (four edits suggested within this section)
1. Suggested structure replacement: “When the armistice ending the General War (GW) was announced, a faction of disgruntled officers on the Romulan capital planet, Romulus, launched a coup that overthrew the Praetor and Emperor.”
2. Missing comma before 'which', suggested edit: “The rebels formed a new government, which they named the Romulan Republic.”
3. Stronger format suggested: “Incensed by the rebels, Proconsul Rolandus declared himself emperor and led his fleet in an effort to restore the empire.”
4. Last line (more precise) edit suggested:“…he was also at a disadvantage because he had few large ships.”
(637.1) – Scenario Setting: Original: “There are two players: The Romulan Republic faction and the Imperial Romulan faction.”
Rationale: “the” should not be capitalized unless referring to a proper noun.
Suggested edit: “There are two players: the Romulan Republic faction and the Imperial Romulan faction.”
(637.13) AREA OF CONFLICT: “Romulan annexed” should be hyphenated if used as a compound adjective (Romulan-annexed).
Suggested: “…including the Romulan-annexed neutral zone hexes..."
(637.14) SETUP ORDER: replace first line; The historical placement (637.4) does not require a placement order with suggested: “The historical placement rules (637.4) do not require a placement order.”
(637.15) MODULES USED: “...This scenario also assumes usage of the following modules…”
Suggested smoother wording: “assumes the use of.”
“This scenario also assumes the use of the following modules…”
(637.16): replace “and/or” with “or.”
Reason: grammatically cleaner with same meaning in context.
(637.161): use lowercase for “territorial rules,” instead of upper case.
Reason: grammar correction.
(637.162): Use lowercase for “asset neutrality,” instead of upper case.
Reason: grammar correction.
(637.2) – Scenario Notes: Original: “All empires agreed to leave the territory of their former enemies and to withdraw to their own territory.”
Issue: Repetitive use of “territory.”
Suggested: “All empires agreed to leave the territory of their former enemies and withdraw to their own space.”
(637.21) ASTRO-POLITICAL ENVIRONMENT: Original: “Even though the fleets likely to face the ISC coolly supported the Republic (since Rolandus enjoyed secret and widespread support within the Republican Star Navy)…”
Issues: Long, complex sentence with nested parentheses. Also “coolly supported” is vague.
Suggested revision: “Although the fleets likely to face the ISC nominally supported the Republic (despite Rolandus having secret and widespread support within the Republican Star Navy) the uncertainty of ISC intentions required them to focus on their primary duty: defending the Romulan people and their territory.”
(637.21) ASTRO-POLITICAL ENVIRONMENT: Original: “…Romulan intelligence sources detected a massive build-up along the entire ISC frontier.”
Suggested replacement: “build-up” replace with “buildup” (standard noun form).
(637.242): Replace “Add a MB which has been setup” with “Add a setup MB.”
Reason: more concise.
(637.243): Add the word “and” after “Condition D (Basing Support)”
Reason: grammatically more correct.
(637.253): Change “Established simultaneously…” with “Established simultaneously with Cordon Bravo…”
Reason: leaving “simultaneously” by itself is confusing (i.e., simultaneous with what?). Correction removes ambiguity.
(637.271) last sentence. Replace “are converted” with “is converted.”
Reason: Grammar correction since the verb refers to “each one,” and therefore is singular.
(637.275) Using Influence Points: This rule is numbered incorrectly and should be (637.273).
(637.282) first sentence. Add “during the damage coefficient roll.”
Reason: Confusing, ensure that the VBIR roll will not be used.
(637.283) Defecting Unit Selection: 2nd paragraph,
Replace with, "The defecting unit is immediately transferred to the opposing battle force, without regard to command limits. The defecting unit functions normally for the gaining side for the remainder of that combat round. Beginning with the next combat round, the defecting unit is treated the same as the original units of the gaining side and is subject to all standard requirements and restrictions including command limits."
(637.422) first sentence. Change “Seltorian War” to “Seltorian war” (i.e., uncapitalize “war”.
Reason: Grammar. The sentence refers to a war with the Tholians, and not the proper name for that war. The alternative would be to change the sentence as follows: “serve as a firewall against the Seltorian War fought between the Seltorians and the Tholians.”
(637.512) last sentence. Change “decades at war” to “decades of war.”
Reason: Grammatically more correct. The alternative is “being at war,” which is not as succinct.
(637.513): CHANGE TO READ: They are subject to either capture or dispute per the Civil War Territory Rules (659.0).
(637.533): Replace “; more parts can be obtained under (442.8)” with “. The Rolandus may use cargo transports (e.g., tugs, LTTs, TTs, APT, PTR) to obtain more parts from the Klingons under (442.8) though the Klingons do not send any KR parts on their own accord.
Reason: Confusing to say Klingons don’t obtain parts, but then say they can be obtained by a rule that permits the Klingons to send parts. Additionally, the semicolon should be replaced by a period and two sentences presented instead of one run-on sentence.
(637.551): At the end of the last sentence change “of play (105.0.)” with “of play (105.0).]
Reason: Corrects typos.
(637.553): In the two bulleted rules, replace the semicolons with periods.
Reason: Correct grammar typos.

(637.623): The word “inclusive” should be in parentheses to be consistent with the use in Rule 637.613.
Reason: Consistent grammar choices.

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:45 pm: Edit

PAGE ONE

BBS Crew: Suggest add to list: Todd Lovas, Jimi Laform (both were play testers for the scenarios Lyran CW and Rom CW).
Question for ADB: Is there a way to pull additional names who have chimed in on the BBS over the past 2-3 years? Some of the more recent folks seem to be missing.


PAGE TWO

(115.7) DEFINITIONS LIST, Line 1 says, "This is an extract to Annex (###) Index."
The missing rule number is: 900 INDEX.

Other changes to (115.7) index entry list are presented as notes.

Influence points:” 658
Note: Suggest removal of quotation marks. Seems a typo.

Interned by the WYN: @@@
Note: The missing rule numbers are: (209.142), (209.152), (556.62) also note Internment rules are under (503.11), (503.4), (503.65). Internment is in many places so it depends if we are looking for a definition or situation enabling the internment (there are several).

Middle Years special rules: 657.0
Note: Suggest removal of the word special as its simply just "Middle Years rules:" and adding the word special doesn't really help players find the entry. The rule number is correct.

Overloaded Tugs: @@@
Note: The missing rule number is: (517.4) OVERLOADED TUGS.
BTW the online Warbook Annex is incorrect showing (514.4) when it should be (517.4).

Special rules for Middle Years: 657
Note: Suggest we remove this entry. The word 'special' has been applied to many rules and listing it with the word special as the lead becomes non-specific and wouldn't actually help a player find rules about the Middle Years (in this case), most likely look at the M section of the index first with a printed book and use CTRL-F search function for Middle Years on the PDF.

Special rules for WYN: 554.0
Note: Suggest we remove this entry. The word 'special' has been applied to many rules and listing it with the word special as the lead becomes non-specific and wouldn't actually help a player find rules about the WYN (in this case), most likely look at the W section first with a printed book and use CTRL-F search function for WYN on the PDF.

WYN special rules: 554.0
Note: Good lead. Players would look at the W section of the index first and find this entry. Curious why it was changed from WYN Specific Rules though. (yes I am a nut)

Lar's soapbox: Note on the use of the word 'special'. There is a real effort to restore the importance of the word special and shift the dynamic away from noting something as 'special' as it has become a general term. The rules in most cases are just the rules and in many cases can be more defined in terms of specifics.
For instance some rules noted as special are actually definitions, restrictions, prohibitions, or exceptions to the rules. The staff has made an effort, since revisions began, to work with ADB and standardized or further define these rules with headers and some clarified writings. The main reason is to reduce the 'at the table' rules-lawyering and reduce the burden of BBS support by ADB staff to answer questions by the players.

(The word special has grown tremendously within the game and is now used over 325 times throughout the published rule books, not including the 600 Scenario section, or the upcoming Civil Wars product). A good portion of the occurrences are in the basic boxed set rule book and will be addressed soon. The Staff teases Lar (in good fun) that he knows this fact.


PAGE THREE

(209.113) Transiting Ships: Reorder the rule to say the following:
"Friendly ships may enter the Cluster once per turn and exit the Cluster once per turn, total, by any means. Any unit that attempts a third transit in the same turn is instantly destroyed. Friendly ships include ships allied with the WYN (556.7), ships conducting trade with the WYN (449.0), and ships conducting authorized blockade runs, as well as other units permitted by the WYN."
Rationale: Flow of rule was split by definition of "friendly ships". Reorder fixes this flow.

(209.114) Attrition Units: Modify 2nd line, 'transition' with "transit" as follows:
Fighters and PFs cannot move through the barrier. Fighters and PFs on a carrier or tender may transit with their host unit.
Rationale: “transition” (indicates change) → should be transit (movement through barrier)

(209.114) Attrition Units: Replace third line which says 'Drone bombardment cannot be conducted through the barrier.' with the following: "No drone bombardment can be conducted through the barrier."
Rationale: Clarifies limits and leaves no room for questioning the intent. Current was technically correct but could be misread.

(209.115) Slow Units: Correct 'tugs' to "transports" and Add rule reference number as follows:
“overloaded tugs” is incorrect and should, appearing for this first time, as “overloaded transports (517.4)”

(209.124) Slow Units: Correct 'overloaded tugs' to "overloaded transports".
Rationale: Accuracy

(209.133) Slow Units: “overloaded tugs” is incorrect and should appear as “overloaded transports (517.4)”
Note: Rule number reference is SVC's call to keep here or not staff was undecided.

(209.134) Unavoidable Combat: Missing hyphen for 'barrier-disabled' combat.
Rationale: Maintain consistency.

(209.143) Prohibited Units: wordy and missing a rule reference, replace with the following:
"Slow units, including auxiliaries and overloaded transports (517.4), may not retreat into or out of the Cluster and are destroyed if they attempt to do so. An overloaded transport may drop pods to enable retreat under (517.26)."
Rationale: Cleaned up language and added missing rule reference.

(209.153) Prohibited Units:, suggest replace with the following:
"Slow units, including auxiliaries and overloaded transports (517.4), may not retrograde into the Cluster. An overloaded transport may drop pods under (517.26) to enable retrograde into the Cluster. Fighters or PFs must be carried on ships in order to retrograde through the barrier."
Rationale: Cleaned up language and added missing rule reference.
Note: Fighters and PFs - These units must be carried on ships to transit the barrier operationally per (209.114) and the same would be true here. Moved the mention to a stand alone line for flow and clarity.


PAGE FOUR

(209.165) Prohibited Units: wordy and missing a rule reference, replace with the following:
"Slow units, including auxiliaries and overloaded transports (517.4), may not use strategic movement to enter or leave the Cluster. An overloaded transport may drop pods under (517.26) to allow strategic movement into the Cluster."
Rationale: Cleaned up language and added missing rule reference.

(209.2) ROBOT-CONTROLLED MOVEMENT: Slow units (e.g., auxiliaries, convoys of all types, SAFs, ENGs, monitors, and overloaded tugs) cannot transit the WYN radiation zone with a live crew.
Suggest replace 'overloaded tugs' with "overloaded transports" in the first line.

(209.2) Note:, line three, fix typo of 'the cluster' with 'the Cluster'. In fact there are 201 instances of 'the Cluster' or 'the cluster' throughout this document and all but one should be capitalized. I have noted the exception below but for reference it is in (554.0) WYN SPECIFIC RULES, 2nd paragraph last line.

(209.241) Disarmed:, suggest replace 2nd line with: "Their defense factor is multiplied by 50% (fractions round up).
Rationale: We missed providing this edit to SVC in October. In Texas staff agreed with SVC's point that "defense factors should be multiplied by 50% and rounded UP" for simplicity and to follow the ADB established doctrine for odd numbered unit crippling. 1 becomes 1, 5 becomes 3, 7 becomes 4, etc. Allows the option to strike last part "; an original defense factor of “1” would remain “1”." as this would then always be true and not needed as a statement.

(209.242) “directed-damage attacks” hyphening should be consistent, suggest add missing hyphen to first instance.

(209.244) Controlled:, suggest replace with the following version:
"Robot-controlled units must occupy command slots. If their number exceeds the flagship’s command rating, robot-controlled units that are not on the line may still be attacked with 1:1 directed damage. However, the owning player may not voluntarily apply damage to these units."
Rationale: Eliminating long running sentence structure.

(209.25) DEMISE: Replace with entire rewritten rule as follows:
"If abandoned by their fleet, treat the robot-controlled ship as a “slow unit” under (302.742). During the slow unit pursuit round, the pursuing player can choose to forgo the damage roll under (302.42), instead having the pursuing force simply make a capture attempt upon the capture-eligible robot-controlled unit during the Troop Action Interphase. A capture succeeds on a die roll result of 2–7 on (2d6), otherwise, the robot-controlled unit is destroyed. Marine units (521.5) or prime teams (522.43) in the pursuit force could be used to increase the chance of capture."
Rationale for proposed changes:
Fix typo of 'robotcontrolled' s/b "robot-controlled".
Suggest incorporating capture eligibility into the rule.
Suggest adding 'result' to die roll and add clarify 2d6 probabilities in familiar terms.

(209.3) Fleet Repair Dock Exclusion:, last line typo fixes: 'scenrio' should be "scenario" and 'cluster' may need capitalization as "Cluster".

Some General Search notes to the staff from these first 4 pages:
Search for 'robot control' and see if the expected hyphens are missing.
Search for 'barrier disabled' and see if the expected hyphens are missing.
Search for 'directed-damage' and see if the expected hyphens are missing.
Search for 'Cluster' and see if the word cluster has been correctly capitalized when referred to as 'the WYN Cluster' or 'the Cluster'.

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:47 pm: Edit

(115.2) 115.7 Publisher Information should read: 115.4
Reason: About The Publisher rule is 115.4 Thomas Mathews 28 Oct 2025

(115.2) 115.4 Publisher Information should read: About The Publisher
Reason: (115.4) is titled About the Publisher in the sectioned title block. Thomas Mathews 28 Oct 2025

(115.7) This is an extract to Annex (###) Index should read: This is an extract to Rules Index (900).
Reason: The Basic Rulebook has the Index under (900). Thomas Mathews 28 Oct 2025

(115.7) Interned by the WYN: @@@ should read: Interned by the WYN: (449.22).
Reason: (449.2) covers the limitations on ships sold to the WYN, and those ships exceeding those limitations. Thomas Mathews 28 Oct 2025

(115.7) Overloaded Tugs: @@@ should read: Overloaded Tugs: (517.4).
Reason: (517.4) is the rule section for overloaded Tugs. Thomas Mathews 28 Oct 2025

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:48 pm: Edit

(638.0) WoR Scenario Line Item (2) 10.24.25

(638.265) Edit to Pool: Add plus signs between the carrier and escorts to show they are together as well as adding square brackets around the Carrier and escorts as follows:
BRH, BPF, [CVS+BRE+DWE], MR, DW, DW.

(638.512) Typo: “6 EPs and 2 XTPs that was smuggled in…” this should be “were smuggled in.”

Style: “All players have no debt.” this could be simplified to “No faction begins with debt.” (smoother phrasing)

(638.513) Typo: “25% percent” is redundant (“25%” or "25 percent" is sufficient).


(638.514) Punctuation: Missing period after reference list: “…generate one EP (659.221)” should end with a period.

(638.518) Minor grammar rewrite: “Commercial convoys, survey, and WYN trade and ship sales, and diplomatic income are not used.” should be rewritten as 'Commercial convoys, survey, diplomatic income, and WYN Trade including ship sales are not used.'

(638.521) Grammar: “For supply grid purposes the notional capital for the Count's faction is their planet at 1001.” Add comma after purposes.

(638.521) Typo: “...and through pro-faction points specified under (638.215) above.” the Reference (638.215) does not exist (check numbering). MARK AS (@@@) until Staff does.

(638.524) Grammar: “twelve homeless ship support lines (which includes one carrier support line)” should be “which include” (plural) or "this includes".

(638.532) Grammar / Typo: “Crown and Count faction ships can roll for DLR and if successful are the ships removed from play…” Should read: “...and if successful, the ships are removed...” (added comma and word order fix).

(638.541) Grammar: “Additionally, Usurper faction can use (502.431)...” should be “Additionally, the Usurper faction” (missing article).

also for Clarity: “Auxiliary unit production is not permitted.” is inconsistent phrasing with other rule restrictions (e.g., “Auxiliary units may not be produced.”) would be better.

(638.543) Add rule reference (659.17) as follows: "Barony minor shipyards under the control of any force (659.17) can only...".

(638.551) Typo: “use offensively cloaking” should be “use offensive cloaking.”

(638.551) Punctuation: “revealed simultaneous” should be “revealed simultaneously.”

(638.553) Typo: “capital assaults actions” → redundant, should be “capital assault actions.”

(638.561) Grammar: “Subtract 3...; Subtract 2...; Subtract 1...; Add one...” — consistent style but inconsistent numeral form (mix of digits and words). Use either all numerals or all words for modifiers. “Add one” should be “Add 1” for consistency.

(638.563) Grammar: “can be crewed and used immediately and repaired normally” awkward; remove phrase "crewed and” for better flow. "...can be used immediately and repaired normally..."

(638.564) Duplication: Rule number (638.564) appears twice. (638.564) Ownership: should be renumbered (638.565).

(638.572) Typo: missing 'the'; “permitted by Usurper’s order of battle (712.0)” should be “permitted by the Usurper’s order of battle.”

(638.61) INSTANT VICTORY - last line corrections, "Increase the Usurper level of victory one step for each of condition #6 and #7 met under (638.6X)" should be "Increase the Usurper level of victory one step for each of the conditions #6 and #7 that are met under (638.66) or (638.67)."

(638.62) Grammar: “...if one faction's total score is 150% higher than the other faction's...” this is mathematically ambiguous; clarify as “1.5×”.

(638.64) Typo: “...and assumes the thrown.” should be “throne.”

(638.65) Redundancy: “If the roll is 9 or more...” repeated twice; eliminate and replace the first instance with the second instance. It should now read, "If the roll is nine or higher, the Duke and Marquis end the war. The side ahead on influence points is the winner." and the 2nd paragraph begins with, "Repeat this step at the end of each player turn, adding one to the roll for each subsequent game turn."

(638.66) INSTANT VICTORY - last line corrections, "The level of victory increases by one step for each of condition #6 and #7 met under (638.66) or (638.67)." should be "The level of victory increases by one step for each of the conditions #6 and #7 that are met under (638.66) or (638.67)."

(638.662) Condition #2: Clarity / typo: “Controls the minor planet at 1202 longer than the Republic...” fix typo: “Republic” should be “Crown”.

(638.665) Condition #5: Typo: "Has more..." should be "Have more..."

(638.668) Usurper Victory Levels: Grammar: “The Usurper wins granted a DRAW...” incorrect; should be “The Usurper is granted a DRAW...”

(638.73) Typo: “a faction's at-start order of battle cannot be used for any purpose until they are repaired.” → “it is repaired” (singular).

(638.678) Crown Forces Victory Levels: Grammar: "The Crown Forces is granted a DRAW..." should be "The Crown Forces are granted a DRAW..."

(638.678) Crown Forces Victory Levels: Grammar: "The Crown Forces is DEFEATED..." should be "The Crown Forces are DEFEATED..."

(638.73) Replace "They can move..." line entirely with; "They can move normally, will defend themselves if attacked, but cannot pin opposing units, hold or dispute territory, or garrison for influence points until repaired."


(638.74) NO ISC: Removing the could be seriously unbalancing. For instance: How would we explain the absent Duke or Marquis Fleets dedicated to the ISC? How would we explain the dedicated ISC resources, ships, and income from the Count and Crown?
Thats said, the Staff and I did like the optional idea of an ISC timer....maybe change the name of this rule to (638.74) ISC Intervention: (see next item).

(638.74) ISC Intervention: Beginning on Turn 2, an ISC fleet appears in hex (1506) and moves toward 1401 one hex per turn (at the end of each full turn). When the ISC fleet enters 1401, the scenario (and war) are over and both the
Crown and Liberator lose. (REVIEW AND POV: Staff looked at this and confirmed that the ISC established Cordon Echo in Spring Y187 which is the beginning of Turn 2. Therefore at the end of Turn 2 this fleet could in fact be at the Pacification Base in 1506 and make their first move.
ISC can be represented by a mere Fleet marker with no counter attack on their ships possible by either side (assume its a HUGE fleet) -OR- A fleet OB could be established with rules for ISC replacements. If its desired to add combat flavor and try to stop them. OBVIOUS NOTE: Attacking the ISC fleet if allowed, becomes a distraction and resource sink, that could break the scenario entirely...but these things play fast so what the heck, why not?)

(638.81) SHIPS OR RESOURCES: Typo, "Remove or add a number of ships or resources associated fleet." should be, "Remove or add a number of ships or resources to the associated fleet."

(638.81?) Remove "A Federation squadon of a CH, 2xNCL, NSC, 3xDW, 3x FFG, is allied to one side or the other." It begins in hex (@@@), strike this portion of the rule, per staff review (Mike and Ryan et al) it violates ISC Pacification rules and this force would be either immediately destroyed by scenario rules crossing over or force the ISC to intervene (not in the rules). By history the ISC stayed out of the Kzinti business because it was considred an internal struggle. This makes it an 'externally supported' internal struggle. If this is necessary, Suggestion would be to add a new rule number, (638.84); correct the 'squadon' to "squadron" typo; change the "CH" (FEDs don't have a CH in F&E) to the correct "CB" or even a "CX". Add some sort of technobabble about "skirting the Pacification" to the north or through the OFFMAP and explain how the forces remain in supply or what their cost is to the Federation or Crown Prince.

(638.9) DESIGNER NOTES Reminder to please write these.

By Steve Cole (Stevecole) on Wednesday, December 03, 2025 - 01:49 pm: Edit

WOR Scenario line items: All line items were created except where noted on:
22-23 OCT 2025 L. Bergen

(638.0) TITLE, says “USURPR” and should be ‘USURPER’
Reason: Typo

(638.0) The end of paragraph one has two typos.
The word ‘nobels’ should be “nobles”; ‘Patriach’ should be “Patriarch”.
Reason: Typos.

(638.0) The end of paragraph two has sentences with repeating text. It says, "At first, they were trying to wrangle concessions from the Crown Prince. Once the Usurper began making secret contact with them, they were waiting to see who would emerge victorious. They were waiting for the right moment to pick a side, as backing the wrong candidate could be disastrous while picking the winning candidate could gain political power."

Consider this more condensed version:
"They initially sought concessions from the Crown Prince, but after the Usurper’s covert overtures, they adopted a cautious stance. Choosing prematurely risked ruin; choosing wisely promised power.”
Reason: clarity, more succinct.

(638.0) The end of paragraph three, last line: Remove the comma after 'Federation' as it is unnecessary.
Reason: Typo

(638.11) the listings for both forces need to be altered as follows:

Currently (1), what is says:
The Unified Liberator Forces consist of the Usurper (WYN) faction and his attached Orion mercenaries plus the Count’s faction (use the white on orange counters).
Replace with:
The Unified Liberator Forces consist of the Usurper (WYN) faction, hired Orion mercenaries, and the Count’s faction (use the white on orange counters). The Liberator Forces may be played by either one or two players.

Currently (2), what is says:
The Kzinti Crown Forces consist of the Crown Prince faction (including his Orion mercenaries) plus the Baron’s faction. The Liberator Forces may be played by either one or two players.
Replace with:
The Kzinti Crown Forces consist of the Crown Prince faction, hired Orion mercenaries, plus the Baron’s faction.

Reasons: restructuring both for clarity and flow.


(638.12) SCHEDULED DURATION: has (@@@) looking for a rule reference.
The rule number is rule (638.34) SCENARIO CONCLUSION.
However it should be noted that this rule (638.34) further points the reader to full descriptions of the Victory Conditions found in (638.6).
Reason: Clarity and referencing added.

(638.163) Influence:, change this rule to say the following: “Rule (658.0) is used to influence the Duke and Marquis to support either side, see (638.273).
Reason: Clarity and referencing added.

(638.21) ASTRO-POLITICAL ENVIRONMENT edit please, the first line says: "Once a supply point was secured, the Usurper knew that to claim..." can remove the word 'that' as unnecessary.
Reason: Grammar

(638.21) ASTRO-POLITICAL ENVIRONMENT first line says: "banner and proclaiming his legitimacy, If the Crown Prince would..." the word 'If' need not be capitalized.
Reason: Typo

(638.211) Interior Bases: The paragraph one has two typos.
The word “compliment” should be 'complement'; the word “Map” should be lower case as 'map'.
Reason: Typos

(638.221) Usurper’s Territory and Income: says in the 3rd/4th line: "...(all other cluster income is used for the home defense)" change to say, '(all other income is used for the Cluster's defense)'.
Reason: Clarity

(638.222) Usurper Headquarters: Add ownership into the title to match the other listings as, “(638.222) Usurper's Headquarters:”
Reason: Aligned Ownership

(638.225) Count’s Headquarters: says "The STX at hex 1001 is the Count's provisional capital for his faction and is the hub of their main supply grid."
Replace with: 'The STX at hex 1001 is the Count faction's provisional capital and the hub of their main supply grid.'
Reason: clarity, more succinct.

(638.226) Count Faction Activation: line 4 says: "Usurper; see (638.233) below. Until then, they may not to engage or impede..." remove the word 'to' Reason: unnecessary.

(638.226) Count Faction Activation: last paragraph says: Regardless of the situation with Battle Station Rampart, the Count still collects and uses any income generated by his provinces and planet he controls or disputes with the Crown forces.
Replace with: "Regardless of the situation with Battle Station Rampart, the Count retains control over and collects all income generated by provinces and planets under Count authority or in dispute with Crown forces."
Reason: cleans up typo and is more direct.

(638.231) Crown’s Territory: Line 5 says, "...only planetary income the Crown faction received is from the..." should be 'receives'.
Reason: Typo

(638.233) Crown’s Infrastructure: line says; 1400 (Barony): Four minor shipyards (CM, DW, and 2xFF). instead should spell out the number as follows:
1400 (Barony): Minor shipyards (CM, DW, and two FF).
Reason: cleaner version

(638.234) Rampart Station: Paragraph two (@@@): Add rule number here:
Capturing a base is impossible under (305.5) but this rule forms an exception due to the unique political situation.
Reason: Reference added.

(638.251) Cordon Echo: Line 1, replace: 'Starting in Spring of Y187 (Turn #2), before any player phases, the ISC establishes Cordon Echo that includes territory along the Klingon-Kzinti border.'
'Beginning in Spring Y187 (Turn #2), before any player phases, the ISC establishes Cordon Echo, covering territory along the Klingon–Kzinti border.'
Reason: cleaner statement.

(638.255) Cordon Re-entry: Edit line: "Once the cordon is established by the ISC, any unit from either faction that enters that cordon is removed from play (presumed to be interned or destroyed); it is counted as destroyed for influence points and victory purposes."
Replace with this: 'Once established, any unit of either faction that enters the ISC cordon is immediately removed from play (interned or destroyed). Such units count as destroyed for influence and victory purposes.'
Reason: clarity and strength

(638.256) Non-Interference: Introduced fix for grammar: "The Usurper’s War of Return was regarded by the ISC as an internal Kzinti affair. The ISC therefore abstained from enforcing pacification cordons within provinces 0701 and 0903 until the domestic conflict ended."
Reason: Grammar fix.

(638.261) Limited Orion Actions: reorganize this section as follows: "Orion mercenary units cannot voluntarily enter an unaligned province until that province becomes politically disputed or faction-controlled; once disputed, such units may contest but not control the province."
Reason: clarity and strength

(638.262) Orion Fealty: These should be two sentences 'Mercenary ships of either side cannot be voluntarily crippled in a battle round unless a friendly force ship with a greater uncrippled defensive value is crippled or destroyed first: crippled mercenary ships cannot be included in the selection of any battle force unless minimum force or flagship selection rules require their inclusion.' please rewrite as follows: "Mercenary ships cannot be voluntarily crippled unless a friendly ship with a higher uncrippled defensive value is crippled or destroyed first. Crippled mercenary ships cannot be included in the selection of any battle force unless minimum force or flagship selection rules require their inclusion."
Reason: Clarity and Grammar

(638.263) Mercenary Logistics: replace the entire statement as follows...'Orion mercenaries are treated as friendly units of the contracting empire for all supply, repair, and free strategic movement purposes.'
(Verified with STAFF.)
Reason: Grammar improvement and condensed statement.

(638.265) Additional Mercenaries:
Replace the entire line starting: "Ships are permanently removed from play if their lease is not renewed with no loss of IPs."
with the following… 'Leased ships are permanently removed from play if their contracts are not renewed; no IP loss occurs.'
Reason: Clean, more direct.

(638.2731) Release Ships:
Replace text with:
“During the Production Phase, a phasing faction that controls the headquarters hex of either the Duke or the Marquis may attempt to influence that commander to release one ship for use by their faction.
If gained by the Liberator forces, the released ship is assigned to the Count faction.
Follow the release procedures in (658.311). Select one ship from the appropriate pool below and remove it once released.”
Reason: Grammar and flow, removes pronouns, tightens structure, improves clarity.

(638.2731), FORMAT ITEM: List of ships includes crippled units, in the Romulan Civil War these units were listed in italics. For consistency change the format on all units listed as crippled in italics.
Reason: Format change

(638.2731) Available Duke's Fleet Ships:
TYPO, 1st line missing comma between FFK and 2xMEC.
MISSING SHIP: 3rd line to 4th line ship missing between 2xCLD, and extra comma, LTT. (STAFF VERIFIED) Add missing MCG so it says “…2xCLD, MCG, LTT…”
Reason: Typos

(638.2732) Repair Units: Replace text with: "A phasing faction may influence an unaligned fleet commander to authorize repairs to that faction’s ships at controlled, unaligned repair facilities; see (658.32)."
Reason: Direct.

(638.2733) Influence Ground Bases: Replace text with: "A faction may influence one neutral ground base to join its cause under (658.33). Ground bases gained by Liberator forces are assigned to the Count faction."
Reason: succinct and clear.

(638.411), FORMAT ITEM: List of ships includes crippled units, in the Romulan Civil War these units were listed in italics. For consistency change the format on All units listed as crippled in italics.
Reason: Format change

(638.412), FORMAT ITEM: List of ships includes crippled units, in the Romulan Civil War these units were listed in italics. For consistency change the format on All units listed as crippled in italics.
Reason: Format change

(638.54) 3rd line reference (502.431) should instead correctly reference (502.434)
Reason: reference mismatch
Ryan Opel 24 OCT 2025

Lar