(319.23) from Offensive Fighter-PF Strikes

"A carrier which conducted such a strike could retrograde as would any other carrier that used its fighters in combat."

What about the escorts? What about any other ships in the hex? This is unclear since carrier groups can be broken down in FO, and one person may interpret this sentence to require breaking down the group since the escorts did not participate in combat and therefore are not eligible to retrograde.

Recommend reword 319.23 as follows: "A carrier, and any assigned escorts, which conducted such a strike could retrograde as would any other carrier (or carrier group) that used its fighters in combat."

SVC APPROVED

By Steve Cole (Stevecole) on Saturday, June 12, 2021 - 03:48 pm: Edit

FIGHTER OPERATIONS CAPTAIN'S LOG AFTER ACTION REPORT FROM CL31 OR CL32
Many people noted that the pictures of counters on the back covers are conveniently printed so that you can create some extra counters if you want.
There are (as one might expect) lots of picky little things in and about the SIT. Now that we have the Master SIT on line, these things were fixed there and need not be listed here, but some examples include the various Kzinti "heavy fighter and/or PF ships" (which now have both versions listed on the MSIT with the relevant dates), the service dates of the B10V and B10s, Hydran DWEs convert from HNs not HRs, etc.
Fighter Operations sells for $29.95 and is SKU 3203.
(319.12) Swarms cannot launch offensive fighter strikes.
(440.6) The Gorn CVD, Lyran DCS, and Lyran NDS are all counted as heavy carriers.
(440.7) We considered several ways to restrict the production of the Lyran CVM and finally just gave it a higher cost. The SIT refers vaguely to a production restriction, and that is it. The Federation DVL is escorted as a medium carrier. The first Federation CVF is built in addition to the normal production schedule and limits, costing 11 EPs plus the fighters.
(443.0) This rule number is used for both Commercial Convoys in Combined Operations and for Fighter Storage in Fighter Operations. We were in such a hurry to get the fighter storage rule into the product that nobody checked the rule number. Fighter storage should be (445.0).
(443.11) (445.11) The (xxx.xx) should be (441.4). When SVC writes a new rule he does all of the cross references like that and lets the staff hunt them down. This saves him time. We missed a couple of these for what seems to be the first time. Base Stations can have depots; see (444.11).
(443.21) (445.21) These fighters can be provided to any carrier "within supply" which (assuming no pesky enemy ships are in the way) could be six hexes away.
(515.53) ESCORTS: Escorts can be produced in several ways, even without producing a carrier. [This rule got badly garbled when we tried to include the CL#25 ruling. The following text is the new complete version which replaces all previous versions.]
(515.531) If a carrier group is scheduled for production and you do not want the carrier but do want the escorts, replace the carrier (and possibly some of the escorts) with equivalent standard warships (757.1) and pay the assigned cost for each ship.
(515.532) If a carrier group is an allowed substitution, you can substitute escorts for some or all of the specified (757.1) equivalent ships and simply not bother to substitute a carrier for the corresponding hull. (In this case, you would build the originally-scheduled standard warship.) Escorts produced as substitutes for standard warships do not count against limits on conversions by starbases. The cost of an escort is defined by the SIT.
(515.533) In addition to (515.532), any race may substitute equivalent carrier escorts for up to three ships on the production schedule or produced as overbuilds in addition to specified carrier group production.
(515.534) Escorts can also be produced by conversion at any starbase from the equivalent warship hull for one point, up to the limit of the conversion capacity. (A very few escorts have fighters, and the cost of the fighters must also be paid at the appropriate rate.) Conversion costs are listed on the SIT.
(515.535) As provided in (308.132) Carrier Escort Damage System, escorts can be produced at the end of the turn to fill carrier groups. As per (308.132B) in CL#25, these do count against the conversion capacity of the starbases used for the conversions. See the penalties in (515.54). [At the present time, (308.132B) is the only means by which a starbase may do multiple conversions in a given turn, each using some of its capacity. New rules in a future product will make this a general rule.]
(518.22) BCV and BCS can have one SWAC. Base Stations cannot use SWACs.
(518.37) SWACs cannot produce a shift in small scale combat or single combat.
(530.221) The Hydran LE and MKH also have heavy fighters.
(532.121) This rule is confusing in its reference to (526.36). It means that FCRs can carry heavy fighters but not F111s.
(532.22) The Federation HDW with A20s is variously referred to as the HDWH and HDWA.
(532.224) Reference to (532.222) should be to (530.222).
(518.35) This rule contains an obsolete reference to SWACS having no effect on fighter limits, but the new mission in (518.46) allows them to do so. This was one of the many sloppily-edited changes made in a flurry of last second euphoria as everyone was happy about the product going to press and determined to shoehorn his favorite rules change into it.
(607.61) Kzinti DNE should have salvage 3; Klingon C6 should have salvage 3.6.
(608.53) Lyran sector A has 5 police ships and gets one more each fall turn to a maximum of 8.
(608.F) See (617.F) for updated sector boundary.
(653.4G) The six free fighters here are in addition to those added in F&E 2K.
(703.0) the E4R appears as a 2-4 in FO and a 1-4 in AO. It all depends on how aggressive the skipper is!
(704.0) Activation of the VLV requires buying its fighters.

By Lawrence Bergen (Lar) on Monday, March 20, 2023 - 07:57 pm: Edit

(319.0) Offensive Fighter Strikes Ruling from CL#49

SUGGESTION:
(319.11) ELIGIBLE SQUADRONS: Fighters (including heavy fighters and F-111s) and PFs (including casual PFs and PFs from the 23rd and 77th divisions) can be used for offensive strikes. Add: Fighters from Police carriers may be used for offensive strikes within their own territory and eligible adjacent Neutral Zone hexes (319.14).

RATIONALE: The question was made to point out the gap in the understanding of the rule. The subsequent ruling answered the question.

The existing rule added for reference:
(531.44) TRANSFERS: Fighters cannot be transferred from police carriers to non-police carriers but can be transferred to other police carriers. (If a police carrier is destroyed, its homeless fighters return to police duties; they are not transferred to the fleet.) Police carriers can make offensive fighter strikes (319.0) into adjacent hexes but cannot be used as independent reaction forces (205.7). Police carriers cannot be in CVEG groups. Police carriers cannot use megafighters.

The CL#49 Ruling Added for reference/support:
Q: According to rule (531.44) police carriers are allowed to make fighter strikes. Can they perform a fighter strike into a neutral zone hex?
A: No ships ever leave your territory, so, yes.

(319.14) PROHIBITED TARGETS: Strikes cannot be made into neutral empires, neutral zone hexes which are prohibited for entry, or the WYN Cluster. Strikes cannot be sent into a hex without an enemy unit to attack.

========

Note: This rule was asked and answered under Police Carriers rule (531.44) TRANSFERS: but in actuality should drive the change under the Eligibility rules in 319.1, specifically 319.11 and referencing 319.14.

L. Bergen - 20 MARCH 2023