OMEGA OCTANT MASTER ERRATA FILE

This file is all Omega Errata as of 17 April 2007. All of thefollowing items have been incorporated into the Omega MasterRulebook. If you have that product, you do not need this file.These items are also incorporated, as appropriate, in newprintings of the Omega Rulebooks included in Omega #1, Omega#2, Omega #3, and Omega #4. These will have Copyright datesof 2007.

This file includes errata for Omega rules, SSDs, andscenarios released in Captain’s Log. The rules and scenariosfrom the Captain’s Logs were included in the Omega MasterRulebook.

Earlier Editions of the Omega #2, Omega #3, and Omega #4rulebooks included some of these errata items. As they havesince been incorporated into new printings of the appropriaterulebooks, current editions (with a 2007 Copyright date) will notinclude these errata items.

This errata file is presented in rule number order and is notbroken down by product.

MODULE COVERS

OMEGA #1 Back Cover Map: CORRECTION: Mæsron has thecombined “æ” character replaced by a rectangle.

(OA0.0) ERRATA

(OA1.0) OMEGA HISTORY: CORRECTION: Pages #4, (3rdparagraph, left; 6th paragraph, left) and #5 (Near ‘Y181 Trobrin’text) contain “O”, these are control characters (should have beenquote marks) left by the new printing software ADB, inc., beganusing with this product. They should not show up in any laterproducts.(OA2.0) CHANGE/CORRECTION: Renumber this rule in ModuleOmega #2 as (OA3.0). Rule number (OA2.0) was used in Omega#1 as the General “rules in Omega work the same was as rulesin the rest of SFB except as specifically noted otherwise” note.(OA3.0) CHANGE/CORRECTION: Change this rule in ModuleOmega #3 to (OA4.0) in keeping with the renumbering of (OA2.0)in Omega #2 as (OA3.0).(OA4.0) CHANGE/CORRECTION: Change this rule in ModuleOmega #4 to (OA5.0) in keeping with the renumbering of (OA2.0)in Omega #2 as (OA3.0) and (OA3.0) in Omega #3 as (OA4.0).

(OD0.0) ERRATA

(OD1.32) ADDITION: Add to end of rule: Leak damage (D3.6)penetrating such a shield would strike the ceramic-compositearmor behind it rather than be resolved as a point of internaldamage.(OD2.216) NEW RULE: SCENARIOS: A given scenario willdefine within its rules whether or not a Hiver mental node ispresent and in operation. In such cases it will either define whichships are part of such nodes, or whether the players are allowedto assign ships as they see fit within these rules.(OD2.224) REVISION: Rule now reads: Only ships of Size Class5 or Size Class 4 may be attuned to mental nodes on board otherships; the command staff of Size Class 3 and larger units is toolarge and independent.(OD2.24) CLARIFICATION: Whether or not a unit is in range forMental Nodes is determined three times during each impulse atthe same time as checking for Hiver Control (O10.031) and Lossof Queen (OR10.032). The Post Combat Segment (6E) afterrolling for UIM breakdowns, as the last action of the MarinesActivity Stage (6B7), and in the Final Movement Actions Stage(6A4) after ships are released from tractor beams. 14 Feb 2007(OD2.253) CLARIFICATION/NEW RULE: Whether or not a unitis still eligible for Mental Nodes (i.e., is in range or the node unit

has lost all control boxes) is determined three times during eachimpulse at the same time as checking for Hiver Control(O10.031) and Loss of Queen (OR10.032). The Post CombatSegment (6E) after rolling for UIM breakdowns, as the last actionof the Marines Activity Stage (6B7), and in the Final MovementActions Stage (6A4) after ships are released from tractor beams.14 Feb 2007(OD2.346) ADDITION/CLARIFICATION: Note that crew qualitywill only occur in special circumstances defined by the rules of ascenario or campaign as Hiver cannot have outstanding crews,or poor crews, normally (OR10.033).(OD2.43) RULE REVISED: BASES: Mental nodes may bepresent on Hiver bases, although this was rare on any but themost crucial installations, all battle stations and starbases willnominally have such a node. A mental node on a base has thesame abilities as one on a ship, and can control ships within 15hexes of the base. The principle problem with base nodes is thatthey are often formed at the last second as ships arrive to defendthe base from attack. It is entirely possible that a given battlestation or starbase may have several defending ships, but nonein a mental node simply because there was not time to form one,or may have some ships in a mental node, but others that arrivedtoo late. Defending ships might be in their own mental nodesseparate from any formed (or not formed) by the base havingarrived as operable mental node groups.(OD2.44) ADDITION: Add to end of rule: (battle station orstarbase).(OD2.451) ADDITION: Add to end of rule: To be explicit, otherthan paying for life support, shields, fire control, ECM, erraticmaneuvers, and arming (but not firing) weapons, and makingrepairs. The ship can take no action except to move away fromthe enemy and must move to stay at least 25 hexes from thenearest enemy unit. It cannot fire at a seeking weapon, or tractora seeking weapon (or anything else), even if knows the seekingweapon is targeted on itself.

OE0.0 ERRATA

(OE01.118) NEW RULE: All phaser-4 Omega phasers can onlybe used on bases. All phaser-1, phaser-2, or phaser-3 Omegaphasers require one option mount, see Annex #8B for costs.Note that some phasers, i.e., Radiation phasers, have rules thatapply to their use by a different race. Omega phasers can only beused in Omega and simulator option mounts.(OE01.24) CORRECTION: The reference to “implosiontorpedoes” should have been to “implosion bolts (OE6.0) andimplosion torpedoes (OFP1.0)”.(OE01.255) NEW RULE: Quantum Phaser-1s cannot be fired asQuantum Phaser-2s, and Quantum Phaser-2s cannot be fired asQuantum Phaser-1s. Either can be fired as a Quantum Phaser-3.A Quantum Phaser-4 can be fired as a Quantum Phaser-4, aQuantum Phaser-1, a Quantum Phaser-2, or a Quantum Phaser-3.(OE01.26) CORRECTION: The Anti-Proton Phaser-1 Table inthe rulebook under rule (OE1.262) wrongly lists a range bracketof 14-19, that range bracket should be 13-19. All of the SSDs(Ymatrian and Worb) have the correct phaser table.(OE01.34) CORRECTION: Change last sentence to read: “Theaddition of this technology also modifies (OE1.231) in that it addsa third form of ship-mounted particle phaser to the OmegaOctant.”(OE02.2) DELETION: Delete the last sentence as it merelyduplicates (OE2.1).(OE02.22) REVISED/CORRECTED: A pulse emitter can be firedup to three times during a single turn. Each firing may be duringthe same or a different impulse and at the same or a differenttarget. Pulse emitters can fire at different targets in the sameimpulse. A pulse emitter cannot fire more than three shots perturn, nor can it fire more than three shots within a 1/4-turn period.The 1/4-turn period can include some shots fired during the final

portion of one turn and some shots fired during the early portionof the subsequent turn.(OE02.41) ADDITION: Add to end of rule: “Pulse emitters cannotbe detected as different from standard pulse emitters (OE2.0) byTactical Intelligence (D17.0), only by their effect, i.e., greaterrange and damage.”(OE03.22) CLARIFICATION: Tachyon Guns do not have acapacitor of any kind, but can hold energy as described in thisrule. Designer’s Note not included in the rule but to helpunderstand the errata item: If they had such a capacitor, it wouldtotally change the dynamics of the weapon, and would probablybe X-technology.(OE03.242) ADDITION: Add to end: “. . . (holding cost 1 point).”(OE04.121) CORRECTION: For purposes of (D4.3222),antimatter cannons fall after heavy hypercannons and disruptor-30s. See Annex #7E.(OE04.41) CLARIFICATION: Change last sentence to read: Theadded power can come from either allocated or reserve power,but must come from the same source AT THE SAME TIME; see(OE4.221).(OE05.348) CLARIFICATION/NEW RULE: Antimatter Cloudsare resolved as part of any other volley of weapons, except thatthe target ship chooses which shield is hit (OE5.342). If two ormore antimatter clouds are fired into a single hex, all the units inthat hex will be damaged by both clouds. As there may beseveral units in a given hex, counters are provided to keep trackby reminding players of the number of ACGs fired into a hex. Aseach is resolved against all the units in the hex, remove thecounter. Remember that ACG damage points are applied to eachunit in the hex at the unit’s discretion as to the shield they areapplied to.(OE05.348) CLARIFICATION: Add to end of rule: Antimattercloud damage to shields is resolved after all other direct-fireshield damage in the Direct-Fire Weapons Fire Stage (6D2).(OE05.353) CLARIFICATION: If the result of a miss or near missputs the ACG in the hex of the firing ship, the cloud is disruptedand never forms, having no effect.(OE06.12) CORRECTION: DESTRUCTION: IBs are destroyedon “Drone” damage points.(OE06.121) CORRECTION: For purposes of damage priority,Implosion Bolts are destroyed after heavy hypercannons and PApanels for the purposes of (D4.3223). See Annex #7E.(OE08.25) CORRECTION: This rule should read: FIRING RATE:Particle probe launchers can be fired only once in any period oftwo turns, and no unit can fire more than one particle probe inany given turn. Most Vari cruisers have two particle probelaunchers, and alternate their arming and firing cycles. Some Varispecialty ships are capable of firing from more than one particleprobe launcher in a given turn. These will be noted in their shipdescription.(OE08.33) ADDITION: Launching P-PRBs does not causefeedback in the Qixavalor cloud (OP1.213).(OE08.41) ADDITION: TERRAIN: P-PRBs cannot be firedthrough a hex containing a planet (P2.321), moon [Exception:(P2.3221)], star (P12.1), black hole (P4.23) or pulsar (P5.32).They can be fired into such a hex. They can be fired throughasteroid (P3.33), ring (P2.223), and dust (P13.4) hexes with thestandard EW penalties applied to firing their PBs.(OE08.42) ADDITION: PLANETARY ATMOSPHERE EFFECTS:Particle beams on particle probes lose one point of their warheadstrength for each hex of atmosphere (P2.54).(OE08.43) ADDITION: WEBS: P-PRBs cannot be fired throughwebs (G10.61), and cannot damage them. P-PRBs can be firedout of web hexes. P-PRBs can fire their particle beams at targetsin webs, provided a legal line of fire exists between the firing shipto the hex the particle probe will be in and the particle probe hasa legal line of fire at the target in the web hex.(OE08.44) ADDITION: NON-VIOLENT COMBAT: Particlebeams on particle probes can use Non-Violent Combat (D6.4).(OE08.45) ADDITION: FIRING AT SIZE CLASS SEVENTARGETS:

(OE08.451) ADDITION: PBs on particle probes are penalized asheavy weapons when fired at drones (FD1.52).(OE08.452) ADDITION: PBs cannot damage plasma torpedoes(FP1.62).(OE08.453) ADDITION: PBs on particle probes cannot be fired atmines.(OE09.351) CLARIFICATION: Fireballs can only be overloadedduring The Energy Allocation Phase (1) of the second turn ofarming, as the power required for an overload must be allocated.They cannot be overloaded through the use of reserve powerduring The Impulse Procedure (6).(OE09.352) ADDITION: Add to the end of the third sentence: andis scored after other direct fire weapons in the Direct-FireWeapons Damage Resolution Stage (6D4).(OE10.211) CORRECTION: The last sentence should read, “Anyfractions after halving this ENERGY are RETAINED” (emphasisindicated words that were changed from the original).(OE10.215) NEW RULE: Bioelectric bolts fired with only a halfpoint of energy do not blind special sensors under (G24.1341). Iffired with more than a half point of energy, they do blind specialsensors under (G24.1342).(OE11.0) CLARIFICATION: There is a seeking weapon mode,whipcrack torpedoes (OFP7.0), which effectively makes this the“bolt” (F8.0) mode for a plasma weapon. 14 Feb 2007(OE11.17) DELETED: The following text was deleted as notapplicable to plasma whips: “Arming status is known at TacticalIntelligence Level L. Total amount of power used to arm theweapon is known at Tactical Intelligence Level M.”(OE11.312) CHANGE RULE TO READ: If multiple differentweapons strike a shield in the same impulse, damage from anyplasma whip in the volley is scored after (in this order)transporter-collector beams (O26.314), energy howitzers(OE14.32) and hypercannon implosion shells (OE16.322), butbefore all other shield damage (although it is still counted as partof the same volley, it is the first damage to be marked off theshields and any reinforcement).(OE11.312) CLARIFICATION: Change to read: If multipledifferent weapons strike a shield in the same impulse, damagefrom any plasma whip in the volley is scored after energyhowitzers (OE14.32) and hypercannon implosion shells(OE16.322) but before all other shield damage (although it is stillcounted as part of the same volley, it is the first damage to bemarked off the shields and any reinforcement).(OE11.442) CLARIFICATION: Note that this rule does notdouble the strength of the plasma whip, but only provides that thedamage it scores is treated as phaser damage (FP1.61). Sothree points of plasma whip damage would only reduce a plasmatorpedo warhead by one point, and the extra point could becombined with another point to create another point of reduction.(OE11.45) NEW RULE: SPECIAL SENSORS: Plasma whipsblind special sensors under (G24.1342).(OE12.0) ADDITION: Add to end of introduction: The system wasevolved from a natural ability of Alunda used by larger creaturesto push smaller ones away from desirable (to an Alunda) things.Tactically, it can also be used on other Alunda ships, or Alundaallied ships, to position themselves to take advantage ofopportunities.(OE12.31) CLARIFICATION: Add to end of second sentence offirst paragraph: “. . . after determining the effects of all otherdirect-fire in that impulse.”(OE12.3331) NEW RULE: CLARIFICATION: The movementcaused by an ARF is performed before all other movement,including that caused by a black hole, in step (6A1) of thesequence of play.(OE12.3332) NEW RULE: CLARIFICATION: Whether or not agiven unit will continue to be affected by a given ARF onsubsequent moves is determined after the completion of its ARFmovement in the current impulse. Thus if a unit is repulsed torange 6 on Impulse #4, it is no longer affected by that particularfield even if the Alunda ship were to move closer, reducing therange to five again by the end of the impulse. Even if the unit, inits own voluntary movement during that same impulse (or

through various involuntary movements, e.g., black holemovement) reduces the range to five or less again it would stillnot be affected.(OE12.334) CORRECTION: The reference at the end of this ruleto (OE12.332) should have been to (OE12.333).(OE12.3353) ADDITION: Add to end of first sentence: “. . . it hasno effect on three or more units of Size Class 4 or larger dockedtogether”.(OE12.3354) CHANGE: Change the second sentence to read: “ASize Class 4 Alunda unit treats a Size Class 2 unit of anotherrace, even a Size Class 2 unit tractored to another Size Class 2unit, under these rules.”(OE12.3364) CLARIFICATION: Add to end of rule: “. . . beingheld in a tractor beam by a unit subject to the attraction-repulsionfield.”(OE12.338) NEW RULE/CLARIFICATION: While the ARF istechnically a direct-fire weapon, it has no inherent means ofcausing damage to a target and is not restricted by the rules on“friendly fire” (D1.5). Alunda units may use their ARFs on otherAlunda units on the same side, and often do so for varioustactical reasons.(OE12.44) NEW RULE: WEBS: ARFs cannot fire through webs(G10.61), and cannot damage them. ARFs can fire out of webhexes, and can help push units stuck in webs through, or pullthem out (OE12.3362), or push units into web hexes provided alegal line of fire exists between the firing ship and the target.(OE13.231) CORRECTION: This rule is incorrectly numbered(OE13.221).(OE13.232) CORRECTION: This rule is incorrectly numbered(OE13.222).(OE13.33) CHANGE/CLARIFICATION: Change last sentence ofthis rule to read: The maximum range of a sting torpedo on mostfighters is 15 hexes, a fighter’s rule, e.g., (OR10.F1) for the Barb-1, will state if the range is less or more.(OE13.33) CLARIFICATION: The Maximum range of a StingTorpedo on a Barb-1 Fighter is 15 hexes.(OE14.32) CHANGE third sentence to read: “They do shielddamage before other direct-fire weapons fire, but aftertransporter-collector beams (OE26.314).”(OE14.321) CLARIFICATION: Add to end of rule: If fired on ashield boundary, use the procedures in (D3.4) to determine thefacing shield.(OE14.325) CLARIFICATION: Note that armor is treatednormally, i.e., any damage that penetrates a shield or otherwisestrikes armor is first scored against the armor.(OE14.42) CLARIFICATION: The two damage elements that arelost are always the ones that would have hit the two non-facingshields of the target (OE14.32) of the Energy Howitzer(s).(OE15.31) ADDITION/CLARIFICATION: Add to end of rule:Accentuated torpedoes affected by a target accentuator mustannounce their new speed in Stage (6B6) as the last action in theLaunch plasma torpedoes step.(OE15.325) NEW RULE/CLARIFICATION: A given targetaccentuator is not limited to accentuating the HEAT torpedoeslaunched by the unit it is on, nor are Heat Torpedoes restricted toaccepting guidance only from the unit which launched them.They can only be affected by a target accentuator fired by a uniton the same side as the unit that launched them.(OE15.42) CLARIFICATION: Add to end of rule: “. . . except byground bases.”(OE16.322) CHANGE second sentence to read: Damage scoredby implosive shells is resolved first, before any other weapons inthe same volley, except energy howitzers (OE14.32) andtransporter-collector beams (OE26.314).(OE16.322) CLARIFICATION: If two different units fire implosiveshells, perhaps in addition to other rounds or weapons (phasers,hellbores, and etc.), so that different phasers on the target will behit (D4.321), use the following procedure to satisfy (D4.34). First[after resolving any energy howitzer shield damage (OE14.32)]determine which firing unit did the most implosive damage (ifboth scored the same amount of implosive damage, roll a die to

select which will be resolved first). Score the damage caused bythat ship’s implosive rounds, and if the shield is destroyed,determine if any implosive damage from that volley will beresolved as internal damage. Then determine which of the twoships will now score the most internal damage to determine theorder of damage resolution for purposes of (D4.321). If the shieldis not destroyed, resolve the implosive damage from the secondvolley in the same way. If the shield is still not destroyed, resolvethe remaining damage of the two volleys normally. Note that thelarger volley may now be the smaller volley if it had moreimplosive shells than the second volley. This same procedure isused if three or more ships fire on the target shield from differentdirections, but the Implosive damage is always resolved first.(OE16.322) CLARIFICATION: If two different units fire implosiveshells, perhaps in addition to other rounds or weapons (phasers,hellbores, and etc.), so that different phasers on the target will behit (D4.321), use the following procedure to satisfy (D4.34). First[after resolving any energy howitzer shield damage (OE14.32)]determine which firing unit did the most implosive damage (ifboth scored the same amount of implosive damage, roll a die toselect which will be resolved first). Score the damage caused bythat ship’s implosive rounds, and if the shield is destroyed,determine if any implosive damage from that volley will beresolved as internal damage. Then determine which of the twoships will now score the most internal damage to determine theorder of damage resolution for purposes of (D4.321). If the shieldis not destroyed, resolve the implosive damage from the secondvolley in the same way. If the shield is still not destroyed, resolvethe remaining damage of the two volleys normally. Note that thelarger volley may now be the smaller volley if it had moreimplosive shells than the second volley. This same procedure isused if three or more ships fire on the target shield from differentdirections, but the Implosive damage is always resolved first.(OE16.322) CORRECTION: The example should read: “Forexample, if a heavy implosive shell caused six damage to a shipand three of that penetrated . . .” Also, damage scored byimplosive shells is resolved first, before any other weapons in thesame volley, except Energy Howitzers (OE14.32). Internaldamage, or damage to unshielded targets, is doubled, thencombined with other damage in the same volley.(OE16.34) ADDITION: Light hypercannons on fighters have amaximum range of 12 hexes.(OE16.35) CLARIFICATION: FEEDBACK: Hypercannons do notnormally cause feedback because they cannot be fired at rangezero.(OE17.11) CLARIFICATION: SSD: Focused energy beams areshown as “FEB” on the SSD. Each is recorded and firedseparately.(OE17.12) CLARIFICATION: DESTRUCTION: Focused energybeams are destroyed on “torpedo” damage points.(OE17.121) CLARIFICATION/NEW RULE: DAMAGEPRIORITY: FEBs are destroyed after special sensors replacing atorpedo and jammers, and before warp augmented railguns.(OE17.13) CLARIFICATION/NEW RULE: CREW QUALITY,LEGENDARY OFFICERS: Outstanding crews use (G21.211),Poor crews use (G21.111), and Legendary Weapons Officersuse (G22.721); treat the focused energy beam as a hellbore(E10.0).(OE17.14) CLARIFICATION/NEW RULE: TECHNOLOGYRESTRICTIONS: Can only be used in Omega and simulatoroption mounts.(OE17.141) CLARIFICATION/NEW RULE: The FEB requiresone option mount space.(OE17.142) CLARIFICATION/NEW RULE: The APB costs 0BPV under Annex #8B.(OE17.142) CLARIFICATION/NEW RULE: The FEB costs 0BPV under Annex #8B.(OE17.15) CLARIFICATION/NEW RULE: TACTICALINTELLIGENCE: Focused energy beams are distinguished fromother weapons and each other (heavy or light) at TacticalIntelligence Level F (D17.4). The arming status (armed or not) isknown at Tactical Intelligence Level L.

