STAR FLEET BATTLES CAPTAIN'S EDITION UPDATE J4-K8 Copyright (c) 1993 Amarillo Design Bureau This file contains the updates, revisions, corrections of mistakes, explanations, clarifications, and resolutions of contradictions for the stated rules sections. Players may produce up to 10 hard copies of this file and pass them out to their friends; copies may not be sold. This file may not be published or re-uploaded without advanced written permission of Amarillo Design Bureau. ============================================== (J4.8172) Last sentence should read: "Two more deck crews canot load the ready rack in that box if there is space available on the rack. The rack cannot be simultaneously loaded by one set of deck crews and provide drones for other deck crews to load on the fighter, even if this is done in different positions on the rack." Add a reference to (J4.823). (J4.821) A deck crew loads a type-VI drone in half of the time it takes to load a type-I drone. In the last line, this is one action per space. (J4.8222) Reference to (J4.896) should be to (J4.891). (J4.8225) Variants of fighters (e.g., C-refit, F-18B) can be rearmed in each other's ready racks, but obviously cannot load a weapon for which they are not authorized. If, for example, a fighter without a C-refit was in a fighter box for a fighter with a C-refit, and the ready rack held a type-I drone in a position that corresponded to a type-VI drone rail, that drone could not be loaded. Type-Is could be loaded by (J4.8962). (J4.824) Reference to (FD2.44) should be to (FD2.443). (J4.825) Reference to (GP9.22) should be (FP9.22). The drones (on a plasma carrier) and plasma-Ds (on a drone carrier) would be loaded by (J4.8962) not by the ready racks. (J4.831) At WS-III, a fusion capacitor would still be holding one charge, the other being on the fighter. (J4.835) Add reference to (J4.897). The reference to (J4.896) is valid, but this can happen only in cases where a drone-armed fighter lands on a foreign carrier during a battle. (J4.881) Reference to (J4.83) should be to (J4.832). (J4.883) The fact that a weapon was ejected from the fighter facilities is known at Tactical Intelligence Level B. (J4.886) Add reference to (J4.8224). (J4.89) Reference to (J8.842) should be to (J4.88). (J4.8962) Drones on ready racks in other shuttle boxes of the same bay count as already being in the bay. (J4.897) The escorts assigned to a Federation NVH are the only exception to the prohibition against escorts having ready racks for large fighters. (J4.9) Some aspects of this rule apply to non-fighter shuttles. Non-fighter shuttles can be lent EW by a scout channel. (J4.91) Add the reference (D6.3143) to natural sources. Non- fighter shuttles can only receive natural EW and EW lent via a scout channel. (J4.922) Non-fighter shuttles can receive lending from scouts. (J4.931) Reference (J4.923) should have been (J4.921). (J4.933) This division into squadrons (J4.462) is not strictly required, but if the fighters are not grouped into squadrons, the squadron EW lending rule cannot be used. (J4.943) Reference to (J8.41) should be to (J8.43). (J4.944) Reference to (J9.11) should be to (J9.14). (J5.11) If WBPs are purchased for fighters as a Commander's Option or in a patrol scenario, they must be purchased for all of the fighters on that carrier. The extra sets of WBPs under (J5.42) are then stored on that carrier. (J5.14) If a fighter uses emergency deceleration (J4.13), the packs are turned off. This does not count against the limit of turning the packs off once per turn. See also (J5.133) for another exception to the limit. (J5.422) The term "fighter" should be "shuttle" as extra warp boost packs could be purchased for the ship's shuttles (as well as the fighters). (J5.432) No deck crew action is required to bring the WBP to the bay from whereever it is stored. (J6.0) Reference to (J6.32) should be to (J6.324). (J6.222) "Erratic movement" should be "erratic maneuvers." (J6.31) While there technically can never be a reduction below 5 (unless class level in the case causes the DF-kill score to be less), the rule is correct as written. (J6.422) This rule is used even if the legendary ace was unable to eject or the POIS was destroyed or captured. That's what makes Legendary Aces a Legend. (J6.51) This rule does not allow a green pilot to carry a pod which is normally prohibited to a green pilot. (J6.632) Reference to (J6.4) should be to (J6.422). (J6.649) There is no penalty for destroying a POIS. That is simply the misfortunes of war. (J7.11) EXAMPLE: Should read "In a single hex ARE..." (J7.122) Shuttles unable to use their weapons (at all, not just until the next turn) are considered unarmed. (J7.22) A fighter in a dogfight can receive EW points, but this has no effect; see (J4.95). (J7.32) Reference (J7.22) should be (J7.21). (J7.326) See (FD1.7) for cases when the drone is not removed. (J7.334) See the exception in (J7.332) for EW, pilot quality, etc. (J7.336 - 2) This also applies to non-fighter shuttles, and creates a temporary exception to (J6.213). (J7.43) Given a dogfight with two Fed and one Klingon shuttles, a third Federation shuttle in the hex could not join. However, a second Klingon shuttle could either challenge the third Fed shuttle or join the dogfight with the two Feds and one Klingon, forcing that to split into two dogfights. In that case, the third Fed shuttle could then join either of the new dogfights. (J7.50) In the Captain's Edition, there is only one impulse chart (with 32 impulses). This reference is a carry over from previous editions which had several charts. Also, the separate firing stages against shuttles and seeking weapons are an exception to the general rule on one set of simultaneous weapons firings, but this applies only in dogfights. (J7.527) This applies to any shuttle with two or more phasers. (J7.53) This is an exception to (J4.24) as noted in (J7.533). (J7.533) Reference to (J7.54) should be to (J7.53). (J7.56) An FA phaser can be fired at a drone fired by a disadvantaged fighter. The only way (currently) for that to happen is a type-VI drone fired from an ADD. A shuttle in a dogfight can fire LS or RS (but not both) weapons at a target ahead or behind. It cannot fire the weapons on one side (LS or RS) at both forward and rear targets, but could fire LS weapons at a target to the front and RS to a target in the rear or vice versa. (J7.651) The "below" in the LS/RS section refers to the LS/RS section of (J7.652). (J7.652) NOTE: This is correct; the worse you are disadvantage the more likely this particular weapon can hit him. (J7.6621) Any breakaway is done AFTER rolling for this collission. (J7.714) Any terrain in the hexes entered affects the fighter normally, e.g. collision with planet or asteroid damage. (J7.731) The "any enemy" refers to "any unit of the enemy force you surrendered to." (J7.822) This applies if any fighter in the dogfight receives asteroid damage. (J7.824) In a hypothetical battle between two Tholians, the units of one Tholian have a different frequency of web than the other, and they cannot pass each other's webs. Typo. Tholian shuttles are never caught in their web Involuntarily. (J8.13) The direct fire weapons are limited to a maximum range of 15 hexes by (J1.31). (J8.134) Should state: Unlike fighters, MRS shuttles can ACCEPT transfers of seeking weapons. (J8.21) Reference to (J2.212) should be to (J2.211). (J8.21) The T-bombs carried by an MRS are taken from the ship's stores. They do not come free with the MRS and cannot be purchased for the MRS in excess of the ship's limits. An MRS loaded with mines counts under (S4.1) as a shuttle prepared for a special mission. (J8.23) The loading rate specified is much lower than would be the case for a non-MRS, but is correct. The lower rate is due to the special arrangement of the MRS. (J8.332) Reference to (FD7.4135) should be (FD7.4153). (J8.42) Reference to (C10.52) should be to (C10.523). (J9.0) In the extract of this rule on page 140 of the Basic Set rulebook, the word ''element'' should be deleted. (J9.0) The addition of the E3A made several mentions that the E2C is "unique" or the "only" such unit obsolete. (J9.136) A manned wild SWAC can be challenged to a dogfight. It continues to function normally. However, due to the consequences of (J3.3), the enemy fighter would be advised to leave the wild SWAC alone. (J9.142) Reference to (J4.93) should be to (J4.934). (J9.2442) The seeking weapons could be diverted by (G24.23) or "destroyed" by (G24.22). (J9.2444) In this case, the SWAC does not explode. (J9.44) E-2 SWACS cannot carry fighter pods. (J9.533) See (D7.836) in the event that the E-3 is boarded while carrying a defending BP. (J9.533) This would not affect the operation of the larger E-3, even though the smaller E-2 loses its SWAC abilities when using (J9.332). (J9.54) E-3 SWACS cannot carry fighter pods. (J10.33) The phaser-2 is limited to a maximum range of 15 by (J1.31). Not all heavy fighters have phaser-2s. (J10.42) The correct title for this rule is HEAVY WEAPONS. Those heavy fighters with two plasma-F torpedoes have two separate plasma-F mounts. (J11.115) MRS shuttles armed with D-torps can carry pods on the torpedo rails. (J11.115) SWACS (either type) cannot carry fighter pods. (J11.13) Carriers receive these pods for free in all scenarios (incuding Patrol scenarios) unless otherwise noted. (J11.2) Extra EW pods cost 1 point each, see Annex #6. (J11.21) Clarification: The EWPs on unlaunched fighters must be set and announced at the start of the turn. (J11.333) If used in a dogfight, the pod can fire a total of 4 times at low power before it is exhausted. After firing once at low power, it cannot be fired at normal power until recharged. After firing four times at low power, it cannot fire at all until it is recharged. Regardless of how many low-powered charges it fired, it still requires the full 1/2 point of energy to recharge. (J11.336) An armed phaser pod is treated as explosive ordnance (G25.3). An unarmed phaser pod is not. (J11.346) An ground attack pod is treated as explosive ordnance (G25.3). (J11.41) This pod is limited to "small objects" and cannot cary drones or type-D plasma torpedoes. (J11.422) Confirming: No more can be bought, even if they are listed in error on some versions of Annex #6. (J12.13) There is no restriction on replacing drones with RALADs. RALADs do not count against the racial percentage of special drones. (J12.32) ADDs are not adjusted, as (J7.661) says. (J13.12) Casual Bases have Control Stations; these represent "key terrain" surrounding or within the location selected for the base. However, by its very nature, there will not be any Ground Defensive Systems at a casual ground base. These are constructs which take time to place, and the entire concept of a Casual Base is that it will exist for only a short period of time and then be abandoned. (J13.212) Shuttles are destroyed by the normal rules for firing on a shuttle on the surface, not as the contents of a box. Rule (R1.14C2) applies to small ground bases. (K0.11) PFs do not use (D22.0). See Note #2 in that rule. (K1.52) Each PF buys its special drones individually. A flotilla cannot concentrate all of its special drones on a single PF (at least not without using cargo transfer during a scenario). (K1.541) This specific rule overrules the general (D17.4) Level E for PFs. (K1.61) The cost reduction for not carrying WBPs applies only in the case of PFs appearing in a scenario without their tender. (K1.63) EXAMPLE: There is an error in the example. The 2nd volly that scored 2 left warp and one center warp hits shows the die roll for the first left warp hit destroying the engine with a 5 roll, but to allocate damage normally, first the pack would have been destroyed by the two normally-allocated damage points, thus the 5 roll would only have destroyed the two engine boxes of the left warp engine. (K1.75) This also applies to fighters operated by the tender. (K1.752) PF scouts cannot lend EW to a fighter squadron, even if was launched by Fi-Cons from the scout's flotilla. A PFS can lend EW to a single fighter by (K1.752). (K1.8) "Valkyrie" is misspelled. (K1.91) If the impact of an ESG on a PF totally destroys the PF, the survival pod is considered to have been destroyed before it could be released. The survival pod is not placed on the map and does not further reduce the ESG. (K1.948) See the errata under (K1.91). (K2.113) Reference to the LDR CC should be to the LDR BC. (K2.323) PFs (including INTs) do not have their turn modes satisfied at the point of launch. (K2.324) Effectively, EM takes effect for PFs at the end of the impulse in which they were released. (K2.344) See exception in (K2.381). (K2.362) For purposes of crew quality, outstanding ship crews would be treated as Good PF crews, and Ace PF crews would be treated as "normal" ship crews. (K2.411) If the DAC calls for a damage point which the PF has and the PFT does not, the owning player can score it on the PF or move to the next column of the DAC at his option. (K2.434) This rule is incorrect; the data in (K2.432) regarding PFLs is correct. See (D18.17) for specific details of surprise. (K2.47) A PF docked to a ship could be destroyed by damage allocated to the PF (K2.41), but as this would cause an explosion that damages the PFT it would be unwise to allocate damage in that manner. A hit-and-run raid might also trigger this event. (K2.621) The tractor is required to undock from an internal bay, even though this uses the (K2.32) procedure which, in most cases, does not require a tractor. (K2.641) This can be done at any mech link. It takes an entire game turn, not 32 consecutive impulses. (K2.65) The initial loading on the PFs is NOT counted against this allocation. (K2.653) There are two exceptions to this rule. In the case of plasma races, as their standard PFs are armed with plasma-Fs, the casual PFT will carry two sets of plasma-D reloads for each plasma rack on the specific type of PF carried. This is in addition to the one loading already held in each rack of the PF. In the case of Orion Pirates, if the PF selects drone or plasma racks for its option mounts, the casual tender will carry two sets of reloads for each rack. This is in addition to the one loading already held in the selected rack. NOTE that while this rule provides for the amount of drones carried, the type of drones carried will be appropriate to the PFs carried. G1Ks, for example, can only use type-VI drones, which standard G1s cannot use in the drone racks. Casual carriage of a drone-armed PFT does not confer drone- handling abilities on a ship otherwise without them. (K2.655) PFTs with plasma-Ds have storage for 100. (K3.13) See (K3.75) for information on this EW variant. (K3.75) These EW "pods" are destroyed by a weapons hit of the type of weapon they replaced. There is no BPV change. (K4.14) The MSSs on mine warfare PFs are another exception. (K4.3) The "explosive ordnance" penalty (G25.3) does not apply to reloading the T-bomb on a PF Leader. The transfer loads the T-bomb directly into the "mine rack" on the PFL. (K5.2) An n/a result from this chart, when scored on the DAC, is treated as "no more of that system" hit and you proceed to the next column on the DAC. (K6.13) The reference to dropping packs during the turn is obsolete; see (K1.62). (K6.32) This is a confusing rule. It applies to PFs launched again. (K7.11) This rule provides that the BPV of a deathrider is identical to a standard PF of the type. (K7.14) The reference to (G24.219) refers to the fact that EW does not distract a Death-Rider as it would a seeking weapon. (K7.20) See (K7.322) for "very slow" targets. (K7.212) An autonomous Death-Rider does not require a lock-on until it goes into seeking weapon mode. (K7.412) A Boarding Party accompanying the major uses his result on the chart. (K7.424) Reference to (G22.52) should also be to (G22.54). (K7.518) There were 24 points of damage, not 25. (K7.71) Any general shield reinforcement will be dropped at the same time as the shields in this case. (K8.212) Ace PF crews can fly a PFS but this won't improve its EW abilities (K8.23). (K8.42) This chart is used even if the survival pod was seen to be destroyed on the map during the scenario. >>END OF FILE<<