(OE17.16) ADDITION: FIGHTERS: FEBs can be used onfighters but require special pods. Further rules for fighter-mounted FEBs appeared in Omega #3, see (OJ2.71) and(OJ2.8).(OE17.24) CORRECTION: Insert “a” between “. . . once in . . .”and “. . . turn . . .”.(OE17.26) CLARIFICATION/NEW RULE: FEEDBACK: FEBs donot normally cause feedback even if fired at range zero, but seethe Qixavalor cloud (OP1.22).(OE17.54) CHANGE RULE TITLE TO: SIZE CLASS SEVENTARGETS: Move rules text down to (OE17.541).(OE17.541) MOVED RENUMBERED RULE: FEBs are heavyweapons penalized under (FD1.52) when firing at drones.(OE17.542) CLARIFICATION/NEW RULE: FEBs cannotdamage plasma weapons (FP1.62).(OE17.543) CLARIFICATION/NEW RULE: FEBs are subject to(M8.52) when used to sweep mines.(OE17.56) CLARIFICATION/NEW RULE: TERRAIN: FEBscannot be fired through a hex containing a planet (P2.321), moon[Exception: (P2.3221)], star (P12.1), black hole (P4.23) or pulsar(P5.32). They can be fired into such a hex. They can be firedthrough asteroid (P3.33), ring (P2.223), dust (P13.4) hexes withthe standard EW penalties. See (OP1.22) for the Qixavlor cloud.(OE17.57) CLARIFICATION/NEW RULE: WEBS: Focusedenergy beams cannot fire through (G10.61) or damage webs.They can fire at targets in webs, or from web hexes to targetsoutside of them if a valid line of sight between the firing ship andthe target exists.(OE18.11) CLARIFICATION: SSD: Antiproton beams are shownas “APB” on the SSD. Each is recorded and fired separately.(OE18.12) CLARIFICATION/NEW RULE: DESTRUCTION:Antiproton beams are destroyed on “torpedo” damage points.(OE18.121) CLARIFICATION/NEW RULE: DAMAGEPRIORITY: Anti beams are destroyed after photons, lightphotons, tachyon guns, and antiproton lances, and before energyspark rings and plasma–L torpedoes.(OE18.13) CLARIFICATION/NEW RULE: CREW QUALITY,LEGENDARY OFFICERS: Outstanding crews use (G21.211),Poor crews use (G21.111), and Legendary Weapons Officersuse (G22.721); treat the focused energy beam as a hellbore(E10.0).(OE18.14) CLARIFICATION/NEW RULE: TECHNOLOGYRESTRICTIONS: Can only be used in Omega and simulatoroption mounts.(OE18.141) CLARIFICATION/NEW RULE: The APB requiresone option mount space.(OE18.15) CLARIFICATION/NEW RULE: TACTICALINTELLIGENCE: APBs are distinguished from other weapons atTactical Intelligence Level G (D17.4). Arming status is known atTactical Intelligence Level L. Total amount of power used to armthe weapon is known at Tactical Intelligence Level M.(OE18.16) NEW RULE: FIGHTERS: APBs can be used onfighters (in Omega #3 only the Dirk fighter appears). APBs onfighters have a maximum range of 11 hexes. See also (OJ.8).(OE18.25) ADDITION: Add to end of rule: If holding energy is notprovided the weapon is discharged (E1.24).(OE18.26) ADDITION: Add to end of rule: If an APB is completedwith reserve energy during a turn and not fired, it can be held(OE18.25) or discharged (E1.24) during the next EnergyAllocation Phase.(OE18.34) CLARIFICATION/NEW RULE: FEEDBACK: If a APBscores a hit on its target at a true range of zero, damage equal toone-fourth the damage caused to the target (drop fractions) isscored on the facing shield of the firing ship. This does notreduce the damage done to the target or affect any other ship.For example, an APB that rolled two sixes on table (OE18.41)would score 15 points of damage on the target, but only threepoints of damage on its own facing shield. Fractions are droppedfor each antiproton beam individually, they are not summed.(OE18.55) REVISED/RENAMED: SIZE CLASS SEVENTARGETS:

(OE18.551) MOVED TEXT RENUMBERED: Antiproton beamsare heavy weapons penalized under (FD1.52) when firing atdrones.(OE18.552) NEW RULE: APBs cannot damage plasma weapons(FP1.62).(OE18.553) NEW RULE: Antiproton beams are subject to(M8.52) when used to sweep mines.(OE18.58) NEW RULE: TERRAIN: APBs cannot be fired througha hex containing a planet (P2.321), moon [Exception: (P2.3221)],star (P12.1), black hole (P4.23) or pulsar (P5.32). They can befired into such a hex. They can be fired through asteroid (P3.33),ring (P2.223), dust (P13.4) hexes with the standard EWpenalties. See (OP1.22) for the Qixavlor cloud.(OE18.59) NEW RULE: WEBS: APBs cannot fire through(G10.61) or damage webs. They can fire at targets in webs, orfrom web hexes to targets outside of them with a valid line ofsight.(OE19.16) NEW RULE: MINIMUM SIZE: TAs cannot be placedon units smaller than Size Class 4 (Exception: Ground Bases).(OE19.22) CORRECTION: “Antiproton beam” should be“antiproton lance.”(OE19.32) ADDITION: Add to rule: When the effective range ofan LNC is different from the true range (D1.4), use the effectiverange to determine if the LNC will function.(OE19.331) CORRECTION: Reference (OE19.223) should be(OE19.333).(OE19.333) CORRECTION: Last sentence refers to antiprotonlances as ANC rather than LNC. Delete the “a” in the phrase “. . .not required that a three APBs . . .”.(OE19.44) CORRECTION: Delete “In emergencies”. Thisconfuses some players that there is some other criteria for usinga LNC as an APB, like being crippled.(OE19.442) CHANGE: When fired as an antiproton beam anantiproton lance on a Ymatrian ship has an FA firing arc.(OE19.48) ADDITION: SIZE CLASS SEVEN TARGETS:(OE19.481) ADDITION: LNCs can target drones, normally(OE19.31).(OE19.482) ADDITION: LNCs cannot damage plasma weapons(FP1.62).(OE19.483) ADDITION: LNCs cannot help APBs sweep mines.(OE19.59) ADDITION: WEBS: LNCs cannot fire through(G10.61) or damage webs. They can fire at targets in webs, orfrom web hexes to targets outside of them with a valid line ofsight.(OE20.0) ADD: This weapon was developed from a Klingon ADDsystem that was in the cargo bay of the Throne of Ozymondas.(OE20.13) NEW RULE: FIGHTERS: Short-range cannon can beused by fighters. See (OJ2.72) and (OJ2.8).(OE20.242) ADDITION: Add to end: It cannot penetrate asubspace energy field (OG14.0) and will not damage anything inan hex of such a field (the field will damage such things).(OE20.27) NEW RULE: FEEDBACK: SRCs will cause feedbackin the Qixavalor clod (OP1.22).(OE20.3) CONFIRM: The short-range cannon increases itsdamage against closer targets while its hit probability decreases.(OE21.111) NEW RULE: DAMAGE PRIORITY: DMPs aredestroyed after phaser-2s, early warp-tuned lasers, improvedpulse emitters, and pulse emitters, but before twin warp-tunedlasers. Light dark matter pulsars are destroyed after phaser-3sbut before light warp-tuned lasers.(OE21.13) ADDITION: Add to end: The H-DMP takes one optionmount and costs one BPV. The L-DMP takes on option mountand reduces the BPV of the unit by a half-point.(OE21.14) ADDITION: TACTICAL INTELLIGENCE: Thepresence of DMPS & (Last S should be lower case? ScottMoellmer 5 April 2007 REPLY: Fixed.(OE21.14) ADDITION: TACTICAL INTELLIGENCE: Thepresence of DMPs can be distinguished at Tactical IntelligenceLevel G (D17.4). The actual DMP type can be distinguished atTactical Intelligence Level I. Arming levels cannot be detected.

(OE21.15) ADDITION: Add to end: L-DMPs are used by SouldraShards (OJ4.0).(OE21.522) ADDITION: Add to end of rule: “. . . if they fire onlyonce in a turn (G24.1342).”(OE21.59) ADDITION: OTHER RULES: For any interaction notspecifically defined otherwise, e.g., webs, DMPs are treatedexactly as phasers are.(OE22.11) ADDITION: SSD: Subspace rockets are designated“SSR” on the SSD. Each is recorded and fired separately.(OE22.12) ADDITION: DESTRUCTION: Subspace rockets aredestroyed on “torpedo” damage points.(OE22.121) ADDITION: DAMAGE PRIORITY: Subspace rocketsare destroyed after plasma-Ss, implosion-Hs, and fireballs, butbefore particle beams.(OE22.13) ADDITION: TACTICAL INTELLIGENCE: SSRs aredistinguished from other weapons at Tactical Intelligence Level G(D17.4). Arming status is known at Tactical Intelligence Level L.Total amount of power used to arm the weapon is known atTactical Intelligence Level M.(OE22.13) ADDITION: TECHNOLOGY RESTRICTIONS: Canonly be used in Omega and simulator option mounts.(OE22.131) ADDITION: The SSR requires one option mount.(OE22.132) ADDITION: The SSR costs 0 BPV under Annex #8B.(OE22.14) NEW RULE: FIGHTERS: Subspace rockets are usedby some Worb fighters. See (OJ2.73) and (OJ2.8).(OE22.23) CLARIFICATION: SSRs are fired during the Direct-Fire Weapons Fire Stage (6D2) of the Impulse Procedure. Theireffect is determined one or more impulses later by die roll(OE22.35) DURING A SUBSEQUENT DIRECT-FIRE WEAPONSFIRE STAGE (6D2). The target and the amount of energy in theSSR (OE22.21) IS RECORDED IN THE FIRE ALLOCATIONSTAGE (6D1) OF THE IMPULSE IT IS FIRED, but not revealeduntil the weapon strikes its target, which may be up to fiveimpulses later (OE22.35) [exceptions; see (OE22.56)]. 14 Feb2007(OE22.359) CLARIFICATION: Some have been confused by theexample indicating the addition 20 points of power to the fourSSRs, and believe it should only be 16. The weapons werearmed with a total of 20 points of power, of which four pointswere reserve power allocated on Turn #1. This four points is alsonot available (i.e., the batteries are empty), and if the Worbwanted to preserve his tactical options, he is going to have toallocate four points to the batteries, and NOT get four points outof the batteries to operate the systems on his ship. In the lastparagraph it is the Worb is who “. . . gains some comfort . . .”(OE22.58) ADDITION: LEGENDARY OFFICERS: LegendaryWeapons Officers have the same effect on SSRs as OutstandingCrews (OE22.561). A Legendary Weapons officer can cancel thepoor crew modifiers (OE22.562), but cannot be combined with anoutstanding crew’s modifiers.(OE23.145) ADDITION: Light photons require one option mountand reduce the BPV of the ship by 0.25 points under Annex #8B.(OE23.15) ADDITION: TECHNOLOGY RESTRICTIONS: Lightand heavy photon torpedoes are Federal Republic of Auroratechnology and can only be used in Omega and simulator optionmounts.(OE23.151) ADDITION: Heavy photons require two adjacentcenterline option mounts and cannot be used on ships smallerthan Size Class 3. It costs two BPV under Annex #8B.(OE23.16) NEW RULE: FIGHTERS: Light photons (OJ2.76) arecarried by some Federal Republic of Aurora fighters in ModuleOmega #3. Fighters able to carry standard and heavy photonsmay be added in later products, and will use the rules in (OJ2.76)for loading. See also (OJ2.8). Photon torpedoes of all three typeshave a maximum range of 12 hexes unless the description of thefighter says otherwise. They can be fitted with proximity fuzes.(OE24.0) CORRECTION: The Tachyosonic Beam tables in thisrule are correct, those on the Singer SSDs are wrong and shouldbe ignored. We apologize for this blunder. It was the result ofcommunications lags between Amarillo, Texas and Dayton, Ohio.(OE24.16) NEW RULE: FIGHTERS: Light tachyosnic beams canbe used on fighters, see (OJ2.74) and (OJ2.8).

(OE24.31) CORRECTION: “. . . Roll one die and . . .” should be “.. . Roll two dice and . . .”.(OE24.315) ADDITION/CLARIFICATION: Add to end of rule: Itcannot be distracted by a wild weasel (J3.0), but remains lockedon its target.(OE24.317) NEW RULE CLARIFICATION: If the target on whicha TSB is focused docks [(C13.0) or (K2.3) to a larger unit orlands aboard (J1.6) a larger unit, the TSB will fire any remainingpulses at the larger unit. If the target is the same size, or larger,than a unit to which it has docked or landed aboard, the TSBremains focused on the original target.(OE24.353) ADDITION: ADD TO END: A TSB that beginsarming at any level can be converted to a critical overload aslong as the first turn’s arming is only six points of power.EXAMPLE: A TSB allocated two points during arming on Turn #1could be converted by applying four points of reserve power. ATSB armed with two points of power on Turn #1 and allocated apoint of power on Turn #2, could be converted to a criticaloverload by being provided six points of reserve power. The firstturn’s arming would be lost and the other six points needed tocomplete the critical overload would have to be provided duringEnergy Allocation of Turn #3.(OE24.353) CORRECTED: To use a critical overload, theweapon is armed with six points of power on the first turn ofarming and six points on the second. No other sequence ispermitted except for a held overloaded torpedo being increasedto a critical overload, which requires three points of power thatmay only be applied during Energy Allocation. A TSB armed as acritical overload may not be held and if not fired it must bedischarged under (E1.24). It has a maximum range of 4 hexes. Acritically overloaded torpedo must be marked with a “C” on theEnergy Allocation Form.(OE24.354) CORRECTION: Example refers to adding two powerto increase one overload level. Should be three power by(OE24.351) to (OE24.353). Holding energy paid to maintain thetorpedo being upgraded by reserve power does not count asenergy for the upgrade of the weapon.(OE24.371) DELETED TEXT: Changed to: See table (OE24.42).(OE24.372) DELETED TEXT: Changed to: See table (OE24.42).(OE24.373) DELETED TEXT: Changed to: See table (OE24.42).(OE24.38) FEEDBACK: Tachyosonic beams only causefeedback in the Qixavalor cloud (OP1.22).(OE24.42) CORRECTION: LTSB on chart should be ELTSB.(OE24.54) REVISED RULE: SIZE CLASS SEVEN TARGETS:(OE24.541) REVISED RULE: TSBs are penalized by (FD1.52) iffired at drones.(OE24.542) ADDITION: TSBs cannot damage plasmatorpedoes.(OE24.543) ADDITION: TSBs cannot be fired at mines due totheir myopic zone (OE24.33).(OE24.58) ADDITION: TERRAIN: TSBs cannot be fired througha hex containing a planet (P2.321), moon [Exception: (P2.3221)],star (P12.1), black hole (P4.23) or pulsar (P5.32). They can befired into such a hex. They can be fired through asteroid (P3.33),ring (P2.223), dust (P13.4) hexes with the standard EWpenalties. See (OP1.22) for the Qixavalor Cloud.(OE24.59) ADDITION: WEBS: TSBs cannot fire through webs,and cannot damage them. TSBs can fire out of web hexes, andcan damage targets stuck in webs, provided a legal line of fireexists between the firing ship and the target in the web hex.(OE25.0) CORRECTION: SONIC PULSERS AND PHASERCAPACITORS: The rule is in error and Singers began usingphaser capacitors in Y175. The reference to Y183 was when theLoriyill began transferring other technology to the Singers.(OE25.11) ADDITION: SSD: Sonic Pulsers are shown as “SP”on the SSD. Each is recorded and fired separately.(OE25.12) ADDITION: DESTRUCTION: Sonic pulsers aredestroyed on “phaser” damage points.(OE25.121) ADDITION: Sonic pulsers fall after dark matterpulsars and twin warp-tuned lasers but before phaser-3s. SeeAnnex #7E.

(OE25.13) ADDITION: TECHNOLOGY RESTRICTIONS: Canonly be used in Omega and simulator option mounts.(OE25.131) ADDITION: Sonic pulsers requires one option mountspace.(OE25.132) ADDITION: Sonic pulsers reduce the BPV of the unitthey are installed on by 0.25 points each under Annex #8B.(OE25.14) ADDITION: FIGHTERS: Sonic pulsers can be usedon fighters without change, see (OJ2.75).(OE25.15) ADDITION: TACTICAL INTELLIGENCE: Sonicpulsers can be distinguished at Tactical Intelligence Level G(D17.4). Arming status (i.e., armed or unarmed, if capacitors arenot available) is known at Tactical Intelligence Level L.(OE25.17) NEW RULE: PHASERS: Sonic pulsers use all therules for phasers except where defined differently below, i.e.,they cannot fire through webs but can fire into webs and out ofwebs so long as a valid line of sight exists. They interact withterrain exactly as phasers do. Legendary officers and crewquality affect them in the same way as phasers. And so on.(OE25.17) NEW RULE: PHASERS: Sonic pulsers use all therules for phasers except were & Should be where? ScottMoellmer 5 April 2007 REPLY: Fixed.(OE25.18) ADDITION: THOLIANS cannot modify SPs to firethrough web.(OE25.21) CORRECTION: The rule is in error and Singersbegan using phaser capacitors in Y175. The reference to Y183was when the Loriyill began transferring other technology to theSingers.(OE25.51) ADDITION: Add to end: “. . . but a surprised ship(D18.0) may not fire a sonic pulser until it has been activated(D18.3).”(OE26.121) ADDITION: PRIORITY OF DAMAGE: TCBs fall afterkinetic cannon-lights and before tractor-repulsor-heavies. SeeAnnex #7E.(OE26.14) NEW RULE: FIGHTERS: Transporter-collectorbeams can be used on fighters, see (OJ2.74) and (OJ2.8).(OE26.25) NEW RULE: Power held in fighter capacitors(OR19.F0) or loaded into the TCB of a fighter can be heldindefinitely at no cost.(OE26.313) CHANGE LAST SENTENCE TO READ: Note thatAndromedans, who do not have shields, and Jindarian asteroidships not operating their minimum shields (R16.1A), andBranthodon dragonships (OR22.0) will always receive thedamage listed in the second position.(OE26.314) CHANGE TO READ: If a TCB hits a ship at thesame time as other weapons, the TCB is assumed to hit first,even before energy howitzers (OE14.32), hypercannon implosionrounds (OE16.322), and plasma whips (OE11.312) for purposesof determining whether shields were available to block damageunder (OE26.312).(OE26.314) CHANGE TO READ: If a TCB hits a ship at thesame time as other weapons, the TCB is assumed to hit first,even before energy howitzers (OE14.32) and hypercannonimplosion rounds (OE16.322), for purposes of determiningwhether shields were available to block damage under(OE26.312). Good point, TCBs are pretty much beforeeverything (sayeth Darn it! From a Ryn lover&<g>) ScottMoellmer 5 April 2007 REPLY: I am pretty sure the Ryn wouldrather it hit after the other weapons, but someone had to make achoice of which of these weapons hit first. I am astounded thatthis problem does not seem to have been noticed er this.(OE26.3411) NEW RULE: In cases of a Ryn "civil war" scenariowhere the target is another unit with CC-armor the number ofdamage points in (OE26.341) is divided by two (dropping anyfractions) because the recovered material is already rich in thematerials needed to replace CC-Armor. Nicely thot. ;) ScottMoellmer 5 April 2007 REPLY: Thanks.(OE26.3411) NEW RULE: In cases of a Ryn “civil war” scenariowhere the target is another unit with CC-armor the number ofdamage points in (OE26.341) is divided by two (dropping anyfractions) because the recovered material is already rich in thematerials needed to replace CC-Armor.

(OE26.3412) NEW RULE: Material recovered from "living"targets to include living space monsters, Branthodon dragonships, and Alunda ships whose shields have been penetratedprovides only half the restorative material. In these cases dividethe number of damage points in (OE26.341) by eight, but roundany fractions up, i.e., the TCB will always recover at least a pointof material to restore the CC-armor.(OE26.3412) NEW RULE: Material recovered from “living”targets to include living space monsters, Branthodon dragonships, and Alunda ships whose shields have been penetratedprovides only half the restorative material. In these cases dividethe number of damage points in (OE26.341) by eight, but roundany fractions up, i.e., the TCB will always recover at least a pointof material to restore the CC-armor.(OE26.355) ADDITION: FEEDBACK: TCBs never causefeedback, not even in the Qixavalor Cloud (OP1.213).(OE26.355) NEW RULE: FEEDBACK: TCBs never causefeedback, not even in the Qixavalor Cloud (OP1.213).(OE26.58) ADDITION: Add to end: “. . . it can only be used insimulators.”(OE26.581) ADDITION: The TCB requires two adjacentcenterline option mounts.(OE26.582) ADDITION: The TCB increases the BPV of the shipby two points. See annex #8B.(OE27.14) NEW RULE: FIGHTERS: Focused tractor beams canbe used on fighters, see also (OJ2.8).(OE27.35) ADDITION: If the target unit is not itself a Boloscounit, the power used for negative tractor is not required to comefrom warp engine sources.(OE27.511) CLARIFICATION: Delete the last sentence of thisrule which reads: “Note specifically that there is no damagebenefit if fired at a target that is at a true range of nine hexes.”(OE28.121) ADDITION: DAMAGE PRIORITY: Gauss cannonsare destroyed after phaser-1s, anti-fighter defense systems, andmedium warp-tuned lasers for purposes of (D4.3221). See Annex#7E.(OE28.14) NEW RULE: TECHNOLOGY: GCs are Qixa onlytechnology. They can only be used in simulator option mountsand require one option mount space. The cost of the weapon isone BPV. Mega gauss cannons cannot be used even in thesimulators.(OE28.15) NEW RULE: SHUTTLES: Gauss cannons are usedon shuttles but are limited to a range of 15 hexes. The Qixa didnot themselves develop fighters, but sometimes employedmercenary fighters from other races. Such mercenary fighters willnot be armed with gauss cannons.(OE28.2) ADDITION: Gauss cannons on Size Class 5 or smallerunits (excluding ground bases) have a maximum range of 15hexes.(OE28.22) CLARIFICATION: Gauss cannons fire during theDirect-Fire Weapons Fire Stage (6D2). 14 Feb 2007(OE28.3) ADDITION: Add to end: A given hex of the Qixavalorcloud can only be subject to spark damage once per damagestage. If two or more gauss cannons that are spark enabledstrike a target in a hex of the Qixavalor cloud, there will be onlyone die roll.(OE28.33) ADDITION: Gauss cannons do not otherwisegenerate feedback even if fired at range zero.(OE28.4) CORRECTION: The Gauss Cannon Table in this rule isincorrect, and the tables on the SSDs are correct, the GaussCannon only scores damage on a roll of “1” at ranges over 25hexes.(OE29.13) NEW RULE: TECHNOLOGY: ESRs are Qixa onlytechnology. They can only be used in simulator option mountsand require one option mount space. The cost of the weapon isone BPV.(OE29.14) NEW RULE: FIGHTERS: The Qixa are not known tohave deployed fighters of their own, but had they done so, it ispossible that a fighter design using this weapon might have beenproduced. If such a design is published at a later date, it willinclude the rules for arming and firing the weapon.

(OE29.34) NEW RULE: FEEDBACK: ESRs cause feedbackdamage to the firing unit if fired at range zero with more than twopoints of energy. If fired at three points of energy the feed back isone point of damage to the facing shield. If fired with four pointsof energy the feedback is two points of damage to the facingshield. This feed back damage is doubled inside the Qixavalorcloud (OP1.0).(OE29.54) REVISED RULE: SIZE CLASS SEVEN TARGETS:(OE29.541) MOVED RULE: Energy spark rings are penalized by(FD1.52) if fired at drones.(OE29.542) NEW RULE: ESRs cannot damage plasmatorpedoes.(OE29.543) NEW RULE: ESRs are penalized by (M8.52) if firedat mines.(OE29.58) NEW RULE: WEBS: ESRs cannot fire through websof greater than strength zero (G10.61), and cannot damagethem. Tachyon guns can fire out of web hexes, and can damagetargets stuck in webs, provided a legal line of fire exists betweenthe firing ship and the target in the web hex.(OE30.11) CLARIFICATION: There will be a parentheticalnumber after the title of the Eyebeam Table that will indicate thenumber of Eyebeams that dragonship has. For example, the OldDragon Ship’s (OR22.7) Eyebeam Table reads “OLD EYEBEAMTABLE (2)”, where the numeral “2” is the number of eyebeams.All dragonships in Module Omega #4 have two eyebeams,dragonships in later products might have more, or might haveonly one.(OE30.113) NEW RULE: The term “eye-beams” is used to referto the product of a dragon-eye firing and does not refer to a newor different system.(OE30.14) NEW RULE: TECHNOLOGY: Dragon-eyes are anorganic component of the space dragon on which the Branthodonship is built. They cannot be used by any non-dragon unit, noteven in the simulators. This includes their use by shuttles orfighters.(OE30.545) CHANGE: Change this rule to read: A dragonshipcan be on passive fire control (D19.0) and operate its dragon-eyes with the natural fire control of the dragon, but cannot gainthe EW benefits of passive fire control (D19.31) due to the natureof the dragon.”(OE30.546) ADDITION: ECM generated by the exoskeletonprotects the dragon as well as the exoskeleton.(OE31.16) NEW RULE: FIGHTERS: Caseless antimatter can beused to arm the antimatter cannons on fighters equipped withsuch weapons. The actual arming of the fighter is identical in allways [except for the reduced energy cost (OE31.11)] as arming anormal antimatter cannon shot. See (OJ2.61) and (OJ2.8).(OE31.21) CLARIFICATION: Caseless antimatter cannon shotsare fired during the Direct-Fire Weapons Fire Stage (6D2). 14Feb 2007

(OFD0.0) ERRATA

(OFD0.0) ADDITION: GENERAL NOTE REGARDING DRONE-LIKE SEEKING WEAPONS LISTED HEREAFTER Exceptwhere specifically provided for otherwise, all drone rules (FD0.0)apply to any weapons listed in section (OFD0.0), e.g., they havea counter which moves across the map, must be guided to theirtargets, can be distracted by scout channels or chaff, etc. This isby no means an all-inclusive list. In other words, these weaponswork like drones except as otherwise listed in their individualrules.(OFD0.0) CLARIFICATION: GENERAL NOTE REGARDINGDRONE-LIKE SEEKING WEAPONS LISTED HEREAFTER:Except where specifically provided for otherwise, all SeekingWeapon Rules (F0.0) and drone rules (FD0.0) apply to anyweapons listed in section (OFD0.0), e.g., they have a counterwhich moves across the map, must be guided to their targets(unless equipped with self-guidance), can be distracted by scout

channels or chaff, are launched when drones are launched in theSeeking Weapons Stage (6B6), etc. This is by no means an all-inclusive list. In other words, these weapons work like dronesexcept as otherwise listed in their individual rules. 14 Feb 2007(OFD1.0) DELETION: Delete reference to Tachyon Missilesacting like drones unless otherwise noted as this is explained inthe general note on drone like weapons (OFD0.0).(OFD1.12) ADDITION: See (OFD1.16) for launch restrictions.(OFD1.123) ADDITION/CLARIFCATION: A given TC rackcannot launch a missile with a quarter turn of its launching amissile on a previous turn. This means that a TC rack thatlaunched a missile on Impulse #26 of Turn #1 cannot launchanother missile any earlier than Impulse #2 of Turn #2.(OFD1.135) CLARIFICATION/NEW RULE: A “destroyed” rackcannot be used to resolve another “drone” damage pointadministered by the DAC even though it still has rack spacesremaining. It must first be repaired. Exception, hit-and-run raidsmay be made against a “destroyed” rack, and any successful hit-and-run will destroy another rack space and the missile within it,or an empty rack space if no spaces holding tachyon missilesremain in that rack.(OFD1.135) ERRATA ITEM: I have rescinded this (since I wroteit, it does not appear anywhere else in the errata, this is just anote to let you all know) and have replaced it with (OFD1.16).(OFD1.16) CLARIFICATION/NEW RULE: The number and typeof missile racks on a given unit determines the maximum rate atwhich it can launch missiles.(OFD1.161) CLARIFICATION/NEW RULE: Rack types TA, TB,TD, or TE must be paired. In all cases racks #1 and #2 are a pair,and racks #3 and #4 are considered a pair, and so on up to themaximum number or racks on a ship, except that any TC racksare never paired with other racks, or even with other TC racks.(OFD1.162) CLARIFICATION/NEW RULE: If a unit has an oddnumber of type TA, TB, TD, or TE racks, the last rack is a pairunto itself. If a unit has two racks of two different type, e.g., oneTA rack and one TB (or TD or TE) rack, these will be paired. Ifthe unit had four racks of all four different types they will bepaired by their numbers, i.e., rack #1 and rack #2 are a pair.Exception: TC racks are never paired with other racks.(OFD1.163) CLARIFICATION/NEW RULE: No single rack oftype TA, TB, TD, or TE can launch more than once in any twoconsecutive turns. For example, a unit with two type-A racks canlaunch a single missile from either rack on Turn #1 but cannotlaunch a missile from both racks on Turn #1). It cannot launch amissile from Rack #1 on Turn #1 and then launch another missilefrom Rack #1 on Turn #2, only Rack #2 would be able to launchon Turn #2. Note that Rack #2 could have launched on Turn #1and Rack #1 would then be the one that could launch on Turn #2.If in either case, if a Missile was launched on Turn #1, and nomissile was launched on Turn #2, either rack could launch amissile on Turn #3 so long as only one of the racks launches amissile.(OFD1.164) CLARIFICATION/NEW RULE: If a unit has both TA,TB, TD, or TE and type TC racks, the restrictions on launch ratesfor the TA, TB, TD, and TE racks remain. The non-TC rackscannot launch more than one missile every other turn from anygiven rack, and no more than one missile from each pair of suchracks in a given turn. TC racks are not restricted by the presenceof other racks and operate at their own rate, i.e., each TC rackmay launch one missile each turn per such rack as long as eachrack only launches one missile in a given turn and has a missileto launch. TC racks never count for determining the launch rateof non-TC racks on a given unit.(OFD1.165) CLARIFICATION/NEW RULE: A TA (or other non-TC rack) rack of a given pair could launch a missile on Impulse#32 of one turn, and the rack in the pair could launch a missile onImpulse #1 of the following turn. There is no quarter turn delaybetween the racks of a given pair launching their missiles so longas the other restrictions of the rules are met.(OFD1.17) CLARIFICATION/NEW RULE: TECHNOLOGY:Tachyon missiles are Omega technology. They can only be used

in simulators outside of the Omega Octant. See Annex #8 for thecost of putting a tachyon missile rack in an option mount. Anyrack includes the cost of standard missiles (OFD1.221) in itscost. Tachyon Rack-Es can only be used in option mounts onbases.(OFD1.212) CLARIFICATION: Propulsion size points are not“mass” under (OFD1.211), but restrict the amount of mass thatcan be added to a missile under (OFD1.23). Example: AStandard Missile (OFD1.221) is size 8, if its propulsion systemwas exchanged for a Propulsion 36 system (OFD1.234) it wouldhave only two size points remaining for mass. The mass wouldreduce the speed of the missile to 34, but the fastest any missilecan move is 32, so the two extra speed would simply be lost inthis case.(OFD1.2716) CLARIFICATION/NEW RULE: Tachyon missilescannot lend their EW to other units, not even to other missiles inthe same hex as themselves.(OFD1.2723) CHANGE/CLARIFICATION: “The change is madein the Seeking Weapons Stage (6B6) at the same point as newseeking weapons are launched” to “The change is made in theSeeking Weapons Stage (6B6) at the same point as new dronesare launched”. 14 Feb 2007(OFD1.2723) CORRECTION: “. . . the missile can have its targetchanged at the controlling unit’s discretion” to “. . . the missile canbe programmed to change targets during flight.” Later in the rule,change the word “drone” to “missile.”(OFD1.2723) CORRECTION: Delete the text “The turn andimpulse of the target change must be recorded in advance.” Add:“The change is made in the Seeking Weapons Stage (6B6) at thesame point as new seeking weapons are launched. The newtarget of the Missile must be announced at that time, it cannot bekept secret under (F3.6).”(OFD1.2723) ERRATA TO REPLACE BOTH OF THE ABOVE:In Y192, a re-programmable guidance module (RGM) wasdeveloped after over a century of observing the Probr HEAT(OFP2.0). Once per turn, and not within a quarter turn of achange made on a previous turn, the missile can be ordered tochange targets during flight. The change is made in the SeekingWeapons Stage (6B6) at the same point as new missiles/dronesare launched. The new target of the Missile must be announcedat that time, it cannot be kept secret under (F3.6). This allows amissile to have its target changed from a wild weasel to anothership, among other uses. The module cannot be used to ignore awild weasel and re-target the ship the weasel is protecting. The 4impulse delay of (OFD1.311) applies after every such targetingchange. While an RGM can be combined with either the ATGmodule or the Type-III module, once a missile has been releasedto its own guidance, the RGM adds no further benefit. In order tochange the missile’s target, the controlling unit must be withineight hexes of the missile in question. An RGM costs 2 BPV and2 size points. All other errata items under this rule are rescinded.(OFD1.274) CORRECTION: Prior to this upgrade chaff onlydistracted tachyon missiles on a roll of one or two, not on rolls of1-4 as the rule currently says.(OFD1.355) NEW RULE: Chaff distracts tachyon missiles under(D11.32) only on a die roll of one or two. A later upgrade furtherreduced the ability of chaff to distract tachyon missiles; see(OFD1.274).(OFD1.355) RESCINDED: This rule addition is rescinded, i.e.,there is no rule (OFD1.355), the contents of this rule remain validand were incorporated into (OFD1.274).(OFD2.37) NEW RULE/CLARIFICATION: RESTRICTEDTECHNOLOGY: Transporter-emitter missiles are Ryn onlytechnology. They can only be used in simulator option mounts.The cost of the rack is zero BPV, but the rack has no missiles.Each missile purchased for the rack costs two BPV and has noassociated reload. Thus a given missile-rack, fully-loaded, wouldcost eight BPV with additional reloads costing another two BPVeach.

(OFD3.0) CHANGE/CLARIFICATION: Change “Ultrawarpmissiles move using the same rules as drones (FD0.0) exceptwhere otherwise noted. They are otherwise not drones and donot use any of the rules of drones unless specifically noted asdoing so, e.g., there are armored ultrawarp missiles (OFD3.254).”to “Ultrawarp missiles move using the same rules as drones(FD0.0) except where otherwise noted. They otherwise act asdrones unless specifically noted as doing otherwise, e.g., thereare armored ultrawarp missiles (OFD3.254), but their smallwarhead (OFD3.21) will not auto-kill a drone (FD1.56)”. 14 Feb2007(OFD3.131) CLARIFICATION: Add after first sentence:. [Anadvanced rack (OFD3.122) with two armed UWMs would loseboth.](OFD3.222) CLARIFICATION: Now reads: If the UWM entersthe hex of a seeking weapon that is tracking it, (or a seekingweapon tracking it enters its hex before it moves under the Orderof Precedence), that seeking weapon impacts (C1.453). If theimpacting seeking weapon destroys the UWM (this will normallybe the case, but note that many UWM warheads are not able todestroy another UWM), the UWM moves no further and isremoved from the board. In this latter case, see also (F2.5).(OFD3.253) CORRECTION: Restricted Availability and LimitedAvailability were mis-applied in this rule. The reference toRestricted Availability should be to Limited Availability, and thereference to Limited Availability should have been to RestrictedAvailability.(OFD3.254) CORRECTION: Restricted Availability and LimitedAvailability were mis-applied in this rule. The reference toRestricted Availability should be to Limited Availability, and thereference to Limited Availability should have been to RestrictedAvailability.(OFD3.255) CORRECTION: Restricted Availability and LimitedAvailability were mis-applied in this rule. The reference toRestricted Availability should be to Limited Availability, and thereference to Limited Availability should have been to RestrictedAvailability.(OFD3.37) NEW RULE/CLARIFICATION: OTHER DRONERULES THAT APPLY TO ULTRAWARP MISSILES: Whileultrawarp missiles are not “drones” (OFD3.0), many drone rulesapply to them under (OFD0.0).(OFD3.371) NEW RULE/CLARIFICATION: Scouts can attractultrawarp missiles (G24.23) or break their lock-ons (G24.22).(OFD3.372) NEW RULE/CLARIFICATION: Ultrawarp missilesare not self-guiding and require a controlling unit, just as non-self-guiding drones do. They go inert and are removed from playunder (FD1.71).(OFD3.373) NEW RULE/CLARIFICATION: Ultrawarp missilescan be identified under (G4.21), which will reveal the sameinformation as if they were a drone, i.e., type of warhead,damage points to destroy, target, etc.(OFD3.374) NEW RULE/CLARIFICATION: If ultrawarp missilesare fired on by heavy weapons they benefit as drones under(FD1.52).(OFD3.375) NEW RULE/CLARIFICATION: Ultrawarp missilesare treated as drones for purposes of their interactions withADDs (E5.0), SRCs (E20.0), and MCIDS (E6.0).(OFD3.376) NEW RULE/CLARIFICATION: Ultrawarp missilesinteract with ESGs as drones under (FD1.53).(OFD3.377) NEW RULE/CLARIFICATION: Ultrawarp missilesscore their listed damage if targeted on another non-plasmaseeking weapon (including another ultrawarp missile), they donot automatically destroy such seeking weapons.(OFD3.38) CLARIFICATION/NEW RULE: RESTRICTEDTECHNOLOGY: Ultra-warp missiles are Qixa only technology.They can only be used in simulator option mounts and requireone option mount space. The cost of the rack is zero BPV andcomes with a complete loading of missiles. Improved racks costtwo BPV each.

(OFP0.0) ERRATA

(OFP0.0) CLARIFICATION: It should be readily obvious that if aweapon here does not include a line on its table for “Bolting” thatthe weapon cannot be bolted. As none of these weapons wereincluded in the cost chart for creating Sabot versions (FP11.11),none can have a Sabot upgrade.(OFP0.0) GENERAL NOTE REGARDING NON-DRONESEEKING WEAPONS LISTED HEREAFTER Except wherespecifically provided for otherwise, all Seeking Weapon Rules(F0.0) and plasma rules (FP0.0) apply to any weapons listed insection (OFP0.0), e.g., they are self-guiding, have a counterwhich moves across the map, can be launched on passive firecontrol at targets more than four hexes distant, can begin armingwith reserve energy but not on the same turn that they werelaunched, are launched when plasma torpedoes are launched inthe Seeking Weapons Stage (6B6), etc. This is by no means anall-inclusive list. In other words, these weapons work like plasmatorpedoes except as otherwise listed in their individual rules. Itshould be readily obvious that if a weapon here does not includea line on its table for “Bolting” that the weapon cannot be bolted.As none of these weapons were included in the cost chart forcreating Sabot versions (FP11.11), none can have a Sabotupgrade. 14 Feb 2007(OFP1.12) CORRECTION: DESTRUCTION: Implosiontorpedoes are destroyed on “Torpedo” damage points.(OFP1.121) CLARIFICATION: This rule is correct; the listings inAnnex #7E (D4.3222) are incorrect. The reference to Annex #7Kshould be Annex #7E.(OFP1.122) CHANGE: Change both references to “drone” hits to“torpedo” hits.(OFP1.1221) CHANGE: Change reference to “drone” hits to“torpedo” hits.(OFP2.25) CHANGE/CLARIFICATION: The text that reads “. . .delivered by the target accentuator . . .” to “Delivered by a targetaccentuator . . .”.(OFP2.321) CLARIFICATION: Note that target accentuatorsoperate in the Scout Functions Stage (6B5) as the final step, sothe HEAT will not begin moving at the accelerated rate until thefollowing impulse (OE15.31) in the Previously Announced SpeedChanges Take Effect Step of the Voluntary Movements Stage(6A2). Heats that are increasing their speed as a result ofaccentuation announce this at the end of the Launch PlasmaTorpedoes Step of the Seeking Weapons Stage (6B6). Heatsthat are no longer under the effects of a target accentuator slowto normal speed in this same stage.(OFP2.321) CLARIFICATION: Note that the target accentuatorneed not be on the ship that launched the accentuated torpedo.(OFP2.331) CLARIFICATION: The target the AccentuatedTorpedo is going to change to must also be recorded, the playercannot select a new target after the torpedo has been launched.Note that the Torpedo’s new target can be its original target, i.e.,there is no actual change recorded, but if the torpedo isprogrammed to change targets, it will, except as provided by(OFP2.334).(OFP2.333) CLARIFICATION: Note that the re-targeting in thisrule is part of the normal programmed re-targeting of the torpedoand not an extra capability. This rule simply refers to the fact thatif the unit that was the original target launched a weasel, theweapon would still follow its re-targeting instructions. And that ifthe target it was to change too also had a weasel out, theweapon would accept the weasel as its new target, but wouldswitch to the correct target if the weasel was voided before it hit.(OFP2.334) CLARIFICATION: If an accentuated torpedo that isnot currently moving under accentuation changes its target asprogrammed before it was launched (OPF2.331) and its target isaccentuated by a target accentuator, the torpedo begins movingat the accentuated speed at that point.

(OFP2.36) CLARIFICATION: All “phaser damage” is treatedunder this rule. Thus a Plasma Whip (OE11.442) which scoredfive points of damage would only reduce the warhead by onepoint (leaving two points that could be added to another point).Note that terrain damage (asteroids) is also calculated as phaserdamage points (FP1.613) for plasma reduction, etc.(OFP2.384) CLARIFICATION: HEAT torpedoes cannot bebolted. For this reason, there is no “Bolt” table at the bottom ofany of the HEAT tables.(OFP2.421) CLARIFICATION: Under (OFP2.25) a torpedo isconsidered accentuated once the energy to create it as such isadded. If such a torpedo enters an atmosphere hex, it does notmatter if it is reacting to a target accentuator and moving atincreased speed or not, it is destroyed. The torpedo is destroyedbefore it damages any targets within the atmosphere.(OFP3.322) CLARIFICATION/NEW RULE: If a kinetic wave isreduced to zero strength while still gaining in size, i.e., in the 1-5or 6-10 range brackets, it is destroyed and removed from play. Itdoes not remain on the map as a zero strength (or negativestrength) wave. The act of reducing it to zero strength destroys itimmediately.(OFP4.11) REVISED: SSD: Dark matter torpedo launchers aredesignated “DMT” on the SSD.(OFP4.12) REVISED: DESTRUCTION: Dark matter torpedolaunchers are destroyed on “torpedo” damage points.(OFP4.121) ADDITION: For the purposes of damage priority and(D4.3222), dark matter torpedo launchers are destroyed afterlight tractor-repulsor beams, see Annex #7E.(OFP4.13) ADDITION: CREW QUALITY: Dark matter torpedoesuse the plasma interactions for crew quality [(G21.114) &(G21.214)] and legendary officers (G22.0).(OFP4.14) ADDITION: TACTICAL INTELLIGENCE LEVELS:Dark matter torpedo launchers are distinguished from otherheavy weapons, at Tactical Intelligence Level F (D17.4). The factthat a dark matter torpedo launcher has been armed isdistinguished at Tactical Intelligence Level L. The number ofturns of arming of a given dark matter torpedo launcher can bedistinguished at Tactical Intelligence Level M. A launcher holdinga dark matter decoy (OFP4.27) will be reported as armed.(OFP4.15) NEW RULE: SIZE RESTRICTIONS: Some SouldraShards are armed with this weapon and are capable of arming itthemselves. No Souldra Shard currently is able to overload adark matter torpedo.(OFP4.312) CLARIFICATION: “DMTs have the same strengthfrom the moment they are launched to the moment of impact,unless damaged by weapons fire or terrain.” This is in error,DMTs do not have their strength reduced by weapons fire orterrain, only their range.(OFP4.47) ADDITION: TERRAIN: Dark matter torpedoes run therisk of changing targets if their target moves behind a hexcontaining a planet (P2.321), moon [Exception: (P2.3221)], star(P12.1), black hole (P4.23) or pulsar (P5.32). They can belaunched into such a hex. They can travel through asteroid(P3.24), ring (P2.223), and dust (P13.3) hexes with the standarddamage effects and penalties. Dark matter torpedoes areaffected by of gravity waves in the same manner as plasmatorpedoes (P9.312).(OFP4.48) ADDITION: ATMOSPHERES: Dark matter torpedoesare affected by atmosphere in the same manner as plasmatorpedoes (P2.852).(OFP4.49) ADDITION: WEBS: Dark matter torpedoes interactwith web as plasma torpedoes do (G10.52).(OFP5.11) REVISED SSD: Particle splitter torpedo launchers aredesignated “PST” on the SSD.(OFP5.12) REVISED: DESTRUCTION: Particle splitter torpedolaunchers are destroyed on “drone” damage points.(OFP5.121) ADDITION: For the purposes of damage priority and(D4.3223), particle splitter torpedo launchers are destroyed aftertachyon missile rack-As, see Annex #7E.

(OFP5.13) ADDITION: CREW QUALITY: Particle splittertorpedoes use the plasma interactions for crew quality [(G21.114)& (G21.214)] and legendary officers (G22.0).(OFP5.14) ADDITION: TACTICAL INTELLIGENCE LEVELS:Particle splitter torpedo launchers are distinguished from otherheavy weapons, at Tactical Intelligence Level F (D17.4). The factthat a particle splitter torpedo launcher has been armed isdistinguished at Tactical Intelligence Level L. The number ofturns of arming of a given particle splitter torpedo launcher canbe distinguished at Tactical Intelligence Level M.(OFP5.15) NEW RULE: FIGHTERS: No fighter currently in thegame can use this type of torpedo. If one is added, it will includerules for arming and launching at that time.(OFP5.37) CLARIFICATION: The reference to the torpedo beingdamaged in the same manner as plasma torpedoes means ittakes two points of “phaser” damage to reduce the warhead byone point.(OFP5.38) CLARIFICATION: It is not possible to program thenumber of sub-torpedoes the particle splitter torpedo will divideinto. Dependent on its arming level, it will split into the number ofsub-torpedoes as given in the table in (OFP5.332). It is also notpossible to program the torpedo to separate in less than eightmoves.(OFP5.38) CLARIFICATION: The Particle Splittler Torpedo splitsin the MW Release Step of the Seeking Weapons Stage (6B6).14 Feb 2007(OFP5.46) ADDITION: AVAILABILITY: Particle splittertorpedoes are restricted Vari technology and cannot beduplicated by other races. They can only be used in simulatoroption mounts. A particle splitter torpedo launcher costs 4 pointsand cannot be placed in wing option mounts in the simulators.See Annex #8B.(OFP5.47) ADDITION: TERRAIN: Particle splitter torpedoes runthe risk of changing targets if their target moves behind a hexcontaining a planet (P2.321), moon [Exception: (P2.3221)], star(P12.1), black hole (P4.23) or pulsar (P5.32). They can belaunched into such a hex. The separate warheads areindividually affected after the weapon splits. They can travelthrough asteroid (P3.24), ring (P2.223), and dust (P13.3) hexeswith the standard damage effects and penalties. Particle splittertorpedoes are affected by of gravity waves in the same manneras plasma torpedoes (P9.312). See (OFP5.372) for atmosphereeffects.(OFP5.48) ADDITION: WEBS: Particle splitter torpedoes interactwith web as plasma torpedoes do (G10.52).(OFP6.112) CLARIFICATION: See (OG19.13) and (OG19.15)for electronic warfare and other weapon effects.(OFP6.114) CLARIFICATION/NEW RULE: There will be aparenthetical number after the title of the Dragonfire Table thatwill indicate the number of Dragonfire “launchers” that dragonshiphas. For example, the Old Dragon Ship’s (OR22.7) DragonfireTable reads “OLD DRAGONFIRE TABLE (1)”, where thenumeral “1” is the number of Dragonfire “launchers” the ship has.Half of the dragonships in Module Omega #4 have twolaunchers, the other half have only one. Dragonships in laterproducts might have more.(OFP6.14) NEW RULE: TECHNOLOGY: Dragon-Fire is anorganic component of the space dragon on which the Branthodonship is built. They cannot be used by any non-dragon unit, noteven in the simulators. This includes their use by shuttles orfighters.(OFP6.33) ADDITION: FEEDBACK: Dragonfire is subject tofeedback in the same manner and under the same conditions asplasma torpedoes (FP1.86). See also the Qixavalor Nebular(OP1.22).(OFP7.0) ADDITION: ADD TO END OF INTRODUCTION: It wasinstalled on “new construction” ships and “new production”fighters beginning in Y127. Some new classes of ships did notinitially include it due to problems integrating the system. It couldnot be retrofitted into older ships.

(OFP7.3) CLARIFICATION: Note, as all plasma torpedoes blindspecial sensors, whipcrack torpedoes will blind special sensors.(OFP7.33) CLARIFICATION: As whipcrack is essentially aseeking function of Plasma-Whips, it essentially defines plasma-whips as the “bolt” mode of whipcrack torpedoes.(OFP7.55) ADDITION: FEEDBACK: Whipcrack torpedoes aresubject to feedback in the same manner and under the sameconditions as plasma torpedoes (FP1.86). See also the QixavalorNebular (OP1.22).

(OG0.0) ERRATA

(OG01.0) CHANGE: Introduction changed to read: The flameshield (occasionally called a “fire shield”) is a defensive item usedexclusively by the Loriyill Collective and at least one trusted ally[the Singers (OR18.0)]. It projects a shield of energy that lookslike fire around the ship, causing an energy backlash againstanyone firing direct-fire weapons at the vessel. GENERALNOTE: All references to Loriyill only use were deleted due to theSingers receiving this technology.(OG01.1321) CLARICATION: Note added that plasma bolts(FP8.0) are treated as direct fire weapons.(OG01.1327) NEW RULE/CLARIFICATION: Damage done tothe ship as a result of feedback from its own weapons is notsubject to backlash, this includes feedback as a result of theQixavalor Cloud (OP1.22). The operation of a flame shield doesnot in and of itself create feedback, not even in the Qixavalorcloud.(OG01.1333) CLARIFICATION: Rule revised to read: While theflame shield is active, the ship cannot launch any weapon orsystem with an FD rule number, i.e., (FD0.0), (OFD0.0), or(MFD0.0), such weapons would be destroyed on launch. Thisaffects only such seeking weapons launched by the protectedship.(OG01.1335) CLARIFICATION: Rule revised to read: Flameshields do not prevent docking (C13.0), and will not affect units ofSize Class 5 or larger which dock or undock to the protected shipor to which the protected ship docks. The flame shield protectsonly the unit generating the shield. Shuttles which dock (or aredocked) to a ship protected by a flame shield (C13.98) aredestroyed.(OG01.134) CLARIFICATION: Change second sentence to read:“They do not harm ESGs, do not interact with mines [exceptcaptor mines under (OG1.132)] or PA mines, and do not affectwebs”.(OG01.214) NEW RULE: The energy in a flame shield at thestart of a scenario is determined by weapons status. At WS–0 orWS–I, a flame shield has no energy. At WS–II, it has two pointsof energy, and at WS–III it has four points of energy.(OG01.24) ADDITION/CLARIFICATION: Energy added in theEnergy Allocation Phase of Turn #1 is lost in the EnergyAllocation Phase of Turn #4. Energy added from reserve poweron Impulse #16 of Turn #1 is lost on Impulse #16 of Turn #4. Ifthe flame shield is activated on Impulse #16 of Turn #4 itfunctions normally, the power allocated 96 impulses earlier is notlost.(OG01.31) REVISED: AVAILABILITY: Flame shields arerestricted technology. Only the Loriyill and other races providedwith the technology in their rules can use it. No other race canuse or understand this equipment. In Simulator option mounts aflame shield requires on option mount and costs 3 BPV. Thethree protected shield facings of the flame shield generator mustbe assigned when it is placed in the option mount.(OG01.323) NEW RULE: Ground bases can operate flameshields normally even within an atmosphere.(OG02.0) MOVED: Second Paragraph moved and renumbered(OG2.11).(OG02.12) NEW RULE: Secondary shields cannot be installedon any non-Sigvirion ship, not even a captured ship converted toSigvirion technology or in the simulators.

(OG02.2) CLARIFICATION: Sigvirion Secondary shields areraised or dropped in the Operate Shields Step of the MarinesActivity Stage (6B7) at the same time and manner as normalshields. 14 Feb 2007(OG02.33) ADDITION: Secondary shields do not operate in aNebula (P6.3), but operate normally in all other terrain types.(OG02.35) ADDITION: Other enveloping weapons operatenormally, but the Sigvirion player can apply secondary shieldboxes to block (or not block) any of the damage elements at hisdiscretion.(OG03.12) CLARIFICATION: The plasma cloud generator canbe activated in any impulse during the Final Functions Stage(6B11) of Impulse Activity AFTER ANNOUNCING EMERGENCYDECELERATION. 14 Feb 2007(OG03.12) CORRECTION: This rule contradicts (OG3.131) andis in error. Rule (OG3.131) is correct that the first hex of cloud isformed on the same impulse, not the next subsequent impulse.(OG03.144) REVISED: Seeking weapons with (FD0.0) rulenumbers, e.g., drones, tachyon missiles, etc., count each impulsethey are in a cloud hex as two impulses against their range orendurance.(OG03.145) REVISED: Seeking weapons with (FP0.0) rulenumbers, e.g., plasma torpedoes, implosion torpedoes, kineticwaves, etc., suffer the effects of four points of phaser damage(FP1.61) per cloud hex traversed. NOTE: This revision is forcedbecause some plasma like weapons lose range, not warheadstrength as a result of damage. This makes all weapons more orless resolve the damage the same, but some weapons will bebetter than others, because they are damaged at three phaserdamage points to one point of reduction. This note is not includedin the rule in the book.(OG03.16) CLARIFICATION: At that time all hexes of cloud areremoved from the board simultaneously at the END OF WEBCASTER STAGE (6D3) OF THE DIRECT-FIRE WEAPONSSEGMENT OF THE IMPULSE PROCEDURE. 14 Feb 2007(OG03.173) ADDITION: Plasma cloud generators are affected byelectronic warfare under the provisions of (D6.37), i.e., they havean assumed success roll of 1-6 and if subject to a shift will fail togenerate a cloud, the power is lost. Crew quality (G21.0) andlegendary officers (G22.0) have no effect on their operations.They never cause feedback, even in the Qixavalor Cloud(OP1.22).(OG03.21) CHANGE: Energy required must come from Alundaenergy sources.(OG03.23) CHANGE: Energy to arm a plasma cloud generatorcan come from any Alunda energy source, including reservepower. It cannot be armed with power transferred from a non-Alunda unit by (C13.41) or (C13.952).(OG03.26) NEW RULE: The energy in a plasma cloud generatorat the start of a scenario is determined by weapons status. AtWS–0, it has no energy; at WS–I, it has one energy; at WS–II, ithas three energy; and at WS–III, it has five energy.(OG03.31) ADDITION: In the simulators it requires one optionmount, costs five points and will only fire directly to the rear of theunit (bases can mount two, the second firing directly to the front).In the simulators the system may be armed with power from anysource.(OG04.135) NEW RULE: Subspace coagulators are not affectedby electronic warfare. THIS RULE IS RESCINDED.(OG04.14) CLARIFICATION: Note that a coagulated hex ofasteroids is a single hex, not an asteroid counter with two morehexes of asteroids surrounding it.(OG04.14) CLARIFICATION: Note that Coagulated Space willhinder the movement of Branthodon Dragonships (OG19.112).THIS RULE IS RESCINDED.(OG04.14) RESCISSION: The Previous Errata Item saying thatCoagulated Space affects Branthdon Dragonship is rescinded.Branthodon dragonships treat these hexes like normal asteroidhexes, i.e., it does not affect their movement (OG19.112).(OG04.1432) NEW RULE/CLARIFICATION: The combination offreestanding web and coagulated space does not create

“anchored web” for any purpose. The web cannot be reinforcedor maintained.(OG04.16) CLARIFICATION: All coagulated hexes are removedfrom the board simultaneously at the end of Web Caster Stage(6D3) of the Direct-Fire Weapons Segment of the ImpulseProcedure. 14 Feb 2007(OG04.171) CLARIFICATION: What this rule means is that(E12.56) is used to determine whether or not a SubspaceCoagulator successfully operates. The electronic warfaresituation is resolved under (D6.372). The Subspace Coagulatoroperates with an assumed success die roll of 1-6. If there is noelectronic warfare shift under (E12.56), the Subspace Coagulatoris automatically successful, but if there is a shift such that one ormore is added to the die, the weapon will fail (the energy is lostand space is not coagulated). Rule now reads: Subspacecoagulators are affected by EW as web casters are (E12.56).The EW situation is resolved under (D6.372). The SubspaceCoagulator operates with an assumed success die roll of 1-6. Ifthere is no EW shift under (E12.56), the Subspace Coagulator isautomatically successful, but if there is a shift such that a resultgreater than six results, the weapon will fail (the energy is lostand space is not coagulated).(OG04.173) ADDITION: It cannot form across a web hex, butcan extend into a web hex. If fired into a web hex of a strengthgreater than zero, it cannot spread beyond the initial hex.(OG04.175) ADDITION: Subspace coagulators are affected byelectronic warfare under the provisions of (D6.37), i.e., they havean assumed success roll of 1-6 and if subject to a shift will fail togenerate a cloud, the power is lost. Crew quality (G21.0) andlegendary officers (G22.0) have no effect on their operations.They never cause feedback, even in the Qixavalor Cloud(OP1.22).(OG04.25) NEW RULE: The energy in a subspace coagulator atthe start of a scenario is determined by weapons status. AtWS–0, WS–I or WS–II they have no prior arming completed. AtWS–III, they can be assumed to have been powered on theprevious turn (they cannot hold energy, but can only use rollingdelay).(OG04.26) NEW RULE: AVAILABILITY: Subspace Coagulatorsare Chlorophon only technology. They can only be used insimulator option mounts. They require two adjacent centerlineoption mounts and cost 8 points.(OG05.02) CORRECTION: The Drex SSDs all list the wrongHET cost with a reduction of 50%(OG05.21) CLARIFICATION: Note that (G21.211) only providesa die roll shift if electronic warfare is in use. If electronic warfareis not in use, the Drex cannot gain the minus one shift rule(G21.211) allows. THIS HAS BEEN FOUND IN ERROR ANDRESCINDED.(OG06.124) CLARIFICATION: The use of a stabilizer must berecorded in the Fire Allocation Stage (6D1) and announced in theDirect Fire Allocation Phase (6D1) before any dice are rolled. Thewritten record must be revealed unless using (D17.61). If the useof a stabilizer is declared for a given aegis fire step, this cannotbe altered once the results of a preceding aegis pulse have beendetermined (the system is not quite fast enough to react thisway).14 Feb 2007(OG06.144) ADDITION: Special scenario rules may provide thata given stabilizer is nearing repair when the scenario begins andwill specify the procedure for completing such a repair.(OG07.12) CLARIFICATION: ACTIVATION: The flame shieldprojector is activated at the same time as normal flame shields(OG1.12), i.e., in Final Functions Stage (6B11). The target of theshield is designated at the same time. 14 Feb 2007(OG07.23) NEW RULE: AVAILABILITY: Flame shield projectorsare Loriyill technology and can only be used by the Loriyill andother races provided in the rules, i.e., the Singers (OR19.0). InSimulator option mounts they require one space and cost 15points. The firing arc must be defined when installed.

(OG07.39) NEW RULE: OTHER INTERACTIONS: Flame shieldprojectors are affected by electronic warfare under the provisionsof (D6.37), i.e., they have an assumed success roll of 1-6 and ifsubject to a shift will fail to generate a flame shield, the power islost. Crew quality (G21.0) and legendary officers (G22.0) have noeffect on their operations. They never cause feedback, even inthe Qixavalor Cloud (OP1.22). A flame shield can be projectedinto or out of a web hex as long as a valid line of sight existsbetween the projecting unit and its target and the projector is inarc.(OG08.14) NEW RULE: AVAILABILITY: Jammers are Hivertechnology and can only be used by the Hivers. In Simulatoroption mounts they require one space and cost 1 point.(OG08.22) CLARIFICATION: Arc Jamming is announced andtakes immediate effect in the Scouts Begin or Voluntarily EndLending Step of the Lock-On Stage (6B3) of the Sequence ofPlay. 14 Feb 2007(OG09.12) NEW RULE: AVAILABILITY: Soul shields areSouldra technology and can only be used by Souldra ships. Theycannot be installed on non-Souldra ships, even ones convertedby the Souldra to their technology, except in the simulators. Inthe simulators, simply install soul shields as provided in(OG9.111) at no change in BPV.(OG09.224) CLARIFICATION: If Tactical Intelligence is not used,this information must be announced in the Energy AllocationPhase at the same time as other races announce whether theirshields are powered or not. 14 Feb 2007(OG09.231) ADDITION: He must announce this if TacticalIntelligence is not being used, and must reveal it at TacticalIntelligence Level I if using Tactical Intelligence and theinformation is requested.(OG09.233) ADDITION: These shield boxes are not lost if theshield block is destroyed unlike normal shields are under(D17.7114).(OG09.2341) CORRECTION: Should read “. . . but the SouldraPLAYER may choose which block in the shield arc is hit.” It is notentirely clear how this works for Qari Kinetic Cannons. Anexample would be more helpful. EXAMPLE: A Souldra ship hasfive shield blocks facing a given direction. It also has two pointsof general reinforcement and two points of specific reinforcementon that shield facing. A Qari heavy penetrating round hits thatfacing shield from eight hexes range. It destroys one point ofgeneral reinforcement (E53.332), but skips the remainingreinforcement (E53.332); it will now apply its damage to a shieldblock. The Souldra player notes that of the five shield blocks onthat shield facing, only one has five boxes (the others have lessdue to previous damage). He scores the remaining five damagepoints on that shield block, thus avoiding any internal damage.Unfortunately, a second KKH penetrating round hit the samefacing on the same impulse. This also destroys one point ofgeneral shield reinforcement and skips the remainingreinforcement. The Souldra player is forced to apply theremaining five points of damage to another shield block, but asall the others have four or fewer points, he will take at least onepoint of internal damage. If the Souldra ship had reserve powerto apply for more specific reinforcement, two points morereinforcement would have been enough to block any internaldamage. In such case the first KKH round would destroy onepoint of general reinforcement, one point of specific, and a fourbox shield block, while the second then destroyed one point ofgeneral reinforcement and the five box shield block.(OG10.132) ADDITION/CLARIFICATION: “The next time thatsame roll is made (and all subsequent hits that are made as partof that volley), skip to the next column on the DAC. For example,if a “6” is rolled on the DAC (normally scored on F HULL), itwould score no internal damage, but the next time a “6” is rolled,that F HULL would be skipped and the next hit listed (IMPULSE)would be scored. Damage would continue to be scored normally

from that point, e.g., moving to the next column if all of the ship’simpulse was destroyed.”(OG10.132) CORRECTION: Example: Insert reference to(OG10.131) after the second use of the word “under”.(OG10.14) CLARIFICATION: Dark matter damage does not do“leak” damage according to (OG10.12), the reference to leakswas intended for those situations when non-dark matter weaponshit the panels that have been filled or degraded by dark matterenergy.(OG12.111) NEW RULE: For purposes of (D4.3223) targetilluminators are destroyed after plasmatic pulsar devices andtarget accentuators, but before web casters. See Annex #7E.(OG12.12) CLARIFICATION: A unit using a Target Illuminatormust announce it is doing so and indicate the target it isilluminating as part of activating the device.(OG12.15) NEW RULE: AVAILABILITY: Target Illuminators areIridani only technology and can only be used by Iridani units.They cannot be installed on non-iridani units, except in thesimulators. In the simulators they require one option mount andcost 1 BPV.(OG12.23) CLARIFICATION: Change second sentence to read:The target must be in the arc of the illuminator and must bewithin an effective range (D1.4) of 20 hexes of the operating ship.ADD: Target Illuminators are themselves affected by electronicwarfare, to include the erratic maneuver status of the ship theyare on or the target they are focused on. The electronic warfaresituation is resolved under (D6.372). The Target Illuminatoroperates with an assumed success die roll of 1-6. If there is noelectronic warfare shift under (E12.56), the Target Illuminator isautomatically successful, but if there is a shift such that one ormore is added to the die, the Target Illuminator will fail (theenergy is lost and the target is not illuminated).(OG12.231) ADDITION: It can be used under the conditions ofdisrupted fire control (D6.68).(OG12.232) ADDITION: Add to end: “. . .except for any naturalEW effects (OG12.23).”(OG13.223) CORRECTION: Typo: “. . . it’s . . .” should be “. . . its. . .”.(OG13.431) CLARIFICATION: It should be obvious that if thesecond DPD is not activated early enough, the ship may appearon the map in a partially phased state, and then completephasing out.(OG13.512) CORRECTION: Should have a reference to(OG13.425) for seeking weapons that violate (F3.31).(OG13.66) ADDITION: AVAILABILITY: Dimensional phasedevices are Souldra only technology and can only be used bySouldra units. They cannot be installed on non-Souldra units, noteven such units converted to Souldra technology, not even in thesimulators.(OG14.23) CLARIFICATION: Subspace energy fields areactivated immediately after the Web Step of the Ship SystemsFunction Stage (6B4), not “. . . immediately after web is laid . . .”.14 Feb 2007(OG14.243) CORRECTION: Insert “and” before “. . . the Direct-Fire. . .”.(OG14.3114) CLARIFICATION: A Black Shard attached toanother unit of Size Class 4 or larger under (OJ4.2) is treated asdocked or landed aboard for purposes of this rule, i.e., it will notbe damaged (although the ship it is attached to will be damaged)by the SEF.(OG14.3116) CLARIFICATION: SEF/ESG JUMPS: If, due tohead-on movement of two ships, a SEF hex “jumps” across anESG hex do the following: First consult the order of precedenceand move the two units as required. If the result of the two units’movement is such that there is no interaction, i.e., the SEF unitmoved into the ESG hex, but the ESG unit moved away from theSEF unit, there is no interaction. If the result of the movement isthat SEF crosses ESG hexes (or the ESG crosses over SEFhexes) evaluate the situation based on the total number of SEFhexes that interact with the field. Note that this can never bemore than four from any one SEF ship.

(OG14.3117) NEW RULE/CLARIFICATION: Short rangedcannons (OE20.0) and ADDs (E5.0), to include RALADs (J12.0),cannot penetrate a SEF and are destroyed on entering such ahex without damaging anything.(OG14.325) CORRECTION: Should be two sentences.(OG15.314) CORRECTION: A unit that has launched a wildweasel cannot move by quantum transporter as it has no activefire control (OG15.343). The mention of a unit moving whileunder a wild weasel is a ghost from an earlier version of therules. Change this rule to read: A ship protected by a wild weaselcannot move by Quantum Transporter (OG15.34). However, awild weasel which itself moves by quantum transporter is notvoided.(OG15.347) CHANGED to read: Neither a cloaked (G13.0) unitor a phased (OG13.0) unit can move by QT movement.(OG15.3556) ADDITION: Ryn MRS shuttles (OR1.S2) are deathdragged at a speed higher than 10.(OG16.23) CORRECTION: The link can bring in at most onecargo space point per impulse, during the Operate Transportersstep of the “Marines Activity Stage (6B7)” of the Sequence ofPlay.(OG16.25) CORRECTION: Delete the fragment “to the end of therule.”(OG17.263) CORRECTION: The reference to (D10.22) shouldhave been to (D20.22).(OG17.265) ADDITION: “. . . and can rotate normally(OG17.15).”(OG17.27) NEW RULE: CREW QUALITY AND OFFICERS:Bolosco ship Stabilizers are not affected in any way by the qualityof the crew, whether poor (G21.1) or outstanding (G21.2), or bylegendary officers (G22.0).(OG18.228) NEW RULE: IWTs never cause feedback, not evenin the Qixavalor cloud (OP1.213).(OG18.33) CLARIFICATION: Warp shunting “. . . is resolved by(OG18.334) during the Operate Tractors Step of the ShipSystems Function Stage (6B4).” 14 Feb 2007(OG18.3433) CLARIFICATION/ADDITION: Add to end of firstsentence: “[this procedure is used even if the unit has anoperating shield pod (OJ3.44)]”. ADD TO THE END: On a RYNship, the damage in (OG18.343) is applied to the armor bankfacing the Bolosco ship which executed the Tractor Crush Attack.(OG18.354) ADDITION/CHANGE first sentence to read: Toresolve the attack, (after resolving any EW effects under(OG18.226), roll a single die and add two.(OG18.356) CHANGE TO READ: The tractor punch does notcause feedback except in the Qixavalor cloud (OP1.22).(OG18.361) ADD TO END OF RULE: Note that any EW effectsunder (OG18.226) will have to be resolved under (D6.37).(OG18.369) ADDITION: Add to end of rule: Pressure fields haveno effect on mines (M0.0), i.e., they cannot sweep a minefield, orDefense Satellites, i.e., the will not knock them out of their orbits.(OG18.4213) ADDITION: The fighter also cannot use its tractorto land if it used its tractor earlier in the turn or within a quarterturn of using it on a previous turn.(OG18.422) ADDITION: It can tow another shuttle or fighterunder the provisions of (J18.0).(OG18.446) CREW QUALITY AND OFFICERS: Other than theirEW effects, outstanding (G21.2) and poor (G21.1) crews have noeffect on the operations of IWTs. Legendary Weapons officers(G22.0) treat IWTs as direct-fire weapons.(OG19.0) CLARIFICATION: NOTE: Throughout these rules theterms “Body” and “Torso” have been used interchangeably. Thiswas a regrettable failing in editing that extended to the SSDswhere “Torso” is used on the damage tables (OG19.32) but theDragonship itself uses the term “Body” for that area. In all caseswhere the term “Torso” appears, it means “Body”. Within theserules, all references to “Torso” have been changed to “Body”.(OG19.112) CLARIFICATION: The ability of Dragonships tomove through asteroid fields unhindered extends to, and

includes, moving through hexes of coagulated space created byChlorophon Sub Space Coagulators (OG4.14).(OG19.134) CLARIFICATION/NEW RULE: The effects ofdisrupted fire control (D6.68) apply to a dragonship’s weaponsnormally, i.e., the dragonship during the period of disruption canonly target seeking weapons near itself. This includes the use ofWing Buffet (OG19.421), but not movement abilities like PowerDive (OG19.422) [although a Rake Attack (OG19.436) could onlybe delivered to a seeking weapon or shuttle during the disruptedperiod].(OG19.152) CLARIFICATION: Note that Dragonfire controlled bythe launching dragon would ignore electronic warfare (to includecloaking devices and the effects of erratic maneuvers), but mightbe released to its own guidance (perhaps due to the “death” ofthe dragonship) and would at that point use electronic warfarenormally.(OG19.333) CHANGE reference to (OR21.031) to (OG19.113).(OG19.411) CLARIFICATION: The number of VEPs available isdetermined in the Energy Allocation Phase after TractorAuctions. 14 Feb 2007(OG19.4212) NEW RULE/CORRECTION: Wing Buffet does notaffect Dragon Fire in any way. Change text that reads “Boloscounits will active stabilizers . . .” to “Bolosco units WITH activestabilizers . . .”(OG19.4212) RESCINDED: The rule about wing buffets notaffecting dragonfire has been rescinded. Change final sentenceto read: Units under the protection of a wild weasel (J3.0) do notlose the protection of the weasel as a result of being moved by awing buffet unless such movement causes the unit to be morethan 35 hexes from the weasel (J3.42). Mines, to include captormines, and DefSats cannot be affected by wing buffets. Wingbuffets cannot affect terrain or units landed on planets orasteroids, whether there is an atmosphere or not.(OG19.4213) CHANGED TO READ: If the buffet is successful,the target unit is immediately moved away from the dragonship toa range of five hexes (the Branthodon at his option maydesignate that the target is moved less than the full five hexes).This has no other effects on the target (it continues moving asbefore, its speed, turn mode, side slip mode, directed turn mode,and facing are unchanged and it suffers no damage). Seekingweapons entering the hex of their target, or otherwise reachingengagement range, will be penalized on their accuracy(OG19.42131). Units or objects in the hexes moved through,such as small moons (P2.23), asteroids (P3.0), etc., have noeffect whatsoever, but see (OG19.4215). The dragonship doesnot need to have a lock-on to the destination hex or any of thehexes in between. The hexes of “wing buffet movement” are notadded to the speed of the unit being moved for any purpose, i.e.,a unit at speed zero is still considered to be at speed zero for allpurposes, a unit at speed 31 is considered to be at speed 31 forall purposes not explicitly excepted [e.g., it avoids collisions(OG19.4215)].(OG19.42131) NEW RULE: Seeking Weapons subject to wingBuffets are penalized by a modifier of plus three (+3) during thefour impulses after they are subject to a wing buffet this is inaddition to any shifts caused by electronic warfare effects andcannot be cancelled by any means. Thus a plasma torpedobuffeted on Impulse #12 would be subject to this modifier if it hitits target on Impulses #13, #14, #15, or #16. This is because thesmall electronic brains of seeking weapons do not have thecomputing power to compensate for their sudden movement.Note that since the movement takes place during the Direct FireWeapons Segment (6D) of one Impulse, a seeking weaponmoved by such a means, even if it enters the hex of its target, willnot impact until the Movement Segment of the following impulse.It is possible that a seeking weapon could begin such amovement Segment in the hex of its target, but not impact duethe target moving out of the hex.(OG19.42132) NEW RULE: In the case of impact seekingweapons, the modifier is resolved on table (D6.361). Thus aplasma torpedo that enters the hex of its target after being

buffeted would have a 50% chance of doing reduced damage. Ifthe target had four points of ECM and the plasma torpedo hadonly its inherent ECCM, then under (D6.34) an additional modifierof plus one (+1) would be added to the die roll under (D6.361).(OG19.42133) NEW RULE: In the case of seeking weaponswhich fire direct fire weapons, e.g., Swordfish drones, themodifier is applied to the weapons table. Thus a phaser-2Swordfish drone programmed to fire at its target at three hexesrange or less would add three to the die roll to resolve the shot.(OG19.42134) NEW RULE: This modifier would be applied toany submunitions launched by a seeking weapon during theperiod of the wing buffet’s affect, i.e., any type-VI drones wouldroll under (D6.361), although they would still not be affected byelectronic warfare (FD5.131). The modifier would be applied toADDs launched by a Starfish drone.(OG19.4214) ADDITION/CLARIFICATION: If the target is to bemoved less than five hexes (OG19.4213) the straight line needbe no further than the distance the dragonship is moving thetarget.(OG19.4215) ADD TO END: A unit forced into an SEF (OG14.0)would be damaged normally.(OG19.422) CLARIFICATION: Branthodon Dragonshipsannounce they are doing a power dive at the same time as mid-turn speed changes in the Announce Movement Change Step ofthe Final Functions Stage (6A4). Power Dives take effect in thePreviously announced Speed Changes take effect Step of theVoluntary Movement Stage (6A2). 14 Feb 2007(OG19.4222) CLARIFICATION: See also (OG19.23) which alsoapplies and (OG19.151) for the effects of the ECM generated byerratic maneuvers on the exoskeleton, e.g., (C10.414) applies toweapons fired by the exoskeleton.(OG19.434) ADDITION: While called “bite”, this is actually thedragonship snapping its jaws together to expel acid drool ratherthan actually “biting” the target unit.(OG19.4342) ADDITION: They affect plasma weapons (FP0.0)as phaser-damage.(OG19.4352) ADDITION: They can affect plasma weapons(FP0.0) as phaser-damage.(OG19.4356) CLARIFICATION/NEW RULE: An ESG field mightbe formed at radius zero in a hex occupied by an ESGgenerating unit and a dragonship. It is also possible that a fieldmight be formed at radius zero and include within its spheresome other unit or units friendly to the ESG generating unit(G23.72). In such a case (G23.562) requires the dragonship tobe outside of the ESG field (assuming it is an enemy of the ESGship). If the Dragonship tried to Claw the ship generating the field(or any other ship within the ESG sphere) it would first have tointeract with the ESG field (this is outside of the normal sequenceof play). Damage from the ESG field would be resolved first, andit is possible such damage might prevent the Claw attack beforeit could be consummated. The dragonship could attack units inthe hex outside the ESG normally.(OG19.4361) CORRECTION: Change text “. . . must be in the apower dive . . .” to “. . . must be in a power dive . . .”(OG19.4366) CLARIFICATION/NEW RULE: An ESG field mightbe formed at radius zero in a hex occupied by an ESGgenerating unit and a dragonship. It is also possible that a fieldmight be formed at radius zero and include within its spheresome other unit or units friendly to the ESG generating unit(G23.72). Note that ESGs form after movement in the SeekingWeapons Stage (6B6) and before the Direct-Fire Stage (6D). Ifthe Dragonship tried to rake the ship generating the field (or anyother ship within the ESG sphere) it would first have to interactwith the ESG field (this is outside of the normal sequence ofplay). Damage from the ESG field would be resolved first, and itis possible such damage might prevent the Rake attack before itcould be consummated.(OG19.4378) CLARIFICATION/NEW RULE: If a Dragon shiphas executed a successful Snatch maneuver against a ship thatsubsequently raises an ESG field, the dragonship is inside that

ESG, even if it is raised at radius zero. This is an exception to(G23.562). If the Dragonship has snatched another ship which isfriendly to the ESG generating ship on the impulse a radius zeroESG is raised, the ESG generating unit cannot declare thesnatched unit to be inside the sphere under (G23.72).(OG19.4433) REVISION/CLARIFICATION: The decision to usethis ability against seeking weapons is made in the DamageDuring Movement Stage (6A3) after tail defense (OG19.4411),but before damage resolution (so, for example, it would be madebefore learning whether a plasma torpedo was real or pseudo).The decision to use this ability against direct-fire weapons ismade after Fire Declaration Step of the Fire Allocation Stage(6D1) when weapons fire is announced but before any to-hit rollsare made. 14 Feb 2007(OG19.4442) CLARIFICATION: At the start of any turn, duringthe Energy Allocation Phase when repair points are allocated, adragonship can begin using its regenerative powers. 14 Feb2007(OG19.4451) CLARIFICATION: This is done during the EnergyAllocation Phase in the Allocate Repair Points Step. 14 Feb 2007(OG20.121) CLARIFICATION: The number of added VEPs iscalculated at the same point where VEPs are created in theEnergy Allocation Phase (OG19.411). 14 Feb 2007

(OH0.0) ERRATA

(OH1.21) CLARIFICATION: Add to end of rule: Transfer rates ofbattery power from one Alunda unit to another under (C13.41) isgoverned by this rule, i.e., no Alunda unit can transfer more thanone point of battery power, and such a transfer counts as its oneuse of that battery for the turn.(OH1.22) CLARIFICATION/NEW RULE: Power from Adrenalinebatteries cannot be transferred to non-Alunda units docked to anAlunda unit by (C13.41).(OH2.214) CLARIFICATION/NEW RULE: JPR energy can betransferred to another unit under the provisions and within thelimits of (C13.41), but such transferred power must be trackedand can only be used by the receiving for the purposes providedby this rule (OH2.21).(OH2.23) REVISED TO READ: RESERVE POWER: Powerprovided by a jammer power reactor cannot be held in reserve. Itmust be allocated and can only be allocated to functions listed in(OH2.21). This is one of the chief disadvantages of this type ofenergy. jammer power reactor power can be allocated to an EWpool under (G24.2114), but the energy points must be specificallydefined as either ECM or ECCM during Energy Allocation.(OH2.26) NEW RULE: TECHNOLOGY RESTRICTIONS:Jammer power reactors can only be used in Omega andsimulator option mounts.(OH2.261) NEW RULE: A jammer power reactor requires oneoption mount space.(OH2.262) NEW RULE: The jammer power reactor costs 1 BPVunder Annex #8B.

(OJ0.0) ERRATA

(OJ0.01) CLARIFICATION/NEW RULE: SQUADRONS IN THEOMEGA SECTOR: Squadrons in the Omega Sector did notfollow the usual established patterns in the Alpha Sector. Instead,squadrons were formed of whatever size seemed appropriate, aswell as along racial lines. Some races used larger squadronsthan others, and some races chose to split a carrier’s fightergroup into squadrons depending on need and the organization ofthe group. Unless otherwise stated, any Omegan carrier’sfighters were organized into a single squadron for purposes of(J4.46) and lending electronic warfare. For example, the MæsronStrike Carrier used a single squadron of 14 fighters, while the

Koligahr SV used a squadron of 10 fighters, and the Drex haveas many as 16 fighters in some squadrons. If a carrier splits itsfighters into multiple squadrons, this fact will be noted in itsdescription.(OJ0.02) CLARIFICATION/NEW RULE: ELECTRONICWARFARE FIGHTERS: Electronic warfare fighters (R1.F7) werenot developed until the Hivers began fielding an experimentalelectronic warfare unit in Y196 during the desperation of theInvasions. Specific two-seat units will be described in a futureproduct. Hivers may convert fighters to two-seat EWF versionsbeginning in Y196 using the rules of (R1.F7); other races can dothis starting in Y197. Fighters armed with tachyon missiles treateach missile as two drones when making such conversions.(OJ1.242) CLARIFICATION: Add after third sentence: It couldfire one phaser on Impulse #32 of one turn, and the other onImpulse #1 of the following turn.(OJ1.242) CLARIFICATION: When Hiver fighters land, theyempty their phaser capacitors, but the capacitors are not de-energized. They can fire them on the turn they launch (if theyspend energy for the capacitor).(OJ1.243) CLARIFICATION: Change second sentence to read:The decision to raise shields must be made in Energy AllocationPhase and must be announced at the start of the turn at thesame point where other units announce if their shields arepowered.(OJ1.243) CLARIFICATION: It has been asked if a fighter otherthan a heavy fighter can use more than one point of power for astronger shield, but the rule is explicit that only one point can beused, and it must be allocated at the start of the turn. Thereference to “points” at the end of the rule is to the fact that aheavy fighter can use two points of power for shields.(OJ1.247) ADDITION: Hiver fighters may use any amount ofpower for this function within the limits of (OJ1.312). [Thisreplaces (OJ1.247) on page 14 of Module Omega-2].(OJ1.247) ADDITION: Standard Hiver fighters can use at mostone point of power per turn (i.e., increasing their speed by amaximum of four) for this purpose. Some advanced fighters maybe able to use more energy for speed during a turn; this will benoted in their descriptions. THIS ITEM SUPERSECED BY THEABOVE ITEM.(OJ1.248) NEW RULE: REPAIRS: Hiver fighters are repaired inthe same manner as normal fighters using the deck crewsprovided in (OJ1.111) or any other standard repair rules that cannormally be applied to fighters. Note that deck crews are notrequired to rearm sting torpedoes as the fighter can arm them onits own.(OJ2.7) CORRECTION: The word “. . . weapon . . .” should be “.. . weapons . . .”.(OJ2.72) CORRECTION: Last sentence “. . . SRC round . . .”should be “. . . SRC rounds . . .”.(OJ2.76) CORRECTION: The next-to-last sentence should read“. . . can only provide weapons to a fighter type it was designatedas serving . . .”.(OJ3.0) CLARIFICATION: As with pods in the Alpha sector, anypods on fighter ready racks have been charged before a scenariobegins regardless of weapons status. Weapons status onlydetermines the number of fighters that have had their podsloaded, or which have been launched.(OJ3.37) CORRECTION: Second sentence: “. . . impulse to firethe its SRC . . .”, delete “. . . the . . .”.(OJ4.12) CORRECTION: Last sentence should read “. . . and33% of the shards . . .”, the “of” is missing.(OJ4.122) CLARIFICATION: Crippled black shards retain their L-DMP.(OJ4.132) CLARIFICATION: All shards are considered to be‘fighter’ shards for purposes of this rule.(OJ4.133) DELETED DUPLICATION: This rule “Shards may notcarry any sort of pod.” was deleted because it simply duplicatespart of (OJ4.111).(OJ4.236) CORRECTION: Last sentence: delete “. . . an . . .”after “. . . a ship from . . .”.

(OJ4.46) CLARIFICATION/NEW RULE: The fighter squadronrule in the Alpha Sector (limiting fighters to squadrons of 12 forEW support) is modified in the Omega sector, where fighterscame in squadrons of many sizes. Except where noted in a shipdescription, all of the fighters on a given ship comprise onesquadron, regardless of the actual number of fighters. The Drex,for example, have as many as 16 fighters in some squadrons.(OJ4.46) MOVED/COMBINED: This clarification/new rule wasmoved to (OJ0.01) and combined with that rule.(OJ5.421) CORRECTION: Change the fourth sentence of thisrule to read as follows: If it self-destructs, it is lost, and itsexplosion strength must be announced. If the shuttle is destroyedby enemy action, its explosion strength would not be revealed inthe same way as a destroyed suicide shuttle’s would not be(J2.152).(OJ5.44) DELETION: This rule was deleted as a duplication of(OJ5.31), rule (OJ5.45) was renumbered to replace it.(OJ5.45) CHANGE: This rule was renumbered (OJ4.44).(OJ5.45) CORRECTION: Third paragraph, reference to (OJ5.31)for ATG should be to (OJ5.32).

(OM0.0) ERRATA

(OM1.315) CORRECTION: Last sentence: “. . . allocated to growit is . . .”, change “. . . is . . .” to “are”.

(OP0.0) ERRATA

(OP1.13) CLARIFICATION: Add to end: Note that units smallerthan Size Class 5 do not take movement damage.(OP1.132) CLARICATION: Add to end of rule: “. . . including ifthe ships are moved as a result of black holes (P4.1). If a ship ismoved by a black hole and moves on its own in the sameimpulse it will resolve damage due to both movements (thedamage might be on different shields).”(OP1.139) ADDITION: The Qixa cannot install this feature inships they capture and convert to their technology.(OP1.211) ADDITION: Add to end of second sentence: “. . . andMagellanic versions of those rules, i.e., ME and MF, and EarlyYears versions of those rules i.e., YE and YF.”(OP1.212) REVISED: Now reads: Non-weapon systems, such aswebs (G10.0), ESGs (G23.0), plasma clouds (OG3.0), etc. (thoselisted in rule section “G” or Omega rule section “OG” orMagellanic rule section “MG”) do not cause feedback but mayhave specific effects defined hereafter. See (OP1.23). Note thatother systems may be added to the game in future and will havetheir own interactions defined in their own rules.(OP1.213) ADDITION: Add to end of rule: Note that otherweapons may be added to the game in future and will have theirown interactions defined in their own rules.(OP1.22) CHANGE: last sentence to read: Calculate thefeedback for each weapon as it is fired to create a total, roundany remaining fraction of 0.5 or more up. ADDITION: Add after:“A fully overloaded photon torpedo (E4.4) would score threepoints of feedback” the following text “(three of them would scoreten points of feedback if no other weapons were fired)”.(OP1.22) CORRECTION: Change to read: “Kinetic Waves score20% of their warhead strength at range one, even if launched ata target at range zero which they nominally could not hit(OFP3.331).”(OP1.221) ADDITION: Add to end of rule: Feedback for weaponslaunched in the Seeking Weapons Stage (6B6) is combined andscored on the appropriate shields after drone launches.Feedback for Magellanic Mass Drivers (ME2.31) is scored at thepoint where they fire in Ship Systems Function Stage (6B4).(OP1.223) ADDITION: Seeking weapons launched before ascenario begins (S4.13) by ships (including PFs) score nodamage on the launching ship (it is assumed to have reinforcedthe facing shield). Seeking weapons launched by fighters or

shuttles score the appropriate feedback damage prior to thescenario beginning.(OP1.233) ADDITION: Add to end: Magellanic Multi-layer shields(MD2.0) must score the damage on a facing outer shield and canonly score damage on a facing inner shield if there is no outershield on that shield facing.(OP1.24) ADDITION: Add to end of rule: A weapon whose addeddamage does less than 0.5 points has no increased effect.(OP1.241) CHANGE EXAMPLE TO READ: A Qixa ship is hit bya photon for 16 damage points, a phaser for 7 damage points,and a phaser-3 for two damage points in the same impulse. Thephoton’s strength would be increased to 19 points, the phaser-1to 8 points, and the phaser-3 would not be increased (20% of 2 is0.4), for a total of 29 damage points. Note that this increaseoccurs before any other calculations are made (e.g., beforehellbore damage is divided up against the shields).(OP1.251) ADDITION: Change to read Captor mines (M4.4),including Omegan Captor Mines (OM2.0) and Magellanic captormines (MM1.0), in the cloud will score feedback damage onthemselves when they use their weapons.(OP1.26) CLARIFICATION/NEW RULE: SHUTTLES ANDFIGHTERS: The launch of a shuttle or fighter will not triggerfeedback, even if the shuttle or fighter is a scatter pack (FD7.0),or suicide shuttle (J2.22).(OP1.261) CLARIFICATION/NEW RULE: Shuttle bombs (OJ5.0)are treated as shuttles.(OP1.262) CLARIFICATION/NEW RULE: Death Bolts(YFD20.0), while launched from shuttle bays, are not shuttlesand do trigger feedback as would drones launched from type-Fdrone racks (FD3.6).(OP1.263) CLARIFICATION/NEW RULE: Fighters and shuttlesare subject to feedback under (OP1.22) when they fire or launchtheir weapons.(OP1.264) CLARIFICATION/NEW RULE: Fighters and shuttlesnever trigger movement damage (OP1.13) being smaller thanSize Class 5.(OP1.265) CLARIFICATION/NEW RULE: In an exception to(OP1.26), if a suicide shuttle or shuttle bomb is launched in thehex of its target, and both the launching unit and target unit arestill in the same hex on the following impulse (F2.323), thelaunching unit is affected by feedback (OP1.22) normally.Specifically, if a suicide shuttle with an 18-point warhead islaunched in the same hex as its target on Impulse #5, and boththe launching ship and the target are still in the same hex aftermovement on Impulse #6, the launching unit takes four points offeedback damage. Note that “the same hex” in this case meansthat the units were all in hex 2215 at the end of Impulse #5 andstill in hex 2215 after movement on Impulse #6.

(OR0.0) ERRATA:

(OR.B) ADDITION: GENERAL COMMENT ON BASES: All of thebases in Omega 2 have positional stabilizers. These arenecessary to prevent scenarios being ended by the simpleexpedient of one side towing the base away, or shoving it into aplanet. If the stabilizers of the base are not operating, all Ω2bases have a towing cost of 0.5, except for the Loriyill DefenseOutpost, which has an assumed towing cost of 1.0.(OR.B) ADDITION: GENERAL COMMENT ON BASES: All of thebases in Omega 3 have positional stabilizers. These arenecessary to prevent scenarios being ended by the simpleexpedient of one side towing the base away, or shoving it into aplanet. If the stabilizers of the base are off, they have anassumed towing cost of 0.5, except for the Loriyill DefenseOutpost, which has an assumed towing cost of 1.00.(OR01.S2) ADDITION: Alunda MRS shuttles can have theirplasma whips armed in whipcrack torpedo mode (OFP7.34).(OR02.06) CORRECTION: PW-3 #10 should have an RS arc.(OR02.07) CORRECTION: PW-3s #9 and #10 on platformshould be #13 and #14.

(OR02.09) CORRECTION: The reference to this being the firstship in the Omega sector to use launch tubes is in error, as theDrex BCV began using these in Y112.(OR02.12) CORRECTION: PW-3 #8 should have an RS arc.(OR02.B1) CORRECTION: SSD: Change half the APRs toAWRs, change Forward Hull to Center Hull.(OR02.P) CLARIFICATION: MAESRON PODS IN CL#21 cannotbe used by Freighters unless specifically noted as being allowedfor that function.(OR03.0) CORRECTION: Errata under this rule number shouldbe (OJ3.0). There is a corrected errata item with the right rulenumber in this file.(OR03.08) CLARIFICATION: This ship operates two squadronsof fighters, each consisting of seven phaser and three cannonfighters.(OR03.09) ADDED: Add to ship description: These ships neverreceived the ACG refit because they lacked the power to exploitit.(OR03.PF2) CORRECTION: The SSD for the Koligahr PFs foundin Captain’s Log #22 did not have a firing arc for the Anti-MatterCloud Generator. The firing arc for the weapon should be RA, thesame as for a Micro-phaser-1 in that position as shown on someof the PFs.(OR04.07) CORRECTION: SSD: There should not be anImplosion Bolt Table on this SSD.(OR04.08) CORRECTION: Rule (OFP2.122) for the SuperHeavy Implosion Torpedo is correct and the SSD is wrong, theweapon has only three damage boxes, not four.(OR05.09) CLARIFICATION: The “Vari FFL were often foundleading squadrons of only one other FF” does enable the Vari tofield two or more FF squadrons in a single battle force eachconsisting of one FFL and one other frigate in violation of thenormal limits of (S8.0), they cannot field two FFLs (unless one isthe flagship) and only one other FF.(OR05.10) CORRECTION: There should have been a PB tableon the SSD for use by the fighters.(OR05.13) CORRECTION: CT: Ship data table still lists ship asCA. Arcs on rear particle phaser-3s should be LS+RR/RS+LRrather than LS/RS+RA. Delete the RA arc note.(OR05.15) CORRECTION: CC: Arcs on rear particle phaser-3sshould be LS+RR/RS+LR rather than LS/RS+RA. Delete the RAarc note.(OR06.012) CLARIFICATION: LOSS OF MANEUVERABILITY:Probr ships are fairly maneuverable, but have a hiddendisadvantage. If at any time all Left Warp OR all Right Warpengines are destroyed [or the wings are jettisoned (OR6.013)],their turn mode is increased (worsened) by one level, i.e., turnmode B becomes C, C becomes D, etc. Turn mode charts forboth the normal and the worsened turn modes are presented oneach SSD. For purposes of destroyed engines, this effect startsat the beginning of the impulse after this condition occurs at theend of the involuntary Movement Stage (6A1). The effect is fromthe beginning of the turn if the wings are jettisoned. 14 Feb 2007(OR06.013) CLARIFICATION: WING JETTISON: Probr shipsmay drop their “wings,” the ship sections that contain left andright warp. Both wings must be dropped simultaneously. This istreated as a ship separation under (G12.0), except as notedbelow. The Probr unit must declare it is jettisoning the wings inthe Announce intention to voluntarily separate section in theSpeed Determination Phase (2), and actually drops the wings inthe ships committed to do so voluntary separate sections of theInitial Activity Phase (5). 14 Feb 2007(OR06.02) CORRECTION: SSD: The warp engine on the rightwing should be marked R WARP.(OR06.03) CORRECTION: SSD: The warp engine on the rightwing should be marked R WARP.(OR06.04) CORRECTION: SSD: The warp engine on the rightwing should be marked R WARP.

(OR06.05) CLARIFICATION: Special Sensors on the ProbrScout are destroyed on “Torpedo” damage points.(OR06.05) CORRECTION: SSD: The warp engine on the rightwing should be marked R WARP.(OR06.09) PQ-3s in wings should be renumbered, PQ-3s #7 and#8 (left-side firing arc) should be #5 and #6 respectively, and PQ-3s #9 and #10 (right-side firing arc) should be #7 and #8.(OR06.F2) CLARIFICATION: The reference to 12 hexes range isthe maximum distance the fighter can be from a target againstwhich it launches its HEAT. Obviously the torpedo may movemore than 12 hexes while in pursuit of the target.(OR07.02) CORRECTION: This ship’s BPV should be 118, not108.(OR07.03) CLARIFICATION: Chlorophon ships become stunnedimmediately (in mid-turn) when the last control box is destroyedand are under the effects of (G2.2) at the end of the damage stepwhere that happens. This is an exception to (G2.20). When aChlorophon ship is stunned, any plotted mid-turn speed changesoccur as programmed, but the Phon ship would not be able to doany unplotted speed changes. Other (G2.2) effects would alsotake immediate effect, i.e., the ship would have to cease erraticmaneuvers if it was already doing erratic maneuvers and would(for the remainder of the current turn) not be able to do an HETeven if one was plotted. Any existing tractor links would have tobe dropped. The ship would benefit from a previously launchedweasel, but could not launch one, etc. It would have to operateunder the limits of (G2.2) the following turn (until the 32 impulsesran out). It could access unplotted speed changes once therepair is complete on the control box. All (G2.2) restrictions applyfrom the point the Phon is stunned to the point where the repair ismade. Anything fired before the ship was stunned does notimpact the limits under (G2.2) as to how and when it could nextfire weapons, and the restriction on firing weapons no longerapplies once the ship has recovered.(OR07.03) CLARIFICATION: Stun lasts for 32 consecutiveimpulses from the point where the unit loses its last control box tothe same point in the sequence of play. This is determined in thePost Combat Segment (6E) after rolling for UIM breakdowns, asthe last action of the Marines Activity Stage (6B7), and in theFinal Movement Actions Stage (6A4) after ships are releasedfrom tractor beams. 14 Feb 2007(OR07.11) CORRECTION: The first prototype ship was inservice in Y104.(OR08.02) CORRECTION: SSD: HET cost is wrong, should be4, not 2.5, while CPU is operational.(OR08.03) CORRECTION: SSD: HET cost is wrong, should be2, not 1.25, while CPU is operational. The PP-1-RS should be #4.(OR08.04) CORRECTION: SSD: HET cost is wrong, should be1.3, not 0.833, while CPU is operational.(OR08.05) CORRECTION: SSD: HET cost is wrong, should be2, not 1.25, while CPU is operational. The PP-1-RS should be #4.(OR08.06) CORRECTION: SSD: HET cost is wrong, should be4, not 2.5, while CPU is operational.(OR08.07) CORRECTION: SSD: HET cost is wrong, should be6, not 3.75, while CPU is operational. The unlabeled hull boxeson the right side of the ship are “aft hull”.(OR08.08) CORRECTION: SSD: HET cost is wrong, should be4, not 2.5, while CPU is operational. The phaser tables on thisship’s SSD are wrong, they should be Wide Angle Phasers (asshown on the ship part of the SSD) and not Particle Phasers.(OR08.09) CORRECTION: SSD: HET cost is wrong, should be4, not 2.5, while CPU is operational. This ship operates all of itsfighters in a single squadron.(OR08.09) CORRECTION: The reference to the ship being ableto launch all of its fighters in ‘two’ impulses should have been to‘three’ impulses. SSD: The firing arc of the HCLs on the X1fighters are LF and RF as given in the fighter’s rule (OR8.F1) andMaster Fighter Chart, the fighter data box on the SSD listing FAarcs is incorrect.

(OR08.10) CORRECTION: SSD: HET cost is wrong, should be2, not 1.25, while CPU is operational.(OR08.11) CORRECTION: SSD: HET cost is wrong, should be1, not 0.625, while CPU is operational. The minimum crew shouldbe three per (G9.41). The firing arcs of the light hypercannonsshould be LF for HCL-A, and RF for HCL-B.(OR08.12) CORRECTION: SSD: HET cost is wrong, should be1.33, not 0.833, while CPU is operational.(OR08.F1) CORRECTION: The firing arc of the HCLs are LF andRF as given in the rule and Master Fighter Chart, the fighter databox on the SSD of the Battle Carrier (OR8.9) listing FA arcs isincorrect. Drex fighters are not advantaged as super computersversus other fighters. The reduction in size of the craft does notleave enough room for a computer intelligence much smarterthan that assisting the pilots of non-Drex fighters.(OR09.0112) NEW RULE: The Alunda Host creature isengineered to support its crew in a perfectly symbiotic manner. Itproduces life support requirements automatically each turn untilkilled, at no energy cost. The life support cost on all Alunda shipsis always zero, and no Alunda unit is ever required to useemergency life support. This has been incorporated into theRacial description in this product, but is included here so thatplayers will be aware of it.(OR09.0151) CLARIFICATION: As with CDR, the “healing” trackgenerates a number of repair points at the start of each turnduring the Allocate Repair Points Step of the Energy AllocationPhase (1) based on the highest unchecked box on the track. Thisis automatic and CAN be used at the same time as other repairs;this is an exception to (D14.26) and (G17.1313). 14 Feb 2007(OR09.02) ADDITION: Whipcrack refit increases BPV by eightpoints.(OR09.03) ADDITION: Whipcrack refit increases BPV by fourpoints.(OR09.04) ADDITION: Whipcrack refit increases BPV by twopoints.(OR09.05) ADDITION: Whipcrack refit increases BPV by twopoints.(OR09.06) ADDITION: Whipcrack refit increases BPV by sixteenpoints.(OR09.06) CORRECTION: SSD: The Attraction-Repulsion Fieldson this ship are labeled “E” and “F”, which letters are also usedby two of the plasma-whips. Change the lettering of TheAttraction-Repulsion Fields to “J” (left side) and “K” (right side).(OR09.07) ADDITION: Whipcrack refit increases BPV by eightpoints.(OR09.08) ADDITION: Whipcrack refit increases BPV by fourpoints.(OR09.09) ADDITION: Whipcrack refit increases BPV by eightpoints.(OR09.10) ADDITION: Whipcrack refit increases BPV by fourpoints.(OR09.B1) ADDITION: Whipcrack refit increases BPV by fourpoints.(OR09.F1) ADDITION: Whipcrack refit: All fighters producedfrom Y128 included the ability to launch whipcrack torpedoes(OFP7.34), there is no change in BPV. Older fighters (“produced”before the refit was initiated) were still encountered as late asY138 in front line service. There are several reports of somebeing encountered as late as Y178 in back water areas, butthese may have been simple cases of the system not beingarmed or the fighters being destroyed before they could launchtheir whipcracks.(OR09.R1) NEW RULE: WHIPCRACK TORPEDO REFIT: Aftermuch effort the Mirn were able to breed in a new capability fortheir ships to launch seeking weapons from their plasma whips inY128 as a defense against the fighters being deployed by theVari. [See (OFP7.0).] Dubbed the whip-crack torpedo refit,virtually all “new construction” had it, but it was never universal.There were always a few ships that had been “built” before the“refit” could be installed. Difficulties in the process, particularlywith newer classes, sometimes resulted in a “modern” ship not

having the refit when it first appeared. The cost of this refit is twoBPV per plasma-whip, and ships equipped with it increase theirBPV by two points per plasma whip. It is denoted by asuperscript “w” added to the ship’s designation, but is not shownon any SSD.(OR10.03) CORRECTION: The Wide Angle Phasers should benumbered 1, 2, and 3, not 1, 3, and 5.(OR10.034) CLARIFICATION: Deployment patterns: In patrolscenarios (S8.0), Hiver fleets may contain no more than one Sizeclass 2 unit and no more than two size class 3 units; a third sizeclass 3 unit may be substituted for the one permitted size class 2.This modifies (S8.33) for the Hivers. A maximum of three mentalnodes (OD2.0) may be present in any fleet. Note, as of theMaster Rulebook’s being published, there is no Hiver Size Class2 unit, but one may be published in a future product.(OR10.04) CORRECTION: Delete the probe ammo track.(OR10.05) CORRECTION: Delete the probe ammo track.(OR10.06) CORRECTION: The rules description for this ship liststhe correct date, and the Master Ship Chart is in error. The shipwas in service in Y183, not Y83. SSD: PW-1 #4 should be #2.(OR10.08) CORRECTION: Delete the probe ammo track.(OR10.12) CLARIFICATION: Hiver destroyers are capable ofindependent operations, but as the basic destroyer lacks acontrol box (bridge, emer, etc.), it would operate under the rulesfor an uncontrolled ship (G2.2) under (OR10.031). This conditionwould exist any time it more than 35 hexes from a Hiver unit witha bridge. For this reason Hiver destroyers were only rarelyencountered on independent operations, although sometimesgroups of them would operate around a “destroyer leader” to beseen in a future product. This unit is size class 5, not size class 4.Minimum Crew should be three, not four. As Hiver ships cannever have outstanding or poor crews (OR10.033) Hiverdestroyers cannot use (K8.0).(OR10.31) CLARIFICATION: Whether or not a unit is in range isdetermined three times during each impulse at the same time aschecking Loss of Queen (OR10.032). The Post Combat Segment(6E) after rolling for UIM breakdowns, as the last action of theMarines Activity Stage (6B7), and in the Final Movement ActionsStage (6A4) after ships are released from tractor beams. 14 Feb2007(OR10.32) CLARIFICATION: Death of a Queen is checked forthree times during each impulse at the same time as checking forLoss of Control (OR10.031). The Post Combat Segment (6E)after rolling for UIM breakdowns, as the last action of the MarinesActivity Stage (6B7), and in the Final Movement Actions Stage(6A4) after ships are released from tractor beams. 14 Feb 2007(OR10.F1) CORRECTION: On the Master Fighter/Shuttle Chart,this fighter should be listed as having a cost of 8/12. This hasbeen incorporated into the Master Fighter Chart in this product,but is included here for clarity.(OR10.F4) CLARIFICATION: This unit operates under the rulesfor Heavy Fighters (J10.0).(OR11.02) CORRECTION: SSD should have the RA arcdescription.(OR11.S1) NEW RULE: Sigvirion shuttles are armed with a pulseemitter that can fire twice per turn (360° firing arc). If they arecrippled, this weapon can fire only once per turn. In Y179 andafter, this becomes an improved pulse emitter (OE2.4) with thesesame firing restrictions (no change in BPV).(OR12.02) CORRECTION: SSD: The Loriyill CA has two PQ3,one is FA+L and the other should be FA+R.(OR12.03) CORRECTION: SSD: PQ-3 #8 should have an FA+Rfiring arc, not FA+L.(OR12.04) CORRECTION: SSD: Delete Probe ammunition track.(OR12.05) CORRECTION: SSD: Delete Probe ammunition track.(OR12.06) CORRECTION: SSD: PQ-3 #8 should have an FA+Rfiring arc, not FA+L.(OR12.07) CORRECTION: SSD: Fireballs C and D should haveFA+R firing arcs.

(OR12.08) CORRECTION: SSD: We forgot to include a Fireballtable for use by the fighters.(OR12.09) CORRECTION: SSD: PQ-3s #8, #9, and #10 shouldhave FA+R firing arcs, not FA+L.(OR12.10) CORRECTION: SSD: Delete Probe ammunition track.(OR12.B1) ADDED: Add the following systems to the base asfollows: 1xTransporter between the Bridge and Fireball A,1xTractor between Center Hull and Fireball F, 1xLab aboveFireball B, 1xLab above Fireball C, 1xLab under Fireball D, and1xLab under Fireball E. Note that doing this will require movingsome of the indicated systems to make the room, but the addedsystems should have been part of the SSD.(OR13.02) CORRECTION: SSD: Souldra Heavy Cruiser H-DMP#8 firing arc should be RA+R.(OR13.03) CLARIFICATION: SOULDRA FF: The description ofthis unit is not in conflict with (OR13.0342), the reference to FFsseeming to be able to last longer without “refueling” is an obtusereference to their numbers, i.e., there were a lot of themencountered.(OR13.035) CORRECTION: 2nd to last sentence: delete “. . . a .. .” in “. . . ships have a two . . .”.(OR13.06) CORRECTION: Correction to SSD: The SSD showscheck off ovals for the dark matter torpedoes of the VioletShards. Violet Shards arm their own dark matter torpedoes(OR13.F2) and do not need to return to their carrier to have themre-armed.(OR13.10) CORRECTION: Correction to SSD: The SSD showscheck off ovals for the dark matter torpedoes of the VioletShards. Violet Shards arm their own dark matter torpedoes(OR13.F2) and do not need to return to their carrier to have themre-armed.(OR13.10) CORRECTION: SOULDRA CV: The shard groupshown on this ship’s SSD does not include the required 33%black shards, this is because the ship seldom operated far fromsources of dark matter energy to support its shards. In acampaign where the ship was not near a source of dark matter, itwould be required to adhere to the 33% rule (OR13.035).(OR13.F) CLARIFICATION: Red and Violet shards are listed.References to Black, Blue, Green and Orange shards weredeleted for space considerations, but are fully covered (as arethe actions of Red and Violet Shards) under (OJ4.0).(OR13.F2) CLARIFICATION: The dark matter torpedo remainsoperational even if the Violet Shard is crippled.(OR14.0) CORRECTION: Last sentence of first paragraph:Change “. . . complete . . .” to “. . . traverse . . .”.(OR14.06) CORRECTION: Third sentence, delete commas after“knights” and “barque.”(OR14.09) CORRECTION: Last sentence, change “. . . is . . .” to“was”.(OR14.M10) CORRECTION: The 360° firing arc shown on themodule SSD were to only be available while it is part of a supplydock, if part of a ship, the phasers are restricted to the L and Rarcs as listed.(OR14.M11) CLARIFICATION: The die roll is made beforeTractor/Negative-tractor auctions in the Energy Allocation Phase(1).(OR15.F0) NEW RULE: REARMING APBS: Ymatrian Fightersare armed, and rearmed, as per (OJ2.0), requiring theprocedures in (J4.88) for energy weapons. For this purpose,each ready rack with a “+” symbol has capacitors capable ofholding the maximum amount of energy (usually five points each)for any APBs of the fighter (there is a separate capacitor on theready rack for each APB on the fighter). It requires one deckcrew action to load one APB charge onto a fighter. Once acharge is loaded onto the fighter, the charge can only be fired ordischarge (E1.24) (requiring one deck crew action). Thecapacitor can be reloaded (same procedure as an APB, i.e., twopoints of power on the first turn, three points of power on thesecond turn for each APB, overloads are not allowed) by theship’s power. APB charges loaded in the storage facility may beloaded on an APB-armed fighter by deck crews. APBs cannot befired from the storage facilities in the shuttle bay. Reloading a

fighter with an APB is a single deck crew action, e.g., it requirestwo deck-crew actions to load both charges on a Dirk fighter).Once loaded the weapons can only be fired or discharged(E1.24).(OR15.F1) CLARIFICATION: Once the fighter’s SEP exceeds13, then under (D23.222) a roll of 5-6 after any subsequent shotresults in breakdown and destruction of the fighter.(OR17.0) CORRECTION: A New Home, paragraph #1 referenceto “astrological computer data,” should be to “astronomicalcomputer data.”(OR17.02) CORRECTION: Delete all references to ADD racksand short ranged cannons being developed from Klingon ADDracks. Add the following as the second paragraph: “The Throneof Ozymondas had a Klingon ADD system and ammunition for itin its cargo bay. The system languished in a warehouse forseveral years until information found by clandestine observationof the surrounding races revealed the potency of the Mæsrons’tachyon missiles. As the basic ADD was of little use againsttachyon missiles, but the ADD rack proved capable ofmodification into a more effective weapon that became known asthe short-range cannon. The system was first deployed with theFederal Republic’s first carrier group in Y144.”(OR17.02) CORRECTION: TECHNOLOGY: In the last sentenceof the second paragraph the reference to (OJ3.0) should be to(OJ5.0).(OR17.05) CORRECTION: There is a contradiction in the racialbackground and the Master Ship Chart on the Year in Servicedate, the Master Ship Chart is correct, i.e., Y173. The SSD ismissing a hit-and-run check-off box for the DERFACS system.The Rear phaser-1s (#3, #4, and #5) have RX firing arcs, and theRX arc description is also missing from the SSD.(OR17.05) CORRECTION: This item is listed twice and is rightboth times.(OR17.07) CORRECTION: There is a contradiction in the racialbackground and the Master Ship Chart on the Year in Servicedate, the Master Ship Chart is correct, i.e., Y175. The SSD ismissing a hit-and-run check-off box for the DERFACS system.(OR17.08) CLARIFICATION: The ship carries pods for itsfighters under (J11.131). Additional pods can be purchasedunder Annex #6.(OR17.11) CORRECTION: SSD: The forward half of the ship isoffset by a half box. The Year in Service date on the Master ShipChart is in error, it should be Y178 not Y175.(OR17.P1) CORRECTION: The SSD is missing a hit-and-runcheck-off box for the DERFACS system.(OR17.R1) ADDED: This refit began in Y181. This refit is notedby a superscript “t” after the ship’s designation, e.g., a destroyerwith the refit would be noted as a “DDt”.(OR17.R2) ADDITION: This refit is simply assumed beginning inY182, and designation is added to the ship to indicate itspresence. If a ship in Y182 or later does not have it, it will benoted in the special scenario rules for that scenario.(OR17.R3) ADDED/NEW RULE: AWR REFIT: Ship mountedAWRs were developed as part of solving the need for the DN toboth move and power its large array of photon torpedoes. Oncethey were developed, the advantage of converting the APRs onall ships armed with at least some photon torpedoes wasobvious. All new construction of such ships from Y179 wereusually completed with AWRs rather than APRs, but sometimes,even as late as Y199, ships were still launched with the olderAPRs due to the costs associated. Older ships were convertedas the resources were available to accomplish it, and most shipshad them by Y184, but the refit was not universal until Y200,although any given group of FRA ships encountered might allhave it after Y184. This refit is noted by a superscript “a” after theship’s designation, e.g., a destroyer with the refit would be notedas a “DDa”. If the destroyer also had, or later received, thetachyon missile refit, it would be noted as a “DDat”.(OR18.0) CORRECTION: The Singers actually received phasercapacitors from the Loriyill and began using them in Y175, thereferences to Y183 are actually other later Loriyill technology

transfers. All SSDs have the wrong Tachyosonic Beam table; usethe one in the rulebook. The SSDs were not updated after achange.(OR18.02) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.03) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.04) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.05) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.06) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.07) CLARIFICATION: SSD: The Tachyosonic Beamtables on this SSD is wrong, the ones in the rulebook are correct.We apologize for this blunder.This SSD actually shows theimproved ship that entered service in Y183. The original Y179ship did not have flame shields and only 13 fighters. An SSD forthe earlier ship will appear in a future product. Annex #7Gincorrectly lists this ship as having only 13 fighters, which iscorrect for the earlier version, but should show 15 fighters for theimproved version. (The two added fighters were both Light HoverFighters and simply replaced two of the admin shuttles, i.e., theearly version had four admin shuttles.) Change the Year inService Date on Annex #3 to Y183.(OR18.08) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.08) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.10) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.11) SSD: The Tachyosonic Beam tables on this SSD iswrong, the ones in the rulebook are correct. We apologize for thisblunder.(OR18.B1) CORRECTION: The carrier chart incorrectly lists asquadron of 16 fighters, the DO has only six fighters.(OR19.06) ADDITION: Ryn units compute their BPV forCommander’s options based on their BPV within the Ryn Nebulaunless special scenario rules say otherwise.(OR19.F0) CLARIFICATION: RYN Fighters are armed, andrearmed, as per (OJ2.0), requiring the procedures in (J4.88) forenergy weapons, and (J4.89) for missile weapons [in this lattercase, as also provided in (OR19.7)]. For this purpose, each readyrack with a “+” symbol has a capacitor capable of holding themaximum amount of energy (usually four points) for the TCB ofthe fighter. In the case of a ready rack for the Render Fighter(OR19.F3), there are two such capacitors. The status of thesecapacitors is the same as that of disruptor freezers in (J4.84) forpurposes of weapons status. Irrespective of whether or not thecapacitor holds one, two, three, or four points of power at thetime it is discharged into the fighter, it requires one deck crewaction to load the fighter. Once a fighter is loaded additionalpower cannot be added to the fighter’s TCB, even if more poweris available, unless the existing charge is first discharged(requiring one deck crew action). When a fighter’s TCB is armed,all power currently in the capacitor (this can include reservepower allocated to the capacitor when arming commences, butreserve power cannot be added to the capacitor after arming hascommenced) must be discharged into it. If a Capacitor washolding two points you could not use one point of power to

partially load fighter A, and then use another point of power topartially load fighter B (after moving it to the capacitor). ACapacitor used to load one fighter during a turn (or finishing theloading during part of a turn) could have reserve power allocatedto it to arm another fighter later in the turn. When a RYN fighter(or MRS) armed with a TCB fires the weapon, all power currentlyin the TCB is fired. A fighter with a fully loaded TCB cannot fire itwith one of its four points of power reserving the other three for alater shot.(OR19.F0) CLARIFICATION: The Ryn SAF fighter needs fourpoints of energy while the RHF needs eight; they reload with onedeck crew action per fighter.(OR19.F1) CORRECTION: Annex #4 should have shown thisfighter armed with a single PQ-3-FA.(OR19.F3) CLARIFICATION: This fighter has two TCBs that aretreated as separate weapons for all purposes. Each can beloaded to a maximum of four points of power, but neither can usepower loaded in the other. This unit operates under the rules forHeavy Fighters (J10.0).(OR20.033) CLARIFICATION: Cargo Destruction: Before anyvolley of internal damage is rolled in either the Damage DuringMovement Stage (6A2) or the Direct-Fire Weapons DamageResolution Stage (6D4) (but after the damage amount has beendetermined), the Bolosco player can, but is not required to, electto “lock the bulkheads” to protect the cargo. 14 Feb 2007(OR20.07) CLARIFICATION: The tug can carry one large pod, orone or two small ones.(OR20.08) CORRECTION: SSD: The Bolosco MD shows ashield cost of 1+1 on the SSD. This should be 1+3.(OR20.PL0) CORRECTION: The Bolosco pods also sufferedfrom the evil SSD gremlin; the BPVs given for Bolosco Pods onthe Master Ship Chart are correct. The BPVs for the Self-Defense Pod and Cargo Pod on most Bolosco Ship SSDs arewrong.(OR21.0) CORRECTION: All the SSDs have Spark Ring tablesshowing 1-2-3 energy when it should be 2-3-4. The Qixa BPVstake some study to grasp. They have higher BPVs if fighting inthat explosive nebula of theirs, but the nebula doesn’t affectscout sensors so the economic BPV of scouts doesn’t go up. Butif a scout is fighting alone, it uses its combat BPV, which does goup in the nebula.(OR21.03) ADDITION: Qixa units compute their BPV forCommander’s options based on their BPV outside of theQixavalor cloud unless special scenario rules say otherwise.(OR21.6) CLARIFICATION: Deck crews are only present if thereare mercenary fighters, and then no more than one deck crewper fighter, otherwise the ship only has the two normal deckcrews provided by (J4.814) and cannot buy extra deck crews.Even with mercenary fighters, this ship is considered a CasualCarrier (J4.62).(OR21.B1) CORRECTION: “. . . damage (treated asunidirectional for purposes of PHASER hits, i.e., any gausscannon on the base can be destroyed).”(OR21.S1) ADDITION: The gauss cannon cannot be armed in“spark” mode (OE28.3).(OR21.S2) ADDITION: The Qixa MRS can fire one of its gausscannons in “spark mode” (OE28.3), but if it does so it cannot fireits other gauss cannon on that turn. It can fire one gauss cannonin spark mode on Impulse #32 of one turn and fire the othergauss cannon normally on Impulse #1 of the following turn (orvice versa). The Qixa MRS cannot fire a spark mode shot withina quarter turn of firing such a shot on a previous turn.(OR22.0) CORRECTION: The Branthodon SSDs suffered frombad editing on our part. We used the terms “body” and “torso”more or less interchangeably. All references to Torso in thedamage charts of the SSDs should be read as “body”.(OR22.02) CORRECTION: The “Spit” line on the hatchlingdragon damage chart should read: 5, 3, 1, 1, -, not 5, 3, 1, -, 1.(OR22.03) CORRECTION: The “Spit” line on the very youngdragon damage chart should read: 5, 3, 1, 1, -, not 5, 3, 1, -, 1.

(OR22.04) CORRECTION: SSD: The young dragon should havea BPV of 110.(OR22.05) CORRECTION: SSD: The Mature Dragon shouldhave a BPV of 126 and the right wing should have 23 boxes.(OR22.06) CORRECTION: SSD: The adult dragonfire tableshould have a “2” instead of a “1” in the last entry for theEnveloping Dragonfire Damage line.(OR22.11) CORRECTION: SSD: The very young scout shouldhave a BPV of 100/70.(OR22.12) CORRECTION: SSD: The adult command dragonshould have a BPV of 180.(OR22.F0) ADDITION: Branthodon Regime fighters arebioengineered from an unknown space-going creature that may,or may not, be related to the one they their shuttles were createdfrom. This lifeform did not have weapons of its own, so theBranthodons crafted on cybernetic weapons systems. One theoryis that the fighters are engineered from parasites common tospace dragons (although no one has reported seeing such aparasite) in the same manner as Alunda Remora fighters.(OR22.S1) CHANGE TEXT TO READ: The Branthodonshuttlecraft was similar to the types operated by the Vari (albeitthey are bio-engineered constructs rather than shuttles). The firstBranthodon dragonships did not use such units, but encounterswith neighboring races quickly taught them the need forshuttlecraft. The Branthodons use the particle phaser as theirstandard phaser type in a cybernetic power system added to theshuttle’s “body”.(OR22.S2) CHANGE TEXT TO READ: The Branthodondeployed their own MRS shuttles (an improvement on thebioengeenered admin shuttle) about same the time as the otherOmega races. These included all the operational characteristicsof an MRS as given in (J8.0).

(OS0.0) ERRATA

(OS0.432) NEW RULE: ADDED TO START OF SCENARIOSECTION: SEEKING WEAPONS(OS0.4321) NEW RULE: ADDED TO START OF SCENARIOSECTION: The races that are involved in this scenario do notoperate Tachyon missiles. In a variation using Tachyon missile-armed units, the players will need to determine how manyCommander’s Option points will be available to modify them inaccordance with the year.(OS0.4322) NEW RULE: ADDED TO START OF SCENARIOSECTION: The races that are involved in this scenario do notuse drones. In a variation where a drone-armed race is used, alldrones are “slow,” i.e., speed–8. Type-II and type-V drones(speed 12) are not available for purchase as special drones.Each drone-armed ship can purchase special drones up to thehistorical racial percentages as part of the Commander’s OptionItems. Note that (S3.2) allows drone ships extra points for thispurpose.(OS01.0) CLARIFICATIION: added to scenario introduction:HISTORICAL NOTE: This scenario was supposed to useKoligahr PBs and a Mæsron FF. The designer literally wrotedown the wrong units. For historical purposes, those were theactual units, but the scenario is balanced for the units presentedin (OS1.2) below, but for a historical version the Koligahr DDsshould be PBs, and the Mæsron CA should be an FF.(OS01.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS1.431).(OS02.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS2.431).(OS02.63) ADDITION: Only one Hiver player can win, and toaccomplish this both Alunda ships must be destroyed and allunits belonging to the other Hive must be destroyed or forced to

disengage. The Alunda ships cannot disengage unless all shipsbelonging to one Hive have been crippled or destroyed.(OS03.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS3.431).(OS04.0) CORRECTION: Change year of scenario to Y56.(OS04.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS4.431).(OS04.63) CLARIFICATION: Reduce the battle size: Remove aDD from BOTH sideS, and reduce the required information totalto 450.(OS05.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS5.431).(OS05.45) NEW RULE/ADDITION: ENDING THE SCENARIO: Ifneither side is able to score any internal damage on the other forthree consecutive turns, after Turn #5, the scenario has endedand the Cholorphons must disengage.(OS06.0) CLARIFICATION: Added to scenario introduction:HISTORICAL NOTE: The Sigvirion CS cruisers in this scenariowere the first ones ever seen, believed to be prototypes. Theclass apparently entered series production in Y109. Why it didnot enter series production earlier remains a mystery. TheChlorophon FFA was also the first of its design. For reasons thatremain obscure the Chlorophon did not build anymore until Y114,entering squadron service in Y115.(OS06.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS6.431).(OS07.0) CORRECTION: Add to introduction: Note, the twoships that appear in this scenario are simulator ships, the CT didnot exist at this time.(OS07.0) CORRECTION: Change the Historical outcome toread: The Trobrin historically chose torpedoes over bolts initially,but eventually built the CT class perhaps indicating the decisionwas considered flawed. Players may use this scenario todetermine if that decision was correct, or not.(OS07.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS7.431).(OS08.0) CORRECTION: The date of this scenario is Y70.(OS08.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS8.431).(OS08.5) CORRECTION: The second and third sentencesshould have been one sentence: If the base is discovered, theProbr win if it is destroyed and no Probr ship is destroyed.(OS09.41) CORRECTION: Chlorophon Units disengage indirection C, not E, Loriyill units disengage in direction E, not C.(OS09.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS9.431).(OS09.422) CORRECTION: EW fighters were not available atthe time of this action. In a variant, if using EW fighters, one ofthe QAs on the Loriyill CV is a QAE. If not using EW fighters, it isa standard QA.(OS10.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS10.431).(OS11.421) CORRECTION: Change to read: MRS shuttles arenot available in the year this scenario is set. In a variant in whichMRSs are available, the Vari CA could be equipped with one,perhaps as a balance factor. If Commander’s options are use,d

qualified units could purchase them [up to the limits in (J8.5)]under (OS11.431).(OS12.45) CLARIFICATION: The ability of the Iridani ship toswitch between NVC and non-NVC fire control a SpecialScenario Rule and does not create any exceptions for otherscenarios, i.e., ships in other scenarios cannot switch betweenNVC and non-NVC fire control based on this scenario.(OS13.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS13.431).(OS13.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(OS14.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS14.431).(OS14.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(OS15.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS15.431).(OS16.421) CORRECTION: Change to read: MRS shuttles maybe purchased [up to the limits in (J8.5)] under (OS16.431).(OS16.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(OS17.424) MOVED RULE: This rule was moved andrenumbered as (OS17.484): The Souldra player may choose anycombination of shards desired within the limits of the DN’scapacity and other rules. Note (OJ4.12) and (OJ4.152).(OS17.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(OS17.433) CLARIFICATION: If the Loriyill player wishes to usea Prime Team (G32.0), he may purchase one or more (25 pointseach) by trading his Commander’s Option points. What thismeans is that the four Loriyill ships have a combined 67.5 pointsthat could be spent for Commander’s Options, and could chooseto not use 25 points of that for one Prime Team, or 50 points of itfor two Prime Teams. Whatever points remain would be used bythe ships normally (but no ship could spend more than wouldnormally be available to it). This is an exception to (S3.26) toallow the use of Prime Teams in this scenario only.(OS17.452) DELETION: This sentence is deleted from thisscenario rule as no one can figure out what it meant: Any T-bombs laid by the other ships are considered used.(OS17.483) CORRECTION: One crew draining/radiationabsorption counts as being “fed” for (OS17.481), (OS17.482),and (OS17.5).(OS17.485) ADDED RULE: The Souldra ship cannot disengageuntil it has “fed” enough to activate all of its systems which wereinactive at the start of the scenario (OS17.48) and/or becameinactive (OS17.483) before it began feeding.(OS18.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(OS19.0) CORRECTION/CHANGE: Change year of theScenario to Y164 and the background to read: In Y164 the Probr

discovered a large-scale Sigvirion infiltration into the highestlevels of their government as a result of their fleets being orderedto attack the Trobrin Empire. The Probr immediately set aboutexcising the infection from their body politic. Revealed, Sigvirionagents quickly scattered to avoid discovery and destruction. Onegroup of these agents booked passage on one of the new Qixatrading cruisers, the Good Trade. The Sigvirions intended toseize control of the ship, but their attempt at a quiet infection wasrevealed when Probr authorities contacted the ship. Fiercefighting broke out as the crew attempted to incise the infection,but discovered that it was too late. With memories still fresh fromthe previous Sigvirion conquest of their homes, the tried todestroy the ship, but found that Sigvirions had already disabledthe self-destruct mechanism, but they were able to destroy theship’s navigational data files before the last of them fell. Duringthe fighting some considerable vandalism was done to the vesselwhich released deadly gases from the ship’s propulsion systems.The Sigs managed to repair the gas release, but not before alltheir hosts had been exposed. Realizing their hosts were dying,the Sigs turned the cruiser towards the nearest organic outpostand set it on a suicide mission.(OS19.421) CORRECTION: Change to read: The year of thisscenario predates the development of MRS shuttles, and no shipin this scenario is qualified to carry one, but in a variant of thescenario where that is possible, they might be added to one side[up to the limits in (J8.5)], perhaps as a balance factor.(OS19.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(OS19.45) ADD TO END OF RULE: The Sigvirion player maychoose if a lost crew unit includes the pilots of any mannedshuttles he has launched. If at least two crew units remain, onecan be operating the ship, and one can be operating theshuttle(s). If only one crew unit remains, the Sigvirion player mustchoose if the shuttles will “go inert” (simply continue flying in astraight line), or if the ship will go inert.(OS20.432) CORRECTION: Change to read: Each missile-armed ship can purchase missile enhancements as part of theCommander’s Option Items provided they are available at thispoint in history.(OS20.453) ADD TO END OF RULE: EXAMPLE: A die roll of“five” would indicate the pocket will move in direction “five”, and asubsequent die roll of “four” would indicate that it will move fourhexes in that direction at a speed of four.(OS21.432) CORRECTION: Change to read: Each missile-armed ship can purchase missile enhancements as part of theCommander’s Option Items provided they are available at thispoint in history.(OS22.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(OS23.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (OS23.431).(OS23.432) CORRECTION: Change to read: Each missile armedship can purchase missile enhancements as part of theCommander’s Option Items provided they are available at thispoint in history.(OS24.432) CORRECTION: Change to read: There are nomissile using ships in this scenario (Ryn TE Missiles cannot bemodified), in a variation where missile-using ships are used eachmissile-armed ship can purchase missile enhancements as partof the Commander’s Option Items provided they are available atthis point in history.(OS24.63) ADD TO END OF RULE: For purposes (OS24.5) theamount of damage is 300 points with a minimum of 25 points perhex side.

(SL0.0) ERRATA

(SL180.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (SL180.431).(SL180.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(SL189.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history. DELETE subrules (SL189.4321) and (SL189.4322).(SL197.421) CORRECTION: Change to read: The year of thisscenario predates the development of MRS shuttles, and no shipin this scenario is qualified to carry one, but in a variant of thescenario where that is possible, they may be purchased [up tothe limits in (J8.5)] under (SL197.431).(SL197.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(SL209.421) CORRECTION: Change to read: The years of thiscampaign precede the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased by races opposing the Iridani [up to the limitsin (J8.5)] under (SL209.431). If using the optional MRS shuttles,the Iridani GL and BQ each begin the campaign with one MRS,and each of the opposition CAs has one MRS. These MRSshuttles count against the allowance for Commander’s Optionsunder (SL209.431).(SL209.432) CORRECTION: Change to read: Each missile-armed ship can purchase missile enhancements as part of theCommander’s Option Items provided they are available at thispoint in history.(SL214.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (SL214.431).(SL214.432) CORRECTION: Change to read: Each missilearmed ship can purchase missile enhancements as part of theCommander’s Option Items provided they are available at thispoint in history. DELETE REST OF TEXT AFTER THIS POINT.(SL219.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (SL219.431).(SL219.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(SL226.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (SL226.431).(SL226.432) CORRECTION: Change to read: There are nomissile using ships in this scenario (Ryn TEMs cannot bemodified), in a variation where missile-using ships are used eachmissile-armed ship can purchase missile enhancements as partof the Commander’s Option Items provided they are available atthis point in history.(SL238.0) CHANGE/CORRECTION: All (SH238.0) referencesare changed to (SL238.0) references.

(SL238.421) CORRECTION: Change to read: If using theoptional MRS shuttles, the Drex DN has an MRS, this is an earlyprototype and counts against the points available to the shipunder (SH238.431).(SL238.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(SL239.0) CHANGE/CORRECTION: All (SH239.0) referencesare changed to (SL239.0) references.(SL239.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(SL245.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles, but in avariant of the scenario where MRS shuttles are available; theymay be purchased [up to the limits in (J8.5)] under (SL245.431).(SL245.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(SL249.432) CORRECTION: Change to read: There are nomissile using ships in this scenario, in a variation where missile-using ships are used each missile-armed ship can purchasemissile enhancements as part of the Commander’s Option Itemsprovided they are available at this point in history.(SL253.421) CORRECTION: Change to read: The year of thisscenario precedes the development of MRS shuttles. If using theoptional MRS shuttles (perhaps as a balance factor since theyear does not allow their use), the Souldra Tanker has the optionof replacing one of its Shards with an Orange Shard [the Souldraversion of the MRS (OJ4.15)]. Such a substitution counts againstthe limits in (J8.5)] under (SL253.431).

ANNEXES ERRATA

ANNEX #3: CORRECTION: MASTER SHIP CHART year inservice date for the Mæsron OB (OR2.B1) should be Y46.ANNEX #3: CORRECTION: MASTER SHIP CHART: The(OR9.9) Alunda Huntship Carrier (OR9.9) should have "V" note.ANNEX #3: CORRECTION: MASTER SHIP CHART: The Yearin Service Date for the Hiver CV (OR10.6) is Y183, not Y83.ANNEX #3: CORRECTION: MASTER SHIP CHART: Year inservice dates for the FRA DD (OR17.5) and DDL (OR17.7) arecorrect, the FRA background is in error. The Year in Service datefor the FRA DN (OR17.11) should be Y178, not Y175.ANNEX #4: CORRECTION: MASTER FIGHTER CHART:Alunda Remora Fighters (OR9.F1) should show ten damagepoints, not nine.The Iridani Gig is in service in Y82.ANNEX #4: CORRECTION: MASTER FIGHTER CHART:Bolosco Conjuror (OR20.F1), Enchanter (OR20.F2), andSorceror (OR20.F3) fighters should be marked as having nochaff.ANNEX #4: CORRECTION: MASTER FIGHTER CHART:Branthodon Wyvern-1 and Wyvern-2 Fighters should be markedas having no chaff.ANNEX #4: CORRECTION: MASTER FIGHTER CHART:Federal Republic Doberman-1 (OR17.F1), Doberman-2(OR17.F2), and Rottweiler-1 (OR17.F3) fighters should bemarked as having no chaff.ANNEX #4: CORRECTION: MASTER FIGHTER CHART: IridaniSkiff 1 (OR14.F1), Skiff 2 (OR14.F2), Skiff F (OR14.F4), Gig(OR14.S1), and Admiral’s Gig (OR14.S2) should be marked ashaving no chaff. Skiff 3 (OR14.F3) and Skiff H (OR14.F5) shouldbe marked as having no chaff, not two chaff.ANNEX #4: CORRECTION: MASTER FIGHTER CHART: RynRMF (OR19.F1) should have a single PQ-3-FA. Ryn SAF

(OR19.F2) weapon should be listed as a TCB, not a T-Col, whichwhile the correct weapon, is not the correct abbreviation for it,should have 1+3x6 listed under speed. Ryn Raker Fighter(OR19.F1), Slasher Fighter (OR19.F2) and Render Fighter(OR19.F3) should be marked as having no chaff. The entry forthe RYN RHF fighter (OR19.F3) under special weapons shouldbe 2xTCB (4 power each).ANNEX #4: CORRECTION: MASTER FIGHTER CHART:Singer Light Hover Fighters (OR18.F1) and Heavy HoverFighters (OR18.F2) should be marked as having no chaff.ANNEX #4: CORRECTION: MASTER FIGHTER CHART:Souldra Black Shard Year in Service Date should be Y160, notY169. Souldra Black Shards (SB), Green Shards (SG), andOrange Shards (SO/MRS) reference numbers are in error, ineach case replace “R” with “J”. Souldra MRS (Orange Shard)was listed with the other Souldra shards and not with other MRSshuttles because it is very different. Souldra Red Shards, VioletShards, and Blue Shards should be listed with reference(OJ4.13). Souldra Shards (OR13.F0) and (OR13.S0) should bemarked as having no chaff. Souldra Shards all received(OR13.F0) rule numbers and were moved to the Souldra racialdescription section in the Omega Master Rulebook. They wereoriginally put in the J Section of the rules as a means of savingspace.ANNEX #4: CORRECTION: MASTER FIGHTER CHART: WorbB2 fighter (OR16.F4), the 3rd phaser listed as AP-360 should beAP-3-360°, and speed is 16, not 9. Worb Broad-2 (OR16.F4)fighters should be marked as having no chaff rather than twochaff. Worb High-1 (OR16.F1), High-2 (OR16.F2), and Broad-1(OR16.F3) should be marked as having no chaff.ANNEX #4: CORRECTION: MASTER FIGHTER CHART:Ymatrian Dirk Fighters (OR15.F1) have no chaff.ANNEX #6: CLARIFICATION: COMMANDER’S OPTIONS:Extra SRC ammo can be purchased at a cost of 0.5 BPV perround. SRC pods for Doberman-2 and other fighters can bepurchased at a cost of 1 BPV each.ANNEX #7E CORRECTION: In the (D4.3223) list, there areduplicate entries for the web breaker and shield cracker. Thehigher priority items (listed just after PPDs and TargetAccentuators) are correct; the listings on the same line as theSubspace Coagulator should be deleted. Implosion Bolts aredestroyed after heavy hypercannons and PA panels.ANNEX #7E: CLARIFICATION: Jammers come on the(D4.3222) damage priority rule between the special sensorreplacing torpedo and the focused energy beam. For purposes of(D4.3222), the sequence between implosion torpedoes on thesame ship is, from best to worst, IT-S, IT-H, IT-M, and IT-L, andthey are destroyed respectively after plasma-R, plasma-S,plasma-G, and plasma-F torpedoes. For purposes of (D4.3222),antimatter cannons fall after heavy hypercannons and disruptor-30s.ANNEX #7E: CORRECTION: IBs are destroyed on “Drone”damage points, not “Torpedo” damage points. ITs are destroyedon “Torpedo” damage points, not “drone” damage points.ANNEX #7G: CORRECTION: MASTER CARRIER CHART TheSinger CV has 15 fighters, not 13.ANNEX #8B ADDITION: Simulator Only, Improved UltrawarpMissile Rack +2.ANNEX #8B ADDITION: Simulator Only, Plasma-Whip withWhip Crack Torpedo refit +2.ANNEX #8B: CORRECTION: OPTIONAL WEAPONS COST:The BPV cost for light photons should be MINUS 0.75, i.e., -0.75.An SRC has a BPV cost of 1.ANNEX #9: CORRECTION: COST TO REPAIR The cost torepair an SRC is 4 points.

END OF FILE