RulesPal
Chat
Rulebook
StarForce Trilogy thumbnail

StarForce Trilogy

StarForce Trilogy Rulebook

Table of Contents

Table of Contents

  • StarForce
    • [1.0] INTRODUCTION
    • [2.0] GENERAL COURSE OF PLAY [BASIC GAME]
    • [3.0] GLOSSARY OF TERMS FOR THE BASIC GAME
    • [4.0] GAME EQUIPMENT
      • [4.1] THE GAME MAP
      • [4.2] THE PLAYING PIECES
      • [4.21] SUMMARY OF UNITS AND MARKERS USED IN THE BASIC GAME AND THE ADVANCED GAME
      • [4.22] SUMMARY OF ADDITIONAL MARKERS USED IN THE ADVANCED GAME ONLY
      • [4.3] GAME CHARTS AND TABLES AND THE RULES FOLDER
      • [4.4] THE SIMULTANEOUS MOVEMENT PLOTTING PAD
      • [4.5] GAME EQUIPMENT INVENTORY
      • [4.6] GAME SCALE
    • [5.0] SEQUENCE OF PLAY [BASIC]
      • [5.1] THE GAME TURN
      • [5.2] GAME-TURN OUTLINE
    • [6.0] HOW TO PLOT SHIFTING
      • [6.1] SHIFT PLOT CODE
      • [6.2] DESTINATIONS
      • [6.3] OVERSHIFT RANGE CODING
      • [6.4] SHIFT PLOT EXAMPLE
    • [7.0] STELLAR SHIFTING [MOVEMENT]
      • [7.1] HOW TO SHIFT STARFORCES
      • [7.2] SHIFT RANGES
      • [7.3] RANGE EFFECTS WHEN SHIFTING INTO LITEZULUS DEFENDED BY ENEMY STARGATES
      • [7.4] SEMI-HIDDEN UNIT DISPLAY
      • [7.5] MAXIMUM SHIFT TABLE
      • [7.6] TRUE [LITE] DISTANCES
      • [7.61] TRUE DISTANCE TABLE
      • [7.62] How to Use the True Distance Table
      • [7.63] Rules of Thumb
    • [8.0] BASIC GAME COMBAT
      • [8.1] WHICH UNITS MAY ENGAGE IN COMBAT
      • [8.2] FIRST COMBAT SEGMENT
      • [8.3] COMBAT STRENGTH CALCULATION
      • [8.4] COMBAT SEQUENCE
      • [8.5] COMBAT DIFFERENTIAL CALCULATION AND PLOTTING FOR THE COMBAT SEGMENT
      • [8.6] COMBAT BREAK-OFF
    • [9.0] STRATEGIC COMBAT RESULTS [Basic Game only]
      • [9.1] STRATEGIC COMBAT RESULTS TABLE
      • [9.2] HOW TO USE THE STRATEGIC COMBAT RESULTS TABLE
      • [9.3] APPLICATION OF RESULTS
      • [9.31] StarGate Preservation
      • [9.32] Examples of Combat Resolution
    • [10.0] ADVANCED GAME DESCRIPTION
      • [10.1] ADVANCED GAME GLOSSARY ADDITIONS
    • [11.0] ADVANCED GAME SEQUENCE OF PLAY
      • [11.1] TACTICAL SEQUENCE OUTLINE
      • [11.12] THE TAC-TURN
    • [12.0] ADVANCED GAME TACTICAL PLOTTING
      • [12.1] UNIT TELEVALUES
      • [12.2] PLOTTING FOR THE TAC-TURN
      • [12.3] ADVANCED GAME TACTICAL PLOT CODES AND ACTIONS
      • [12.4] TAC PLOT EXAMPLE
      • [12.5] PLOT MODIFICATION
    • [13.0] TAC-SHIFTING, MODE CHANGING, AND BREAK-OFFS
      • [13.1] TAC-SHIFTING [Moving StarForces on the Tactical Display]
      • [13.2] MODE CHANGING
      • [13.3] BREAK-OFF
    • [14.0] ADVANCED GAME COMBAT [Cast and Anti-Cast]
      • [14.1] WHEN CASTS MAY BE MADE AND WHAT UNITS MAKE THEM
      • [14.2] THE STRENGTH AND RANGE OF CASTS
      • [14.3] THE NUMBER OF CASTS A UNIT MAY MAKE, THE TARGETS AFFECTED AND THE EFFECTS OF MULTIPLE CASTS
      • [14.4] DETERMINING IF AN ENEMY UNIT IS IN THE VOLUME OF THE CAST
      • [14.5] THE ANTI-CAST
      • [14.6] CAST RESOLUTION
      • [14.7] NEUTRALIZATION
    • [15.0] RANDOMIZATION AND THE STELLAR RANDOMIZER
      • [15.1] EFFECTS OF RANDOMIZATION
      • [15.2] USING AND READING THE STELLAR RANDOMIZER
      • [15.3] PLACING THE RANDOMIZED UNIT ON THE STELLAR DISPLAY
    • [16.0] INTRODUCTION TO THE SCENARIOS
      • [16.1] THE RACES AND THEIR STAR SYSTEMS
      • [16.2] HOW THE SCENARIOS ARE ORGANIZED
      • [16.3] SETTING UP THE GAME EQUIPMENT TO PLAY THE SCENARIOS
    • [17.0] SCENARIO 1, THE ALPHA CENTAURI CAMPAIGN
    • [18.0] SCENARIO 2, THE EPSILON ERIDANI CAMPAIGN, 2405 A.D.
    • [19.0] SCENARIO 3, THE RISE OF THE HUMAN LEAGUE, 2415 A.D.
    • [20.0] SCENARIO 4, 2430 A.D. PHH - HL SHOWDOWN
    • [21.0] SCENARIO 5, 2451 A.D. L'CHAL-DAH CONTACT
    • [22.0] SCENARIO 6, 2462 A.D. SECOND PHH - HL WAR
    • [23.0] SCENARIO 7, 2465 A.D. REVOLT OF EPSILON INDI
    • [24.0] SCENARIO 8, 2476 A.D. THE WAR WITH THE RAME
    • [25.0] SCENARIO 9, 2480 A.D. L'CHAL-DAH EXPANSION
    • [26.0] SCENARIO 10, 2482 A.D. WAR OF THE DEFENSE LEAGUE
    • [27.0] SCENARIO 11, 2487 A.D. THE WAR FOR IDENTITY [Three-Player Game]
    • [28.0] SCENARIO 12, 2505 A.D. THE WAR FOR THE LEAGUE [Three-Player Game]
    • [29.0] SCENARIO 13, 2775 A.D. THE FIRST XENOPHOBE INCURSION
    • [30.0] SCENARIO 14, 2785 A.D. THE SECOND XENOPHOBE INCURSION
    • [31.0] SPECIAL RULES FOR THE XENOPHOBE SCENARIOS
      • [31.1] DEPLOYMENT OF XENOPHOBE STARGATES
      • [31.2] UNKNOWN SPACE AND ITS EFFECTS UPON SHIFTING
      • [31.3] MODIFIED SEQUENCE OF PLAY AND HIDDEN MOVEMENT
      • [31.4] FIRST GAME TURN RULES [FIRST INCURSION ONLY]
      • [31.5] NOVA INDUCEMENT AND COMBAT RESOLUTION
      • [31.6] FIRST GAME-TURN RULES AND STANDARD RESULTS OF FIRST INCURSION [SECOND INCURSION ONLY]
      • A NOTE ON THE OPTIONAL RULES [Sections 32.0 through 37.0]
    • [32.0] RESERVE STARFORCES
      • [32.1] HOW RESERVE STARFORCES ARE CALLED INTO CONTESTED LITEZULUS
      • [32.2] LIMITATIONS ON RESERVE STARFORCES
      • [32.3] RESERVE STARFORCES AND STARGATES
      • [32.4] SPOILING RESERVES
    • [33.0] FAKERFORCES
      • [33.1] CAPABILITIES AND LIMITATIONS OF FAKERFORCES
      • [33.2] PLOTTING FAKERFORCES
      • [33.3] DEPLOYMENT
    • [34.0] GATELINK
      • [34.1] GATELINK CAPACITY
      • [34.2] ORIGINS AND DESTINATIONS
      • [34.3] PLOTTING A GATELINK
    • [35.0] SITUATIONAL CONTINUITY
      • [35.1] DURATION OF COMBAT SITUATIONS PER GAME-TURN
      • [35.2] FORCES INVOLVED IN THE FIRST AND SECOND CYCLES OF PROLONGED COMBAT SITUATIONS
      • [35.3] WHEN AND HOW NEW FORCES ARRIVE IN A PROLONGED SITUATION
      • [35.4] HOW UNITS MAY LEAVE A PROLONGED SITUATION
      • [35.5] CONDITIONS FOR PERMANENT NEUTRALIZATION OF STARGATES
      • [35.6] STELLAR SHIFTING AND STARGATES IN PROLONGED SITUATIONS
    • [36.0] BATTLE MODE CREW FATIGUE
      • [36.1] EFFECTS OF TWO CONSECUTIVE GAME-TURNS OF BEING IN BATTLE MODE
      • [36.2] EFFECTS OF THREE CONSECUTIVE GAME-TURNS OF BEING IN BATTLE MODE
      • [36.3] RECOVERY FROM BATTLE MODE FATIGUE
    • [37.0] SEQUENTIAL PLAY
      • [37.1] SEQUENTIAL STELLAR SHIFTING
      • [37.2] SEQUENTIAL BASIC GAME COMBAT
      • [37.3] SEQUENTIAL ADVANCE GAME TAC-SHIFTING
      • [37.4] SEQUENTIAL ADVANCED GAME COMBAT
      • [37.5] CAUTIONARY NOTE
    • [38.0] THE RESCUE MISSION (A Solitaire Game)
      • [38.1] DETERMINING THE LOCATION OF THE ENDANGERED SYSTEM
      • [38.2] INITIAL STARFORCE DEPLOYMENT
      • [38.3] SIMULATING THE UNCERTAINTY OF NOVA
      • [38.4] HOW POPULATION POINTS ARE RESCUED
      • [38.5] VICTORY LEVELS
    • [39.0] VERBAL PLOTTING
    • [100.0] STARFORCE SCENARIO 100: THE OUTLEAP, 2400-2500 A.D.
      • [107] ORGANIZATION
      • [108] STELLAR DEBARKATION
      • [109] WAR, TRUCE & ALLIANCE
      • [110] CONSOLIDATION
      • [111] CONTROL
      • [112] SCENARIO SET-UP
      • [113] VICTORY CONDITIONS
      • [114] POLITICAL DOMINATION OPTIONAL RULE
    • [41.0] SCENARIO 15, 2946 A.D., THE THIRD XENOPHOBE INCURSION
    • [42.0] SCENARIO 16, 2981 A.D., THE FAKERWAR
    • [43.0] SCENARIO 17, 3010 A.D., RXPEXY DISPUTE
    • [44.0] SCENARIO 18, 3175 A.D., US REVOLUTION
    • [45.0] SCENARIO 19, 3447 A.D., THE WAR OF OBSOLESCENCE AND TREACHERY
    • [46.0] SCENARIO 20, 2947 A.D., OPERATION CARTHAGE [Solitaire Game]
    • STARFORCE ERRATA
  • Outreach
    • [1.0] INTRODUCTION
    • [2.0] GLOSSARY OF BASIC TERMS
    • [3.0] GAME EQUIPMENT
    • [3.2] PLAYING PIECES
      • [3.21] Unit Counter Manifest
    • [3.3] SET-UP
    • [3.4] INVENTORY OF GAME PARTS
  • [4.0] SEQUENCE OF PLAY
    • [4.1] THE GAME-TURN
    • [4.2] GAME-TURN OUTLINE
  • [5.0] STELLAR SHIFTING
    • [5.1] HOW TO CONDUCT STELLAR SHIFTS
    • [5.2] THE CONCEPT OF CONTINUAL SHIFTING
    • [5.3] RESERVE SHIFTS
    • [5.4] SCATTER
    • [5.5] EFFECTS AND IMPLEMENTATION OF SCATTER
    • [5.6] THE SCATTER TABLE
    • [5.7] EFFECTS OF SPECIAL GALACTIC PHENOMENA ON SHIFTING
  • [6.0] EXPLORATION
    • [6.1] THE MECHANICS OF EXPLORATION
  • [7.0] CONTACT
    • [7.1] HOW TO CALCULATE THE CONTACT INDEX
    • [7.2] USE OF THE CONTACT MARKER
    • [7.3] EFFECTS OF BEING IN CONTACT
    • [7.4] CONTACT TABLE
  • [8.0] INTERACTION
    • [8.1] HOW TO USE THE INTERACTION DISPLAYS
    • [8.2] INTERACTION OPTIONS
    • [8.3] INTERACTION MATRIX
    • [8.4] RANDOM INTERACTION OPTION TABLE
  • [9.0] CONFLICT
    • [9.1] THE MECHANICS OF CONFLICT
    • [9.2] CONFLICT TABLE
  • [10.0] REDUCTION
    • [10.1] THE PROCESS OF REDUCTION
    • [10.2] THE MECHANICS OF REDUCTION
    • [10.3] REDUCTION TABLE
  • [11.0] FATE
    • [11.1] HOW TO USE THE FATE TABLE
    • [11.2] EXPLANATION OF FATE TABLE RESULTS
    • [11.3] DISSOLUTION
    • [11.4] THE FATE TABLE
  • [12.0] CIVILIZATION LEVEL
    • [12.1] THE EFFECTS OF CIVILIZATION LEVEL
  • [13.0] AUTONOMOUS UNITS
    • [13.1] PLACEMENT OF AUTONOMOUS COUNTERS
    • [13.2] ACTIVITY OF AUTONOMOUS FORCES
    • [13.3] HOSTILE AUTONOMOUS FORCES
  • [14.0] RESOURCE ALLOCATION
    • [14.1] CREATION, AUGMENTATION, AND DE-NEUTRALIZATION OF STAR-GATES
    • [14.2] CONSTRUCTION AND MAINTENANCE OF STARFLEETS
  • [15.0] BEACON STARS
    • [15.1] HOW TO DISCOVER AND PLACE NEW BEACON STARS
  • [16.0] INTERSTELLAR DUST
  • [17.0] THE GALACTIC NUCLEUS AND WISDOM CHITS
    • [17.1] USAGE OF GALACTIC NUCLEUS HEXES
    • [17.2] WISDOM CHITS
  • [18.0] SCENARIOS
    • [18.1] CONFLICT OVER SCORPII [Two-Player scenario]
    • [18.2] ROUTE TO THE NUCLEUS [Three-Player Scenario]
    • [18.24] Special Rules
    • [18.3] PSL OUTLEAP [Solitaire Scenario]
    • [18.4] STRUGGLE FOR CYGNUS-CARINA [Four-Player Scenario]
    • [18.5] LUCK OF THE DRAW SCENARIO
    • COUNTER SHEET ERRATA
  • StarSoldier
    • [1.0] INTRODUCTION
    • [2.0] GENERAL COURSE OF PLAY
    • [3.0] GAME EQUIPMENT
      • [3.1] THE GAME MAP
      • [3.2] PLAYING PIECES
      • [3.3] GAME CHARTS & TABLES
      • [3.4] INVENTORY OF GAME PARTS
  • [4.0] BASIC GAME SEQUENCE OF PLAY
    • [4.1] SEQUENCE OUTLINE (Basic Game)
  • [5.0] "SIMULTANEOUS" MOVEMENT
  • [6.0] DISTINCTIONS BETWEEN SPECIES
  • [7.0] STARSOLDIER TASK SUMMARY CHART
    • [7.1] TASK CHART
  • [8.0] MOVEMENT
  • [9.0] FIRE COMBAT
    • [9.2] OPPORTUNITY FIRE
    • [9.3] MULTIPLE FIRE COMBAT
    • [9.4] RESTRICTED FIRE
    • [9.5] HEAVY WEAPON SOLDIERS
    • [9.6] HOW TO RESOLVE FIRE COMBAT
    • [9.61] How to Compute the Attack Strength
    • [9.62] How to Compute the Defense Strength
    • [9.63] How to Calculate the Attack Differential
    • [9.7] BASIC GAME FIRE COMBAT RESULTS TABLE
  • [10.0] LAUNCHED WEAPONS
    • [10.3] DETONATION AND ITS EFFECTS
  • [11.0] TASK POINTS AND THE TASK POINT LEVEL TRACK
  • [12.0] TERRAIN
  • [13.0] PLAYING THE BASIC GAME
  • [14.0] STANDARD GAME SEQUENCE OF PLAY
  • [15.0] DIVIDING THE GAME-TURN INTO STAGES
  • [16.0] COMMAND COMMUNICATIONS
  • [17.0] PRESERVATION LEVEL
  • [18.0] OPACITY GRENADES
  • [19.0] HOMING MISSILES
  • STARSOLDIER CHARTS & TABLES
    • [6.4] SPECIES CAPACITY CHART
    • [9.8] FIRE COMBAT RESULTS TABLE (BASIC GAME)
    • [10.4] SCATTER TABLE
    • [10.5] LAUNCHED WEAPONS COMBAT RESULTS TABLE (BASIC GAME)
    • [10.24] FREE FLIGHT MISSILE INTERCEPTION TABLE
    • [12.6] TERRAIN CHART
    • [21.5] SUPPORT PLATFORM DAMAGE TABLE
    • [26.1] STANDARD GAME COMBAT RESULTS CHART
    • [26.2] LAUNCHED WEAPONS COMBAT RESULTS TABLE
    • [41.3] UNIT ORGANIZATION COST CHART
    • [41.6] ORBITAL GROUND SUPPORT AVAILABILITY CHART
  • [20.0] ORBITAL BOMBARDMENT
    • [20.1] ORBITAL BOMBARDMENT
    • [20.2] ORBITAL LASER BARRAGE
    • [20.3] ORBITAL OPACITY BOMBS
  • [21.0] SUPPORT PLATFORMS
    • [21.1] MOVEMENT OF SUPPORT PLATFORMS
    • [21.2] OFFENSIVE ABILITIES OF SUPPORT PLATFORMS
    • [21.3] SUPPORT PLATFORMS ON DEFENSE
    • [21.4] EFFECTS ON PRESERVATION
    • [21.5] SUPPORT PLATFORM DAMAGE TABLE
  • [22.0] ANDROIDS
    • [22.1] RESTRICTIONS ON ANDROIDS
  • [23.0] THE RAME
    • [23.1] RAME KILLER SWARMS
    • [23.2] EFFICIENCY RATING
    • [23.3] COMMAND COMMUNICATIONS
  • [24.0] XENOPHOBES
    • [24.1] RESTRICTIONS ON XENOPHOBES
    • [24.2] EFFECTS OF NEUTRON BOMBS
  • [25.0] UNIT ORGANIZATIONS
    • [25.1] UNIT ORGANIZATION CHART
    • [25.2] EXPLANATION OF UNIT ORGANIZATION
  • [26.0] COMBAT RESULTS TABLE
  • [27.0] GENERAL GAME SITUATIONS
    • [27.1] PATROL SITUATION
    • [27.2] RECON SITUATION
    • [27.3] ASSAULT SITUATION
  • [28.0] THE EPSILON ERIDANI CAMPAIGN/SKIRMISHES ON EPSILON INDI, 2405 AD
  • [29.0] RISE OF THE HUMAN LEAGUE/BATTLES ON EPSILON INDI, 2415 AD
  • [30.0] PHH-HL SHOWDOWN/ATTACK ON TAU CETI, 2430 AD
  • [31.0] L'CHAL DAH CONTACT, 2451 AD
  • [32.0] SECOND PHH-HL WAR, 2462 AD
  • [33.0] REVOLT OF EPSILON-INDI, 2465 AD
  • [34.0] WAR WITH THE RAME, 2476 AD
  • [35.0] L'CHAL DAH EXPANSION, 2480 AD
  • [36.0] WAR OF THE DEFENSE LEAGUE, 2482 AD
  • [37.0] WAR FOR IDENTITY, 2487 AD
  • [38.0] DEFEAT OF THE XENOPHOBES, 2785 AD
  • [39.0] PROTECTING SETTLERS FROM THE LOCAL FAUNA
  • [40.0] OTHERWORLD ENVIRONMENTS
  • [41.0] THE LINK GAME
    • [41.1] TRANSPORT OF STRIKE COMMANDS
    • [41.2] ASSAULT PROCEDURE
    • [41.3] UNIT ORGANIZATION COST CHART
    • [41.4] CIVILIANS
    • [41.5] ORBITAL GROUND SUPPORT
    • [41.6] ORBITAL GROUND SUPPORT CHART
    • [41.7] ORDER OF BATTLE CHART
    • [41.8] ADDENDA TO THE LINK GAME
  • SEQUENCE OF PLAY SUMMARIES
  • SUMMARY OF FORMULAS USED IN COMBAT PROCEDURES
    • [25.1] UNIT ORGANIZATION CHART

StarForce

[1.0] INTRODUCTION

StarForce is a simulation of interstellar warfare as it might be fought in the 25th through 27th centuries. The game is not meant to be predictive, i.e., its designer does not purport that the "future" shown in its scenarios and rules will be the actual future. The game should not be viewed as an extrapolation of present day trends into the far future. Rather, the game is a set of imaginary conditions and technology which make possible far-flung interstellar societies (and conflict in those societies).

The main technological advance which makes the whole game "future" possible is a means of "shifting". Shifting relies upon a combination of human telesthetic and telekinetic abilities with sophisticated, intelligent machines, to temporarily join two widely separated points in space in order that a ship may shift instantly from one point to the other. In this manner, all relativistic time-space problems are neatly sidestepped and communications between star systems light years apart are made feasible.

There are two versions of the game, both of which may be modified (and made more complicated) by the use of optional rules. The basic version of the game is known as the Basic Strategic Game and it uses rules sections 1.0 to 9.0. In this version all play takes place on the large star map known as the Stellar Display. The Advanced Game uses most of the same rules sections (omitting 8.0 and 9.0) plus sections 10.0 through 15.0. The Advanced Game uses both the Stellar Display and the smaller Tactical Display. Both games use a common set of counters and markers.

Both games also share the set of game situations (scenarios) given in sections 16.0 through 31.0. It is strongly recommended that Players acclimate themselves to the strange terminology and unusual game system by playing a few "learning" games using the basic rules. The one feature that experienced gamers will have the most difficulty getting used to is the three-dimensional quality of the game and the demands that such an environment makes upon the Players.

[2.0] GENERAL COURSE OF PLAY [BASIC GAME]

Each Player assumes the role of the overall operational commander of the SpaceForces of a race or political subdivision of that race. At the beginning of each Game-Turn he writes the movement orders that his StarForce units will execute, shifting them across the light-years to gain control of star systems and to defeat Enemy StarForces. Combat situations occur when opposing forces occupy the same position in the same Game-Turn. Control of these positions is determined by the use of a probability table that yields an outcome when forces of given strengths engage each other in combat. In these combat situations, the Players will also write orders for their StarForce units, allocating varying amounts of their total strength to defensive and offensive roles. Each specific game (scenario) has a set of objectives (victory conditions) which the Players must attempt to achieve. Usually these victory conditions require the control of specific star systems.

[3.0] GLOSSARY OF TERMS FOR THE BASIC GAME

Lite - an abbreviated form of the phrase "light year" (the distance light travels in a year - 9.458 trillion kilometers). Each hexagon on the Stellar Display measures one Lite across.

LiteZulu - an exact three dimensional position on the Stellar Display. All positions on the Stellar Display are rendered in terms of their four-digit hex number and their Zulu coordinate (i.e., how many Lites above or below the two dimensional plane that location is). There are 37,639 LiteZulus on the Stellar Display. For example, Sol is located in LiteZulu 2020/0; Alpha Centauri is in LiteZulu 1821/-4.

Randomizer, Decimal - four sets of 0 to 9 chits which are used to produce random numbers for the various tables in the game. Place these chits in a wide-mouthed opaque container (e.g., a coffee mug) from which they can be easily drawn.

Star System - any one of the variously colored discs on the Stellar Display. Each star system consists of a star and its associated planets (the planets are not represented due to the large scale). Star systems are grouped into three classes as distinguished by the size of their symbol: 1) the three "home" systems of the three races (e.g., Sol is the home system of the Human Race); 2) the secondary systems (those having colonizable planets, but no native, sentient life forms); 3) the tertiary systems (those stars which have planets that require "terraforming" before colonization). Players should note that the stars are named according to various human, present-day astronomical cataloging systems. In some cases the full catalog name has been shortened to the "declination" of the star. Even though the game takes place 500 years in the future, the relative position of the stars on the Display would not have changed within the scale of the game, so that the map is fairly accurate representation of the present-day stellar neighborhood with minor distortions due to rounding off and the hexagonal grid. Players interested in astronomy should also note that although some of the star systems on the map are actually binaries or trinaries, they have not been symbolized as such.

StarForce - a fleet of four interstellar spaceships represented by a single counter; the operational, mobile unit in the game. StarForces shift about on the Stellar Display and engage each other in combat.

Shift - the instantaneous movement of StarForce units from point to point in space. All movement in the game is in terms of shifting. StarForces have a basic Shift Range of five Lites (which may be extended with the aid of other StarForces, StarGates, or by a risky procedure known as Overshifting). Note that, unlike almost all games, movement in StarForce is not traced step-by-step through the intervening space between point of origin and destination; rather it is a transfer from point of origin to destination without ever having traveled through the space between.

StarGate - a space station in orbit around a star, which is not itself capable of shifting but which is capable of augmenting the shift abilities of Friendly StarForces. It may also participate in combat somewhat in the manner of a fortress or strongpoint.

Stellar Display - the large, strategic map of all the star systems within twenty Lites of Sol (approximately). This local neighborhood of stars is fixed upon a plane extended out from the equator of the planet Earth. Star systems are located "horizontally" on this plane by being placed in the appropriate numbered hex. Their "vertical" distance from it is given in terms of their Zulu coordinate, i.e., how many Lites above or below the plane their position lies. If the map were provided in actual three-dimensional substance, it would appear as a "sphere" composed of 37,639 hexagonal solids. Since such a map is impractical, the system of plus and minus numbers combined with position numbers on the hexagonal grid are used to produce this three-dimensionality on a two-dimensional map surface. Players will note that stars are grouped by color coding to indicate whether they are below, in, or above the equatorial plane of the map. (see Zulu Limit)

True [Lite] Distance - this is the true three-dimensional, straight-line distance between any two points on the Display. Players should always bear uppermost in their minds the three-dimensionality of the game; points that may seem close together on the map two-dimensionally may in actual three-dimensional terms be very far apart. See 7.6 for further explanation.

Zulu Coordinate (or number) - a number that expresses the "vertical" distance (in Lites) of a given point from the two dimensional plane of the map. Zulu numbers are always expressed as a positive (+) or negative (-) number, indicating whether the point is above or below the plane. For example, Sol is at Zero Zulu, i.e., right in the plane of the map. LiteZulu 2020/+21 is 21 Lites away from Sol, even though it appears in the same two-dimensional hex. Examine the map. Find hex 2039 (right under the name of the game). LiteZulu 2039/0 is closer to Sol than LiteZulu 2020/+21, even though 2020/+21 is in the same numbered hex as Sol.

Zulu Limit - the highest plus or minus number allowable within that area of the map. Note that the map is divided into concentric rings centered around Sol. Each of these rings has a Zulu Limit number printed in it.

NOTE TO ALL PLAYERS: A thorough reading of the glossary and a careful examination of the charts and tables associated with the game will greatly facilitate your understanding of the rules.

[4.0] GAME EQUIPMENT

[4.1] THE GAME MAP

The Stellar Display and the Tactical Display - The 22" x 34" mapsheet has two playing fields printed on it. The larger one is the Stellar Display, showing 74 star systems in a three-dimensional "sphere" of space measuring roughly 40 light-years in diameter. The Stellar Display is used in both the Basic and Advanced games. The Tactical Display is used only in the Advanced Game. It is a representation of a small segment of any given position on the Stellar Display. The Tactical display is .01 light-years in diameter. See the Basic and Advanced Glossaries for a fuller description of both Displays.

[4.2] THE PLAYING PIECES

On the die-cut counter sheet there are five differently colored sets of combat unit counters plus a number of markers and chits. Players should punch these pieces out of the sheet (pressing on the faces of the counters) and sort them by color and type into the compartmented plastic tray.

[4.21] SUMMARY OF UNITS AND MARKERS USED IN THE BASIC GAME AND THE ADVANCED GAME

StarForce unit - [counter illustration]

StarGate unit - [counter illustration]. Note that the code letters and numbers on StarForce and StarGate counters are for identification purposes only.

Decimal Randomizer Chit - [chit illustration]

[4.22] SUMMARY OF ADDITIONAL MARKERS USED IN THE ADVANCED GAME ONLY

Stellar Randomizer Chits - [chit illustration: "26" over "-6"]. The first or second half of hex coordinate is the upper figure; the Zulu coordinate is the lower figure.

Neutralization Markers - [marker illustration: "N"]

Tactical Situation Markers - [marker illustration: "TAC SIT"]

Star Marker - [marker illustration]

[4.3] GAME CHARTS AND TABLES AND THE RULES FOLDER

Almost all the charts and tables used in both game versions will be found, in duplicate, on the game map. These charts and tables will be fully explained in the appropriate rules sections. Players will note that the rules are organized in their order of use in the Game-Turn. Players are advised to peruse the outline at the beginning of the rules if they have not already done so. Players should familiarize themselves with all the components of the game before reading any further. Do not expect to understand the various tables at first glance.

[4.4] THE SIMULTANEOUS MOVEMENT PLOTTING PAD

StarForce is played in simultaneous Game-Turns. Players write out in advance the actions their units will perform in the coming Game-Turn. The SiMove Plotting Charts are merely a handy format for organizing this order writing. When the pad is used up, Players can use ordinary lined paper or order new pads from SPI.

[4.5] GAME EQUIPMENT INVENTORY

Each complete game of StarForce should contain the following items:

  • One game map (22" x 34")
  • One set die-cut counters (200 pieces)
  • One rules folder
  • One Simultaneous Movement Plotting Pad
  • One box/lid/cover sheet assembly

(Note that unlike almost all other SPI games there is no die in StarForce. The various tables are based on the decimal system and use chits to generate random numbers, thus obviating the need for a die.)

If any of the inventoried items are missing or damaged beyond utility, Players should contact SPI within fifteen days of their purchase. Write: StarForce, Customer Service, Simulations Publications, Inc., 44 East 23rd Street, New York, N.Y. 10010.

[4.6] GAME SCALE

Each LiteZulu on the Stellar Display is one Lite across by one Lite deep. The Stellar Display is 39 Lites across by 43 Lites "deep". The Stellar Game Turn represents twelve hours of real time.

The MiniLiteZulus on the Tactical Display are each one MiniLite across by one MiniLite deep (one MiniLite=one-third of a light-day). The Tactical Display is one hundreth of a Lite across by one hundreth of a Lite deep. Each Tac-Turn represents thirty minutes of real time.

[5.0] SEQUENCE OF PLAY [BASIC]

[5.1] THE GAME TURN

StarForce: Alpha Centauri is played in Game-Turns. During each Game-Turn each Player plots his movement secretly and then simultaneously executes it. After Movement Execution the Players may or may not go into combat depending on whether they simultaneously occupy one or more LiteZulus. There is not necessarily a limit to the number of Game-Turns in each scenario (a scenario being one particular situation, set of initial forces, and set of Victory Conditions). The game usually will continue until one Player wins a victory. All action must take place in the sequence as outlined below or it is a violation of the rules and not permitted.

[5.2] GAME-TURN OUTLINE

A. Stellar Shift Plot Phase: Each Player writes secretly the new LiteZulu position that each of his StarForces will shift to in the Shift Execution Phase. (see 6.0 for How to Plot Shifting).

B. Shift Execution Phase

  1. Safe-Shift Execution Segment: Move all StarForces that are making shifts within their safe maximum (see 7.2).

  2. Overshift Execution Segment: For StarForces which are conducting shifts greater than their safe maximum, consult the Overshift range section on the Maximum Shift Table (7.5) and draw a chit once for each StarForce that is Overshifting, taking the action indicated by the Table.

  3. Zulu Coordinate Readout Segment: For each numbered hex in which two or more Players have units (StarForces or StarGates) they inform one another of their respective Zulu number of these forces, thus determining whether or not they occupy the same LiteZulu. Players also reveal the Zulu number of any StarForce which is in a LiteZulu adjacent to an Enemy StarGate. Note that there are twenty LiteZulus adjacent to each StarGate, that is, the one in the LiteZulu directly "above", the one in the LiteZulu directly "below" and the three (plus one, zero and minus one) Zulu levels respective to the StarGate Zulu Coordinate in the six adjacent hexes (see also 7.41).

    At this point, if opposing Players do not have opposing units in the same LiteZulu, Players proceed to the following Game-Turn. If, however, they do have units in the same LiteZulu opposing one another, they proceed to the Combat Execution Phase.

C. Combat Execution Phase: If opposing forces are in the same LiteZulu, a Strategic Combat Sequence is initiated, i.e., a series of Strategic Combat Segments are played until the situation is resolved, namely, until only one Player's forces remain in the given LiteZulu. Note that more than one Combat situation may arise in a given Game-Turn. Players pick the largest combat situation to be resolved. They then continue until it is resolved and proceed to the next largest combat situation. Optionally, Players may decide to resolve one Segment at a time for each situation until all are resolved (this is a slightly more complicated technique, but is more realistic).

  1. Initial Combat Segment: Each Player totals up the Strength Points of his forces in that LiteZulu. Note that entering StarForces and certain "defending" StarForces may have different Strength Point values (see 8.2). The first Combat Segment is then executed by comparing the attacking and defending Strength Points allocated by each Player, taking the difference and referring to the Strategic Combat Results Table, picking a chit from the Decimal Randomizer and receiving a result which is immediately applied (see 8.0). If there are still opposing forces in the same LiteZulu, proceed to the second Combat Segment.
  2. Second [and Subsequent] Combat Segment: Each Player recomputes his Strength Points based on the number of StarForces remaining and the change in Strength for the second Combat Segment (see 8.2) plus any StarGates. Play continues through a series of Combat Segments until one Player or another has been removed from the contested LiteZulu.

D. Stellar Neutralization Recovery Phase

(This Phase is only applicable to the Advanced Game and a Modified Basic Game).

All units which were neutralized in the previous Game-Turn are returned to normal use and strength (remove Neutralization Marker).

[6.0] HOW TO PLOT SHIFTING

GENERAL RULE: During the Shift Plot Phase of each Game-Turn, the shifting of the various StarForces is secretly written out in advance. Players, when plotting, should take two columns of the Simultaneous Movement Pad in order to plot a single Game-Turn. The first column should be used to plot the activity the StarForce is engaged in in that Game-Turn, and the second column should be used to plot the planned destination LiteZulu of the StarForce. Individual StarForces are identified by letters which correspond to lines on the SiMove pad.

[6.1] SHIFT PLOT CODE

S - Normal shift by StarForce without assistance or enhancement;

ES - Enhanced shift; this represents a StarForce moving to a LiteZulu which has been "enhanced" by another Friendly StarForce or StarGate.

GS - Gate Shift; extended shift made by using an assisting Friendly StarGate; this represents a shift which is assisted by a Friendly StarGate which is in the beginning LiteZulu.

EGS - Enhanced Gate Shift; extended shift by StarGate to a LiteZulu enhanced by a Friendly StarForce; this represents a StarGate assisting the StarForce in moving and another Friendly StarForce enhancing the destination LiteZulu. Note that this is a one-way process, you may not shift from an enhanced LiteZulu to an assisting StarGate in the same manner.

GGS - Gate-to-Gate Shift; extended shift from assisting StarGate to another assisting StarGate.

E - Enhancing; this represents that a StarForce is engaged in nothing other than enhancing the destination of another Friendly StarForce.

Note that an enhancing StarForce may only be used by one given StarForce once per Shift Plot Phase.

[6.2] DESTINATIONS

In the second box for every shifting StarForce is written the LiteZulu which is planned to be the ending LiteZulu for that shifting StarForce. If a given StarForce is engaged in enhancing for another StarForce then write an "E" in the second box. A planned-ending-LiteZulu should be written in pencil if an Overshift is involved. If, due to the Overshift Results Table, a given StarForce does not complete its intended shift the actual ending position (LiteZulu) should be written in that box.

[6.3] OVERSHIFT RANGE CODING

Whenever an Overshift is plotted for a StarForce, write the key letter of the appropriate Overshift range column in a circle after the basic shift code. For example, if a StarForce were making a normal shift to a destination six Lites distant, the letter "A" would be written in a circle after the normal "S" code.

[6.4] SHIFT PLOT EXAMPLE

UnitStarting LiteZuluMovement Plot (1st column)Destination Plot (2nd column)
A2020/0S2422/-3
B2020/0S2422/-3
C2036/+1GGS2020/0
D2036/+1GGS2020/0
E2422/-9E2422/-9
F1821/-4ES2422/-9

[7.0] STELLAR SHIFTING [MOVEMENT]

GENERAL RULE: Movement is not movement through space, as is normally thought of, but rather movement from one point in space directly to another point in space without having traversed the intervening distance. This movement, or transfer, is referred to as a "shift" when performed on the Stellar Display. Players must always keep in mind that they are shifting in a three-dimensional environment, although the Stellar Display is a two-dimensional surface depicting a plane coinciding with the equator of the planet Earth. In conjunction with the Zulu coordinate system, it represents a three-dimensional space extending above and below that plane.

In Stellar shifting, there is no "Movement Allowance" such as in many other SPI games. Rather, StarForces have Shift Ranges which cannot be exceeded except in certain circumstances. The basic Shift Range of a StarForce is five Lites. This may be increased through the assistance of a Friendly StarGate or the "enhancing" of a given shift by other Friendly StarForces.

SHIFT PROCEDURE: A Simultaneous Movement Pad is included with each copy of StarForce. Each line across represents the activity of a single StarForce. During each Stellar Shift Plotting Phase, Players, using one line across for each StarForce, write the Plot Code (i.e., the type shifting to be engaged in) and the expected destination LiteZulu in the second box.

During the Stellar Plot Execution Phase, Players place their StarForces in their newly plotted positions (if they successfully shift). In certain cases, Players may attempt to shift a distance greater than allowed. This is called Overshift and entails some risk-taking by the shifting StarForces.

[7.1] HOW TO SHIFT STARFORCES

[7.11] During the Shift Plot Phase all StarForces may be plotted to shift (with the exception of StarForces which are being used to enhance a given LiteZulu).

[7.12] The distance of a shift is calculated in terms of Lites. In order to calculate the actual number of Lites shifted, the Players should refer to the True (Lite) Distance Table (see 7.6).

[7.13] Any number of Enemy or Friendly StarForces and other units may exist in the same LiteZulu without interfering with one another for movement purposes. StarForces which begin the Shift Plot Phase in the same LiteZulu may shift out to different LiteZulus or to the same LiteZulu without any interference. StarForces which do not begin in the same LiteZulu may shift into the same LiteZulu, again without interference.

[7.14] A combat situation is never begun until both types of shifts, that is safe shifts and Overshifts, are completed. Only then does a combat situation begin to be executed.

[7.2] SHIFT RANGES

[7.21] Normal, unassisted safe shift range for a given StarForce is five Lites. This number is constant for all StarForces and is, therefore, not printed on the playing pieces.

[7.22] Enhanced safe Shift Range for a StarForce is ten Lites. An enhanced shift is defined as a shift to a Friendly StarGate, or to a non-shifting, Friendly StarForce which has been assigned the task of enhancing its LiteZulu.

[7.23] A StarForce used to enhance its current LiteZulu may not itself shift and may only enhance that LiteZulu for a single Friendly StarForce.

[7.24] A StarGate has a basic capacity of assisting two StarForces in their shifting. This capacity may be increased to four StarForces if all the involved StarForces are performing exactly the same shift, i.e., all the StarForces are shifting from the same point of origin to the same destination.

StarForces shifting from an assisting StarGate to an ordinary, unenhanced LiteZulu have a Shift Range of ten Lites. StarForces shifting from an assisting StarGate to a LiteZulu enhanced by a Friendly StarForce have a Shift Range of fifteen Lites (note that in this case there must still be one enhancing Friendly StarForce in the destination LiteZulu for each shifting StarForce). StarForces shifting from one StarGate to another have a Shift Range of twenty Lites.

[7.25] When using only its basic capacity of assisting two StarForces, a StarGate may perform any combination of tasks, e.g., it may enhance its location for one in-shifting StarForce and assist the shifting of one out-shifting StarForce or it could assist the out-shifting of two StarForces to two different destinations. It may not perform such mixed missions when exceeding its basic capacity.

[7.3] RANGE EFFECTS WHEN SHIFTING INTO LITEZULUS DEFENDED BY ENEMY STARGATES

[7.31] Whenever a StarForce attempts to shift into a LiteZulu containing an active Enemy StarGate, it must add four Lites to the calculated distance of the shift. For example, if a StarForce in 2022/0 attempts to shift into 2020/0 (Sol) which contains an Enemy StarGate, the distance of the shift would be treated as six Lites (rather than two) which would force the StarForce to risk an Overshift on the "A" Range column. If a StarForce were being assisted by a Friendly StarGate, it could be up to six Lites away from an Enemy StarGate and still shift to it without risking Overshift.

[7.32] A StarForce which begins the Game-Turn adjacent to an Enemy StarGate (i.e., in any one of the twenty LiteZulus within one Lite of the StarGate's position) may always shift into that StarGate's LiteZulu without risk of Overshifting. Note that this is true even in the Xenophobe Scenarios which reduce the normal Shift Range of Xenophobe StarForces to one Lite when operating in PSL space and PSL StarForces to one Lite when operating in Xenophobe space (see scenarios 13 and 14 and their special rules).

[7.4] SEMI-HIDDEN UNIT DISPLAY

[7.41] The positions of StarForces are revealed to the opposing Player only to a limited extent. Upon the completion of all shifts, the owning Player places one StarForce counter in every numbered hex that contains at least one Friendly StarForce. The exact Zulu Coordinates of the individual StarForces in that numbered hex are revealed in only two cases: One, in the case of Friendly StarForces in one of the twenty LiteZulus adjacent to an opposing StarGate or, two, when opposing StarForces are in the same numbered hex. In the first case, the quantity and Zulu Coordinate(s) of only those StarForces actually adjacent to the opposing StarGate are revealed. In the second case, each Player must reveal to the opposition the Zulu Coordinates only of all Friendly StarForces in the hex, not the number of StarForces.

[7.42] The actual number of StarForces is only revealed when opposing units are actually in the same, identical LiteZulu (or when StarForces are adjacent to an Enemy StarGate).

[7.43] The LiteZulu of a StarGate is always known by all Players (exception, see Xenophobe scenarios). StarGates are always assigned to a given Star system and only one StarGate per system is allowed.

[7.5] MAXIMUM SHIFT TABLE

(see the map)

[7.51] The Maximum Shift Table details the Shift Ranges of StarForces when performing one of the five basic types of shifting described in 7.2. For each type of shift there is a Safe Maximum (within which the StarForce is guaranteed to arrive at its destination) and the Overshift Ranges (which cross-index with an Overshift results section to give the outcome of Overshifting given distances).

[7.52] Examples of Overshifting:

  1. A StarForce in 1819/+7 is attempting to shift (unassisted in any way) to 1922/+2. This is a true distance of six Lites. The result would be resolved on the "A" column of the table. There is a 70% chance of safe shifting and a 30% chance of Mirror shifting. The Player draws one of the 0 to 9 chits and gets a result of "7" indicating a Mirror Shift; the StarForce is placed in LiteZulu 1717/+12 instead of its intended destination.
  2. A StarForce is making an Enhanced Gate Shift from Sol (2020/0) to a Friendly StarForce in LiteZulu 2325/+16 (adjacent to Sigma Draconis). This is a true distance of seventeen Lites and the result therefore would be resolved on the "B" range column. The Player draws a "4" chit and completes the shift safely.
  3. Three StarForces are using a StarGate in 1319/+1 to make a Gate-to-Gate Shift to a StarGate in 3223/+17. This is a true distance of twenty-five Lites, and would therefore be resolved on the "C" range column of the Overshift results table. The Player draws a result of "9" indicating all three StarForces are Randomized.

[Diagram: "Final Destination as a result of Mirror Shifting" (hex 1717, 1717/+12) and "Point of Origin" (hex 1819) and "Plotted Destination" (hex 1922) on the Stellar Display, illustrating 7.52 example 1.]

[7.53] Explanation of Overshift Results and Their Application

  • S = Safe Shift. Complete shift as plotted.
  • M = Mirror Shift. Shift the StarForce in exactly the opposite of the three-dimensional direction plotted.
  • R = Randomized. In the Basic game, the StarForce is removed from play for the remainder of the game.

When two or more StarForces are making exactly the same Overshift from the same point of origin to the same destination and they are making either a simple Gate Shift or a Gate-to-Gate Shift, only one result chit is drawn for all the StarForces involved. When the shift is a Normal Shift, an Enhanced Shift, or an Enhanced Gate Shift, the Overshift results are determined on a StarForce-by-StarForce basis, drawing one chit for each unit.

[7.54] Determining the Final Resolution of a Mirror Shifted StarForce

Mirror shifting results in the StarForce being positioned in exactly the opposite direction from that which was plotted. Draw an imaginary straight line from the center of the two-dimensional destination hex through the center of the two-dimensional hex-of-origin and continue it backwards until it passes through the center of a two-dimensional hex exactly the same distance from the point of origin as the intended destination hex. Now reverse the Zulu-change of the plot to determine the final LiteZulu position of the Mirror Shifted StarForce.

The accompanying diagram illustrates the example of Mirror Shifting given in 7.52, example 1. [7.55] Whenever the results of Mirror Shifting (or Randomization in the Advanced Game) would place a unit off the Stellar Display, an adjustment is made to maintain the unit within the confines of the map. If the "uncontrolled" shift exceeds the Zulu limits of the Display, reduce the Zulu number until it is just within the maximum allowed at that particular point in the volume. If the two-dimensional limits of the Display are exceeded, bring the StarForce back along the line of the Mirror Shift until it attains the map.

[7.6] TRUE [LITE] DISTANCES

If StarForce were a two dimensional game, there would be no difficulty in determining the distance from one point to another on the map: Players would simply count the number of hexagons from one point to another and that would be that. Due to the three-dimensionality of the game, however, things are not so simple. "Straight line" distances must be calculated through the three-dimensional volume at every conceivable angle. Stars that look relatively close may actually be far apart due to their three-dimensional displacement in space.

It would not be accurate to calculate distances in the most obvious way, i.e., counting the distance in hexes two dimensionally and then simply adding the "up" or "down" differential between two points. Doing that would not give the shortest distance between two points. What one really wants to know in this case is the length of the hypotenuse of the right triangle formed by the "horizontal" and "vertical" distances. Luckily, Pythagoras figured this one out a while back by developing the simple formula stating that the sum of the squares of the two other legs of the triangle (A2+B2=C2). Rather than burden Players with the task of figuring out square root problems every time they shift their StarForces, we've supplied a table that does it for them. (See the True Distance Table).

[7.61] TRUE DISTANCE TABLE

(see, also, the abbreviated version of the table on the map)

Columns are the Planar Differential (the two-dimensional distance); rows are the Zulu Differential. The entry at the intersection is the true distance in Lites, rounded off to the nearest Lite. Table reproduced from the printed True Distance Table; see the note below the table.

ZD \ PD01234567891011121314151617181920
00123456

Transcriber's note: the printed True Distance Table is a grid of rounded true distances. The grid above was regenerated from the rounding rule in 7.62 (true distance = square root of (Planar Differential squared plus Zulu Differential squared), rounded to the nearest whole Lite) and checked against the printed rows, which it matches.

[7.62] How to Use the True Distance Table

Distances in StarForce are measured in Lites; every two-dimensional hex is one Lite across and every Zulu increment or decrement is a distance of one Lite. To discover the true, three-dimensional distance between two points simply count the two dimensional distance and then calculate the Zulu differential between the two points. On the True Distance Table, cross index the Zulu differential with the distance across the Equatorial Plane (the two-dimensional distance). The figure indicated will always be the true distance (rounded off to the nearest Lite).

[7.63] Rules of Thumb

Although the True Distance Table is easy to use, even it gets to be a bore if one has to refer to it every time a shift is made. Such will not be the case if the Player keeps a few "rules of thumb" in mind when figuring distance. In this discussion, the term Zulu Delta (ZD) will be used to refer to the "vertical" distance between two points and the term Planar Delta (PD) will be used to describe the two-dimensional "horizontal" distance between two points.

  1. If either the Zulu or the Planar Delta is "1" or "0" then the true distance is either equal to "1" or equal to the Delta greater than "1". For example, Epsilon Eridani and Tau Ceti are PD 4 by ZD 1 distant from each other. Ignore the ZD to calculate the distance.

  2. Rule One can be extended to cover greater distances:

    • If one Delta is "2" or less and the second Delta is "4" or greater, then the second Delta is the true distance.
    • If one Delta is "3" or less and the second Delta is "9" or greater then the second Delta is the true distance.
    • If one Delta is "4" or less and the second Delta is "16" or greater then the second Delta is the true distance.
  3. If one Delta is "3" or less, and one Delta is "4" or less than the true distance is "5" or less (i.e., within the safe maximum for a normal shift).

  4. When the Zulu numbers of the two positions have the same sign (i.e., plus or minus) subtract the smaller from the larger to discover the Zulu Delta; for example, subtracting -4 from -16 yields a Zulu Delta of 12. When the signs are different, ignore them and add the two numbers together; for example, +5 added to -3 equals a Zulu Delta of 8. Of course, when one of the Zulu numbers is Zero, the Zulu Delta is equivalent to the second Zulu number.

  5. The true distance will never be greater than one and a half times the larger of the two Deltas.

[8.0] BASIC GAME COMBAT

GENERAL RULE: Combat occurs between opposing units who, after executing their plotted movement, are in the same LiteZulu. Unlike most other simulation games, in a combat action there is no set role of attacker or defender. Rather, each of the opposing sides may be either an attacker or defender, or both, in a given Combat Segment.

PROCEDURE: For each Player involved in a specific Combat action, total the Strength Points of all his units involved in that LiteZulu. This represents, for each Player, a pool of Strength Points, from which he may allocate his attack and his defense. From this pool, each Player should simultaneously write down the number of points allocated to attack and the number of points allocated to defense. Combat is executed simultaneously, that is, the effects of combat are taken into consideration after each Player has attacked in turn. Either Player may attack first. He states the number of Strength Points he has attacking and the opposing Player states the number of Strength Points that are defending. State the comparison as the difference between the attacking Strength Points and the defending Strength Points. Consult the Basic Game Combat Results Table, draw a chit from the Decimal Randomizer and read the result on the appropriate line under the Differential Column. The result is not applied immediately. The formerly defending Player now proceeds with his attack against the formerly attacking Player. Repeat the above resolution procedure. After both Players have executed their attacks the results are applied. Each combat action continues until only one Player's units are left in that LiteZulu. There may be any number of Combat Segments until this final resolution. After a given combat action is completed, the Players proceed to any other combat actions which might have occurred in that Game-Turn. After all combat actions are resolved, proceed to the next Game-Turn. Note: Players may wish to resolve Combat Situations in a concurrent fashion, i.e., execute all first Combat Segments in all situations, then all second Combat Segments, etc. This optional routine is more complicated to keep track of, but is somewhat more realistic.

CASES:

[8.1] WHICH UNITS MAY ENGAGE IN COMBAT

[8.11] During the Combat Segment of a given Game-Turn, Players must engage units in combat which are in the same LiteZulu as opposing units. Only those Friendly units in a given LiteZulu with opposing units may participate in combat (and only with those opposing units). Combat is not voluntary; units are compelled to engage in combat by the act of having ended their Shift Execution Phase in the same LiteZulu as opposing units (exception: see First Combat Segment 8.2).

[8.12] There is no limit to the number of units, opposing or Friendly, which may be in a single, given LiteZulu and therefore involved in a single combat action.

[8.2] FIRST COMBAT SEGMENT

[8.21] During the First Combat Segment of each combat action, StarForces that have just entered the LiteZulu (i.e., did not begin the Shift Plot Phase in that LiteZulu) have a different Strength than for the subsequent segments in the same combat action (see 8.3 Strength Calculation).

[8.22] In the First Combat Segment StarForces which have just entered the LiteZulu may not attack nor be attacked by opposing StarGates, or opposing StarForces which have themselves just entered that LiteZulu. They may only be attacked (and may only attack) Enemy StarForces which began the Game-Turn in that LiteZulu.

[8.23] StarForces which began the Shift Plot Phase in that LiteZulu have the option of refusing combat for the first Combat Segment. If the Player does refuse combat, no combat is possible during that Combat Segment. Play then proceeds to the second (and any following) Combat Segments.

[8.24] After the first Combat Segment (i.e., in the second and further combat segments of a given combat action) all units are at full Strength. Moreover, subsequently, all units in that contested LiteZulu must engage in combat, whether in attack or defense. Note that if both Players allocate all of their Strength Points to defense, this is still defined as "combat" even though no resolution takes place.

[8.3] COMBAT STRENGTH CALCULATION

[8.31] In all Combat Segments, StarGates are worth five Strength Points.

[8.32] In all Combat Segments, StarForces which began the Game-Turn in a given LiteZulu are worth three Strength Points.

[8.33] In the First Combat Segment (only) of a given combat action, StarForces which have just entered the LiteZulu are worth only two Strength Points. After the First Combat Segment in that combat action the surviving StarForces are worth three Strength Points.

[8.34] In the Combat Segment in which they perform a break-off (see 8.6) StarForces are worth only two Strength Points (and may only use that Strength defensively).

[8.4] COMBAT SEQUENCE

[8.41] As stated before, there may be more than one combat action in a given Game-Turn. There is one combat action for each different LiteZulu on the Stellar Display in which there are opposing units.

[8.42] For each combat action, there is at least one (the First) Combat Segment and there may be an indefinite number of Combat Segments following that. Note that there are differences between First Combat Segments and all subsequent Combat Segments (8.2). Combat continues with the sequence of plotting Attack and Defense Strength Points by each Player and execution of the simultaneous attacks until the LiteZulu is occupied only by units of one Player, or no Players.

[8.43] Note that a given unit may only be in one contested LiteZulu per Game-Turn. Thus, if a StarForce wishes to break off and withdraw to a Friendly StarGate or any other LiteZulu, (see Combat Breakoff, 8.6), that StarGate or LiteZulu must not be (or have been) occupied by Enemy units in that Game-Turn.

[8.5] COMBAT DIFFERENTIAL CALCULATION AND PLOTTING FOR THE COMBAT SEGMENT

[8.51] The simultaneous combat situations are expressed as a difference between attacking Strength Points less the defending Strength Points. For instance, if seven Strength Points have been allocated to attack by one Player against four Strength Points allocated to defense by another Player, the Combat Differential Calculation would be expressed as "+3". The appropriate column is consulted on the Combat Results Table.

[8.52] Except for the reduction in Strength Points during the First Combat Segment and a similar reduction during break-off, unit Strengths are never affected during Strategic Combat by any means. Their Strength is always full. It is not unitary; the "pool" of Strength Points may be applied and divided in any manner.

[8.53] In order for a Player to be considered an attacker during a particular Combat Segment, he must have allocated at least one Strength Point to the attack.

[8.54] Plotting the Allocation of Strength Points

If Players are using the normal technique of resolving each combat action from start to finish before going on to any others occurring in that Game-Turn, they may simply write their combat allocations on scrap paper, stating Attack Strength allocation first and Defense second. For example, if the Player with a total of eight Strength Points at his disposal wished to attack with only two, he would write "2/6". If one or more of a Player's StarForces are going to break-off at the end of that segment, he must indicate which StarForces are doing so. Remember, when a StarForce breaks off it is worth only two Strength Points for that Segment and those Points may only be used defensively. If a Player had two StarForces and wished one to break off and one to attack with all its Strength, he would write the following plot: "3/2, M(B) to 2020/0" - indicating StarForce "M" breaks off to Sol (2020/0).

If Players are going to resolve Combat Segments concurrently, they will have to use a separate sheet from the SiMove pad and identify each allocation by LiteZulu.

[8.6] COMBAT BREAK-OFF

[8.61] At the end of any Combat Segment, from the second Combat Segment onward, either Player may choose to withdraw some or all of his units. This is known as "breaking-off". It need only be done in a given combat action and it does not affect other combat actions that are going on simultaneously.

[8.62] Only StarForces may break-off an action; StarGates are immobile and may not, therefore, break-off action.

[8.63] Units may preferentially break-off to one of two locations. They may break off to the LiteZulu from which they entered the contested LiteZulu. If they Overshifted into the combat action LiteZulu, they need not suffer Overshift upon returning to the LiteZulu from which they entered. Alternatively, they may withdraw to any uncontested Friendly StarGate. This StarGate must be within ten Lites of the point of break-off.

[8.64] If neither of the above alternatives in 8.63 are available, the withdrawing StarForces must withdraw to an adjacent, uncontested LiteZulu of their own choice.

[8.65] StarForces which are breaking-off do so immediately after combat execution in a given segment. Remember, StarForces which are breaking-off are worth only two Strength Points each (which may only be used defensively).

[8.66] StarForces which are breaking-off may break-off into different LiteZulus even if they originate from the same LiteZulu.

[8.67] StarForces may never break-off into a LiteZulu that was contested at any time during that Game-Turn.

[8.68] Stalemate Break-Off

In a given combat situation, if neither Player suffers any losses after the completion of the first six Combat Segments, then all of the StarForces belonging to the Player who does not have a StarGate in that LiteZulu must break-off and end the action. The same judgment must be made at the completion of each set of six Combat Segments and the same compulsion to break-off is applicable if during that set of six Combat Segments no losses were inflicted on either Player. If the combat situation is one of those rare instances that take place in a LiteZulu which has no StarGate, the Player with the greater number of StarForces which did not begin the Game-Turn in that LiteZulu must break-off, after six stalemated Segments. If neither Player has StarForces which began the Game-Turn in that LiteZulu, then both Players are forced to break-off.

[9.0] STRATEGIC COMBAT RESULTS [Basic Game only]

[9.1] STRATEGIC COMBAT RESULTS TABLE

Players should see the map, where they will find two copies of the table, and a brief summary of the results.

[9.2] HOW TO USE THE STRATEGIC COMBAT RESULTS TABLE

The table is used to resolve combat during the combat execution segment. The Decimal Randomizer Chits are used to produce random numbers to indicate which result will apply to a given situation. When a Player attacks in a given situation, he picks one chit (blindly) from the Randomizer and reads the result aloud. Cross-indexing that chit number with the appropriate attack-defense differential column will yield a combat result. If both Players are attacking in a given situation, both draw a chit before applying results. Note that no more than one chit at a time should be drawn and it should be immediately placed back into the Randomizer before another draw is made. Differentials are calculated by subtracting the opposing Player's Strength Points from the attacking Player's attack Strength Point allocation. For example, five Strength Points allocated to the attack opposed to three Strength Points allocated to the defense would mean the attacker would read his result from the "+2" column on the table.

If more Strength Points have been allocated to the defense than the opposing Player has allocated to the attack, the attack will be made at a negative differential (or may be disallowed altogether if it falls below -3).

[9.3] APPLICATION OF RESULTS

The result numbers on the table are the number of StarForces (not Strength Points) eliminated by the attack. StarGates are equivalent to two StarForce units for combat results purposes. They may never be partially affected (by a "1" result for example). Results are applied at the end of the Combat Execution Segment, after both Players have executed their attacks. The units involved must suffer the losses indicated if at all possible. Of course, units may never suffer losses greater than their value. The losing Player decides which of his units will be lost.

The only case in which a Player will be forced to lose a StarGate is when the result against him is two or more, and he does not have sufficient StarForces present to make up the required loss.

Note: The Stellar Randomizer (15.0) may be used in conjunction with the Strategic Combat Results Table simply by substituting a Randomization result for each StarForce loss.

[9.31] StarGate Preservation

If a Player loses his StarGate in a combat situation, but also manages to destroy or drive off all the Enemy StarForces in that Game-Turn, the StarGate reappears in the immediately ensuing Game-Turn. It may not, however, be used for shifting, position-finding, or combat in the Game-Turn in which it reappears and if the Enemy Player has forces remaining in that LiteZulu at the end of that Game-Turn, the StarGate permanently disappears. If, however, the StarGate survives this one Game-Turn in "limbo", it returns to full strength and normal use at the very start of the next Game-Turn (for example, a StarGate which was "destroyed" in combat on the third Game-Turn, reappears in the fourth Game-Turn, and is returned to normal use for the fifth Game-Turn).

[9.32] Examples of Combat Resolution

"Alpha" Player with two StarForces and one StarGate in the contested LiteZulu allocates nine of his eleven Strength Points to attack "Bravo" Player's three StarForces. Bravo Player has allocated four of his nine Strength Points to attack Alpha's forces. Alpha Player draws a "0" chit from the Decimal Randomizer and cross indexes that result with the "+5" column of the Combat Results Table. The Table indicates a loss of two Bravo StarForces. Bravo draws a "9" chit and reads the result on the "+2" column which indicates a loss of three Alpha StarForces. Now the Bravo Player removes two of his StarForces from the map and Alpha must lose his StarGate plus one of his StarForces in order to fulfill the "lose 3" result. This leaves each Player with one surviving StarForce. In the next Combat Execution Segment, both Players attack each other's StarForce with an allocation of one Strength Point. Alpha draws a "7" chit and Bravo draws a "3". Both results are read on the "-1" column. Bravo is destroyed and Alpha survives. Since Alpha has completely eliminated the enemy forces from the LiteZulu, this combat situation is over (and, moreover, Alpha's StarGate will reappear in the next Game-Turn).

[10.0] ADVANCED GAME DESCRIPTION

Advanced StarForce is distinguished from the basic game mainly by its more detailed and complex system of combat action and resolution. Combat no longer takes place on the Stellar Display. Instead, each combat situation is transferred to the Tactical Display where StarForces make use of tactical maneuver and force allocation to decide the outcome.

All of the rules of the Basic Game are used with the exception of 5.2C (the Basic Game Combat Execution Phase) and Sections 8.0 and 9.0. Players are cautioned that the Advanced Game presents interesting tactical intricacies at the expense of playability. If Players have neither the time nor the patience to deal with this increased complexity, they should not get involved with the Advanced Game. Simply because the title of this game-version is "Advanced", Players should not misconstrue this to mean that the Basic Game is strictly for novices. The Advanced version is presented to sate the appetites of those gamers who desire detailed play. Both versions should be appreciated on their own merits without ascribing an intellectual hierarchy to them.

[10.1] ADVANCED GAME GLOSSARY ADDITIONS

Note that some of the terms in the glossary will not make complete sense unless understood in the context of the entire rules. Do not expect to totally grasp all the implications of some terms simply by reading these introductory definitions.

Anti-cast - the defensive value of a given StarForce (effective for the entire Tac-Turn) derived to by subtracting the TelePoints allocated to other functions from the total available. StarGates also develop Anti-cast strengths but on a Phase by Phase basis.

Cast (or Combat Cast) - a three-dimensional projection of combat strength into a certain specified portion of the Tactical Display. Both StarForces and StarGates may make casts. The word is used in the sense of a broadcast or the casting of a net.

Disruption - a tactical combat result which halves the total number of TelePoints available to a StarForce or StarGate until the Disruption Recovery Phase of the next Tac-Turn.

MiniLite - the Tactical Display analog to the Stellar Lite. One MiniLite is equivalent to a third of a Light Day. Each numbered hexagon on the Tactical Display is one MiniLite across.

MiniLiteZulu - the Tactical Display analog to the Stellar LiteZulu. There are 1001 MiniLiteZulu positions on the Tactical Display. A position on the Tactical Display is given in terms of its three-digit hex number followed by its MiniZulu number, e.g., 110/+2.

MiniZulu Limit - the entire Tactical Display has a vertical limit plus or minus five. Note that the Tactical Display is not subdivided into rings as is the Stellar Display.

Mode - a StarForce on the Tactical Display is said to be in either one of two modes: Stellar Mode or Battle Mode. Stellar Mode is the "normal" travel mode of a StarForce. Battle Mode is the optimum fighting configuration for a StarForce. It sacrifices some of the mobility of the Stellar Mode for an increase in combat power. StarForces change mode by the expenditure of TelePoints. StarGates do not have different modes.

Neutralization - a combat (or movement) result which affects both StarForces and StarGates. A StarForce is neutralized when it suffers randomization (either through Overshift result or Cast result) or when it executes a break-off maneuver from the Tactical Display. A StarGate is neutralized when it suffers two successive disruption results in combat. StarForces and StarGates recover from neutralization in slightly different ways.

Randomizer, Stellar - a set of 43 chits numbered with two sets of figures. The Stellar Randomizer is used to develop the new position (on the Stellar Display) of StarForces which are randomized as result of combat or as a result of Overshifting.

Tactical Display - the smaller of the two fields of hexagons printed on the map. The Tactical Display represents a volume of space one hundreth of a Lite across and one hundreth of a Lite deep. This is roughly one-millionth of the volume represented by a Stellar LiteZulu. Note that the Tactical Display uses its own numbering system on its hexagons. The lefthand digit of each three digit number indicates the planar distance from the center hex. The middle digit indicates the "sextile" (60° wedge) that that hex falls within. The right hand digit counts the number of hexes clockwise from one of the six primary planar axis of that ring of hexagons. The foregoing explanation of the number system is presented simply for curiosity value.

Tactical Sequence - the interruption of the Stellar Game-Turn to resolve a combat situation by running a series of Tac-Turns.

Tac-shift - the Tactical Display analog to Stellar shifting. StarForces Tac-shift by allocating TelePoints to do so. StarForces may not "Over-Tac-shift". StarGates may not Tac-shift nor may they aid StarForces in their Tac-shifting.

TeleValue - the overall movement/combat/defense ability of a StarForce or StarGate quantified in terms of TelePoints. Each Tac-Turn, Players decide how they will allocate these Points to the various game functions performed by their units. StarGates have a TeleValue of 64 (see the map for the TeleValues of StarForces in given modes).

[11.0] ADVANCED GAME SEQUENCE OF PLAY

The Stellar Game-Turn is exactly the same in the Advanced game as in the Basic Game with the exception that Basic Game-Turn Phase C (the Combat Execution Phase) is replaced by the Tactical Sequence. A Tactical Sequence is initiated under the same conditions as the Combat Execution Phase is in the Basic Game, i.e., whenever opposing units occupy the same LiteZulu after executing Stellar shifts. The Tactical Sequence is composed of an indefinite number of Tac-Turns (which are further subdivided into a number of Phases). Each Tactical Sequence is carried through to resolution before initiating the Tactical Sequence for any other Tactical Situation. All Tactical Situations are resolved before going on to the next Stellar Game-Turn.

[11.1] TACTICAL SEQUENCE OUTLINE

[11.11] TACTICAL SITUATION DEPLOYMENT PRE-PHASE

Before the first Tac-turn of a given situation can be started, the forces involved must be transferred from the Stellar Display to their starting positions on the Tactical Display. Leave a "Tac Sit" marker on the Stellar Display to help mark the LiteZulu involved.

Step 1: If there is a StarGate involved, place it in the exact three-dimensional center of the Tactical Display (MiniLiteZulu 000/0). Step 2: If the Stellar LiteZulu involved contains a star system assume the star to be in position 000/-1. Players may wish to place the Star marker to remind them of its presence.

Step 3: Both Players secretly write down the coordinates of the MiniLiteZulu(s) in which their respective StarForces are going to start. Initial deployment of StarForces in this step is performed under the following restrictions:

  • A. StarForces which began the Stellar Game-Turn in the LiteZulu may be deployed anywhere on the Tactical Display (individually or in groups). They may be considered to be in Battle Mode if the owning Player wishes.
  • B. StarForces which shifted into the LiteZulu during that Stellar Game-Turn may be in any MiniLiteZulu which has a hex number in the 500 series (for example, 551/-2) or any MiniLiteZulu with a Zulu number of plus or minus five (for example, 000/+5). StarForces which shifted in from the same LiteZulu must initially deploy on the Tactical Display within the same MiniLiteZulu or in positions within one MiniLite of all the members of that common group. All incoming StarForces are in Stellar Mode.

Step 4: Place all StarForces on the Display. Do not reveal their MiniZulu coordinates at this time. Begin the first Tac-Turn of the Sequence.

[11.12] THE TAC-TURN

A. Tac Plot Phase: Players secretly write down (plot) the actions which their units will take during both of the Execution Phases of this Tac-Turn.

B. First Tac Execution Phase:

  1. Tac-shift and Mode Change Segment: Players simultaneously execute all Tac-shifts and Mode changes plotted for this Execution Phase.
  2. Combat Cast Segment: Players simultaneously execute any combat casts they have plotted to take place in this Execution Phase.
  3. Cast Results Application Segment: Players apply the results of the Combat Casts made in Segment Two of this Execution Phase. StarForces which have been randomized are removed from the Tactical Display and held aside to be placed on the Stellar Display at the end of this Stellar Game-Turn.
  4. Plot Modification Segment: StarForces which have had their TeleValue for the Second Execution Phase halved by a Disruption result in the First Execution Phase must have their Plots adjusted to reflect this fact. Second Phase Tac-shifts and Break-offs are aborted and half the plotted TelePoint cost of the aborted action is diverted to the Anti-cast for the Second Execution Phase. Casts plotted for the Second Execution Phase are still made but at half value.

C. Second Tac Execution Phase:

  1. Tac-shift and Break-off Segment: Players simultaneously execute all Tac-shifts and break-offs plotted for this execution Phase (except those aborted by First Phase results).
  2. Combat Cast Segment: Same as in Phase B (except for halving of effective strength due to disruption).
  3. Cast Results Application Segment: Same as in Phase B.

D. Position Revelation Phase: If a Player has an undisrupted/un-neutralized StarGate on the Tactical Display, his opponent must reveal to him the exact position of all of his StarForces. Independent of the presence of a StarGate, Players must reveal to each other the positions of all units which occupy the same numbered hex on the Display. A disrupted StarGate is treated as a StarForce with respect to intelligence gathering. A neutralized StarGate cannot ascertain the position of any Enemy StarForce.

E. Disruption Recovery Phase: StarForces and StarGates which were disrupted in the previous Tac-Turn are returned to normal, undisrupted status (assuming that they haven't suffered an additional combat result in this Tac-Turn).

F. Situation Judgment Phase: If the Tactical Display now contains no mutually hostile units (disregarding neutralized StarGates) the Tactical Sequence is ended for the LiteZulu in question. If hostile units still oppose each other on the Display, the Players begin another Tac-Turn.

G. Stalemate Judgment: If neither Player has made at least one viable combat cast (i.e., one that required a chit pick) in the preceding twelve Tac-Turns of this situation, then the non-StarGate owning Player must execute a break-off with all his forces within the next two Tac-Turns (without making any further casts). If there is no StarGate on the Display, the Player who did not have StarForces beginning the Game-Turn in that LiteZulu is compelled to break-off. If neither began the Game-Turn in the LiteZulu then both Players must break-off.

[12.0] ADVANCED GAME TACTICAL PLOTTING

GENERAL RULE: During each Tac Plot Phase, each Player secretly records on a SiMove sheet all the operations that his units will perform in the coming two Execution Phases of that Tac-Turn. Once plotted, these operations may not be voluntarily changed. These operations are (with one exception) always mutually exclusive for a given unit within a given Execution Phase. The overall capability of a unit to perform these operations is measured in terms of TelePoints. Allocation of TelePoints to one activity diminishes the ability of the unit to perform other activities in the same Tac-Turn.

CASES:

[12.1] UNIT TELEVALUES

StarForces and StarGates have specific TeleValue which they can allocate in terms of TelePoints to perform different operations in the Execution Phases of the Tac-Turn.

[12.11] Summary of Unit TeleValues

UnitModeTeleValue
StarForceStellar32
StarForceBattle64
StarGateNot Applicable64/64

[12.12] StarForces use their TeleValue to cover all their operations through both Execution Phases. StarGates have a TeleValue that is fully available for both Execution Phases of a Tac-Turn (i.e., StarGate Points allocated for use in the First Execution Phase do not diminish those available for use in the Second Execution Phase and vice-versa).

[12.2] PLOTTING FOR THE TAC-TURN

Each Tac-Turn consists of one Tac Plot Phase followed by two Execution Phases. Players should use two consecutive boxes on the lines of the SiMove sheet to write the plot for each of their StarForces and StarGate.

[12.21] Undisrupted StarForces can perform any one of the following four actions in a given Execution Phase: Tac-Shift, Mode Change, Break-off, or Combat Cast. After writing one of these operations for each Execution Phase, for each StarForce and indicating the number of TelePoints of the unit's per-Turn TeleValue expended in each of the plotted operations, the Player records any unused TelePoints as the Anti-cast that unit will have during that entire Tac-Turn.

[12.22] An un-neutralized StarGate may plot only one type of operation for each Execution: Combat Cast. Unlike StarForces, however, a StarGate can plot more than one cast per Execution Phase. The Anti-cast of a Stargate can vary from the First to the Second Execution Phase because the Stargate is allowed to use its full TeleValue each Execution Phase and can have two completely different plots written for it in a Tac-Turn.

[12.23] Once written, plots may not be voluntarily changed. The plot for the Second Execution Phase, however, is subject to modification as a result of combat effects of the first Execution Phase. See 11.12B-4.

[12.3] ADVANCED GAME TACTICAL PLOT CODES AND ACTIONS

CodeActionPrefixes and Suffixes and Example
TTac-shiftPrefix with TelePoint cost; suffix with destination. Example: 32T 421/+3. Phase Allowable: 1st and/or 2nd.
MMode ChangePrefix with Telepoint cost; suffix with "b" when changing to Battle Mode; with "s" when changing to Stellar Mode. Example: 16Ms. Phase Allowable: 1st only.
BBreak-offSuffix with Stellar Lite Zulu destination. Example: B 2020/+1. Unit must be in Stellar Mode. Phase Allowable: 2nd only.
CCombat CastPrefix with TelePoints allocated; suffix with "p" or "n" to indicate relative Zulu direction. Further suffix with "Clock number" to indicate planar direction. Example: 32 Cp9. Phase Allowable: 1st and/or 2nd.
AAnti-CastPrefix with TelePoints allocated. Example: 8A. Phase Allowable: 1st and/or 2nd.

[12.31] Tac-Shift Plot: This is similar to writing a Stellar Shift plot with the addition of the TelePoint expenditure for the true distance traveled written as a prefix.

[12.32] Mode Change Plot: Mode changes can only be plotted to occur in the First Execution Phase. Players should note the operative value of the unit for the Tac-Turn is the TeleValue of the unit when in the Mode to which it is being changed. For example, a StarForce plotted to change to Battle Mode has the use of 64 TelePoints, 32 of which it must expend for the Mode Change, leaving it 32 Points to allocate for a Second Phase Plot (and/or to allocate for its Anti-cast).

[12.33] Break-off Plot: Break-off can only be plotted for the Second Execution Phase and only if the unit is going to be in the Stellar Mode by the Second Execution Phase.

[12.34] Combat Cast Plot: A StarForce can only have one cast per Execution Phase plotted for it. A StarGate can have several cast plots per Execution Phase (in fact as many as twelve different casts per Phase). Casts are always prefixed with the TelePoint Strength of the cast and suffixed with a "p" (positive) or "n" (negative) to indicate the relative Zulu direction of the cast. The "horizontal" direction of the cast is indicated by writing a "clock number" that indicates through which apex of the hex the cast is being made.

[12.35] Anti-cast Plot: The Anti-cast is not so much plotted as it is developed as the remainder of a unit's TeleValue after TelePoints have been allocated to other operations.

[12.4] TAC PLOT EXAMPLE

This example shows the Plot for the first Tac-Turn of two StarForces which have shifted in to contest a LiteZulu:

UnitStarting PositionFirst Execution PhaseSecond Execution Phase
A542/+428T 160/+14A
B543/+532Mb32T 442/+4

(The example is a handwritten plot on the printed rules page; the entries above are read from that plot.)

StarForce "A" is shown to be making a six MiniLite Tac Shift in the First Execution Phase, doing nothing in the Second Execution Phase and maintaining an Anti-cast of four TelePoints.

StarForce "B" is shown to be changing to Battle Mode in the First Execution Phase, making a Tac shift of one MiniLite in the Second Execution Phase and having no TelePoints remaining to devote to its Anti-cast.

[12.5] PLOT MODIFICATION

If due to a disruption result suffered in the First Execution Phase of a Tac-Turn, a unit can no longer literally fulfill its plot for the Second Execution Phase, then a modification of that plot must be made. The effect of disruption is to halve the TeleValue of a unit. Modifications are made in the following manner:

[12.51] If the StarForce was plotted to execute a Tac-shift or break-off in the Second Execution Phase, that plot is cancelled. The TelePoints allocated to that Tac-shift are halved and are contributed to the Anti-cast of the StarForce.

[12.52] If the StarForce (or StarGate) is plotted to execute a combat cast in the Second Execution Phase, the effective strength of the cast is cut in half (due to the disruption) but it is still executed. If a cast with a plotted strength of "2" is thereby reduced to an unallowable "1", the cast is not made (and that one TelePoint is added to the modified Anti-cast of the unit).

[12.53] The Anti-cast defense of the unit is halved. After this halving is made, any halved TelePoint allocation from aborted Tac-shifts or disallowed casts are added to this figure to produce the modified, effective Anti-cast of that unit for the Second Execution Phase of that Tac-Turn.

[12.54] Examples of Plot Modification

  1. A StarForce in Battle Mode which was plotted to perform no operation in the First Execution Phase and to make a 32 TelePoint cast in the Second Execution Phase (leaving 32 TelePoints as its Anti-cast) would modify its cast to 16 and its Anti-cast for the Second Execution Phase would also be reduced to 16.
  2. A StarForce in Battle Mode which was plotted to perform a two MiniLite Tac-shift in the First Phase (expending 48 TelePoints) and to make a cast of 8 TelePoints (maintaining an 8 TelePoint Anti-cast) would perform its Tac-shift, suffer the disruption result in combat and have its cast reduced to 4 and its Anti-cast reduced to 4 for the Second Execution Phase.
  3. A StarForce in Battle Mode which was plotted to Tac-shift three MiniLites (costing 56 TelePoints) in the Second Execution Phase and maintain an Anti-cast of 8 TelePoints throughout the Tac-Turn, would have its Tac-shift cancelled and have 28 TelePoints added to its reduced Anti-cast of 4 yielding an effective Second Phase Anti-cast of 32.
  4. A StarForce in Battle Mode which was plotted to change to Stellar Mode in the First Phase and to break-off in the Second Phase would change mode (leaving 16 Points for the Second Phase break-off), cancel the break-off and halve the 16 Points assigned to it and use it as an 8 Point Anti-cast.

[13.0] TAC-SHIFTING, MODE CHANGING, AND BREAK-OFFS

GENERAL RULE: When operating on the Tactical Display, StarForces engage in tactical shifting (very similar to shifts on the Stellar Display), Mode changing (changing from normal stellar travel configuration to a more powerful combat configuration), and breaking-off (leaving the Tactical Display and stellar shifting to a different LiteZulu). All of these operations require the expenditure of TelePoints from the unit's total available TeleValue. No more than one of these operations may be performed by a given StarForce in a Given Execution Phase. None of these operations may be performed by StarGates.

CASES:

[13.1] TAC-SHIFTING [Moving StarForces on the Tactical Display]

Tac-shifting is in most ways identical to Stellar shifting in that it is movement in three dimensions, instantaneously, without traversing the intervening space. The distance of the Tac-shift is measured in terms of MiniLites (this is a true distance measurement and Players are referred to the Abbreviated True Distance Table printed on the map). Tac-shifting is distinguished by the fact that TelePoints must be expended to Tac-shift given distances and that Overshift is not allowed on the Tactical Display.

[13.11] StarForces in Stellar Mode have a maximum Tac-shift Range of ten MiniLites (which would cost all 32 TelePoints available to them on a given Tac-Turn).

[13.12] StarForces in Battle Mode have a maximum Tac-Shift Range of five MiniLites (which would cost them all 64 TelePoints available to them on a given Tac-turn).

[13.13] Tac Shift TelePoint Cost: The first fifth of their total Tac-Shift Range travelled, in a given Execution Phase, always costs StarForces in Battle or Stellar Mode one half of their total, undisrupted TeleValue. Each additional fifth travelled costs one half of the remaining TelePoints. For example, a StarForce in Stellar Mode executing a Tac-shift of three MiniLites would expend 24 TelePoints in doing so. See the TelePoint Cost Table on the map to get a clearer idea of the costs involved.

[13.14] Note that if a StarForce (in either Mode) is plotted to Tac-shift in both Execution Phases, the maximum distance it could travel in that entire Tac-Turn would be two fifths of its Tac Shift Range. This is mentioned to underscore the fact that each Tac shift is a separate operation, the cost of which is calculated for that Execution Phase.

[13.15] Note that if a StarForce in either mode is in a disrupted condition, the maximum Tac-shift it could make in a given Tac-Turn would be one fifth of its range. In other words, the Tac-shift cost remains the same and is not halved along with the disrupted unit's TeleValue.

[13.16] There is no limit to the number of StarForces that can occupy a single MiniLiteZulu. StarForces may Tac-shift into or "through" each other's positions without interference. StarForces may Tac-shift into or "through" a StarGate's position without interference.

[13.17] When a star system is present on the Tactical Display, StarForces may not Tac-shift into its MiniLiteZulu from a distance of greater than one MiniLite, nor Tac-shift out of the star system's position to a point more than one MiniLite distant. StarForces may Tac-shift "through" a star's position without interference. The limitation only applies when either beginning or ending a Tac-shift directly in the star's MiniLiteZulu.

[13.18] There is no "Semi-Hidden Unit Display" on the Tactical Display. Each StarForce counter on the Tactical Display represents only one StarForce and every unit on the Display must be represented. Enemy unit positions are revealed in the Position Revelation Phase of each Tac-Turn; see the Sequence of Play.

[13.19] StarForces may not Tac-shift off the Tactical Display, i.e., they may never be plotted to a position with a MiniZulu greater than plus or minus five nor a hex number outside the "500" series.

[13.2] MODE CHANGING

The normal mode of a StarForce is the Stellar Mode. This is the mode it is in when shifting on the Stellar Display. When on the Tactical Display, a StarForce may change to Battle Mode, a combat configuration which sacrifices a certain amount of mobility for an increase in combat power. StarForces in Stellar Mode have a TeleValue of 32; in Battle Mode they have a TeleValue of 64.

[13.21] Changing mode costs half of the TelePoints of the resulting mode, i.e., a StarForce changing from Stellar to Battle Mode expends half of the 64 Battle Mode TelePoints and has 32 TelePoints remaining to use for other operations in that Tac-Turn. Similarly, a StarForce changing from Battle Mode to Stellar Mode has 16 TelePoints remaining to use for other operations in that Tac-Turn.

[13.23] No other operation may be executed in the First Execution Phase in which a StarForce changes mode.

[13.24] A StarForce must be in Stellar Mode in order to execute a break-off maneuver in the Second Execution Phase.

[13.25] If Players are going to use a mixed force of StarForces, some in Stellar and some in Battle Mode, in the same Tactical Situation, they may use one of the spare sets of StarForce counters to represent units in Battle Mode. The Mode status of an Enemy Player is always known by the Friendly Player.

[13.3] BREAK-OFF

Break-off is the technique by which undisrupted StarForces in Stellar Mode may voluntarily leave the Tactical Display before the end of the Tactical Sequence. Assuming all conditions have been met, the Player may plot a Break-off maneuver for any or all of his StarForces in any Tac-Turn. All break-offs are executed in the Second Execution Phase.

[13.31] It costs a Stellar StarForce 16 TelePoints to execute a Break-off.

[13.32] Break-offs are the very first operation executed in the Second Execution Phase. Remove the StarForces that are breaking-off and hold them aside until all Tactical Situations are resolved for that Stellar Game-Turn, then place the StarForces in their new LiteZulu on the Stellar Display.

[13.33] Units may break-off to one of three locations:

  1. The LiteZulu in which they began the Game-Turn (if it was not contested at any time during the Game-Turn).
  2. A Friendly StarGate within ten Stellar Lites which is not itself in a LiteZulu that was contested at any time during the Game-Turn.
  3. Any uncontested LiteZulu of the twenty LiteZulus adjacent to the one in which the Tactical Situation is taking place.

[13.34] If breaking-off to a StarGate, the StarForces count against the capacity of that StarGate during the next Stellar Game-Turn. If all StarForces Break-off in the same Tac-Turn as many as four units may break-off to the same StarGate. If breaking-off at different times or from different Tactical Situations, only two StarForces may break-off to that StarGate. This is simply a corollary of the StarGate capacity case (7.24).

[13.35] When executing a break-off to a StarGate or to a former position, StarForces are not subject to Overshift results, even though they may have Overshifted to enter the contested LiteZulu in the first place.

[13.36] StarForces which execute break-offs are neutralized (see 14.7) for the duration of the next Game-Turn.

[14.0] ADVANCED GAME COMBAT [Cast and Anti-Cast]

GENERAL RULE: In the Advanced Game, all combat takes place on the Tactical Display. StarForces and StarGates allocate TelePoints to project Combat Casts into the three-dimensional volume of the display. The effective strength of these casts are compared to the Anti-cast Strength of any Enemy units caught within them. The Anti-cast is subtracted from the Cast Strength and the resultant number determines what column of the Cast Resolution Table will be used. A chit drawn from the Decimal Randomizer and the number drawn is cross-indexed with the appropriate column on the Cast Resolution Table. The result indicated is applied during Cast Results Application Segment of the Execution Phase.

CASES:

[14.1] WHEN CASTS MAY BE MADE AND WHAT UNITS MAKE THEM

Casts may be made in any Tac Execution Phase in which the casting unit is not plotted to Tac-shift, change mode, or break-off. StarForces in either mode may make casts, and StarGates may make casts (unless they are neutralized). All casts in a given Execution Phase are considered to be simultaneous.

[14.2] THE STRENGTH AND RANGE OF CASTS

All casts, regardless of strength, have a range of five MiniLites of true distance. The cast projects outward from the casting unit in a three-dimensional wedge shape (see cast pattern). The exact direction is plotted in advance during the Tac Plot Phase. Units must allocate TelePoints to a cast in certain fixed quantities. The effective strength of the cast diminishes as the distance of the target increases.

[14.21] A given unit may only make casts at one of the following levels of strength (in TelePoints): 2, 4, 8, 16, 32, or 64. No other cast strengths may be plotted by any unit. Note that all the allowable casts are powers of two (i.e., 2x2x2x2x2x2).

[14.22] The strongest cast a Battle Mode StarForce could make would be a cast of 64 in a single Execution Phase (and this would mean it could perform no other operation for that entire Tac-Turn and would not have any Anti-cast protection). A StarGate could make two 64 TelePoint casts, one each Execution Phase of the Tac-Turn.

[14.23] Casts only have their full, plotted strength in the MiniLiteZulu that the casting unit occupies. The effective strength of the cast is cut in half for each MiniLite of distance out from this point. See the Cast Attenuation Table on the map.

[14.24] A given cast affects 94 MiniLiteZulus on the Tactical Display (fewer if made towards the edges where some of it will fall outside the Display). The basic shape of this Cast Volume is shown in the accompanying perspective drawing which represents MiniLiteZulus as hexagonal cells (like a honeycomb). There is also a two dimensional rendering of the cast pattern given on the map.

[14.25] When plotting a cast, its direction is always relative to the point of origin, i.e., its direction in the horizontal plane will be described as a 60° arc emanating through two of the hexsides of the casting unit's position and plotted as the relative clock number formed by the apex of those two hexsides. For example, when viewing the numbered hexagons from a right-reading viewpoint a cast to the "3 O'clock" direction would be a cast directly to the right.

[Figures: "The Directional 'Clock'" hexagon diagram (clock numbers 1, 3, 5, 7, 9, 11); "A Three-Dimensional Rendering of the Volume Affected by a Combat Cast (numbers indicate effective ranges)".] The MiniZulu direction of the cast is always relative to the casting unit's position. A cast must always be plotted as positive ("upward") or negative ("downward") relative to the point of origin. For example, a unit at MiniZulu +3, and casting positively could not affect any Enemy unit "below" +3 on the Display.

[14.26] Example of MiniLiteZulus Affected by a Typical Cast (in tabular format)

Cast is being made from 260/-2, positively, to 5 O'clock. The Strength allocated to the cast is 32 TelePoints. By cross-indexing the affected hex numbers with the MiniZulu coordinate at which they are affected, the Player will be able to read the effective strength of the cast in that exact MiniLiteZulu:

Hex Number-2-10+1+2+3
26032168421
251,16016168421
250,150,000884221
342,241,140,130442

• = that MiniLiteZulu is completely out of range.

Players will be relieved to know that they will not have to figure out such a complete scheme of affected hexes when they make their own casts; only the effect on MiniLiteZulus with targets in them need be calculated.

[14.27] The orientation of a counter on the Display has no bearing upon which directions it may cast to, i.e., their is no "facing" of counters as in some games.

[14.3] THE NUMBER OF CASTS A UNIT MAY MAKE, THE TARGETS AFFECTED AND THE EFFECTS OF MULTIPLE CASTS

A StarForce in Battle or Stellar Mode may never plot more than one cast per Execution Phase. A StarGate, on the other hand, may plot as many as twelve different casts per Execution Phase. Friendly units are never affected by their own casts or the casts of other Friendly units.

[14.31] If a StarGate is plotting more than one cast for a given Execution Phase, each cast must be made to a different direction (either different Zulu directions and/or clock directions).

[14.32] The attenuation effect of each cast is calculated individually even when two units are casting in the same direction from the same MiniLiteZulu with the same number of TelePoints. The Effect upon a given target in a given MiniLiteZulu is, however, additive. For example, if three different units were making casts which overlapped in a given MiniLiteZulu containing an Enemy unit, that Enemy unit would be subjected to the effective combined total of all three of those casts. If a StarGate makes two or more simultaneous casts that overlap each other, they are additive as well.

[14.33] A given cast affects all Enemy units caught within its range: Enemy (or Friendly) units do not "screen" or block out casts for other Enemy units which may be "behind" them. The star system which may be present on the Tactical Display does not interfere with casts into or through its position.

[14.4] DETERMINING IF AN ENEMY UNIT IS IN THE VOLUME OF THE CAST

Since the MiniLiteZulu coordinates of StarForces are not routinely revealed until the end of the Tac-Turn, there will sometimes be some doubt as to whether or not an Enemy unit which appears to be within the Cast Volume of a particular cast, actually is. Use the following procedure to make the determination.

[14.41] If an Enemy unit is in the two-dimensional pattern of the cast, the casting Player reads out the MiniLiteZulu (having that hex number) that his cast is affecting. He does this one MiniLiteZulu at a time until he reads out the one that the Enemy unit is in (in which case the opposing Player announces the fact) or until he has exhausted the list of affected MiniLiteZulus having the same hex number as the target.

[14.42] Even if the cast would not have an affect upon the Enemy unit in question, the Enemy Player must reveal the position of any of his units which are within the nominal Cast Volume. In this way, casting also becomes a method of intelligence gathering.

[14.43] The casting Player does not directly have to reveal the position of his casting unit(s), nor does he have to reveal the strength of the cast until the target(s) are actually acquired (i.e., determined to be in the Cast Volume).

[14.44] Since the position of the StarGate is always known, any target within the cast of the StarGate can simply be announced by the owning Player once the direction of the Gate's cast(s) has been announced.

[14.5] THE ANTI-CAST

The Anti-cast is the defensive value of a StarForce or StarGate. For StarForces it is the remainder of the unit's Tac-Turn TeleValue after the expenditures for all other operations during that Tac-Turn have been subtracted. For StarGates it is the remainder of the Gate's Execution Phase TeleValue after subtracting the expenditures for all casts made in that Phase.

[14.51] The maximum possible Anti-cast a StarForce in Battle Mode could have would be 64 (assuming it plotted no other operations for the entire Tac-Turn). The maximum possible for a Stellar Mode StarForce would be 32. StarForce Anti-casts are plotted to be in effect for the entire Tac-Turn.

[14.52] The maximum possible Anti-cast for a StarGate is 64 per Execution Phase. StarGate Anti-casts can be varied from Phase-to-Phase.

[14.53] The Anti-cast of a given unit cannot be reduced during a given Execution Phase. The effective Second Phase Anti-cast of a StarForce can be reduced if it has suffered a disruption result in the First Execution Phase.

[14.54] Friendly units in the same MiniLiteZulu do not add their Anti-cast values together and cannot aid the defense of another.

[14.6] CAST RESOLUTION

[see the Cast Resolution Table on the map]

[14.61] How to Use the Cast Resolution Table: Total up the effective (after attenuation) cast values of all casts being made upon a given Enemy-occupied MiniLiteZulu. For each Enemy unit in the MiniLiteZulu, determine the TelePoint Differential column to be used by subtracting the unit's Anti-cast from the combined effective cast upon that position. Draw a chit from the Decimal Randomizer and cross index the result with the proper Differential column to find the outcome of the cast. Do this procedure for each Enemy unit in the MiniLiteZulu. Do not apply the results until all casts have been made by all Players.

Example: Enemy StarForces "A" and "B" in 251/+2 are caught in the casts of three Friendly units, the combined effective value of which is nine TelePoints. StarForce "A" has an Anti-cast of two; StarForce "B" has an Anti-cast of eight. The casting Player picks a chit to discover the effect upon "A" and draws a "5". Reading the result on the "+4 thru +7" column indicates a disruption. The draw for "B" is "6"; reading on the "+1" column indicates that the cast had no effect on "B".

Note: TelePoint Differentials of greater than 32 are treated as 32. TelePoint Differentials of less than Zero have no effect. For a casting Player to use the Zero column he must be effectively casting into the MiniLiteZulu with at least one TelePoint.

[14.62] Explanation of Cast Results

  • • = No effect.
  • D = StarForce disrupted (no effect on StarGate). The StarForce has its TeleValue cut in half until the Disruption Recovery Phase at the end of the next Tac-Turn. If a unit receives a Disruption result in the First Execution Phase, its Second Execution Phase plot may have to be adjusted. StarForces which receive a disrupted result while already disrupted are randomized.
  • R = StarForce Randomized (StarGate Disrupted). In the Results Application Segment, remove the affected StarForce from the Tactical Display. At the end of the Stellar Game-Turn the unit suffers randomization procedure (see 15.0) which will leave it in a neutralized state for the next Game-Turn. A single "R" result obtained against a StarGate simply has the effect of a disruption (i.e., the Gate's TeleValue is halved until the Disruption Recovery Phase of the next Tac-Turn). If the StarGate should suffer a second "R" result before it recovers from the first, it is neutralized. See Neutralization, 14.7. A StarGate can never suffer randomization as does a StarForce.

Note: If Players find it convenient, they may turn disrupted StarForces and StarGates face down on the Display to indicate their status.

[14.7] NEUTRALIZATION

Units can be neutralized in three ways: as a result of randomization or mirror shifting when an adverse result is obtained on the Overshift Results Table; as a result of combat randomization or StarGate Neutralization; and as a result of executing a Break-off maneuver. Units which exist on the Stellar Display in a neutralized state have no intellegence-gathering ability (i.e., they can't detect the positions of Enemy units in the same numbered hex).

[14.71] Effect of Neutralization on StarForces

Neutralized StarForces are prohibited from the Stellar shifting for one complete Game-Turn and are in a continual state of disruption if they are caught in a tactical situation (which means if they suffer a "D" result in that Tactical Sequence they will be randomized and neutralized for another complete Game-Turn).

[14.72] Effect of Neutralization upon StarGates

The StarGate is stripped of all TeleValue. If the Tactical Situation is resolved in favor of the Enemy (i.e., only Enemy units remain on the Tactical Display at the end of the Tactical Sequence) the StarGate is permanently removed from play. If the StarGate is alone on the Display at the end of the Sequence or if Friendly StarForces have driven the Enemy off, the StarGate remains neutralized for the next complete Game-Turn. If the Enemy Player does not have forces in the Gate's LiteZulu at the end of that Game-Turn, the StarGate returns to normal use and strength in the Neutralization Recovery Phase.

[14.73] When using Neutralization rules in a Modified Basic Game, StarForces have a Combat Strength of "1" when neutralized; StarGates have a Zero Strength. When the StarGate does not recover its Strength, this is termed permanent neutralization.

[15.0] RANDOMIZATION AND THE STELLAR RANDOMIZER

GENERAL RULE: StarForces can suffer randomization as a result of Overshifting or as a result of combat on the Tactical Display. Randomization is an involuntary uncontrolled shift into a LiteZulu somewhere on the Stellar Display. The exact LiteZulu a unit is randomized to is determined by the use of the Stellar Randomization chit system. This is a set of 43 dual numbered chits, which render the full coordinates of a LiteZulu by making three draws from the set. The first two draws develop the four digit hex number (by reading the top number on the chit and combining them) and the third draw yields the Zulu coordinate (by reading the plus or minus number on the bottom of the chit).

CASES:

[15.1] EFFECTS OF RANDOMIZATION

When a unit is Randomized it is also neutralized, and does not recover from that neutralized state until the Neutralization Recovery Phase of the following Game-Turn. See 14.7.

[15.11] If the top number of either of the first two Randomizer chits drawn read "Dstr", the unit is permanently destroyed (and removed from the map for the remainder of the game). A "Dstr" chit drawn as the third chit has no effect.

[15.12] If the top number on either of the first two chits drawn reads "Brkf" instead of a number, the unit is either neutralized in place (if randomization was a result of Overshifting) or forced to make immediate break-off from the Tactical Display (even if it is the First Execution Phase of the Tac-Turn and/or even if the unit is in Battle Mode). The break-off destination is any one of the immediately adjacent, uncontested LiteZulus, at the owning Player's discretion.

[15.13] If by some freak chance, a unit is randomized to a LiteZulu containing a star system, it is destroyed instead. The exception to this is, if by even greater chance, the unit is randomized to the LiteZulu it presently occupies (either due to a combination of the three chits). In such a case, the unit is neutralized in place. Since there's only one chance in 40,000 of this happening, the rule is moot, at best.

[15.2] USING AND READING THE STELLAR RANDOMIZER

Place all 43 chits in a large, wide mouthed, opaque container (a pipe-tobacco can is ideal). Each time a randomization is called for, the affected Player shakes the container slightly and draws one chit and records the top two numbers. He replaces the chit, shakes the container and draws another and records the top number on that chit. He replaces the chit and draws a third chit, this time reading the bottom number on the counter. The combination of the two digit numbers in the first two yields the new hex number the unit will be in. The plus or minus number read on the third draw is the new Zulu coordinate. If either the first or second draw yields a "Dstr" or "Brkf" chit, the procedure stops at that point and the effect is applied.

[15.3] PLACING THE RANDOMIZED UNIT ON THE STELLAR DISPLAY

At the end of the Neutralization Recovery Phase, after all units which were randomized/neutralized throughout the present Game-Turn are returned to normal, Players position their newly randomized units on the Stellar Display. If the position produced by the chit-draws is one which is within the limits of the Stellar Display, simply place the unit in that position (recording it on the SiMove Plot sheet) and place a Neutralization marker on the unit.

If the position is one that exceeds the limit of the Stellar Display, it must be adjusted just enough to bring the randomized unit back onto the Display. If the unit is exceeding the limit of the Stellar Display by virtue of a Zulu number that is too "high" or "low", simply reduce that number until the position is just within the outer Zulu limit. If the position is outside the Display because the second two digits of the hex number are too high or low, adjust those figures until the new position of the unit is just within the edge of the Display.

Example: A randomized unit is directed to be placed in LiteZulu 2937/+13. No such position exists. The hex number of the position is adjusted to 2935 (the hex number in the 2900 row which comes closest to the theoretical position) and the Zulu coordinate is reduced by two to "11", the upper limit of the Display at that point.

[16.0] INTRODUCTION TO THE SCENARIOS

GENERAL RULE: StarForce is composed of scenarios, each of which presents a given game situation that Players may set up and compete in. Each scenario is a self-contained module which uses only the rules and scenario information.

CASES:

[16.1] THE RACES AND THEIR STAR SYSTEMS

Each of the three races have their own natural star systems: their home system and the colonies. Note that all the systems inhabited prior to First Stellar Peace are listed even though some were not colonized until during the course of the game, and others remained neutral during many of the wars, and thus do not appear in the scenarios. A pronunciation guide is given for each of the major stars.

[16.11] Human Race and its systems:

  • Home system: Sol, 2020/0 (Sole)
  • Colonies:
    1. Alpha Centauri, 1821/-4, colonized by Sol; (AL-fah-SEN-tor-ee)
    2. Tau Ceti, 3015/-3, colonized by Sol; (Tau SE-tee)
    3. Epsilon Eridani, 2713/-2, colonized by Sol; (EP-se-lon Ear-e-DON-ee)
    4. 82 Eridani, 3009/-14, colonized by Tau Ceti
    5. Epsilon Indi, 2523/-10, colonized by Sol; (EP-se-lon IN-dee)
    6. Delta Pavonis, 2427/-18, colonized by Epsilon Indi; (DELL-tah Pah-VOH-niss)
    7. Eta Cassiopeiae, 3018/+15, colonized by Sol; (A-tah KASS-see-oh-PAY-uh)

[16.12] L'Chal-Dah Race and Its Systems:

  • Home system: Sigma Draconis, 2326/+17; (SIG-mah drah-KOH-niss)
  • Colonies:
    1. HR 8832, 3223/+18;
    2. 61 Cygni, 2626/+7; (SIG-nee)

[16.13] Rame Race and its Systems:

  • Home system: 70 Ophiuchi, 2036/+1; (Oh-FEE-oo-kee)
  • Colonies:
    1. 36 Ophiuchi, 1636/-8
    2. HR 7703, 2833/-11

[16.2] HOW THE SCENARIOS ARE ORGANIZED

Each of the scenarios is organized on an identical basis. It begins with the title and a brief introduction placing it within the framework of the Future Notes. Then each Player's available stellar system, which automatically have StarGates, are listed, as well as the number and initial placement of his StarForces. This section is titled "Orders of Battle and Deployment".

After these deployment instructions, the scenario's Victory Conditions are detailed. This dictates the objectives of the Players in the game. Occasionally a single objective is shared by the Players, sometimes a general condition must be achieved by any of the Players and occasionally totally different conditions are tailored for a given Player.

After this, Special Rules are detailed, if there are any necessary in that scenario. These may modify the standard rules, indicate the use of the additional Xenophobe rules, or give one Player a specific advantage, such as a free plot prior to the nominal start of the game.

Generally speaking, the scenarios are not limited by a time limit, in Game-Turns. They may go on forever, until the Victory Conditions are fulfilled.

Finally, the scenario recommends in what form it should be played: as a Basic Game, or Advanced, or possibly some combination of the two. Thus the scenarios are related to the rules for the maximum Player enjoyment.

[16.3] SETTING UP THE GAME EQUIPMENT TO PLAY THE SCENARIOS

[16.31] Take the Game Map and back-fold it along the machine-made folds. This will make the map lie flat on the table. Small pieces of masking tape (not permanent, cellophane tape) may be used at the corners to hold the map against accidental brushes of the hand. Ideally, Players should get themselves a piece of 24x36x1/16th inch Plexiglas to place over the map. This can be obtained at most hardware and building supply stores. Although it will cost about $10 for such a sheet of plastic, its a good one-time investment that can be used with all SPI game maps to provide a perfectly flat, one-piece playing surface.

[16.32] Place the map on a large, smooth table and arrange seating on opposite sides of long edges of the map. Place the game box with the counters sorted in it, at one end of the map and the rules booklet at the other end. Provide each Player with a pencil and a few sheets of the SiMove pad as well as some scrap paper.

[16.33] Provide two wide-mouthed, opaque containers, one for the Decimal Randomizer chits and one for the Stellar Randomizer chits.

[16.34] Chose the scenario to be played and deploy the forces called for in the order of battle. Begin the game.

[17.0] SCENARIO 1, THE ALPHA CENTAURI CAMPAIGN

After the development of telesthetic powers, the Solar Hegemony established a permanent colony at Alpha Centauri, the nearest stellar system. After several years of developing their own economy and StarGate, the colony declared independence. Sol dispatched a group of StarForces which neutralized the StarGate and seized its mechanisms. The first Human interstellar war was over in less than one day.

[17.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Sol Player: 2020/0 (Sol)4
Alpha Centauri Player: 1821/-4 (Alpha Centauri)1

[17.3] VICTORY CONDITIONS

Sol must permanently neutralize the Alpha Centauri StarGate within four Tac-Turns (or Combat Segments) of first entering the Tactical Display to win. If not, Alpha Centauri "wins".

[17.4] SPECIAL RULES

none

[17.5] RECOMMENDED FORMAT

This scenario is intended to teach the basic mechanics of StarForce. It is not recommended for balance. Players should use the Advanced Game.

[18.0] SCENARIO 2, THE EPSILON ERIDANI CAMPAIGN, 2405 A.D.

[18.1] INTRODUCTION

Sol has now colonized three star systems. One of them, Epsilon Eridani, has decided to split from the Solar Hegemony and attempt to seize a newly accessible habitable system, Epsilon Indi (2523/-10), for its own.

[18.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Solar Hegemony Player: 2020/0 (Sol)4
Epsilon Eridani Player: 2713/-2 (Epsilon Eridani)3

[18.3] VICTORY CONDITIONS

Either side must hold Epsilon Indi system at the beginning and end of two consecutive Stellar Game-Turns (this is termed "occupation" and is used in other scenarios) or permanently neutralize the opposing force's StarGate. Permanent neutralization of the Enemy StarGate takes precedence over holding Epsilon Indi.

[18.4] SPECIAL RULES

The Epsilon Eridani forces may make full Stellar shift before the beginning of the first Game-Turn and the simultaneous plotting of both forces.

[18.5] RECOMMENDED FORMAT

This is another scenario intended to familiarize Players with the StarForces rules. It may be played with equal enjoyment either with the Basic Game rules or the Standard Game rules. Do not use the Reserve StarForces Optional Rule (32.0).

[19.0] SCENARIO 3, THE RISE OF THE HUMAN LEAGUE, 2415 A.D.

[19.1] INTRODUCTION

Following the successful revolt of Epsilon Eridani (2405 A.D.), the Solar Hegemony collapsed and was replaced by the Pan-Human Hegemony (PHH). The PHH was still Sol-oriented, although not as much as the older Solar Hegemony. However, a still more frontier-oriented society, the Human League (HL), arose and challenged the PHH by seizing Epsilon Indi (which has no StarGate in this scenario).

[19.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
PHH Player: 2020/0 (Sol)5
PHH Player: 1821/-4 (Alpha Centauri)3
HL Player: 3015/-3 (Tau Ceti)3
HL Player: 2713/-2 (Epsilon Eridani)2
HL Player: 3009/-14 (82 Eridani)2

[19.3] VICTORY CONDITIONS

PHH Player must permanently neutralize two enemy StarGates, or re-occupy (see 2405 A.D. Victory Conditions) Epsilon Indi and permanently neutralize one enemy StarGate. HL Player must neutralize StarGate at Sol or Alpha Centauri. The first Player to accomplish his Victory Conditions is the winner. If both accomplish them in the same Game-Turn, the Human League wins.

[19.4] SPECIAL RULES

The Human League Force may make one free Stellar shift prior to the beginning of the first Game-Turn.

[19.5] RECOMMENDED FORMAT

This scenario may be played with equal pleasure either in the Basic or Advanced Game modes, though the latter is more intriguing.

[20.0] SCENARIO 4, 2430 A.D. PHH - HL SHOWDOWN

[20.1] INTRODUCTION

The antagonism between the PHH and HL grew worse. Essentially the PHH wanted centralization on Sol and expansion limited to already-inhabitable planets. The HL desired more independence from the Home System and the terraforming of systems not naturally habitable. The proponents of either system were in near equilibrium when the final break took place.

[20.2] ORDERS OF BATTLE AND DEPLOYMENT [see Special Rule 20.4]

Star Systems and StarGatesStarForces
2020/0 (Sol)5
1821/-4 (Alpha Centauri)3
3015/-3 (Tau Ceti)3
2713/-2 (Epsilon Eridani)3
2523/-10 (Epsilon Indi)1
3009/-14 (82 Eridani)2
2427/-18 (Delta Pavonis)1

[20.3] VICTORY CONDITIONS

The Player with the greater number of StarForces at the beginning of the game must permanently neutralize two enemy StarGates. The Player with the lesser number of StarForces must permanently neutralize one enemy StarGate. If identical in number of StarForces, the first Player to permanently neutralize two Enemy StarGates is the winner.

[20.4] SPECIAL RULES

In this scenario system-control is assigned randomly. One Player picks a chit for each of the above-listed star systems: an even number indicates that he receives the system and its StarForces, and odd number indicates that his opponent does. As the chits are drawn from the Decimal Randomizer, do not replace them until every system has been assigned.

[20.5] RECOMMENDED FORMAT

This is a fast-playing and variable scenario. It is best played by the full Advanced Game version. Players should feel free to make a deliberate assignment of systems if they find a mix which balances well in relationship to their style of play.

[21.0] SCENARIO 5, 2451 A.D. L'CHAL-DAH CONTACT

[21.1] INTRODUCTION

Ever since first venturing out of the Solar system, humans awaited First Contact. Finally, in 2451, a small fleet of L'Chal-Dah from Sigma Draconis has stumbled across the nearest Human colony, Eta Cassopeiae, defended only by its own StarGate. They attempt to probe and/or capture, with access to their own StarGate at 61 Cygni by break-off.

[21.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Human Player: 2020/0 (Sol)2
Human Player: 1821/-4 (Alpha Centauri)1
Human Player: 3015/-3 (Tau Ceti)1
Human Player: 2713/-2 (Epsilon Eridani)1
Human Player: 3009/-14 (82 Eridani)0
Human Player: 2523/-10 (Epsilon Indi)1
Human Player: 3018/+15 (Eta Cassiopeiae)0
Human Player: 2427/-18 (Delta Pavonis)0

[21.3] VICTORY CONDITIONS

Human Player must permanently neutralize all Enemy StarGates; L'Chal-Dah Player must permanently neutralize the Sol StarGate, or any other two Human StarGates.

[21.4] SPECIAL RULES

The Game begins with a Tactical Display deployment of two L'Chal-Dah StarForces, and the deployment of the defending Eta Cassiopeiae StarGate. Play proceeds on the Tactical Display before any Stellar Display plotting.

[21.5] RECOMMENDED FORMAT

This is definitely most enjoyable as a full Advanced Game with full optional rules.

[22.0] SCENARIO 6, 2462 A.D. SECOND PHH - HL WAR

[22.1] INTRODUCTION

Although the PHH had been defeated in 2430 A.D., the basic cause of the conflict had yet to be resolved. Both sides strengthened themselves as much as possible, and tightened their control over other systems. Thus when hostilities again broke out the opposing sides were more clearly delineated.

[22.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Human League Player: 3015/-3 (Tau Ceti)3
Human League Player: 2713/-2 (Epsilon Eridani)2
Pan-Hegemony Player: 2020/0 (Sol)4
Pan-Hegemony Player: 1821/-4 (Alpha Centauri)2
Variable Allegiance [see Special Rules]: 3009/-14 (82 Eridani)2
Variable Allegiance [see Special Rules]: 2427/-18 (Delta Pavonis)2
Variable Allegiance [see Special Rules]: 2523/-10 (Epsilon Indi)1

[22.3] VICTORY CONDITIONS

The Player with the greater number of StarForces at the beginning of the game must permanently neutralize two Enemy StarGates. The Player with the lesser number of StarForces must permanently neutralize one Enemy StarGate. If identical in number of StarForces, the first Player to neutralize two Enemy StarGates is the winner.

[22.4] SPECIAL RULES

One Player picks a chit for each of the above listed variable star systems: an even number indicates that he receives the system and its StarForces, an odd number indicates that his opponent does. (see 22.3)

[22.5] RECOMMENDED FORMAT

This scenario is best played by the full Advanced Game version.

[23.0] SCENARIO 7, 2465 A.D. REVOLT OF EPSILON INDI

[23.1] INTRODUCTION

Soon after the PHH-HL War of 2462 A.D. which had ended in an indecisive victory for the Pan-Human Hegemony, Epsilon Indi revolted against PHH control. Most of the members of the old Human League rallied to support Epsilon Indi, with the exception of Epsilon Eridani, who, having been beaten twice by the PHH, decided to switch sides. The L'Chal-Dah chose to remain neutral, intervening on the side of the PHH only when victory became apparent.

[23.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Pan-Human Hegemony Player: 2020/0 (Sol)4
Pan-Human Hegemony Player: 1821/-4 (Alpha Centauri)2
Pan-Human Hegemony Player: 2713/-2 (Epsilon Eridani)1
Epsilon Indi Player: 2523/-10 (Epsilon Indi)2
Epsilon Indi Player: 3015/-3 (Tau Ceti)2
Epsilon Indi Player: 2427/-18 (Delta Pavonis)2
Epsilon Indi Player: 3009/-14 (82 Eridani)1

[23.3] VICTORY CONDITIONS

The PHH Player wins by permanently neutralizing the Epsilon Indi StarGate or any other two Enemy StarGates. The Epsilon Indi Player wins by permanently neutralizing the Sol StarGate or any other two Enemy StarGates.

[23.4] SPECIAL RULES

The first Player to permanently neutralize an Enemy StarGate receives on the following Game-Turn:

L'Chal-Dah Forces:

StarGatesStarForces
2326/+17 (Sigma Draconis)2
2626/+7 (61 Cygni)1
3223/+17 (HR 8832)1

See Special Rules on inter-race cooperation in 2487 A.D. Scenario (27.4). If both Players neutralize an Enemy StarGate on the same Game-Turn the L'Chal-Dah remain neutral.

[23.5] RECOMMENDED FORMAT

This scenario is best played with the full Advanced Game version.

[24.0] SCENARIO 8, 2476 A.D. THE WAR WITH THE RAME

[24.1] INTRODUCTION

After the absorption of the L'Chal-Dah into the Human League on Associate basis, the combined leagues made contact with yet a third, more alien race, the Rame, originating from 70 Ophiuchi. After some years of relatively peaceful contact, the Human League attempted to subjugate the Rame.

[24.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Rame Player: 2036/+1 (70 Ophiuchi)6
Rame Player: 1636/-8 (36 Ophiuchi)0
Rame Player: 2833/-11 (HR 7703)0
Human League Player, Human: 2020/0 (Sol)6
Human League Player, Human: 1821/-4 (Alpha Centauri)0
Human League Player, L'Chal-Dah: 2326/+17 (Sigma Draconis)4
Human League Player, L'Chal-Dah: 2626/+7 (61 Cygni)0

[24.3] VICTORY CONDITIONS

HL Player must permanently neutralize all of Rame Player's StarGates, without having the Sol or Sigma Draconis StarGates neutralized. Rame Player wins if he avoids this condition for twenty Stellar Game-Turns.

[24.4] SPECIAL RULES

See Special Rules for 2487 A.D. on inter-race cooperation (27.4).

[24.5] RECOMMENDED FORMAT

This should be played as an Advanced Game, with rule 32.0, Reserve StarForces.

[25.0] SCENARIO 9, 2480 A.D. L'CHAL-DAH EXPANSION

[25.1] INTRODUCTION

The L'Chal-Dah continued their new policy (begun in 2465 A.D.) of expansion and activity in stellar politics by attempting to strengthen their power base at the expense of the Rame.

[25.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
L'Chal-Dah Player: 2326/+17 (Sigma Draconis)3
L'Chal-Dah Player: 2626/+7 (61 Cygni)1
L'Chal-Dah Player: 3223/+17 (HR 8832)3
Rame Player: 2036/+1 (70 Ophiuchi)3
Rame Player: 1636/-8 (36 Ophiuchi)1
Rame Player: 2833/-11 (HR 7703)1

[25.3] VICTORY CONDITIONS

The first Player to permanently neutralize any Enemy Home System StarGate, or any other two Enemy StarGates wins.

[25.4] SPECIAL RULES

The L'Chal-Dah Forces may make one full Stellar shift before the simultaneous plotting of both forces.

[25.5] RECOMMENDED FORMAT

This scenario is best played using the full Advanced Game version.

[26.0] SCENARIO 10, 2482 A.D. WAR OF THE DEFENSE LEAGUE

[26.1] INTRODUCTION

After the Rame were defeated by the L'Chal-Dah in 2480 A.D., the two formed the L'Chal-Dah dominated Defense League. Renouncing their associate status in the PHH, the L'Chal-Dah attempted to free themselves from human interference, with the ultimate goal of defeating the Humans entirely (perhaps then giving the Humans associate status in their league).

[26.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Defense League Player, Rame: 2036//1 (70 Ophiuchi)1
Defense League Player, Rame: 1636/+1 (70 Ophiuchi)1
Defense League Player, Rame: 2833/-11 (HR 7703)1
Defense League Player, L'Chal-Dah: 2326/+17 (Sigma Draconis)2
Defense League Player, L'Chal-Dah: 2626/+7 (61 Cygni)1
Defense League Player, L'Chal-Dah: 3223/+17 (HR 8832)1
Pan-Human Hegemony Player: 2020/0 (Sol)5
Pan-Human Hegemony Player: 1821/-4 (Alpha Centauri)

Transcriber's note: the orders of battle above are reproduced as printed. Two entries are printed with values that differ from the system listings in 16.1 and may be misprints: the Rame entry "2036//1" (printed with a doubled slash) and the Rame entry "1636/+1 (70 Ophiuchi)", where 16.13 lists 36 Ophiuchi at 1636/-8. They are kept as printed here; the sign and the system name of the second entry should be checked against the printed source.

[26.3] VICTORY CONDITIONS

The PHH Player wins by permanently neutralizing the StarGates at Sigma Draconis and 70 Ophiuchi, or any other four Enemy StarGates. The DL wins by permanently neutralizing the Sol StarGate or preventing PHH victory. The game ends after the completion of twenty Game-Turns. [26.4] SPECIAL RULES

The L'Chal-Dah and the Rame may not use one another's StarGate or StarForces to improve shift radius, although they are fully compatible in combat (see 27.4 for more elucidation).

[26.5] RECOMMENDED FORMAT

This scenario is best played using the full Advanced Game version.

[27.0] SCENARIO 11, 2487 A.D. THE WAR FOR IDENTITY [Three-Player Game]

[27.1] INTRODUCTION

After several years, the Human League with its Associates, L'Chal-Dah and Rame, collapsed. Three factions emerged: the Pan-Sentient League (advocating complete freedom for all biologic and cybernetic sentients); the shrunken HL; and a resurgent PHH. The First Interstellar Peace established the PSL as dominant throughout the sphere.

[27.2] ORDER OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
PSL Player: 2326/+17 (Sigma Draconis)4
PSL Player: 3223/+17 (HR 8832)0
PSL Player: 2626/+7 (61 Cygni)0
PSL Player, Rame: 2036/+1 (70 Ophiuchi)3
PSL Player, Rame: 1636/-8 (36 Ophiuchi)0
PSL Player, Rame: 2833/-11 (HR 7703)0
PHH Player: 2020/0 (Sol)3
PHH Player: 2523/-10 (Epsilon Indi)2

[27.3] VICTORY CONDITIONS

A Player loses the scenario when any two of his colonial StarGates are permanently neutralized, or when his home system StarGate is permanently neutralized. However, his units remain in play and he may continue playing (acting as a "spoiler" or allying with another Player). The last Player who has not lost, wins. Note that Tau Ceti (3015/-3) is the Human League "home" system.

[27.4] SPECIAL RULES

1. Inter-Race Compatability and Cooperation: The StarGate of one race may not be linked to the StarGate of another race in order to make a Gate-to-Gate shift. Nor may the StarGate or StarForce of one race enhance its position for an in-shifting StarForce of another race. The StarForce of one race may make a simple Gate shift from the StarGate of another cooperating race and a Gate-to-Gate shift if both StarGates are owned by the same race. Forces of different races are fully compatable in combat.

2. Alliances: Players may confer with each other and make verbal deals, they are bound only by what they actually plot each Combat Segment (or each Tac Plot Phase). Players indicate when plotting whether or not they wish their combat effect to affect both of the other Players in a particular LiteZulu or only one (if, indeed, both are in the LiteZulu). In the basic game, they must also indicate whether or not they wish their defensive allocation to be added to that of another Player (this is only operative if that other Player has also indicated mutual defense). If three Players are contesting the same LiteZulu and none are cooperating in combat, each Player makes separate resolutions of combat against each other Player, using his full allocated Strength against Basic Game (in the Advanced Game there is less of a problem since all hostile casts are additive and no defensive effects are ever additive).

Transcriber's note: the printed sentence above reads "using his full allocated Strength against Basic Game"; the words "In the" appear to be missing before "Basic Game" in the printed text. Transcribed as printed.

3. Two-Player Version: There are only two active roles: the Pan-Sentient League and the Pan-Human Hegemony. The Human League is considered to be wavering and factionated, and until it is committed, its forces and systems are inoperative and do not count towards victory. Each Game-Turn (at the end of the Stellar Plot Phase) each Player draws a chit from a set of ten Decimal Randomizers put aside to represent the political wavering of the HL. Each Player adds the chit to those drawn on previous Game-Turns (these political chits are not returned to the special Randomizer). The Player who achieves a total of 23 (or more) "political chit points" has "convinced" the Human League to join his cause and gets the use of HL forces at the beginning of the next Game-Turn (the Inter-Race Compatability rules still apply). If either one (or both) of the Players loses one of his colonial StarGates before either Player has 23 political points, that Player must skip a turn at chit-pulling on the Plot Phase immediately following the permanent neutralization of the StarGate. If one Player wins before either Player reaches 23, both Players alternately draw all the remaining chits to see if the Human League decides to declare war on the winner (in which case, the HL forces would be operated by the losing Player; the systems and forces of the initially losing League or Hegemony are inoperative and are removed from play). The victory conditions remain the same.

[27.5] RECOMMENDED FORMAT

2487 A.D. should be played with Basic Game rules, and the 15.0 rules section of the Advanced Game. It is still functional with all of the Advanced Game rules.

[28.0] SCENARIO 12, 2505 A.D. THE WAR FOR THE LEAGUE [Three-Player Game]

[28.1] INTRODUCTION

The PSL temporarily lapsed when the Pan-Human hegemony rose to power again in two systems. The Rame and L'Chal-Dah pulled out of the PSL, while the other human systems remained neutral. The conclusion of this war saw the end of intra-sphere rivalries. The PSL was re-established with unanimity.

The three sides essentially fought for control over the new colony of Delta Pavonis, which had yet to orbit and crew its StarGate.

[28.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Rame Player: 2036/+1 (70 Ophiuchi)4
Rame Player: 1636/-8 (36 Ophiuchi)0
Rame Player: 2833/-11 (HR 7703)0
L'Chal-Dah Player: 2326/+17 (Sigma Draconis)4
L'Chal-Dah Player: 3223/+17 (HR 8832)0
L'Chal-Dah Player: 2626/+7 (61 Cygni)0
PHH Player: 2020/0 (Sol)5
PHH Player: 2523/-10 (Epsilon Indi)0

[28.3] VICTORY CONDITIONS

Players lose the game if their home system StarGate is permanently neutralized (see 2487 A.D.); Players may win by controlling Delta Pavonis LiteZulu (2427/-18) for four consecutive Game-Turns.

[28.4] SPECIAL RULES

See 27.4. L'Chal-Dah is uncommitted in a two-Player version.

[28.5] RECOMMENDED FORMAT

This scenario is best done as a Basic Game with Advanced rule 15.0 and Optional Rule 33.0, FakerForces.

[29.0] SCENARIO 13, 2775 A.D. THE FIRST XENOPHOBE INCURSION

[29.1] INTRODUCTION

After two and one-half centuries of generally pacific conduct and gradual terraforming of all the depicted star systems, the PSL sphere was invaded by a rabid species known only as the "Xenophobes". They began inducing novas in PSL stars (causing them to explode) incinerating the inhabitants. Not knowing where they were coming from, and the thought pattern being so alien as to be largely undetectable, the PSL StarForces were forced to search the periphery of its Known Volume for the Xenophobe "base camp" StarGates. The Xenophobes were inhibited by smaller shifts due to unfamiliarity with the PSL Volume.

[29.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Xeno Player: three StarGates, positioned randomly (See 31.0 Special Rules)12 (total)
PSL Player: All systems on the Stellar Display (except 1511/+1, 1812/-2, 2734/+2)6 (deployed as desired)

Beginning with Game-Turn Two, the PSL receives one additional StarForce every even-numbered Game-Turn, until twelve additional StarForces have been received. StarForces appear at the start of the plot Phase in any LiteZulu having an un-neutralized PSL StarGate.

[29.3] VICTORY CONDITIONS

Scenario continues until all Xeno StarGates have been destroyed or all PSL Home Systems stars (Sol, Sigma Draconis, and 70 Ophiuchi) have gone nova. At that time, Victory is determined according to the number of Victory Points, the Player with the higher total winning.

Xeno Victory Points:

  • 20 Points for each PSL home system destroyed

  • 10 Points for each secondary star system destroyed

  • 3 Points for any tertiary system destroyed

  • 5 Points for each "destroyed" result against PSL StarForces PSL Victory Points:

  • 25 Points for permanent neutralization of Xeno StarGate

  • 1 Point for each "destroyed" result against Xeno StarForces

Xenophobe Player wins automatically if all the PSL Home systems are destroyed.

[29.4] SPECIAL RULES

See section 31.0, Xenophobe Special Rules.

[29.5] RECOMMENDED FORMAT

Players should use the Basic Game modified by the use of Randomization rules (15.0) for both Overshift results and combat results. Players may add optional rules to suit their taste for complexity. Playing the Xenophobe scenarios using the Advanced Game can be interesting, but will be extremely time consuming (seven to twelve hours of play would not be unusual). See the Special Rules, 31.0.

[30.0] SCENARIO 14, 2785 A.D. THE SECOND XENOPHOBE INCURSION

[30.1] INTRODUCTION

After the First Incursion of the Xenophobes had been driven off by the PSL, a watchful peace ensued. Approximately 30 billion PSL sentients died in the First Incursion, creating a shortage of telesthetics and forcing a reduction in the number of PSL StarForces. 10 years after the First Incursion, the Xenophobes returned.

[30.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Xeno Player: two StarGates, positioned randomly (see 31.0 Special Rules)8 (total)
PSL Player: All systems on the Stellar Display (except 1511/+1, 1812/-2, 2734/+2)4

Beginning with Game-Turn Two, the PSL receives one additional StarForce every even-numbered Game-Turn until a total of eight additional StarForces have been received. These StarForces appear at any LiteZulu having an un-neutralized PSL StarGate.

[30.3] VICTORY CONDITIONS

Essentially the same as 29.3. See 31.6 in the Special Rules.

[30.4] SPECIAL RULES

See 31.0.

[30.5] RECOMMENDED FORMAT

Same as recommended in 29.5.

[31.0] SPECIAL RULES FOR THE XENOPHOBE SCENARIOS

GENERAL RULE: Since a special situation is being simulated in the two Xenophobe incursion scenarios, a number of special rules must be applied to the game.

CASES:

[31.1] DEPLOYMENT OF XENOPHOBE STARGATES

In the First Incursion, three Xenophobe StarGates must be deployed; in the Second Incursion, two must be deployed. Use the following random procedure:

[31.11] Draw two chits (secretly) from the Stellar Randomizer. This will indicate the hex position of the first Xenophobe StarGate. The Xenophobe Player then decides if the hex position of the first StarGate will be two Lites distant from the positive outer limit of the Stellar Display or two Lites distant from the negative outer limit. For example, if the chits drawn indicate hex number 2033, the first Xeno StarGate could be positioned at LiteZulu 2033/+19 or 2033/-19. Whichever the Xeno Player chooses, the remaining Xeno StarGates must be positioned on the same outer limit of the Stellar Display.

The hex numbers of the remaining Xeno StarGates are chosen in the same manner. If any of the hex numbers drawn are ones outside the two-dimensional limits of the Display, the number is adjusted in a manner similar to that described in 15.3. The positions of Xeno StarGates are not known to the PSL Player (and the StarGate counters are not displayed on the map). In order to discover them the PSL Player must shift adjacent to them.

[31.12] After positioning his StarGates, the Xenophobe Player sets up his available StarForces in those same positions, in any distribution he desires.

[31.2] UNKNOWN SPACE AND ITS EFFECTS UPON SHIFTING

For the PSL Player, unknown space is defined as any LiteZulu outside the normal Zulu limits of the Stellar Display. For the Xenophobe Player, unknown space is defined as any LiteZulu within the normal Zulu limits of the Stellar Display. Additionally, any LiteZulu which is further than ten Lites from a Xeno StarGate is considered as unknown space to the Xeno Player, even if it is outside the normal Zulu limit of the Stellar Display.

[31.21] Effects of Unknown Space on Shifting: Whenever the destination LiteZulu of a Stellar shift is in unknown space, the Maximum safe shift is reduced to one Lite for a normal shift (plot code "S") and to five Lites for a Gate assisted shift (plot code "GS"). Other types of shifts are unaffected (i.e., plot codes "ES", "EGS" and "GGS"). See the Maximum Shift Table on the map. If the destination LiteZulu is in known space and the point of origin is in unknown space, then normal shift ranges apply.

[31.22] Entering a LiteZulu Held by an Enemy StarGate: Players do not add four Lites to the effective distance of their shift when entering an Enemy StarGate-LiteZulu. This is a suspension of standard case 7.31. This means that in order to enter an Enemy StarGate-LiteZulu without risk of Overshift, a Friendly unit must be adjacent to the StarGate or within five Lites if shifting with the aid of a Friendly StarGate.

[31.3] MODIFIED SEQUENCE OF PLAY AND HIDDEN MOVEMENT

Since the two opposing space forces are telesthetically "blind" to each other over any appreciable distance, all shifting is completely hidden, i.e., it is plotted without displaying any counters on the Stellar Display until a combat situation is imminent.

The Xenophobe Player secretly plots his projected shifting for all the Game-Turns up to and including the Game-Turn in which he will enter a LiteZulu adjacent to a PSL StarGate. He does not at this time execute this plot. The PSL Player plots and executes Game-Turn by Game-Turn the shifts he desires his forces to make. As he executes his shifts he announces what Game-Turn he is executing. If the Game-Turn he is executing is the Game-Turn in which the Xenophobe Player has forces adjacent to a PSL StarGate, the Xenophobe Player informs the PSL Player of this fact after the PSL has executed that Game-Turn's plot. He also tells the PSL to which StarGates he is adjacent (but not the composition of the forces which are adjacent) and the exact position of his adjacent forces. Both Players then plot and execute the next Game-Turn. Assuming that the Xenophobe Player enters a PSL StarGate LiteZulu in that Game-Turn, a combat situation would ensue. At the end of that Game-Turn, the Xenophobe Player would inform the PSL if there are any Xeno forces adjacent to PSL StarGates. If not, the Xeno Player would make another series of advance plots and the procedure described above would again be pursued. If there are Xeno forces adjacent, only the next Game-Turn's plot would be written after the Xeno Player informs the PSL Player which StarGate LiteZulus he is adjacent to.

[31.31] If the PSL Player is searching unknown space in an attempt to locate the Xeno StarGates, he must tell the Xeno Player Game-Turn-by-Game-Turn which unknown LiteZulus he is shifting into. If one or more of these LiteZulus is adjacent to a Xeno StarGate the Xeno Player must reveal the position of that StarGate.

The PSL Player does not have to reveal the size of the forces with which he is searching. When the PSL finds a Xeno StarGate the Xeno Player cancels his plot back to the Game-Turn of discovery and both Players proceed to write and execute their shifts for the next Game-Turn. For example, if the Xeno Player had plotted to be adjacent to a PSL StarGate on Game-Turn Fifteen but the PSL has come adjacent to a Xeno StarGate on Game-Turn Twelve, the Xeno Player would cancel his plots for Game-Turns Thirteen through Fifteen and write a revised plot for Game-Turn Thirteen. As long as one or the other Player is adjacent to an Enemy StarGate, the plotting and execution takes place on a normal Game-Turn by Game-Turn basis. Players always inform each other of this adjacency in the Zulu Coordinate Readout Segment of the Game-Turn in which the condition exists.

[31.32] If the Xeno Player has StarForces in a LiteZulu in which the PSL is searching (or if the PSL has forces in the same LiteZulu adjacent to his StarGate that the Xeno Player is revealed to be in) then the Xeno plot is cancelled back to that point and a combat situation ensues. This allows Players to set up ambushes for each other.

[31.33] If at any time during his projected plot the Xeno Player will be making Overshifts, he must openly resolve these (in advance of actually executing them) but he need not tell the PSL Player the forces involved. Of course, Overshifts which apply to cancelled plots are themselves cancelled unless the Xenophobe Player maintains those plots after having had the opportunity to cancel them.

Similarly, the PSL Player must openly resolve any Overshifting he performs on a Game-Turn by Game-Turn basis.

[31.33] If there occurs a fifteen Game-Turn period in which the Xeno Player does not make an attack on a PSL StarGate, the Xeno Player forfeits the game.

Transcriber's note: the printed text numbers both of the two paragraphs above "31.33"; they are transcribed with their printed numbers.

[31.4] FIRST GAME TURN RULES [FIRST INCURSION ONLY]

In the First Incursion scenario, the PSL is completely unaware of the existence and threat of the Xenophobes until they make their first attack. Additionally, the Xenophobes do not know the full extent of the PSL hegemony and are a hair-trigger bloodthirsty race of psychopaths. To simulate this the following provisions are applied:

[31.41] Pre-Game Plot: Before the game actually begins for both Players, the Xenophobe Player may plot and execute as many as ten Game-Turns of shifting. During this time the PSL Player does nothing. On or before the end of these ten pre-Game-Turns the Xenophobe Player must bring forces adjacent to one or more PSL StarGates. He then announces to the PSL Player that the next Game-Turn is the official start of the game, the "First" Game-Turn. Note that unlike all subsequent situations, the Xeno Player does not announce his positions nor the StarGates to which he is adjacent. He merely announces the fact of adjacency. In the first Game-Turn the Xenophobe Player must attack one or more PSL StarGates.

[31.42] Surprise Attack Provision: In the first Game-Turn (only) the Xenophobe Player may automatically destroy one PSL StarGate (and induce nova in its star) without having to resolve any combat in that LiteZulu regardless of the PSL forces present. All PSL StarForces present must immediately plot a break-off maneuver. If the Xenophobe Player is attacking more than one PSL StarGate and system in the first Game-Turn, he must designate which is to be the victim of the surprise attack before knowing whether or not there are PSL StarForces present. Any other systems being attacked on the first Game-Turn are resolved normally. None of the three home systems may be designated as the object of the surprise attack (even if only one system is attacked and it is a home system. In such a case the Xeno Player would lose the advantage of a surprise attack.). The surprise attack force must be at least two StarForces in strength.

[31.5] NOVA INDUCEMENT AND COMBAT RESOLUTION

The Xenophobe murderers use the star of the system as a weapon. By planting a Conversion Trigger in the heart of the sun they cause it to nova (greatly accelerate its energy output) in order to scorch the orbiting planets and destroy all life. In order to perform this triggering successfully, the StarGate defending the system must be dealt with first. The following cases simulate this:

[31.51] Nova Inducement: In the Basic Game, if the Xenophobe Player has one or more StarForces present in the PSL LiteZulu in which the StarGate has been eliminated (neutralized) he may cause the star to go nova in any Combat Segment following the elimination of the StarGate. One Xeno StarForce must be assigned to task of triggering the star, and it must be plotted to break-off in the Combat Segment in which the star is triggered. If it is randomized before it can break-off, the star is not triggered. If it successfully breaks-off, the star is triggered and the StarGate is destroyed permanently. Remaining opposing StarForces may remain behind to fight (but the outcome is academic, since the system has been destroyed).

[31.52] Nova Inducement in the Advanced Game: In order to plant the Conversion Trigger in the star, at least one Xeno StarForce must spend an entire Tac-Turn in the star's MiniLiteZulu. It must be in Stellar Mode and assign half its TelePoints to the task of planting the trigger (which actually is completed in the Position Revelation Phase of that Tac-Turn). If the Xeno StarForce is disrupted (or randomized) before that time, the trigger is not considered planted and the star will not go nova. The PSL StarGate must be in a disrupted (or neutralized) state during the planting of the trigger. In the Tac-Turn following the successful planting of the trigger, the Xeno StarForce must Tac-shift out of the MiniLiteZulu containing the star and attempt to execute a break-off maneuver in the Second Execution Phase. The star goes nova during the Combat Cast Segment of the First Execution Phase (After successful planting of the trigger) and any StarForces in the MiniLiteZulu with the star are destroyed in the Results Application Phase. Any remaining StarForces may still contest the LiteZulu but they may not enter the MiniLiteZulu containing the star. The StarGate is not permanently destroyed until the resolution of the Tactical Sequence.

[31.53] When playing either Xenophobe scenario, Players should use the Basic Game system (preferentially) and modify it by using rule 15.0, Randomization, instead of using total elimination. When Xenophobe units are randomized (whether as a result of combat or Overshifting) they are removed from the game for three entire Game-Turns following the one in which they were randomized. They reappear (in a normal, ready state) at the beginning of the fourth Game-Turn after randomization. They reappear at any un-neutralized Xeno StarGate of the owning Player's choice. When Xeno units randomize (either in combat or shifting) the Xeno Player should still draw two chits in order to receive a possible destroyed result. When PSL units are randomized (even when operating in unknown space) they follow the randomization procedure as detailed in 15.0 and must adjust their final position as per 15.3, always re-positioning themselves in known space.

[31.54] When using the Basic Game Combat Resolution Table, the attacking Player determines how the defending Player will take his losses.

[31.6] FIRST GAME-TURN RULES AND STANDARD RESULTS OF FIRST INCURSION [SECOND INCURSION ONLY]

The Second Incursion found the PSL weaker but warier. No surprise attack could catch them completely off-guard. To simulate this, use the following provisions in the Second Incursion Scenario:

[31.61] Pre-Game Plot: The Xenophobe Player has a pre-game plot of five shifts during which the PSL Player does nothing. If at the end of those five pre-Game-Turns, the Xenophobe Player is not adjacent to a PSL StarGate, he merely informs the PSL Player that the First Game-Turn is about to begin. The Xenophobe Player has five official Game-Turns in which to come adjacent to one or more PSL StarGates for the first time. There is no surprise attack; all PSL StarGates and forces perform normally.

[31.62] Standard Results of the First Incursion: As a result of the First Incursion, the following star systems do not have StarGates and do not count for Second Incursion Victory points: 2036/+1 (70 Ophiuchi), 2626/+7 (61 Cygni), 3018/+15 (Eta Cassiopeiae), 1521/+16, 1532/-3, 2026/0, 2228/-4, 2623/+11. Since all other PSL systems have StarGates, Players should use the StarGate markers to mark those systems that have had their StarGates destroyed.

[31.7] XENOLINK

Players may wish to combine the two Xenophobe scenarios into one long game. To do so, play the First Incursion scenario until all three Xeno StarGates are found and eliminated (neutralized) regardless of PSL home systems destroyed. When all three Xeno StarGates have been neutralized, assess the damage that the PSL has suffered and make the following force reductions (from the original eighteen PSL StarForces) for the Second Incursion, based on that damage:

  • A. Remove three PSL StarForces for each PSL home system destroyed.
  • B. Remove one PSL StarForce for each secondary colony destroyed.
  • C. Remove one PSL StarForce for each five tertiary systems destroyed (rounding fractions up).
  • D. Remove one PSL StarForce for every three PSL StarForces that suffered a destroyed result in the First Incursion.

Reduce the Xenophobe StarForce order of battle (the original twelve) by the following amount: One StarForce for each StarGate neutralized in the First Incursion (since all three must be neutralized in order for the First Incursion to end in a linked game, this reduction is academic). One Xenophobe StarForce for every two that received a destroyed result in the First Incursion.

Do not use the Standard Results of the First Incursion detailed in 31.62. Rather, use the actual results of the First Incursion as obtained in the game. Second Incursion Xenophobe StarGates must be placed on the same side of the Stellar Display as in the First Incursion (i.e., positive or negative).

A NOTE ON THE OPTIONAL RULES [Sections 32.0 through 37.0]

The Optional Rules are just that: rules which the Players may add to the game at their discretion. Players may use some, all, or none of the Optional Rules as they desire. The Optional Rules will always complicate a given scenario, so Players should proceed with caution and not feel compelled to add every (or any) Optional Rule. Some of the Optional Rules can be used as balancing elements for Players whose style of play matches the flavor that a given rule lends to a given scenario. There will be a necessary period of experimentation in which Players can discover which Optionals appeal to them. The most complicated game possible would be one which uses both Xenophobe scenarios in a linked Advance Game, employing all of the Optional Rules. This would not necessarily be the best game possible (and has a good chance of being the worst).

[32.0] RESERVE STARFORCES

GENERAL RULE: As much as one-third of a Player's current StarForce strength may be placed on reserve status in a given Game-Turn. Such units have the plot code "Rs" assigned to them in the Stellar Shift Plot Phase and may not shift during that Shift Execution Phase. After all normal Stellar shifts have taken place, and after it is known which LiteZulus are being contested, but before it is known exactly what forces are contesting the LiteZulus, the StarForces on reserve status have their reserve plot modified to indicate which of the contested LiteZulus they can be called into. A given unit cannot be slated as a reserve for more than one contested LiteZulu per Game-Turn.

CASES:

[32.1] HOW RESERVE STARFORCES ARE CALLED INTO CONTESTED LITEZULUS

After two Tac-Turns (or one Combat Segment in the Basic Game) have elapsed in a given LiteZulu, Players who have reserve StarForces on call to that LiteZulu may call them to appear at the beginning of the third Tac-Turn (or second Segment). Not all of the StarForces on call to that LiteZulu need be called in, nor need any be called in at that time; they may be called in at the beginning of some later Tac-Turn (or Combat Segment). Reserve StarForces may Overshift.

[32.11] Reserve StarForces called into a contested LiteZulu appear in Stellar Mode (meaning, in the Basic Game, they have a Combat Strength of "2") and must be plotted to appear (in the First Execution Phase) in a MiniLiteZulu which will be occupied by a Friendly, un-neutralized StarForce or StarGate which is already in the LiteZulu.

[32.12] In the Tac-Turn in which they appear, reserve StarForces may be plotted to perform any action which could normally be plotted for the Second Execution Phase of that Tac-Turn. No plot may be written for the First Execution Phase. They have 32 TelePoints available for plotting.

[32.13] Reserve StarForces are subject to the effects of any First Execution Phase Enemy casts which may be made into their MiniLiteZulu-of-appearance. Their Anti-cast depends upon what they have been plotted to do in the Second Execution Phase.

[32.2] LIMITATIONS ON RESERVE STARFORCES

[32.21] No more than one-third of a Player's total current StarForce strength (not counting neutralized StarForces) may be placed on reserve status in a given Game-Turn. This third is calculated by rounding down, but can never be rounded down to less than one StarForce eligible for reserve status.

[32.22] StarForces which have a reserve plot written for them in one Game-Turn may not have any other Stellar plot written for them in the following Game-Turn. If the Player wishes to take a unit off reserve status, he must not write any plot for that unit in the Game-Turn following that in which the "Rs" plot was last written for that unit.

[32.33] Neutralized units may not be placed on reserve status.

Transcriber's note: the printed text numbers this paragraph "32.33", the same number as the Enemy StarGates paragraph in 32.3 below; both are transcribed with their printed numbers.

[32.3] RESERVE STARFORCES AND STARGATES

[32.31] Friendly StarGates: Reserve StarForces may use the next-Game-Turn capacity of a Friendly StarGate in the LiteZulu in which they are being held in reserve. This is calculated exactly as described for the advance use of StarGate capacity for break-off (see 13.34).

[32.32] Reserve StarForces may not in any way use the capacity of the StarGate in the LiteZulu to which they are being called.

[32.33] Enemy StarGates: Reserve StarForces may be called into a LiteZulu in which there is an active Enemy StarGate. They are subject to the normal addition of four Lites to their nominal shift distance with the modification that for every Friendly StarForce which began the Tac-Turn (or Combat Segment) in the contested LiteZulu, they may reduce the addition by one Lite (until it is reduced to zero addition). In this calculation, StarForces which begin the Tac-Turn in a disrupted state count as one-half (i.e., there must be two Friendly disrupted StarForces in order to reduce the shift addition by one Lite). If the Enemy StarGate is itself disrupted at the time of the reserve call the standard distance addition is reduced to two Lites before calculating further reductions. Note that the presence of Enemy StarForces has no effect upon any of these calculations.

[32.4] SPOILING RESERVES

Enemy Units may attempt to spoil reserve forces by attacking them before they can be called. Such situations should be resolved first before resolving other contested LiteZulus.

[32.41] If reserve StarForces are challenged by Enemy StarForces while they are standing by on reserve, they are considered to be in Stellar Mode (in the Basic Game, this means they will have a First Combat Segment strength of "2" even though they began the Game-Turn in that LiteZulu). If the reserve forces were slated for a destination which called for the use of a Friendly StarGate, the reserve units so slated must deploy in the MiniLiteZulu of that StarGate (meaning in the Basic Game that they cannot attack nor be attacked in the First Combat Segment).

[32.42] Reserve StarForces which suffer a combat result, Tac shift, change to Battle Mode, or make a combat cast while standing by on reserve, immediately have their reserve plot cancelled (they may not be called that Game-Turn and are freed from the restrictions of 32.22). In the Basic Game, forces which a Player wishes to maintain on reserve status in a contested LiteZulu may not use their strength to attack and may not increase their strength to "3" after the First Combat Segment. They may only defend until the Player decides to release them from reserve status.

[32.43] If two or more LiteZulus are contested while having reserves standing by in them, Players must resolve them in order of "greatest involvement". "Greatest involvement" is ranked in the following order:

  1. Contested LiteZulu with Friendly Reserves standing by which has Friendly reserves on call to that position (i.e., a reserve with a reserve on call).
  2. Contested LiteZulu with the greatest number of forces standing by on reserve.
  3. Contested LiteZulu whose reserve is on call to the contested LiteZulu with the greatest total forces involved.

[32.44] If even when following the above priority of resolution, a conflict still arises (i.e., reserves standing by in a contested LiteZulu, while their reserve destination is being resolved), the Player may commit such reserves if he leaves behind forces which exceed the Enemy spoiling the force by at least one StarForce (a StarGate is equivalent to two StarForces in this calculation). Note that the Friendly StarGate in such a contested LiteZulu cannot perform a Gate Shift (GS) for the exiting Reserve StarForces.

[33.0] FAKERFORCES

GENERAL RULE: Each StarForce is composed of four Teleships. This rules allows StarForces to be broken up into four individual Teleships. These individual Teleships are known as FakerForces. Though they represent only a single ship, FakerForces are represented on the Stellar Display as StarForces, and are thus used to deceive the Enemy Player.

PROCEDURE: At the beginning of any Game-Turn in the scenario, Players may split their StarForces into FakerForces. No more than 10% of a Player's total StarForces may be split in this manner (round fractions up, i.e., 10% of eleven equals two StarForces which equal eight FakerForces). FakerForces are represented by StarForce counters for all purposes, and Players must make a notation on their plot sheets as to which StarForces are actually FakerForces. The true composition of FakerForces is not revealed until they are in the same LiteZulu as an Enemy StarForce or StarGate. At the beginning of the game certain letters are assigned FakerForces (see 33.2).

CASES:

[33.1] CAPABILITIES AND LIMITATIONS OF FAKERFORCES

FakerForces count as one-quarter of a StarForce for all StarGate capacity considerations, Basic Game combat losses, and victory point calculation purposes.

[33.11] FakerForces have the exact same Stellar Shift Range as a full StarForce. On the Tactical Display their Tac-shift Range and TeleValue is as indicated on the TelePoint Cost Table on the map.

[33.12] FakerForces may only enhance for each other on a one-for-one basis. They may never enhance for a StarForce even if there are four FakerForces in the LiteZulu. StarForces may, however, enhance a destination for as many as four FakerForces (if all are coming from the same point of origin; if not, the StarForce may only enhance for as many FakerForces as are coming from the same point of origin). Similarly, StarGates may enhance for as many as sixteen FakerForces if all are coming from the same point of origin. If FakerForces are coming from different points of origin, the StarGate may enhance its LiteZulu for as many as two groups of four FakerForces. Each group counts as one StarForce against the basic Gate capacity of two StarForces per Game-Turn. The same capacity considerations apply when plotting "GS" or "EGS" or "GGS" operations for FakerForces.

[33.13] In the Basic Game Combat, each FakerForce is worth one-half of a Strength Point (this never is increased or decreased). There must be at least two FakerForces in the same LiteZulu in order to contribute any Strength to the attack (an odd half-point may however be contributed to the defense and the defense total is rounded up). FakerForces are equivalent to one-quarter of a StarForce for loss purposes.

[33.14] FakerForces may be re-combined into a StarForce if all four FakerForces end the Shift Execution Phase in the same (uncontested) LiteZulu. They may not be recombined when on the Tactical Display or when in a Basic Game combat situation.

[33.15] FakerForces have the same abilities as Starforces with respect to intelligence gathering on the Stellar Display and the Tactical Display. They perform as a StarForce in the Zulu Coordinate Readout Segment of the Stellar Game-Turn and the Position Phase of the Tac-Turn.

[33.16] FakerForces may not be placed on reserve status.

[33.17] The only time FakerForces are revealed to be such is when they are adjacent to an Enemy StarGate (in the non-Xenophobe scenarios), when they are in a contested LiteZulu, or when they are on the Tactical Display.

[33.2] PLOTTING FAKERFORCES

The letter designations of FakerForces and StarForces are interchangable; in any Stellar Plot Phase in which FakerForces and StarForces are in the same LiteZulu the owning Player may redesignate the units, switching the designations of the StarForces and FakerForces. In this way the Enemy Player will never be able to permanently discover the true composition of a Player's forces. Players should be scrupulously accurate in these redesignations and be prepared to offer proof upon challenge.

[33.3] DEPLOYMENT

Before the beginning of the game the owning Player may deploy his FakerForces as he wishes in any LiteZulu containing a Friendly StarGate, so long as at least one FakerForce remains in its starting LiteZulu, i.e., in the LiteZulu of its component StarForce. (Exception: no FakerForce of either Player may begin the game in the Eta Cassiopeiae LiteZulu in the 21.0 scenario).

[34.0] GATELINK

GENERAL RULE: StarGates may be linked together in a chain like arrangement of Gate-to-Gate-to-Gate (etc.) shifts. All Gates involved in such a GateLink must be assigned exclusively to that operation and must, of course, be Friendly, un-neutralized StarGates.

CASES:

[34.1] GATELINK CAPACITY

All the StarGates in the Link have a combined capacity equal to that of one StarGate. GateLinks are uni-directional if the maximum capacity of four StarForces are sent through the Link. GateLinks are bi-directional if the normal, two StarForce limit is observed.

[34.2] ORIGINS AND DESTINATIONS

The GateLink must be a linear linkage (there can be no branching out of the Link to different StarGates even if the minimum capacity is used). There may be no closed loops in the GateLink. Each StarGate in the Link must be within twenty Lites of the next StarGate in the Link. Overshifting is prohibited in a GateLink.

[34.21] If maximum capacity is being used, all the StarForces involved must begin in the same LiteZulu (one of the "ends" of the Link), but need not end in the furthest StarGate in the Link. Some may drop off the Link at intermediate StarGates within the linkage. If normal capacity (two) is used, the GateLink is bi-directional and the StarForces involved may each come from a different end of the Link (they must start in the ends of the Link and there can only be two StarGates designated as the ends). Once again, they need not complete the full linkage but may drop off at any intermediate StarGate in the Link.

[34.3] PLOTTING A GATELINK

Plot the GateLink by writing, in order of linkage, the identity numbers of the StarGates involved. Example: 4-1-6-2. Since the positions of all StarGates (except in the Xenophobe scenarios) are known Players can simply write the StarGate identity number of their point of origin and destination inserting the code "GL" between them. Example (referring to the Link just described): 4GL6. This would indicate a GateLink shift beginning at StarGate "4" and ending at StarGate "6".

[34.31] Reserve StarForces cannot use GateLinks.

[34.32] Xenophobe StarForces may plot a GateLink between two or three of their StarGates even if none are within twenty Lites of another. The Xenophobe Player can be assumed to be linking into StarGates further "into" his system which fill the gaps in the linkage. Therefore the Xenophobe Player could link all three of his StarGates in any order he desired.

[34.33] Just as all other plots, GateLinks do not persist from Game-Turn to Game-Turn; they must be re-plotted each Game-Turn as desired. Of course, the linkage can be modified in subsequent plots.

[34.34] A Player can set up any number of GateLink systems in a given Game-Turn providing that none share a common StarGate.

[35.0] SITUATIONAL CONTINUITY

GENERAL RULE: In both the Basic and Advanced Games, there are artificial constraints which force the resolution of combat situations within the Game-Turn in which they occur. This is done primarily for purposes of simplicity. If they wish, Players may continue combat situations from Game-Turn to Game-Turn until they are resolved naturally (i.e., without forcing stalemate-ending breakoffs, etc.).

CASES:

[35.1] DURATION OF COMBAT SITUATIONS PER GAME-TURN

In the Basic Game, each Situation is played for a period of six Combat Segments in the first Game-Turn; in the Advanced Game each combat situation is played for a period of twelve Tac-Turns in the first Game-Turn. If the situations are unresolved at the end of these periods, that situation persists into the next Game-Turn. These periods are referred to as situation Cycles. The second and subsequent Game-Turns into which a situation persists are two Cycles in duration. Situations which persist into a second or subsequent Stellar Game-Turn are called prolonged situations.

[35.2] FORCES INVOLVED IN THE FIRST AND SECOND CYCLES OF PROLONGED COMBAT SITUATIONS

In the First Cycle of a prolonged situation, only the forces which remained in the LiteZulu at the end of the previous Game-Turn are involved. Forces which Stellar shifted into that LiteZulu in the current Game-Turn are not considered to have arrived until the very beginning of the Second Cycle of that Game-Turn.

[35.3] WHEN AND HOW NEW FORCES ARRIVE IN A PROLONGED SITUATION

StarForces which Stellar shift into a contested LiteZulu arrive at the very beginning of the Second Cycle. In the Basic Game they arrive just as in-shifting StarForces usually do, i.e., with a Combat Strength of "2" per StarForce. In the Advanced Game, StarForces arrive in Stellar Mode in any pre-plotted MiniLiteZulu at plus or minus five, or at any point in the "500" ring of hexes, just as usual Incoming StarForces pre-plot the MiniLiteZulu in which they will appear during the Stellar Shift Plot Phase of that Game-Turn.

[35.31] In the Basic Game, Players must decide if they wish to engage in-shifting StarForces in combat (using only First-Cycle StarForces to do so, see 8.2) in the First Combat Segment of the Second Cycle. The same restrictions apply as in the Basic Game, with the following additions:

  • A. If Alpha Player is in-shifting and also has First Cycle StarForces present, Bravo Player must be able to attack/defend with all his available forces if he exercises his option to do so. This means that if Bravo is the StarGate owning Player he may not exercise his option and may only use his First Cycle StarForces and his StarGate against Alpha's First Cycle StarForces. Alpha's in-shifting StarForces must be ignored for the First Combat Segment of the Second Cycle.
  • B. If both Players have in-shifting StarForces as well as First Cycle StarForces (and possibly a StarGate) both must wish to engage in-shifting forces and both must be able to involve their entire available force with the entire Enemy force, as per condition A, above. If one or the other Player does not wish to engage in-shifting Enemy StarForces or cannot fulfill the conditions to do so, then only First Cycle forces can be involved in combat in the First Combat Segment of the Second Cycle.

[35.32] In the Advanced Game, arriving StarForces make normal plots for the First Tac-Turn of the Second Cycle. Their availability for combat is solely dependent upon the availability of targets or attackers within range.

[35.33] Reserve StarForces may only be called in during the Second Cycle.

[35.4] HOW UNITS MAY LEAVE A PROLONGED SITUATION

StarForces may only leave a prolonged situation in the same manner that they leave a normal situation: by combat break-off.

[35.5] CONDITIONS FOR PERMANENT NEUTRALIZATION OF STARGATES

In order for a StarGate to be permanently neutralized, the Enemy Player must have at least one unit in the LiteZulu with the neutralized StarGate for one complete Combat Segment (or two Tac-Turns) without Friendly StarForces being present.

[35.6] STELLAR SHIFTING AND STARGATES IN PROLONGED SITUATIONS

StarGates which are involved in prolonged situations may not be used for Stellar shifting operations of any kind.

[36.0] BATTLE MODE CREW FATIGUE

The Telesthetic crews of StarForces suffer from great fatigue if the StarForce is in Battle Mode on two or more consecutive Game-Turns. A StarForce may never be in Battle Mode for more than three Game-Turns in a row. The Basic Game Battle Mode equivalent is the increase to a three Strength Point in the second Combat Segment of a combat situation. When using this rule, Players have the option to decline this increase and remain in the two Strength Point Stellar Mode.

CASES:

[36.1] EFFECTS OF TWO CONSECUTIVE GAME-TURNS OF BEING IN BATTLE MODE

If a given StarForce changes to or stays in Battle Mode for two consecutive Game-Turns it suffers the following limitations on its performance in the third Game-Turn:

  • A. It adds two Lites to the effective distance of any Stellar shift it may make or enhance in the third Game-Turn. This does not include GGS and GS type shifts (where the crew of the StarGate is actually doing all the shifting).
  • B. It must always allocate at least one Strength Point to the defense in any third Game-Turn Combat Segment (or, in the Advanced Game, may not make a cast with more than half its TelePoints in any Tac-Turn in the third Game-Turn).

[36.2] EFFECTS OF THREE CONSECUTIVE GAME-TURNS OF BEING IN BATTLE MODE

A StarForce which remains in or changes to Battle Mode for three consecutive Game-Turns suffers the following effects in the fourth Game-Turn (this is in addition to the effects it suffered in the third Game-Turn):

  • A. The StarForce is neutralized (in place) for the fourth Game-Turn. It recovers from this neutralization in the Neutralization Recovery Phase of that Game-Turn.
  • B. If the StarForce is neutralized as a result of combat or break-off in the third Game-Turn, the StarForce is neutralized until the Neutralization Recovery Phase of the fifth Game-Turn.

[36.3] RECOVERY FROM BATTLE MODE FATIGUE

A StarForce recovers from the effects of two consecutive Game-Turns of Battle Mode by suffering the effects of the third Game-Turn without changing to or remaining in Battle Mode during the third Game-Turn. It becomes completely normal during the Neutralization Recovery Phase of the third Game-Turn.

A StarForce recovering from the neutralization effect of three consecutive Game-Turns in Battle Mode does so during the Neutralization Recovery Phase of the fourth Game-Turn.

[37.0] SEQUENTIAL PLAY

GENERAL RULE: Players who dislike plotting or who would like to play a game against themselves solitaire fashion may use the following suggested Sequential Play approach.

CASES:

[37.1] SEQUENTIAL STELLAR SHIFTING

All StarForces are represented by individual counters on the Stellar Display. Players take turns moving one of their units at a time, alphabetically according to identity code. For example, Alpha Player shifts StarForce "A"; Bravo Player shifts StarForce "A"; Alpha shifts "B", etc., until all StarForces have been accounted for. Players must still record the Zulu coordinates of their StarForces (unless they trust each other implicitly and can keep the relationships in their head. This is possible in scenarios with small orders of battle). All shifts are considered to take place simultaneously. Players alternate by Game-Turn the Player who'll be first to move his first unit.

[37.2] SEQUENTIAL BASIC GAME COMBAT

Each Player takes one of the spare Decimal Randomizer sets and uses it to declare how many Strength Points he is using to attack. Numbers larger than nine can be represented by showing two or more chits. Players reveal their attack strength allocation simultaneously.

[37.3] SEQUENTIAL ADVANCE GAME TAC-SHIFTING

Players indicate their allocation of TelePoints to Tac-shifting by making their Tac-shifts, each Player alternating with the other in Tac-shifting one unit at a time and announcing their expenditures as they make them. Players Tac-shift units furthest from the center of the Tactical Display first, working their way inward, unit by unit.

[37.4] SEQUENTIAL ADVANCED GAME COMBAT

Players make their combat casts alternately, one unit at a time. The unit furthest from the center of the Display makes its cast first, then the other Player makes a cast with his unit furthest from the center of the Display. Units which have not yet made a cast and who could possibly be affected by a cast being made, must have their Anti-cast announced by the owning Player before the casting Player announces the strength of his cast. All cast effects are still applied simultaneously and additively.

[37.5] CAUTIONARY NOTE

Of course, Players realize that the structure of the standard game is built around simultaneous plotting and that any attempt to circumvent that structure will result in distortions. Players who really dislike plotting should play scenarios with small orders of battle. If they have opponents that they really trust, much plotting can be done on the "keep-it-in-your-head" honor system. The sequential system presented here is just a rough guide - Players will have to make on-the-spot decisions when conflicts and questionable situations arise.

[38.0] THE RESCUE MISSION (A Solitaire Game)

GENERAL SITUATION: After the First Xenophobe Incursion, it was discovered that a faulty Conversion Trigger had destabilized the star of an inhabited system. Analysis indicated that the star would take several years to go nova, and so, an orderly evacuation program was instituted allowing an eighteen-month safety margin. Near the end of the program, quite unexpectedly, new data indicated that the star would go nova in no more than ten days. Calling in additional StarForces, the PSL began a crash evacuation program to rescue the 20 million humans remaining on the single planet in the system.

GENERAL RULE: Players have twelve StarForces available to lift off 60 Population Points (each Population Point represents a third of a million humans). A combined set of two Decimal Randomizers is used to simulate the uncertain time of the nova. The actual star in question is determined randomly at the start of the game. Players win the situation by getting all the population safely off the planet.

[38.1] DETERMINING THE LOCATION OF THE ENDANGERED SYSTEM

Pick a chit from the Stellar Randomizer and read the top two-digit number. Read that number as one of the hexes in the "2000" column of hexagons (the same column that Sol and 70 Ophiuchi are in). If the bottom number of the chit is positive trace a clockwise orbit around Sol maintaining a constant hex distance from it (this will describe a large hexagonal circle just like the rings of Zulu Limits printed on the map). If the bottom number is negative, trace the orbit counter-clockwise. The first tertiary star system that the orbit traces through (in a two-dimensional sense) is the endangered system. If there is no tertiary system in that orbit, pick another chit.

[38.2] INITIAL STARFORCE DEPLOYMENT

Four StarForces at 2020/0 (Sol), two StarForces at 2336/+17 (Sigma Draconis), four StarForces at the endangered star system, and two StarForces at the (undestroyed) tertiary system nearest to the endangered star (in true distance). If two stars are equally near, use the one which is also nearest to Sol. All StarForces are empty. All systems have StarGates except the endangered star and those destroyed in the First Incursion (see 31.62).

[38.3] SIMULATING THE UNCERTAINTY OF NOVA

Take two Decimal Randomizer sets and place them in a container. Each Game-Turn (during the un-used Combat Phase), the Player makes one or two chit draws from this Nova Randomizer to determine if the star goes nova at that point (ending the game, destroying whatever population remains in the system, as well as any StarForces which are presently in that LiteZulu).

How to Draw Chits from the Nova Randomizer: Draw the first chit; if it is not a Zero, stop, do not place the chit back in the Randomizer. Go on to the next Game-Turn; the star has not gone nova. If the chit is a Zero, place it back in the Randomizer, make a second draw. If the second draw is not a Zero, keep that chit out and go on to the next Game-Turn. If the second chit drawn is a Zero, the star novas and the game immediately ends. Note that the total number of chits in the mix decreases by one chit each Game-Turn (which, of course, increases the chances of the star going nova in the next drawing). This procedure will provide a maximum of 18 safe Game-Turns; the star is guaranteed to explode on the nineteenth Game-Turn.

[38.4] HOW POPULATION POINTS ARE RESCUED

Each StarForce can lift one Population Point. To load a Population Point on a StarForce, it must begin and end the Game-Turn in the endangered star's LiteZulu. To unload the population Point, the StarForce must begin and end the Game-Turn in the LiteZulu of any other star system on the Display (except those destroyed as a result of the First Incursion, see 31.62). Loaded and unloaded StarForces may participate in any sort of shifting and enhancement that the standard and optional rules allow. Overshift results remain the same. StarForces may not perform enhancing operations while loading and unloading.

[38.5] VICTORY LEVELS

Victory is measured in terms of how many Population Points are saved (each equalling one Victory Point). A perfect score of 60 Victory Points is a Decisive Victory over the situation; a score of 50 to 59 is a Substantive Victory; 40 to 49 is a Marginal Victory. Less than 40 Points is a defeat. If a StarForce is lost in the rescue attempt (either by Overshift results or being incinerated) subtract three points from the score. Don't forget to count as lost any Population Points on destroyed StarForces at the time of destruction.

[39.0] VERBAL PLOTTING

GENERAL RULE: If Players trust each other, they may do much of the plotting for StarForce in their heads and only occasionally write down coordinates, and such, to support their memories. Combat allocations can be simply announced more or less simultaneously. This technique was used in much of the playtesting of the game and was very effective in speeding up play (particularly the Advanced version with its two levels of plotting).

[100.0] STARFORCE SCENARIO 100: THE OUTLEAP, 2400-2500 A.D.

The history of the Outleap from 2341 to 2785 is often seen as a collection of "wars" amid a largely peaceful and economically minded expansion of sentient starfaring races. However, the same history can be represented on a larger level of political and economic conflict, showing why governments of individual planets and systems had such an intense interest in interstellar hegemonies and leagues. This Scenario shows the forces behind the rapid colonial expansion of various races and systems, and the political, economic and military complications that ensued.

[101] INTRODUCTION TO PLAY

The full advanced game rules of StarForce should be used. Furthermore, FakerForces rules must be used, and Reserve StarForces and GateLink optional rules are strongly recommended. Situational Continuity and Battle Mode Crew Fatigue may be introduced if desired.

The game is played by yearly turns, called EcoYears (economic years), which include an indefinite number of normal (strategic) Stellar Game-Turns.

It is very useful to make some additional counters for this Scenario. Each Player should receive 16 "Control" Markers to use to denote control of colonies without StarGates, about 20 (possibly more if Players feel it necessary) "EE Group" Markers, and StarSoldier Division Markers (SS Divisions) in denominations of 1, 2, 4 and 6 divisions. About a half dozen of each denomination is usually sufficient.

[102] ECOYEAR TURN PROCEDURE

GENERAL RULE: Overall play of the Scenario proceeds EcoYear by EcoYear, until Victory Conditions are met or the time limit exhausted at the end of a given year.

PROCEDURE: Each EcoYear is divided into the following Phases, in which all Players may participate:

  1. Diplomacy Phase: Players engage in public and secret bargaining.
  2. Income Phase: Players openly determine population resources and MegaLaborCredits (MLC) available; including transfers of the latter between Players.
  3. Expenditure Phase: Players secretly determine building and maintenance of items using available population resources and MLC's. New StarGates are then deployed.
  4. Organization Phase: Players organize available items, embarking those desired on StarForces, and denoting initial StarForce LiteZulu locations. Then all StarForces are placed on the Stellar Display.
  5. Stellar Phase: Players begin play of normal strategic-advanced game, using Stellar Game-Turns, and Tac-Turns where required. Phase has at least three Stellar Game-Turns.
  6. Consolidation Phase: conquest and control of systems is determined, with appropriate StarGate changes. All StarForces are then withdrawn from the Stellar Display, and EE Groups may also be withdrawn by the Owning Player if desired.

[103] DIPLOMACY

GENERAL RULE: In the Diplomacy Phase of each EcoYear, Players may discuss deals or other matters that interest them secretly and openly. Secret meetings between any and all Players are limited to a single 15 minute period, begun whenever any one Player requests it during the Phase. This limit should be strictly followed to avoid unnecessary delay of play. There is no limit on public diplomacy.

CASES:

[103.1] Normally all political deals and arrangements must be made in the Diplomacy Phase of the EcoYear. Players should adhere to the spirit of this rule, in the interest of playing the game rather than talking about it. However, Players are entitled to request and respond to calls for alliances, wars and truces during other Phases. They should not engage in any prolonged debate over such requests and responses at that time, but rather wait until the next Diplomacy Phase.

[103.2] The sole exception to Rule 103.1, above, is when allies are allowed shift support, in which case the allies may coordinate their Stellar Shifting together during Stellar Game-Turns.

[104] HOME & COLONIAL SYSTEM INCOME

GENERAL RULE: Home systems and habitable colonies with one or more Population Resource Points will contribute Population Resource Points and MegaLaborCredits (MLC) to a Player that controls them, during the Income Phase of the EcoYear.

PROCEDURE: Determine Population Resources and MLC of each system controlled, and total each separately to determine total available. Calculations are public, not secret. Note that home system values vary with race, colonial system MLC values with the Population Resources.

CASES:

[104.1] Home systems automatically contribute their full Population Resources and MLC Value to their original Player each EcoYear. The home system cannot be changed or conquered during the course of the game.

[104.2] All inhabited non-home systems are considered colonies. Both primary and secondary systems may be colonies, depending upon the exact Scenario Set-Up procedure used.

[104.3] A Player may elect to increase the Population Points of each and/or any colonial system he controls, or leave it at the current level, when determining income. If Population is increased, only half the MLC of that system is received (based on increased Population Value). Colonial systems with the maximum Population Resource Value may not be increased. If population is not increased, the full normal MLC of the system is received, based on the Population Value. See Colonial Population and Colonial MLC Tables.

[104.4] A Player totals all MLC received in the current EcoYear, and adds all MLC left over from the previous year. This grand total is the amount of MLC that may be "spent" that year. Note that MLC may be given away to other Players, and may be reduced due to political events suffered in the previous EcoYear.

[104.5] A Player totals all Population Resources in the current year, and compares that total to the total of the previous year. If there has been any increase, then that increase is available for building new StarForces and StarGates. Increases not used in previous years are also available. It is important that a running list of Population totals for each year, as well as increases available and used, be kept, because current population total also affects new construction. Population Resources are not transferable between systems or Players.

[104.6] Except for the option given in 104.3, Population Resources and MLC are not related. Home System Population/MLC Value Table

Home SystemPopulationMLC
Human1954
L'Chal-Dah1757
Rame2052
Other1855

Maximum Colonial Population Table

Star SystemPop.
Alpha Centauri (1821/-4)17
Beta Hydri (2420/-21)10
CD-20 (0732/-7)9
61 Cygni (2626/+7)17
Delta Pavonis (2427/-18)12
82 Eridani (3009/-14)11
Epsilon Eridani (2713/-2)15
Epsilon Indi (2523/-10)16
Eta Cassiopeiae (3018/+15)13
HR 7703 (2833/-11)14
HR 8832 (3223/+18)12
36 Ophiuchi (1636/-8)

Colonial MLC Value Table

PopulationMLC
110
214
318
421
523
626
727
830
931
1032
1135
1236
13

[105] TERTIARY SYSTEM INCOME

GENERAL RULE: Tertiary systems are incapable of supporting significant populations, but may be occupied by Economic Exploitation (EE) Groups, which may find items of significant value to the race, measured in terms of MegaLabor Credits (MLC) income to the occupying and controlling Player.

PROCEDURE: After the first EcoYear, each worthwhile system controlled by a Player and occupied by an EE Group contributes MLC to that Player's income. Amount of MLC varies with the type of system and a randomizer chit pick, as shown on the Tertiary System Income Table.

Income derived from tertiary systems, and the chit pick that produced it, must be public. However, the type of system discovered is kept secret if a Player desires.

CASES:

[105.1] The first year a tertiary system is occupied by an EE Group, exploration for valuable materials is undertaken. During the Income Phase of the EcoYear a randomizer chit is secretly drawn for each system undergoing initial exploration, and the results secretly noted by the exploring Player. The system may prove to be worthless — have no materials of value, or have very rare (VRM) or rare (RM) minerals, or special vegetable life (SV) suitable for bionic purposes.

[105.2] Exploration results are different for each Player. If another Player occupies the same system, he makes a separate exploration, and must abide by its result. If a Player abandons a tertiary system and then returns, he is not allowed another exploration. Thus, it is possible for a system to prove valuable to one Player and worthless to another.

[105.3] Each EcoYear after the exploration year, each Player that occupies the system with an EE Group and controls the system openly draws one randomizer chit and consults the Tertiary System Income Table. He then announces the MLC income result. Due to the construction of the table, this may give other Players a hint of what his exploration results were.

[105.4] For purposes of victory determination, and general Player interest, VRM systems average an output of 7.4 MLC yearly, RM systems 5.8 MLC, and SV systems, 5.4 MLC.

Tertiary System Income Table

Chit PickExploration ResultIncome ResultIncome ResultIncome ResultChit Pick
0VRM system9VRM9RM5SV0
1RM system8VRM8RM5SV1
2RM system10VRM7RM7SV2
3SV system13VRM7RM7SV3

* EE Group destroyed during course of exploration; remove EE Group from game as built item.

Transcriber's note: the three "Income Result" columns carry no printed column headings; the cells are transcribed exactly as printed.

[106] EXPENDITURES

GENERAL RULE: Population Resources and MLC are used to create new TeleShips and StarGates, up to the limit of total current Population Resources. MLC alone may be used to build Seed Colonies, EE Groups and StarSoldiers (SS) Divisions. All previously built items may only be continued to be used in subsequent years if a maintenance cost in MLC is expended. Failure to maintain an item simply makes it unavailable for that year, failure to maintain never destroys an item.

PROCEDURE: Each Player makes a secret Expenditures List, giving maintenance of items already built, new items built, and already built items not maintained (and thus not available) in that year. The list should be retained, so that opponents can examine it at the end of the game.

CASES:

[106.1] A list of already built TeleShips, StarGates (with location), Seed Colonies not yet used, EE Groups and SS Divisions must be maintained, and updated to reflect losses from year to year. Except for StarGates, which are permanently located once built, only a list of the quantity of each is necessary, since they can be redeployed at the start of each EcoYear. Each of these items may be activated in a particular year by expending the maintenance cost. Items not activated are retained in limbo, and may be used in future years, even though they were not used in the present one. Non-maintained items are never lost.

[106.2] Building new TeleShips and StarGates requires the use of both Population Resources and MLC. Population Resources spent to build new Forces and Gates must not exceed population increase of that year over the previous year (plus unexpended increases of the previous years). In other words, only new "unused" Population Resources may be used for building new Forces and Gates. Furthermore, the Population Resources involved in all TeleShips and StarGates of the Player may never exceed the current population. If current inventory of Ships (Forces) and Gates exceeds Population Resources, no new items of either may be built until population catches up. Total population puts a limit on all construction. However, already built Ships and Gates may be maintained even though their requirements might be in excess of current population. This would come about if a Player lost one or more systems to another Player.

[106.3] All other items only require MLC to build, and all items only require MLC to maintain. This MLC must be spent again each year to maintain the item, although some items can be maintained for nothing, and are, therefore, "free" once built. No items need be maintained in the same EcoYear in which they were built; building cost includes maintenance for the first year.

[106.4] New StarGates may only be built if there is a controlled system to place them in. StarGates may only be placed in primary or secondary systems with three or more (3+) Population Resource Points, and only in systems currently without a StarGate. A system may never have more than one StarGate. Location of newly built Gates must be specified with building, and placement on the Stellar Display in the appropriate LiteZulu made at the conclusion of the Expenditures Phase.

[106.5] Location of all other newly built or maintained items is not necessary until the following Organization Phase of the EcoYear.

EXPENDITURES CHART

ItemTo Build: Pop.To Build: MLCTo Maintain: MLC
TeleShip182
StarForce (4 TeleShips)4328
StarGate73010
Seed Colony0151
EE Group060
StarSoldier Division021

Transcriber's note: the printed chart shows a small mark after the StarGate maintenance figure "10" with no matching footnote on the page; it is transcribed as "10".

[107] ORGANIZATION

GENERAL RULE: After Players determine items available to them for the EcoYear (see Expenditures), they organize their TeleShips into Star Forces, embark items upon them, and deploy the StarForces among controlled primary and secondary systems.

PROCEDURE: All organization is initially done in secret and recorded. StarForces are then deployed, one or more per hex, as per Semi-Hidden Display rules (7.4). Embarkation is kept secret until item is disembarked.

CASES:

[107.1] Available TeleShips must be organized into FakerForces of one ship, and StarForces of four ships. The number of FakerForces may not exceed half the number of StarForces, except that a Player is always allowed to form up to four (4) FakerForces, regardless of how few StarForces he has available. Organization and number of FakerForces and StarForces used in the previous year has no effect on current year organization. Organization may be changed during the game only within the FakerForces rules limits (see 33.1).

[107.2] Available Seed Colonies, EE Groups, and StarSoldier (SS) Divisions may be embarked on Forces. Items not embarked are considered unavailable that year, even if a maintenance cost was paid. Embarkation is only possible during the Organization Phase of the EcoYear.

[107.3] A StarForce may embark up to one Seed Colony or one EE Group or one to six SS Divisions. A combination of items may not be embarked on the same StarForce. A FakerForce may embark one SS Division if desired, never more. Because embarkation is only possible in this Phase, FakerForce combination during a Stellar Game-Turn only serves to combine any SS Divisions carried by the components.

[107.4] Starting locations of all StarForces and FakerForces must be secretly written, so that starting deployments are made in ignorance of enemy deployments. Note that newly built StarGates will have been already openly deployed (in the previous EcoYear Phase). Deployment is limited in three ways. First, StarForces and FakerForces may only deploy in controlled primary or secondary systems. Second, systems without a StarGate may not have more than one force (one StarForce or one FakerForce) deployed in them. Third, no system may have more TeleShips deployed in it than the home system; remember that a FakerForce contains only 1 TeleShip, a StarForce, four TeleShips. Note that the total number of TeleShips deployed in the colonies could exceed the total at home, provided that the amount in any one colony did not exceed the amount at home.

[107.5] After deployment locations have been prepared, Forces are placed on the Stellar Display.

[107.6] EE Groups already debarked into a tertiary system in some previous EcoYear, and still placed in the system at the start of the current year (i.e., were not withdrawn in the previous year) may not be redeployed. They remain in that system during the Organization Phase of the EcoYear. EE Groups withdrawn from a system in the previous year and newly built groups may only be embarked on a StarForce, they may not be directly deployed into a tertiary system.

[108] STELLAR DEBARKATION

GENERAL RULE: Debarkation of EE Groups, Seed Colonies and SS Divisions into appropriate star systems is allowed during the Stellar Game-Turns.

PROCEDURE: StarForces and/or FakerForces debarking items into a system should add a "DB" to their Shift Plot. In the case of debarking SS Divisions, the number of divisions debarked may be specified if less than the full complement is to be debarked (i.e., DB-4SS indicates four SS Divisions are to be debarked).

CASES:

[108.1] No Force may ever debark items into a LiteZulu occupied by any opposing Force or StarGate, except LiteZulus solely occupied by a permanently neutralized StarGate. Furthermore, in order to debark items, the carrying Force must be in the LiteZulu to which the items are debarked (i.e., Forces may not debark items from distant LiteZulus using their Shift capability, since debarking is not a Telekinetic process).

[108.2] To debark SS Divisions, a Force must remain in the same LiteZulu for one entire Stellar Game-Turn. To debark a Seed Colony or EE Group, the StarForce must remain in the same LiteZulu for two entire consecutive Stellar Game-Turns. The Force may not shift while debarking, but may enhance the shifting of other Forces into that LiteZulu. If opposing Forces shift into the LiteZulu during debarkation, the debarkation is prevented, and must be started over again after the opposing Forces are removed, or started over again at some other time, and possibly in some other LiteZulu. Debarking Forces involved in a tactical situation are automatically in Battle Mode. IMPORTANT: Remember that no Force may shift into a LiteZulu and debark any item during the same Stellar Game-Turn; nor may a Force debark and then shift out in the same Stellar Game-Turn.

[108.3] EE Groups may be debarked into any tertiary system not already occupied by an EE Group and/or SS Division of an Enemy Player. An EE Group may be debarked into a tertiary system already occupied by an EE Group of another, non-hostile Player. EE Groups not debarked during the Stellar Phase of the EcoYear are available again the next year; and may be reembarked on a Force again. Once debarked, EE Groups may only be withdrawn from a system at the end of the EcoYear, during the Consolidation Phase.

[108.4] Seed Colonies may only be debarked into an unoccupied primary or secondary system (i.e., a system without any population). Upon completion of successful debarkation, the Seed Colony is immediately converted (at the end of that Stellar Game-Turn) to one Population Resource Point, and control of the system is awarded to the Player who debarked the Seed Colony. Debarking Seed Colonies is an irreversible process, because the resulting population may never be moved.

[108.5] SS Divisions may only be debarked into an Enemy colonial system. They may be debarked into a system already occupied by SS Divisions. Debarking SS Divisions must at least match the Population Resources of the system (on a one-to-one basis), or, if the system is already occupied by SS Divisions, must be at least double the number of SS Divisions already in the system if those in the system are hostile. If Friendly SS Divisions are in the system, additional divisions may be debarked in any amount. Failure to debark at least the minimum number of SS Divisions results in the immediate destruction of all the debarking divisions. Successful debarkation of SS Divisions into a system occupied by Enemy Divisions results in the destruction of all Enemy Divisions.

[108.5a] An SS Division may be debarked into an Enemy tertiary system containing an EE Group. The SS Division will destroy the Enemy EE Group, but will, in turn, be destroyed itself unless a Friendly EE Group is also debarked into the system on the following Stellar Game-Turn. No more than one SS Division may be debarked into a tertiary system per EcoYear.

[108.6] Note that these rules prevent Friendly SS Divisions from being used for purely defensive purposes, to forstall Enemy occupation. However, once Enemy occupation is made, they may be moved in to reconquer the system for its original owner, at which point any number may remain stationed there. SS Divisions, like other items, may not be reembarked during Stellar Game-Turns. During the Consolidation Phase of the EcoYear, after control is determined, all SS Divisions are withdrawn from all systems; a "standing garrison" is not maintained from one year to the next.

[108.7] All debarkation is open. The type or size of the debarkation is never kept secret.

[109] WAR, TRUCE & ALLIANCE

GENERAL RULE: The number of Stellar Game-Turns in an EcoYear varies depending upon the political decisions made by the Players. A declaration of war may prolong the number of Stellar Game-Turns to be played.

PROCEDURE: War may be declared at any instant during a Stellar Game-Turn, including after Shift Execution, but before Combat Execution, thus allowing a certain form of "surprise" attacks. A truce may be requested at the conclusion of any Stellar Game-Turn by any party at war. Players are not to make complex bargains, political deals or otherwise hold involved political discussions during the Stellar Phase. Alliances may be declared at the conclusion of any Stellar Game-Turn, and apply as long as the parties wish it, or until the war is concluded with a truce.

CASES:

[109.1] War

[109.11] If any Player declares war upon another, those two Players are automatically hostile to each other (opposed, Enemies, whatever). Other Players may declare war on either or both parties individually, as they desire. Note that a declaration of war by one Player automatically makes the target of the declaration at war with him, too.

[109.12] A Player must declare war in order to cause use of the advanced game Tactical procedure (i.e., cause a battle), and must declare war in order to make a combat cast effective against another Player's Forces or Gates, or to land an SS Division in a system controlled by another Player.

[109.13] A Player may only declare war upon Players already involved in a war, or Players which control a system within 20 Lites of a controlled system of the declaring Player.

[109.14] If Players are at war and have EE Groups in the same system, the Player who controls the system must immediately destroy Enemy EE Groups in the same system.

[109.15] The Stellar Phase of an EcoYear ends whenever the third or any later Stellar Game-Turn ends without a declared war still continuing. Thus, at least three Stellar Game-Turns are insured in a given year, but more are prohibited unless war occurs. The Stellar Phase ends simultaneously for all Players (i.e., either all Players are involved in the Phase, or it is over; thus a single war will continue the Phase for all Players, even though some may not be at war).

[109.2] Alliances

[109.21] Players not at war with each other, but at war with the same Enemy, may form an alliance at the conclusion of any Stellar Game-Turn. Allies automatically combine combat casts against their mutual Enemy (see 27.42 for details).

[109.22] Whenever one or more Forces or Gates of two allies occupy the same LiteZulu at the conclusion of the same Stellar Turn, shift supporting is allowed. Shift supporting means Forces and Gates of one ally may participate in stellar shifts involving Forces and/or Gates of the other (see 109.23 for a special limitation).

[109.23] When different races are allied, shift supporting suffers two limitations. Star Forces of one race may not enhance the stellar shifting of those of another race. StarGates of different races may not participate in Gate-to-Gate shifts or links. However, StarForces of one race may freely use the Gates of another in a normal Gate Shift or Enhanced GateShift, and both may plan joint shifting maneuvers.

[109.24] Triple or larger alliances are possible, provided all conditions are fulfilled by all involved Players.

[109.3] Truces

[109.31] Any warring Player may request a truce after any Stellar Game-Turn, and he may request it of any or all Players he is currently at war with. A Player must request a truce if he has not debarked any SS Divisions into an Enemy occupied system or been involved in a Tactical battle resolution procedure in the last ten Stellar Game-Turns. This might require more than one party in a war to request a truce at the same time, putting a Player in the position of both requestor and receiver at the same time.

[109.32] Any Player who requests truce on a Stellar Game-Turn must consult the Truce Politics Table once for each Turn he requests truces. Note that many requests in the same Turn only incur one check on the table. A Player who is refused one Turn may request again on another Turn. Results of the Truce Politics Table must be made public.

[109.33] A Player who receives a truce request may respond positively or negatively. If a positive response is made, the war is over, and the Players may not again declare war upon each other in that EcoYear (but may in any subsequent year). The receiver may stipulate any type of MLC payment, control of systems, or other privileges as part of his positive response. However, the requestor must only honor those stipulations noted in the Truce Politics Table for the particular chit pick he made. In many cases, the chit pick permits him to ignore all stipulations.

[109.34] If a receiver responds negatively, then he, too, must consult the Truce Politics Table and make an appropriate chit pick for his negative response. In some cases, the chit pick automatically forces him to make a positive response, as per the rules in 109.33. For each negative response, a receiver makes to each truce call, another chit pick is necessary. Thus, if a Player is at war with two other Players, and both request truces Turn after Turn, he must make two chit picks each of those Turns, as long as he wishes to respond negatively.

[110] CONSOLIDATION

PROCEDURE: In the Consolidation Phase of the EcoYear, Players first determine control of all star systems with items debarked on them. Control Markers and StarGates are adjusted accordingly. Then most playing pieces are removed from the Stellar Display, in preparation for the following year.

CASES:

[110.1] Players first determine conquest and control of all star systems, adjusting Control Markers accordingly. Players controlling a system with a permanently neutralized StarGate of some other Player may exchange that StarGate for one of their own (i.e., take control of the StarGate also).

[110.2] All neutralization markers are removed from all items, including "permanent" neutralization.

[110.3] Players may now withdraw any and all items of theirs from the Stellar Display, with two exceptions: Location and existence of StarGates may not be changed, and size and location of Population Resources may not be changed. EE Groups may be withdrawn from the Display if desired. All Forces and SS Divisions must be withdrawn.

[110.4] Items withdrawn should be noted, so that a final record of remaining available materials after that year can be shown at the end of the game, and to assist the Player in calculating his expenditures in the next year. Withdrawn items are simply removed from the Display so that they may be maintained or put "in limbo" for the next year as desired, and those maintained in the next year may be redeployed in systems as desired, and consistent with the Organization Rules. Ability to withdraw items from the Stellar Display is therefore mainly an advantage, but can cause frustration if the Stellar Phase ends one Stellar Game-Turn before a Player finishes debarking a Seed Colony or EE Group.

[111] CONTROL

GENERAL RULE: Control is the occupation politically of a system. Systems of opposing Players are controlled by landing SS Divisions to destroy Enemy EE Groups or control a system's population.

CASES:

[111.1] The systems a Player begins on he controls. The first Player to debark any item into a system controls that system.

[111.2] A system occupied by SS Divisions is automatically controlled by the Player who has the most SS Divisions in that system.

[111.3] Joint control is impossible, although an EE Group may be in a system controlled by another non-hostile Player. If, for some reason, two Players can simultaneously lay claim to controlling a system, each picks a randomizer chit, and the higher picker is awarded control.

[112] SCENARIO SET-UP

PROCEDURE: Home and any initial colonial systems are determined by selecting one of the options given below. Then each Player computes available Population Resources and MLC. He then doubles the MLC. Then each Player may use these Population Resources and doubled MLC to build items as he desires. After expenditures are completed, results are revealed and StarGates placed. Play then starts with the first EcoYear, which will have its own Income and Expenditures, meaning that, overall, each Player is allowed triple his MLC before making his first Stellar Shifts.

SET-UP OPTIONS

[112.1] Basic Racial Primary Systems: This system is only possible in two- or three-Player games. One Human, Rame and L'Chal-Dah Marker is placed in an empty randomizer and each Player draws one marker. The result indicates the Player's race and home planet, which is automatically that race's primary system (Sol, 70 Ophiuchi or Sigma Draconis).

[112.2] Optional Racial Systems: In this version as many Players as different counter sets are possible, mainly five, unless additional counters are constructed. Each Player secretly names three different choices, in order of desirability, for his home system. Choices must be over 10 lites apart. Players also write if they wish to be Human, L'Chal-Dah or Rame. Players then reveal choices. All first choices are honored first, conflicts are resolved by randomizer chit picks in favor of the high-picker. Losers in the first choices then take their second choice, with conflicts again resolved by picks. If somehow a Player loses in all three of his choices, he may choose any system which remains available more than 10 lites from the other Players' systems. Such a Player automatically loses his original choice of race, and becomes an entirely new race. If no appropriate primary or secondary system is available over 10 lites from all other systems, the Player may choose any appropriate tertiary system and consider it secondary.

[112.3] Xenophobe Races: When using the 112.2 procedure, if a Player is forced out of all his choices of systems and races and becomes a new race, he may secretly opt to become a Xenophobe. In this case, he wins only by wiping out all other races in the volume via induced nova effects. See 31.5 for Nova Inducement rules. All other Xenophobe rules do not apply, since the race originated in the volume, and is, therefore, telepathically similar and able to shift with equal ease as all other races (i.e., ignore all special StarGate and Unknown Space rules). Players may only use conversion triggers and Nova inducement if they are Xenophobes, or if combating a Xenophobe Player who has already used such weapons. In other words, novas may only be induced by or against a Xenophobe.

[112.4] Optional Colonial Bonuses: In any of the above set-up options, Players may optionally wish to start the game with some colonial development already underway. In this case, each Player automatically is given control of the secondary system nearest his home system, with one Population Resource Point on that system. Only secondary systems within 10 lites may be so colonized. If the nearest secondary system is another Player's home system or equa-distant to another Player's home system, then no pre-game colonies are possible. This option is only suggested to introduce a bit of diversity into Scenarios that might get a little stale in their opening stages.

[113] VICTORY CONDITIONS

GENERAL RULE: Players must, at the start of the game, decide which Victory System they wish to use. All Players use the same Victory System, except the Xenophobe races, which are required to eliminate all other races in the volume to win (see 112.3).

VICTORY SYSTEMS OPTIONS

[113.1] Political Victory: The first Player to have imposed at least one truce on every Player in the game is declared the political victor. Note that the victor can win regardless of the number of truces imposed upon him. This system is suggested for Players wishing relatively short Scenarios, or in games with a large number of Players.

[113.2] Timed Economic Victory: After the 10th EcoYear of play, the Player with the greatest wealth (see 113.4) is the winner.

[113.3] Volume Economic Victory: At the end of the first year where all primary and secondary systems either have one or more Population Points or have gone nova, the game ends and the Player with the greatest wealth (see 113.4) wins. At the start of the game Players, by mutual agreement, may wish to reduce the number of systems from all 17 to 12, or 10, if only a few Players are involved in the game.

[113.4] Greatest Wealth is computed by doubling a Player's normal yearly MLC income in all his currently controlled populated systems, adding the average incomes of all controlled tertiary systems (see 105.4), multiplying by the total Population Resources, then dividing by ten times the number of systems controlled, and finally adding the MLC left over from the last Expenditures Phase (i.e., "cash on hand"). An equation summarizing this process is given below:

(2H+T)P/10S+C

where H = income of habitable controlled systems, T = income average of tertiary controlled systems, P = total population, S = number of controlled systems, and C = MLC left over from last Expenditures Phase.

[114] POLITICAL DOMINATION OPTIONAL RULE

GENERAL RULE: This optional rule allows one Player to make others subservient to him through taxation, and thus shows how the Hegemonies and Leagues actually formed in the early decades of the Outleap. Its primary effect in game terms is to introduce even greater political complications, and to allow Players to maintain a temporary superiority longer, and make warfare a common event, often as Players attempt to exert or throw off domination of another.

CASES:

[114.1] A Player may make another subservient to him when he accepts a truce. The truce requestor must accept subservience if his home system StarGate is permanently neutralized at that time, and Enemy StarForces occupy the home system's LiteZulu, or if he requested a truce of the same Player in the previous year at any time. In all cases, the truce requestor may accept subservience if he desires, but is not required to do so.

[114.2] A subservient Player must give 10% of his total MLC income each EcoYear to the Player who dominates him. If more than one dominates him, he need only pay the Player that first dominated him. The subservient Player may be asked to supply any other items or MLC, but giving it is strictly voluntary.

[114.3] A subservient Player may only escape his status by declaring war on the dominating Player. If he can avoid neutralization of any of his StarGates during the first ten Stellar Turn of war, or if he can neutralize any Enemy StarGate before one of his own is neutralized, or if he accepts a truce offer from his Enemy, the subservience is lifted. A Player subservient to many Players need only overthrow subservience to the original dominating Player.

[114.4] A dominating Player may in no way use the Population Resources or other items of subservient Players. He collects his taxes, and must get voluntary cooperation for anything more. Thus dominance - subservience does not affect the basic individuality of each Player's decisions and interstellar empires.

[114.5] In the strange case that Players wish to rig up a subservient relationship for their mutual benefit, a brief war must be declared and a truce formed, per the normal rules. This means the necessary risks of the Truce Politics Table must be taken. Players must remember that they are never entirely their own masters, and the demands of the peoples they govern are represented by the war & truce mechanics.

[41.0] SCENARIO 15, 2946 A.D., THE THIRD XENOPHOBE INCURSION

[41.1] INTRODUCTION

Sixteen decades of peace lulled the PSL into a false sense of security. When the Xenos, supposedly planet-bound, broke the PSL blockade and made a final thrust for victory, the PSL was caught dangerously weak. The Wanderers, never having fought the Xenos nor known firsthand of their barbarity, were hesitant until the Xenos novaed a PSL star.

[41.3] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Xenophobe Player: two StarGates, positioned according to (31.0)6
PSL Player: All systems on the Stellar Display2

Beginning with Game-Turn Two, the PSL receive one additional StarForce every even numbered Turn until a total of six additional StarForces have been received. On the Game-Turn following the destruction of the first PSL system, four additional PSL StarForces appear. StarForces appear at any Friendly StarGate.

[41.3] VICTORY CONDITIONS

Xenophobe Victory Points:

  • 50 Points for each PSL home system destroyed
  • 30 Points for each secondary system destroyed
  • 5 Points for each tertiary system destroyed
  • 1 Point for each destroyed PSL StarForce

PSL Victory Points:

  • 80 Points for each Xeno StarGate permanently neutralized
  • 10 Points for each Xeno StarForce destroyed

Xenophobe Player wins automatically if all PSL home systems are destroyed.

[41.4] SPECIAL RULES

See Section (31.0), Xenophobe Special Rules.

Transcriber's note: the printed scenario numbers its orders-of-battle paragraph and its victory-conditions paragraph both as "41.3" and has no 41.2; both are transcribed with their printed numbers.

[42.0] SCENARIO 16, 2981 A.D., THE FAKERWAR

[42.1] INTRODUCTION

Human, L'Chal-Dah and Rame politicians attempted to dominate the PSL Congress. StarForce commanders divided their Forces into FakerForces, maneuvering to intimidate neutrals (especially the Wanderers) into aligning with their respective leaders. The war proved inconclusive, and the election of 2982 brought new unity to the PSL.

[42.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
Human Player: Sol, Alpha Centauri, Tau Ceti, Epsilon Indi, Epsilon Eridani, 82 Eridani, Delta Pavonis4
L'Chal-Dah Player: Sigma Draconis, 61 Cygni, HR 8832, Eta Cassiopeiae4
Rame Player: 70 Ophiuchi, HR 7703, 36 Ophiuchi, CD-204

[42.3] VICTORY CONDITIONS

The first Player to have FakerForces in eight uncontested tertiary systems for two consecutive Game-Turns wins. OR the first Player to have eight FakerForces in Wandering's End (2223/+8) wins, if there are no Enemy FakerForces there.

Setup note printed in the scenario's introduction: the Wanderers Home System is located in hex 2223/+8.

[42.4] SPECIAL RULES

StarForces must break down into FakerForces as soon as possible. Combat between FakerForces is possible, but FakerForces may not assault StarGates. Each time a system is entered by a FakerForce for the first time a chit is picked. If it is an "8" or "9," the FakerForce is randomized (the StarGate thought it was under attack and counter-attacked). If opposing FakerForces fight in a neutral star hex, the neutral StarGate is ignored.

[43.0] SCENARIO 17, 3010 A.D., RXPEXY DISPUTE

[43.1] INTRODUCTION

After being refused entry into the PanSentient League, the RxPexy attempted to remove PSL colonists from RxPexy space, and then launched a campaign against PSL space.

[43.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
PSL Player: All systems on Stellar Display (incl. Wandering's End) plus four systems deployed randomly according to (31.1)16
RxPexy Player: Six systems deployed randomly within six hexes of the PSL randomly deployed systems8

[43.3] VICTORY CONDITIONS

PSL Victory Points:

  • 10 Points for each RxPexy StarGate neutralized

RxPexy Victory Points:

  • 10 Points for each randomly deployed PSL StarGate neutralized
  • 5 Points for each PSL tertiary StarGate neutralized
  • 15 Points for each PSL secondary or home StarGate neutralized

[43.4] SPECIAL RULES

All randomly deployed systems must be on the same side of the Volume (i.e., either positive or negative). The Volume extends ten more hexes vertically for purposes of Known Space shift limits.

[44.0] SCENARIO 18, 3175 A.D., US REVOLUTION

[44.1] INTRODUCTION

The Union of Sentients declared independence, and the PSL launched an uninspired campaign to return the US to PSL control. The RxPexy took advantage of the PSL's involvement to again try to eject PSL colonists from their territory.

[44.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
PSL Player: All systems from (43.2)18
US Player: six systems deployed randomly according to (31.1)6
RxPexy Player: same as (43.2), on opposite side of Volume from US6

[44.3] VICTORY CONDITIONS

PSL Victory Points:

  • 10 Points for each US StarGate neutralized
  • 5 Points for each RxPexy StarGate neutralized

US Victory Points:

  • 100 Points if no US StarGates are neutralized by Game-Turn Forty
  • 20 Points for each PSL StarGate neutralized

RxPexy Victory Points:

  • 10 Points for each PSL tertiary StarGate neutralized
  • 15 Points for each randomly deployed StarGate neutralized
  • 20 Points for each secondary or home StarGate neutralized

[44.4] SPECIAL RULES

RxPexy/PSL hostilities do not commence until Game-Turn Four (i.e., no attacks until then; units may shift into enemy space). US/PSL hostilities begin on Game-Turn One. As all stars have Gates, it is suggested that StarGate counters be used to show the location of randomly deployed stars.

[45.0] SCENARIO 19, 3447 A.D., THE WAR OF OBSOLESCENCE AND TREACHERY

[45.1] INTRODUCTION

A Gnostech labor strike allowed the RxPexy to launch an attack on the other PSL races in their old, inefficient, dangerous and slow tachyon cruisers. After a few days of debate, the Gnostechs returned to duty and the RxPexy were defeated.

[45.2] ORDERS OF BATTLE AND DEPLOYMENT

Star Systems and StarGatesStarForces
RxPexy Player: Same as (44.2)5 (tachyon)
PSL Player: Same as (44.2), plus US systems24

[45.3] VICTORY CONDITIONS

PSL Victory Points:

  • 40 Points if no PSL systems are occupied on Game-Turn Twenty (StarGate may have been neutralized)
  • 10 Points for each neutralized RxPexy StarGate

RxPexy Victory Points:

  • 15 Points for each tertiary or random StarGate neutralized
  • 25 Points for each home or secondary StarGate neutralized

[45.4] SPECIAL RULES

PSL StarForces and StarGates are considered inactive (nonexistent) at the start of the game. Pick chit at end of each Game-Turn; when "9" is picked, StarForces and StarGates are activated. StarForces may appear at any system. Tachyon cruisers may move two lites per Turn, they have no Defense Strength. Tachyon cruisers neutralize StarGates by moving into LiteZulu of inactive Gate, thereby neutralizing it permanently. Tachyon cruisers may TacShift normally.

[46.0] SCENARIO 20, 2947 A.D., OPERATION CARTHAGE [Solitaire Game]

[46.1] INTRODUCTION

After defeating the invasion force of the Third Incursion, a PSL squadron shifted to the Xenophobe home system. The system, and all its occupants, were destroyed by conversion bombs just as a Xeno transport fleet was shifting to a safe haven in a "secretly located" system, where they could breed more of their repulsive kind to eventually return to PSL space.

The Scenario is played on the Tactical Display. Deploy the Xeno StarGate normally and the Xeno Transport (StarForce) randomly. Four PSL StarForces enter the Display normally on Game-Turn One. Their objective is to neutralize the StarGate and induce a nova before the Transport shifts off the Display. Xenophobe response is determined by chit pick, according to the chart below. (It is assumed that the Xenos, defeated and deranged, would have lost much of their tactical flexibility.) The Transport is in Stellar mode.

[46.2] XENOPHOBE RESPONSE CHART

Pick separate chits for Gate and Transport.

ChitResponse (Gate)Response (Transport)
1Full attack on nearest unitFull attack on nearest unit
2Full defenseFull defense
350% attack, 50% defense50% attack, 50% defense
4Full attack on nearest unitTacShift away from PSL units
5Full defenseChange mode
6Full defenseBreakoff (if in Battle mode, full defense)
750% attack, 50% defenseTacShift away from PSL units
825% attack, 75% defenseFull defense

The game ends when the Transport breaks off, or when the system is incinerated.

STARFORCE ERRATA

In early editions of StarForce, certain values in this Scenario were in error. These are corrected below.

The printed errata restates the Rescue Mission rules (§38.0, 38.1, 38.2 and 38.5) with corrected values. On reading, the restated text matches §38.0 through §38.5 above, so it is not reproduced a second time.

Outreach

[1.0] INTRODUCTION

Outreach is a simulation of intra-Galactic exploration and conflict. Extrapolating some of the trends depicted in SPI's StarForce game, Outreach posits large-scale, telesthetically-guided interstellar travel by a variety of species. The game centers around a period of relatively rapid expansion by ambitious, dynamic civilizations striving to increase the range, and perfect the utilization of their access to the resources and experiences of the Universe.

The game is divided into Game-Turns, during which each Player has the opportunity to explore unfamiliar reaches of the Galaxy, to contact any sentient beings with similar capacity for telesthetic interstellar travel, to interact with any that are contacted, and to allocate resources to such tasks as the settlement of explored areas, the production and maintenance of space-faring forces, and the increase of the level of the Player's "own" civilization. The object of the game is to locate and explore star systems, obtaining resources from them while attempting to neutralize similar efforts by other players.

Outreach may be played by one, two, three, or four players.

[2.0] GLOSSARY OF BASIC TERMS

For the convenience of the Players, the most significant of the terms which are referred to in the Rules are defined below:

StarFleet: The basic unit of strength in the game, each StarFleet represents, in addition to actual space-faring ships, an allocation of such resources as time, energy, personnel, equipment, etc. The shift of a StarFleet into a hex may therefore represent not solely a redisposition of forces in the military sense, but also—or, alternatively—an economic decision to apply resources to the development of that hex. There are three types of Starfleets: Regular, Explorer, and Dreadnought.

Shift: The instantaneous movement of StarFleets from point to point in space, or in game terms, from one hex to another. All movement in the game is in terms of shifting. Unlike most games, movement in Outreach is not traced through contiguous hexes between the points of origin and destination; rather it is a transfer from the point of origin directly to the destination without any actual movement through the intervening space.

Stargate: A permanent self-sufficient settlement or collection of settlements in a hex which enhances the ability of Friendly and Allied Starfleets to shift into the hex and which, when augmented, produces Resource Points which may then in turn be expended for the raising and maintenance of Starfleets. Each Stargate starts the game with a "0" value; the value may be increased by allotting Resources to it. (See 14.13, 14.14).

Force: A starfleet, or group of starfleets, owned by the same player or "directing will" which begin the Movement Phase in the same hex.

Friendly: A term describing the status of one Force or Stargate vis a vis another. A Force is Friendly to a second Force only if both are owned or controlled by the same Player or "directing will".

Autonomous Units: Units belonging to an imaginary "directing will", representing the forces of beings with telesthetic transport capacity which are not "owned" by any of the actual Players in the game. Autonomous units arrive according to special rules, and their actions are regulated by those rules. Autonomous units are controlled by a "Caretaker."

Caretaker: The Player controlling a given Autonomous force. The player "discovering" that force becomes its Caretaker.

Contact: The method whereby forces of different players within the same hex determine whether they have actually met and can thereby initiate interaction.

Interaction: The process which determines the relationship—friendly, neutral or hostile—between different forces that have effected contact.

[3.0] GAME EQUIPMENT

In producing a map of the galaxy for Outreach, we were somewhat handicapped by the fact that no one has ever really seen the whole thing! This problem is compounded by the presence of thick, obscuring clouds of interstellar dust, which at various distances, and with variable success, block our view along the plane of the Galaxy in almost every direction. The map is therefore based on the best guesses of experts, which in turn are based upon observations of the portion of the Galaxy which can be seen (parts of several spiral features are clearly discernable) and extrapolations based on the appearance of other galaxies with presumably similar features. At any rate, all the individual stars listed by name on the game-map are correctly situated relative to each other in the plane of the Galaxy.

The 22" x 34" mapsheet depicts an area some 28,000 by 50,000 light years, including approximately one-third of the Galaxy. Each hex is some 1200 light years in diameter, and represents a portion of space some 1500 light years thick. The game-map contains several different features:

Spiral Axis (green) Hexes: These hexes lie in the central realm of the Galactic spiral features and contain the thickest concentrations of planet-rich stars.

Spiral Fringe (gray) Hexes: These are situated along the edges of the spirals and contain relatively fewer Stars than the Spiral Axis Hexes.

Inter-Spiral (black) Hexes: These are the hexes defining the spaces between the spiral arms comprising the Galaxy. Few stars exist in these regions.

Galactic Nucleus Hexes: The center of the Galaxy, closely packed with older stars which are unlikely to possess many planets.

Galactic Core Hexes: These three hexes indicate the very center of the Galaxy. No one has any idea what is there.

Beacon Stars: Hexes containing essentially the largest and most radiant stars visible from Earth. Each star has its official designation or name printed in its hex. Names have no bearing on play and are included in the interest of scientific accuracy.

Interstellar Dust Hexsides: Much of the Galaxy is obscured from Earth because of the presence of these thick, obscuring clouds. They seem to be concentrated in the area of the spiral arms. All of the ones we know of are included on the map [as well as many we don't know of.]

[3.2] PLAYING PIECES

On the die-cut counter sheet there are four differently-colored sets of Player pieces, four sets of Autonomous Force Counters, and 100 other miscellaneous markers. Players should punch these pieces out of the counter-sheet and sort them by color and type into the compartmentalized plastic tray.

[3.21] Unit Counter Manifest

Player-owned StarFleet counters: Each counter may represent any number and/or combination of types of StarFleets, each with a fleet designation on the front and a "C" marked on the back. The "C" side is used to indicate contact (See 7.0). Each player will keep track of the composition of the total Force that each of his StarFleet counters represents on a separate piece of paper.

Player-owned StarGate counters: Each counter may represent one StarGate of any System Point Value (see 14.1). Each player will maintain a record of the current System Point Value of each of his Friendly StarGates on a separate piece of paper.

Autonomous Force StarFleet Counters: Unlike the Player-owned counters, each of these always represents one Autonomous Force StarFleet. The type of StarFleet (Dreadnought or regular) is determined by the backprinted symbol on each counter, which is only revealed when necessary for Conflict or Reduction resolutions (see Sections 9.0, 10.0).

Autonomous Force StarGate Counters: Each counter represents one Autonomous Force StarGate. Unlike the Player-owned StarGate counters, the System Point Value of these StarGates is non-changeable and printed on the back of each counter.

Wisdom Chits: There are ten of these; all have a "W" printed on the front. Nine are blank on the reverse side, while one has an "X" on the reverse side.

Beacon Stars: These counters represent "new" stars discovered during the game. (See 15.0)

Potential Value (PV) Chits: Each PV chit determines the Potential System Point Value of a particular hex on the map (See 6.0). There are three values on the chit. The value in the upper left hand corner is operative if the applicable hex is Spiral Axis; the one in the center is applicable if the hex is Spiral Fringe; and the one in the bottom right hand corner applies to Interspiral hexes. Thus, using the chit pictured, if the hex it were chosen for were Interspiral, its Potential System Point Value would be "two"; if it were Spiral Fringe, its Potential System Point Value would be "one"; if it were Spiral Axis, the hex would have a Potential SP Value of "five".

[3.3] SET-UP

Determine how many people will be playing and select an appropriate scenario (see 18.0). The Players sit around the map so that it is clear who is sitting to the left of whom (see 4.2). Each Player receives a set of counters and deploys them according to the instructions in the Scenario set-up.

[3.31] Place all the Wisdom Chits on the table (not the game-map) "W"-side up. Then, without revealing the reverse sides, place one Wisdom Chit, selected at random, in each Galactic Core hex for a total of three used. Each time a Wisdom Chit is returned to those deployed off board all Wisdom Chits are mixed again (see Case 11.15).

[3.32] Place all Potential Value Chits in a wide-mouthed container. Players draw PV Chits from this container at random when necessary (see Rule 6.0), and the chits are returned to the container when no longer needed on the map.

[3.4] INVENTORY OF GAME PARTS

A Complete game of Outreach includes:

  • One Rules booklet
  • One Sheet of Die-Cut Playing Pieces
  • One 22" x 34" Game Map
  • Four Identical Sheets of Charts
  • One Game Box
  • One Plastic Die

[4.0] SEQUENCE OF PLAY

[4.1] THE GAME-TURN

Outreach is played in Game-Turns. During each Game-Turn, Players will have the opportunity to move their forces, to explore unfamiliar regions of the Galaxy, to interact with any other forces with which they may come into contact, and to allocate their resources to various political, military, and economic projects as they see fit. The Scenarios (18.0) define the number of Game-Turns which the Game will last; generally, play will continue until one or more Players have achieved a victory (as defined in each scenario). All action must take place in the sequence outlined below. Any action occurring outside the sequence as outlined is a violation of the Rules and is not permitted.

[4.2] GAME-TURN OUTLINE

A. SHIFT ORDER DETERMINATION PHASE

The Players seat themselves around the game map. Each Player draws a chit from among the PV chits and totals all three numbers which appear on the chit. The Player with the highest total moves first, and the Player immediately to the left of the first player moves second, and so forth. This procedure determines the Shift Order for that Game-Turn only; i.e., the Player moving first on Game-Turn One will not necessarily move first on Game-Turn Two.

B. SHIFT PHASE

1. Regular Shifts:

Beginning with the first Player and continuing in clockwise Player order all StarFleets may attempt movement from one hex to another hex in accordance with the Rules governing Stellar Shifting (5.0). As each StarFleet (or group of StarFleets) is shifted, the success of the move is determined by consulting the Scatter Table (5.5), and any effects called for by that table are applied immediately. After all Player movement is complete, any eligible autonomous forces are moved by their "caretaker" in accordance with the rules governing the actions of autonomous forces (13.0).

2. Reserve Shifts:

Beginning with the last Player to complete Regular Shifts, and continuing in reverse order back to the first Player to move, each Player may move one "reserve" StarFleet or stack of StarFleets which did not conduct a Regular Shift earlier in the Game-Turn (see 5.2).

C. EXPLORATION PHASE

Beginning with the first Player and continuing in order with each of the other Players, any "unexplored hexes" in which a Player has one or more StarFleets may be explored. Refer to the Exploration Table (6.7) to determine the success of exploration efforts (see 6.0).

D. GALACTIC INTERRELATION PHASE

1. Contact Segment:

For each hex in which there are forces which do not belong exclusively to one Player, the Contact Table (7.4) is consulted to determine if the forces in question are aware of each other's presence (see 7.0).

2. Interaction Segment:

For each hex which contains forces controlled by different players, each of the affected players may refer to the Interaction Matrix (8.3) to determine the relationships between the two Players. The Interaction Matrix is also used to define the relationship between a Player and any Autonomous Force which may be contacted. Players may change their relationship vis a vis the other players' forces each turn, within the confines of 8.0.

3. Conflict Segment:

For each hex which contains more than one Force conflicts between pairs of forces may occur (see 9.0), as long as contact has been established and according to the relationships of the parties involved.

4. Reduction Segment:

"Reduction" is the neutralization (a process which renders the gate useless) of StarGate counters. Neutralization may occur in hexes where there is (1) a StarGate counter and (2) one or more Unfriendly Forces and no Friendly Force (see 10.0).

E. FATE PHASE

Beginning with the first Player and continuing in order with each of the others, Players roll on the Fate Table, applying, if they so desire, Resource Points to influence the results. Any results applicable from such die rolls are implemented immediately. In the event of the discovery of an Autonomous Force, recourse to the Interaction Table and possibly the Conflict and/or Reduction Tables will be called for.

F. RESOURCE ALLOCATION PHASE

The Players calculate their Resource Point totals based on the amount of System Points controlled. Each Player may transform existing StarFleets into StarGates or gain the allegiance of neutral settled hexes. Each Player may also expend Resource Points to construct new StarFleets and/or to settle hexes with a Friendly StarGate. (see 14.0)

[5.0] STELLAR SHIFTING

GENERAL RULE:

During the Shift Phase, each Force may conduct Stellar Shifts (movement) from one hex to another. Shifting is not movement through space, as is normally thought of, but rather it is "jumping" from one point in space directly to another point without having physically traversed the intervening space. This transfer from point to point is referred to as a "shift." As such, there are no "Movement Allowances" for StarFleets (as there are for units in many other SPI games). The capacity of a Force to shift from one point to another is theoretically unlimited, although in practice there are several factors which enhance and/or constrain their capacity to move. For example, shifts of long distances are generally more risky than shorter shifts. A "risky" shift may fail and result in the shifting Force being "scattered." This risk decreases as the Civilization Level increases.

The Movement Phase consists of Regular Shifts by each Player, followed by the movement of Autonomous forces and any Reserve Shifts conducted by the Players.

PROCEDURE:

Starting with the first Player and continuing in order (see Case 4.2), each Player conducts Regular Stellar Shifts for as many of his StarFleets as he wishes to move. The distance of the shift is calculated in hexes and cross indexed with a die-roll on the Scatter Table (5.38). If a "scatter" result is obtained, the effects are applied immediately. After all Regular Shifts have been completed, any Autonomous StarFleet movements called for by the rules governing the use of Autonomous Forces are conducted (see Rule 12.0). Finally each Player, starting with the last Player to conduct Regular Shifts and proceeding in reverse order, has the option to conduct Reserve Shifts for one Force (only).

[5.1] HOW TO CONDUCT STELLAR SHIFTS

[5.11] During the Shift Phase, each Player may move (or shift) as many or as few of his StarFleets as he wishes. Players may never shift, nor examine other Player or Autonomous Forces or StarGates (Exception: see 13.23).

[5.12] Each Force is shifted individually. Once a Player stops shifting one Force and begins shifting another, the first Force may not conduct any more Stellar Shifts until a subsequent Shift Phase.

[5.13] Friendly StarFleets occupying the same hex at the beginning of the Shift Phase may combine to form one or more Forces. Friendly StarFleets in different hexes at the start of the Shift Phase may not combine to form one Force during that Shift Phase. Therefore, a Force which shifts from hex A to hex B may not "pick up" a StarFleet in hex B and then shift to hex C during that Shift Phase. The original Force, by itself, may, however, shift to hex C, providing the requirements of Case 5.21 are met.

[5.14] There is no limit to the number of StarFleets that may occupy any one hex. The number of StarFleets in a hex has no effect on the ability of any one Force to shift in or out of that hex.

[5.15] Each StarFleet has a Civilization Level Range (CLR) which limits the distance over which it may shift in relative safety. The CLR of a StarFleet is equal in hexes to the square of the owning Player's Civilization Level (exception, for Autonomous Civilization Levels see 11.2). For example, if Player A has a Civilization Level of one, the CLR of all his StarFleets is one hex; if Player B has a Civilization Level of 3, all his StarFleets have a CLR of nine (3 X 3) hexes. A Force may conduct a Stellar Shift that exceeds its CLR only if it shifts from (not "to") a Friendly or Allied StarGate.

[5.2] THE CONCEPT OF CONTINUAL SHIFTING

[5.21] A Force which successfully completes a shift (i.e., does not scatter), the distance of which is less than or equal to that Force's CLR, to a hex containing a Friendly or Allied StarGate, may continue its movement by conducting another shift. There is no limit to the number of shifts which a Force may make to hexes containing Friendly or Allied StarGates during one Movement Phase, so long as these conditions are fulfilled.

[5.22] A Force which successfully shifts to a hex which does not have a Friendly or Allied StarGate must cease movement for that Game-Turn.

[5.23] A Force which successfully completes a shift which is greater in distance than that Force's CLR must cease movement for the rest of that Game-Turn (see 5.15).

[5.24] A Force for which a "scatter" result is obtained on the Scatter Table may suffer attrition (see 5.51). Any surviving StarFleets are immediately transferred to their designated scatter hex (see 5.52), and must cease movement for the rest of the Game-Turn. Exception: Autonomous Forces never suffer attrition.

[5.3] RESERVE SHIFTS

Forces that have not conducted a regular Shift in a given Game-Turn may use Reserve Shift under certain conditions. Except where noted the Rules governing Regular Stellar Shifts apply equally to Reserve Shifts.

[5.31] Each Player may conduct Reserve Shifts only after all Autonomous Force movement (if any) has been finished.

[5.32] Only one Friendly Force per Player may be moved by Reserve Shift in any given Shift Phase.

[5.33] Forces which have conducted one or more Regular shifts during a given Game-Turn may not be moved by Reserve Shifting in the Game-Turn.

[5.34] A Force may only conduct Reserve Shifts that are equal to or less than that Force's CLR (see 5.15).

[5.4] SCATTER

All Forces which conduct Stellar Shifts of a distance greater than one hex run a risk of scatter and attrition. Scatter is involuntary, uncontrolled shifting of a force to a hex other than the one to which it was intended the Force should shift. Certain factors and conditions affect the chances for, and the potential severity of, scatter. In addition, forces that scatter may suffer attrition; i.e., they may lose some of their StarFleets.

[5.41] Calculate the length of the shift, in terms of the number of hexes, by tracing the shortest possible path of contiguous hexes between the hex the StarFleet(s) is shifting from and the hex it is attempting to shift into. In calculating the shift length count the destination hex, but do not count the hex of origin. A die is thrown and the result cross-referenced with the appropriate column, corresponding to the shift-length, on the Scatter Table. This determines the amount of attrition (if any) the force will suffer as well as the distance (in hexes) of any scatter. A second separate die-roll then determines the direction of the scatter (see 5.52).

[5.42] If a Force shifts to a hex with a Friendly or Allied StarGate or a Beacon Star the Player adds "one" to any die roll on the Scatter Table.

[5.43] If a shifting Force includes at least one Explorer StarFleet add "one" to any die-roll on the Scatter Table.

[5.44] If a shifting Force consists exclusively of Explorer StarFleets, the Player adds two to any die roll on the Scatter Table.

[5.45] If a Player's Civilization Level is greater than "one," add the difference between that Civilization Level and the number "one" to any die-rolls for that Player's Forces on the Scatter Table. For example, a Player's Civilization Level is 3; he will add "2" to the die-roll (3—1=2).

[5.46] Additions to die-rolls on the Scatter Table are cumulative. For example, if an Explorer StarFleet belonging to a Player with a Civilization Level of "one" shifted to a Friendly StarGate in a hex containing a Beacon Star the Scatter Table die roll would be adjusted by "+4".

[5.5] EFFECTS AND IMPLEMENTATION OF SCATTER

[5.51] If a Force that is attempting to shift a distance greater than its CLR (see 5.15) scatters, any attrition losses are doubled. Calculate the losses in StarFleets from the Percentage Loss Table and then double that number. Remember Autonomous Forces never suffer attrition.

[5.52] If a Force scatters, the direction of the scatter from the original destination hex is determined by rolling the die. See the scatter diagram on the map. The die roll corresponds to one of the numbered directions on the scatter diagram. Example: A Force intends to shift into hex 2020. The modified die roll result on the 6-8 column of the Scatter Table is 4. Therefore, the force scatters the 6 hexes. The die is rolled again and compared to the Scatter diagram; a "one" would send that force to hex 2014; a three would put it in hex 2623.

[5.53] A Force which scatters is removed from play if:

a) it scatters off the board;

b) its attempted and unsuccessful shift was from or to a Galactic Nucleus hex; or

c) it has no unblocked line of sight (see 15.0) to a Friendly or Allied StarGate from the hex into which it has scattered. Exception: If a Force attempting a shift to a Friendly or Allied StarGate scatters, it is not removed from play.

[5.6] THE SCATTER TABLE

(see separate sheet)

[5.7] EFFECTS OF SPECIAL GALACTIC PHENOMENA ON SHIFTING

[5.71] The chances of scatter for Forces which shift into Beacon Star hexes are reduced (see 5.42).

[5.72] A Force which shifts out of or into a Galactic Nucleus hex and is scattered is immediately removed from play.

[5.73] A Force may shift through an InterStellar dust cloud (see 16.0) hexside only if the shift is from one Friendly or Allied StarGate to another or from one hex to an adjacent hex. A Force is considered to be shifting "through" a dust cloud hexside if the line of sight from the hex it is shifting from to the hex it is shifting to is blocked by a dust cloud hexside (see 15.15).

[6.0] EXPLORATION

GENERAL RULE:

Each Spiral Axis, Spiral Fringe and Inter-spiral hex on the board has a potential System Point (SP) value. At the beginning of the game each Player knows the potential SP value of a few hexes. In order to discover the value of an unknown hex, a Player must "explore" that hex with StarFleets. This is done by each Player during the Exploration Phase of the Game-Turn.

PROCEDURE:

Count up the number of Friendly Explorer StarFleets in each hex that is to be explored and multiply this number by "2". Add to this the number of regular StarFleets. Roll the die for each hex and cross-index the die-roll with the adjusted StarFleet total on the Exploration Table (6.2). The result says whether or not Exploration was successful. Exploration Table rolls are resolved in turn, starting with the first Player (see 4.2).

[6.1] THE MECHANICS OF EXPLORATION

[6.1] A Player who successfully explores a hex which:

a) has not previously been successfully explored, and which

b) has no Potential Value chit in it, randomly picks a Potential Value chit (see 3.32) and places it face down in the explored hex. Only the Player who conducted the exploration may see the face of the Potential Value chit, until such time as that hex is successfully explored by another Player.

[6.12] A Player who successfully explores a hex with a Potential Value chit already in it gains the right to see the value of the chit.

[6.13] A Player may not explore any hex which contains any StarGate counter (even Friendly), even if that hex also contains a Potential Value chit.

Example: if a Player explores a hex and receives a high potential value he may forestall other-player exploration of that hex by building a StarGate.

[6.14] Autonomous Forces never use the Exploration Table (see 11.0).

[6.15] Galactic Nucleus hexes may not be explored.

[6.16] Potential Value chits are removed from any hex which contains a StarGate that has a System Point Value equal to the Potential Value of the hex (see Case 14.16).

[7.0] CONTACT

GENERAL RULE:

Whenever a hex is occupied by a StarGate counter and/or a Force(s) any of which are not Friendly to or Allied with one another, the Players consult the Contact Table to determine whether or not all forces, etc., involved become aware of each other's presence in that hex. At his option, a Player may seek to avoid Contact. Each distinct group of Friendly StarFleets and/or Friendly StarGates (Player-owned or Autonomous) in a hex must (separately) consult the Contact Table. Once Contact in a hex is established it automatically affects all Forces and the StarGate (if any) in that hex. Players may only proceed to use Interaction when Contact has been established.

PROCEDURE:

Players resolve all Contact situations starting with the lowest-numbered affected hex. For each Player-owned Force and/or Stargate involved in a possible Contact resolution, the owning Player calculates the Contact Index maximum and minimum for each Force involved and then determines which column on the Contact Table he will choose to utilize. In general, the Player will be able to choose any Index number between the maximum and minimum that he wishes, according to the action he wishes to undertake. For each Active Autonomous Force/StarGate, the Caretaker for such Force calculates the largest possible Contact Index. For each Passive Autonomous Force/StarGate, the Contact Index is the number of Starfleets in the hex. If there is a Stargate present (Autonomous) the Caretaker adds "3" to the Index, if the Autonomous Force is Passive. The Contact Index for each distinct Friendly Force/StarGate in each hex is now announced simultaneously, and each Index is cross-referenced with a die roll on the Contact Table. If a "C" is the result on any roll for a particular hex, invert any one Player-owned Starfleet counter in that hex and place it on top of all the other counters and chits in that hex. That hex is now said to contain a "Contact" marker. Repeat this procedure until all combinations of non-Friendly, non-Allied Forces/StarGates in the same hex (that are eligible) have used the Contact Table.

[7.1] HOW TO CALCULATE THE CONTACT INDEX

[7.11] To determine the highest possible Contact Index, add the number of Friendly Explorer Starfleets in the hex to the total number of all the Friendly Starfleets in that hex; then add in the System Point Value (see 14.0) of any Friendly StarGates present. This is the maximum possible Contact Index.

[7.12] The lowest possible Contact Index is the System Point value of the Friendly StarGate (if any) in the hex. If no Friendly StarGate is present, then the lowest possible Contact Index is "zero."

[7.13] A Player may select any Contact Index he wishes as long as it falls between the highest and lowest possible values (inclusive) for that hex.

[7.2] USE OF THE CONTACT MARKER

[7.21] A "C" result on the Contact Table affects all Forces and StarGate (if any) in that hex. All forces in that hex are considered to be "in Contact" with each other so long as they remain in that hex.

[7.22] At the start of the Contact Segment of each Galactic Interrelation Phase, any Forces which have shifted into a hex containing a Contact marker are placed under the Contact marker. Any such Forces are automatically in Contact with all other Forces and/or the StarGate in that hex.

[7.23] During the Resource Phase, any Player who places a StarGate counter (see 14.1) in a hex containing a Contact Marker must place it beneath the Contact Marker. The StarGate is automatically considered to be in Contact with all Forces in the hex.

[7.24] Allied Forces (see 8.2) are considered to be in Contact with each other at any time that they are in the same hex. So long as all Forces and/or StarGate in a hex are Allied with each other no Contact Marker is utilized. However, if a non-Allied Force shifts into the hex a Contact Table resolution is required.

[7.25] A Contact Marker is automatically placed in any hex which, at the beginning of the Contact Segment, has three or more Forces in it under the following provision: At least one Force must be allied to a second Force which in turn is Allied to a third, which is not Allied to the first Force. Example: Player "A" is Allied with Player "B". Player "B" is allied with Player "C". Player "C" has never had any Force or StarGate in Contact with Player "A". At the beginning of the Contact Segment, Forces of all three Players are present in a hex. Invert any of the present StarFleet counters belonging to a Player and place them on top of all other chits and counters; they are all in Contact.

[7.26] An inverted StarFleet counter ("Contact Marker") is returned to face-up status again (removed) whenever all Forces and/or the StarGate in that hex are Friendly or Allied (see 7.24).

[7.27] The inversion of a StarFleet counter to indicate Contact in a hex has no effect on the particular Force represented by the counter. It may conduct stellar shifts, Conflict, Reduction, etc., as usual. If the inverted StarFleet counter indicating Contact shifts away from the hex in which it was inverted, one of the remaining Player-owned StarFleet counters is then inverted to indicate Contact.

[7.3] EFFECTS OF BEING IN CONTACT

[7.31] Interaction Matrix resolutions (See 8.2, 8.3) are possible, and may be required, only in a hex containing a Contact Marker and/or between Forces/StarGates in Contact.

[7.32] Conflict (9.0) and/or Reduction (10.0) are possible only in a hex containing a Contact Marker and/or between Forces/StarGates in Contact.

[7.4] CONTACT TABLE

(See separate sheet.)

[8.0] INTERACTION

GENERAL RULE:

The Interaction Matrix is used to define how Players in Contact may interrelate with each other (within the scope of the game) as well as with any Autonomous force with which they may come into Contact. There are three Interaction Options: A) Co-operation, B) Neutral, and C) Hostile. Each Player picks an Option separately with regard to each other Player or Autonomous force (hence, it is possible to be co-operative towards one Player while being hostile towards another). These Option choices are kept track of on an Interaction Display. Players may alter their choice of options once each Game-Turn during the Interaction Segment. Autonomous force Options, with regard to a Player, may be altered randomly after all Player Options choices have been made during the Interaction Segment. By cross-referencing Options between Players who have forces in Contact on the Interaction Matrix, the Players can determine what courses of action they may take in reference to each other.

PROCEDURE:

At the start of each Interaction Segment, each Player determines which other Players and Autonomous Forces have StarFleets or StarGates in Contact with any of his own StarFleets or StarGates. For each Player or Autonomous Force with which he is in contact, each Player places a corresponding-color marker in an Option Space in the "We" section of the Interaction Display. Then, all Interaction Displays are simultaneously revealed. Each Player determines the Option chosen by each other Player toward his color. He then moves each color marker down into the "They" section, to the space in that column which corresponds to the choice toward his color of that Player.

Any random Autonomous Force Interaction Option changes (8.4) that are called for are now determined by die rolls on the appropriate Autonomous Force Random Interaction Option Table column, and the Interaction Displays are adjusted accordingly.

[8.1] HOW TO USE THE INTERACTION DISPLAYS

Each Player has an Interaction Display. The Interaction Display shows the current Interaction Options chosen by the Player vis-a-vis each other Player and Autonomous force and vice versa. Each Player's Interaction with each other Player or Autonomous force is unique and is determined separately. During the Interaction Segment, Players may alter their Interaction Option choices by re-arranging their Interaction Displays. After all Player choices have been made, Autonomous force Options with regard to certain Players may be altered randomly and the Interaction Displays adjusted accordingly.

[8.11] During the Interaction Segment, Players must choose Interaction Options (see 8.2) vis-a-vis any other Player(s) and any Autonomous Forces with which they have come into contact for the first time since the last Interaction Phase.

[8.12] After all Player Interaction Option choices have been made, Options must be selected randomly for Autonomous Forces which have been Contact with one or more Players for the first time since the last Interaction Phase. The "No Previous Option" column of the Random Interaction Option Table (8.4) is utilized. (Note that this applies both to Passive Autonomous Forces which will not have previously interacted with any Players in the game, and Active Autonomous forces which will have interacted with one or more other Players previously. (See 13.2).

[8.13] The horizontal dimension on the Interaction Display is used to keep track of the owning Player's Interaction Option Choices. For each other Player and/or Autonomous Force in the game with which the owning Player has at some point come into Contact, a StarGate counter of the appropriate color (or any other convenient marker) should be displayed in the appropriate vertical column of the Interaction Display. The choice of which column will indicate the owning Player's Interaction Option choice vis-a-vis the other. Example: If Player "X" has chosen Interaction Option "C" (hostility) with regard to Player "Y", Player "X" places a Player "Y" StarGate counter in the third column of his Interaction Display.

[8.14] The vertical dimension of the Interaction Display is used by each Player to keep track of the other Player's Autonomous Forces' Interaction Option choices vis-a-vis him. The Option chosen by others determines which horizontal column the StarGate counters will be placed in on the Interaction Display.

[8.15] During each Interaction Segment, a Player may alter his prior choice of Interaction Options by [8.16] Players may alter their Interaction Options only for Players and Autonomous forces with which they are in Contact (see Rule 7.2).

[8.17] Counters may never be removed from an Interaction Display unless a Player or Autonomous force is eliminated from the game (see 10.25). If a Player "loses contact" with another Player, the latter's StarGate counter remains in place on the former's Interaction Display and may not be moved until Contact is re-established.

[8.18] There are no Autonomous Force Interaction Displays, and Autonomous Forces may never Interact with each other.

[8.19] Autonomous Force Interaction Options may be altered during the Interaction Segment only after all Player alterations have been completed and under the following conditions: If a Player has had any counters on his Interaction Display shift from or to Option "C" during the current Interaction Segment, then all Autonomous forces with which he is in Contact are subject to random alteration of their Interaction Options in relation to him (only). For each Autonomous force, roll a die and cross-reference it with the appropriate column of the Random Interaction Option Table (8.4) to determine the Option chosen. (Exception, see Case 13.26.)

[8.2] INTERACTION OPTIONS

There are three Interaction Options: A=Co-operation, B=Neutrality, and C=Hostility. Each Player picks one of these Options with regard to every other Player and/or Autonomous force with which he comes into Contact, and vice versa. These combinations of Options limit the Interactions (in Game terms) which are possible between them. During the Interaction Segment, for every Player and/or Autonomous force that a Player comes into Contact with, each Player will select one of the three Options. After each Player has chosen his Options, each interacting pair of Players determines what combination of Options they have selected between the two of them. Then, after any possible Autonomous force alterations are resolved, each Player determines what Option combinations have resulted between him and each Autonomous force with which he is in Contact. Find the result from the list of options pairs below:

The Interaction Options

A/A: All Forces and StarGates of both sides are considered Allied. Friendly Forces may freely utilize Allied StarGates for shifting purposes and vice versa (Cases 5.21, 5.42). Friendly and Allied Forces/StarGates in the same hex during the Contact Segment are automatically considered to be in Contact (Case 7.24). A Force may never attack a Force to which it is Allied, nor may it reduce an Allied StarGate.

A/B: The Player choosing "B" may utilize the Player choosing "A"'s StarGates for shift purposes as if they were Allied, but not vice versa. Contact between other "A" and "B" Forces in other, mutually-occupied hexes is not automatic. Neither side may attack or reduce the other.

A/C: Contact in other, mutually-occupied hexes is not automatic. "A" may not attack or reduce "C." "C" Forces may attack "A" Forces or reduce "A" StarGates. Any such attacks are resolved two columns to the right from where they would be under normal circumstances on the Conflict Table. Any possible reductions are likewise resolved two columns to the right on the Reduction Table. Example: If a "C" Force attacks an "A" Force of equal strength, the die roll on the Conflict Table would be cross-indexed with the "200%-299%" column, rather than with the "100%-149%" column.

B/B: Forces of neither side may use the other's StarGates for shifting purposes, nor is Contact in other mutually-occupied hexes automatic. Either side may freely initiate conflict or Reduction resolutions against the other.

B/C: If "C" attacks any "B" force, or attempts to reduce any "B" StarGate, the attack or reduction is cross-indexed with the column on the Conflict Table or Reduction Table one column to the right of the one which would normally be used. Contact in other, mutually-occupied hexes is not automatic.

C/C: Conflict is automatic and mandatory in any hex in which both sides are in contact. Any losses incurred by the defender are doubled. (Translate the percentage loss given into a number of StarFleets and then double that number.) Note that although conflict is automatic, contact is not.

[8.3] INTERACTION MATRIX

(See separate sheet.)

[8.4] RANDOM INTERACTION OPTION TABLE

The RIOT is used by each Autonomous force's Caretaker to determine that force's Interrelations Options vis-a-vis each Player it is in contact with. If there has been no previous contact, the Caretaker uses that column. Otherwise he uses the appropriate (previously rolled) option column. Exception: see Case 13.26.

[9.0] CONFLICT

GENERAL RULE:

Conflict may occur during the Conflict Phase between non-Friendly, non-Allied Forces in hexes which contain a Contact Marker, subject to the restrictions outlined in Section 8.2.

PROCEDURE:

For each hex in which Conflict is possible, each Player present announces simultaneously whether or not he intends to attack (i.e., have conflict). Autonomous Forces will attack or not as mandated by the Rules governing their employment (Section 13.0). All attacking Players now simultaneously indicate their Approximate Conflict Capacity. However, for each attacking Autonomous Force, the Caretaker reveals the True Conflict Capacity. The Player (or Autonomous force) with the highest stated capacity attacks first. He chooses a force to attack (the defender) and both reveal their True Conflict Capacity. The attack is resolved on the Conflict Table. Losses are subtracted and the Player (or Autonomous Force) with the second highest Approximate (or True) Capacity now attacks (if that Force has any surviving StarFleets). This procedure is repeated until all attacks in the hex have been resolved. Players then proceed to the next hex in which there will be conflict and repeat the process.

[9.1] THE MECHANICS OF CONFLICT

[9.11] All Friendly StarFleets in a hex are considered to be one Force for the purposes of resolving Conflicts. No StarFleets may be "held back" or split into a second Force.

[9.12] Each Force in a hex may attack once and only once during the Conflict Phase. However, a given Force in a hex may be attacked any number of times during the Conflict Phase.

[9.13] Each Force attacks and defends independently. Two or more Forces may never combine for one single attack or defense.

[9.14] The True Conflict Capacity of a Force is the total number of StarFleets in the hex minus the number of Explorer StarFleets plus the number of Dreadnought StarFleets. Example: Player Z has 5 regular StarFleets, 3 Explorers, and 7 Dreadnoughts. It's true capacity is 19 (15—3+7=19).

[9.15] The Approximate Conflict Capacity of a Force is its True Conflict Capacity plus or minus (at the owning Player's option) up to 50% of the total. Thus a player with a true capacity of 10 may declare his approximate capacity to be anywhere between 5 and 15 (inclusive).

[9.16] For each Dreadnought StarFleet in an attacking Force, add "one" to the die roll in resolving the attack on the Conflict Table.

[9.17] For each Dreadnought Starfleet in a defending Force, subtract "one" from the die roll in resolving the attack.

[9.18] Losses are selected by the owning Player as he chooses. However, Autonomous Dreadnought StarFleets are always lost last (after all regular Autonomous StarFleets have been lost).

[9.19] Any die roll less than —2 is treated as —2, die roll greater than +9 is treated as +9.

[9.2] CONFLICT TABLE

(See separate sheet.)

[10.0] REDUCTION

GENERAL RULE:

Reduction is a process whereby an "enemy" StarGate is rendered useless. In some cases it may eliminate the StarGate entirely. A StarGate that has been successfully reduced is considered "neutralized"; it cannot be used for any purpose by anyone.

[10.1] THE PROCESS OF REDUCTION

Starting with the lowest numbered hex in which reduction is possible and continuing through to the highest, the owner of each Player Force (or the Caretaker of each Autonomous Force) calculates and reveals the Reduction Capacity of the Force attempting Reduction (10.22). The strongest Force (in terms of Reduction capacity) resolves the first Reduction attempt, rolling a die and cross-referencing the result with the appropriate column on the Reduction Table (10.3). If it is unsuccessful, the next-strongest Force (if any) resolves the second attempt, and so on, until the StarGate is Neutralized and/or all Forces for which a Reduction Capacity was revealed have resolved a Reduction attempt. If any Reduction attempt is successful, the StarGate counter is inverted to indicate its Neutralization.

[10.2] THE MECHANICS OF REDUCTION

[10.21] Reduction may be conducted only in a hex which, at the beginning of the Reduction Phase, has a StarGate in it and which does not have any StarFleets Friendly to that StarGate in it.

[10.22] Perform the following function to determine which column on the Reduction Table will be used: A) Add the total number of Dreadnought StarFleets in the reducing Force to the Civilization Level of the owning Player; this yields the Reduction Capacity of that force. B) Add the System Point Value of the StarGate to the Civilization Level of the owning Player; C) Subtract B from A. Reduction may be conducted only by a Force which includes at least one Dreadnought StarFleet. Example: Six Dreadnoughts owned by a Player with a Civilization Level of 2 attempt to reduce a StarGate with 3 System Points to a Civilization Level of 1. The Differential is 4: (6+2)—(3+1).

[10.23] Neutralized StarGates are useless; they are considered Friendly to no one. They do not enhance the shifts of any Player or Autonomous Force into their hexes, nor do they count toward any Player's System Point or Resource Point totals. However, neutral StarGates may be "De-neutralized" (to a Friendly status) by any Player (see 14.18).

[10.24] If a StarGate with a System Point Value of "zero" is Neutralized it is considered destroyed and removed from play. It is replaced with a Potential Value Chit of "zero".

[10.25] If a Player is at any time reduced to having no Friendly StarGates, he is eliminated from the game. All remaining Friendly StarFleets are also immediately eliminated from play.

[10.3] REDUCTION TABLE

(See separate sheet.)

[11.0] FATE

GENERAL RULE:

During the Fate Segment each Player, starting with the First Player and continuing in turn, must roll once on the Fate Table. Any relevant results are applied immediately.

[11.1] HOW TO USE THE FATE TABLE

[11.11] Each Player adds up his total number of System Points. He then throws a die and cross-references the die roll with his total System Points. Die rolls may be adjusted or the System Point column changed by the expenditure of Resource Points or by certain other actions of the Player. Players should note that various results are contingent upon certain pre-conditions and may be ignored if these conditions have not been fulfilled.

[11.12] A Player must add "one" to any Fate Table die roll for each "X" the rolling Player obtained on the Exploration Phase of the current Game-Turn. The adjusted die roll total may not exceed "six." (Exception—See Case 11.13.)

[11.13] A player may add "one" to any Fate Table die roll for each expenditure of 50 Resource Points by the rolling Player. Thus if a Player expends 150 Resource Points to affect the die roll he may add 3 to such die-roll. However, the adjusted die roll total may never exceed "eight."

[11.14] A Player may Shift one column to the left on the table for every five Resource Points the rolling Player expends for that purpose. This expenditure is in addition to and separate from the expenditure in 11.13. Thus a Player may expend 55 Resource Points and shift one column to the left and add one to the die roll.

[11.15] A Resource Point expenditure for the purpose of affecting a Fate Table roll must be made prior to that roll. Each expenditure affects only one Fate Table roll.

[11.16] Certain Fate Table results are pre-conditioned on the expenditure of Wisdom Chits. (see 11.2) Any such expenditures must be made prior to the Fate Table roll for which they are intended. The expenditure of a Chit affects only one Fate Table die roll. Expended Chits are placed with undeployed Wisdom Chits off the board (see 3.31).

[11.17] All applicable results obtained from a Fate Table die roll are applied immediately.

[11.18] The Fate Table is never utilized "by" Autonomous forces.

[11.2] EXPLANATION OF FATE TABLE RESULTS

A: After years of becoming increasingly "separatist", a sector of the Civilization comprised mostly of one particularly unsociable species severs all ties with the main body. Effect=10% Dissolution. (See 11.3)

B: A Charismatic and Fanatical religious Leader rises to prominence in the Central System of the confederation of beings. His Belief spreads more or less rapidly from system to system; then, having seemingly approached the peak of its potential, the Belief suddenly and dramatically is imbued with an almost Universal appeal when the by now revered Leader's heir apparent is martyred by virulent anti-Belief fanatics of his own species. The Belief develops a haughty presumptuousness that transforms into intolerance when met with resistance, and things turn nasty. Eventually the Belief becomes the focal point for those who remain within the social, political and economic fold, and the expulsion of the dissidents strengthens, rather than weakens the Civilization's cohesion. Effect=30% Dissolution; ignore any and all subsequent Dissolution results.

C: A festering and long-standing inability of two species (which are the most significant) to get along at last breaks out into irreconcilable conflict. The struggle is brief but brutal, and in its aftermath a genuine consensus finally develops—to split right down the middle. Effect=50% Dissolution.

D: The discovery of a highly potent and nutritious organic drug, which combines a mildly hallucinogenic effect with irregular but frequent jolts of ecstatic euphoria, proves highly addictive to some three-quarters of the sentient populations of the Federation. The effects of its consequent wide usage are disastrous for the cohesion of the Federation. Effect=70% Dissolution.

E: A gradual but irreversible trend to decay develops in the capacity of the Central Authority to retain active control. A crisis reveals the bankruptcy of the old order, and the consequence is a non-violent but virtually complete secession of most of the races from the Empire. Effect=80% Dissolution; decrease Civilization one Level.

F: A relatively authoritarian "regime" assumes control over a vast reach of space. But resentment builds up against the two chauvinistic ruling species, a tiny minority in the overall population of the area. The Authoritarian Leadership foolishly allows it to grow, until a Revolution leading to anarchy is the result. Effect=90% Dissolution. Decrease Civilization Level "one."

G: Appearance of Autonomous Force: Place 2 StarGates and 5 StarFleets (Civilization Level of "one".) on the game-map (see 13.1).

H: Appearance of Autonomous Force: Place 3 StarGates and 7 StarFleets (Civilization Level of "one".) on the game-map (See 13.1).

I: Appearance of Autonomous Force: Place 4 StarGates and 9 StarFleets (Civilization Level of "one".) on the game-map (See 13.1).

J: Appearance of Autonomous Force: Place 5 StarGates and 12 StarFleets (Civilization Level of "two".) on the game-map (See 13.1).

K: Increase Civilization two levels. (Utilizing scientific data obtained from an Expedition to the Core, an obscure, eccentric researcher attempting to regulate the speed of light accidently discovers a means of communication which, with 90%+ reliability, assures instantaneous communication between points infinitely far apart in space.) Note: the Player must have expended two Wisdom Chits previously in order to use this event. Otherwise, it is ignored. (see 11.16). May only be used once per Player.

L: Increase Civilization One Level (The natural and unfettered interplay of the various cultures of richly cross-fertilized and lead to exciting new plateaus in sentient experience.) Note: the Player may be required to have expended at least one Wisdom Chit in order to use this event. (See Fate Table). In such a case, if no Wisdom Chit has been expended...it is ignored. (See 11.16).

[11.3] DISSOLUTION

[11.31] [Printed as "11.13"; numbered 11.31 here to follow 11.3 and the sequence 11.32–11.34.] Dissolution results in the Neutralization of StarGates Friendly to the Player rolling on the Fate Table. Each fate result lists a percentage of the Player's System Points which are to be Neutralized.

[11.32] The Player rolling a Dissolution result on the Fate Table calculates the number of his System Points that have to be Neutralized (as per the Fate result), rounding up to the nearest System Point. The Player must then select a number of Friendly StarGates to be Neutralized, whose total System Point value is at least equal to the number of SP's to be removed. These StarGates are now considered Neutralized (see 10.2 and 14.17).

[11.33] Players may choose any Friendly StarGates they wish to be Neutralized, so long as the total System Point value of the Neutralized StarGates is equivalent to the percentage of System Points that the Dissolution result calls for.

[11.34] A Player may never suffer the same Dissolution Result more than once in the same game. It is recommended that Players note any Dissolution results obtained by each Player to avoid confusion.

[11.4] THE FATE TABLE

(See separate sheet.)

[12.0] CIVILIZATION LEVEL

GENERAL RULE: Each Player's Civilization Level reflects the level of science and culture he has attained. Each Player (and Autonomous Force) is constrained in several ways by the Level of his Civilization. It is possible for a Civilization Level to be increased or decreased.

[12.1] THE EFFECTS OF CIVILIZATION LEVEL

[12.11] All Players start the game with the Civilization Level assigned in the scenario they choose.

[12.12] The ability of a Force to conduct stellar shifts is affected by the Civilization Level of the owning Player or Autonomous Force (Cases 5.15 and 5.45).

[12.13] The chances of success of a particular Reduction resolution are in part dependent upon the Civilization Levels of the sides involved (10.22).

[12.14] The ability of a Player to De-neutralize StarGates is affected by his Civilization Level (Case 14.18).

[12.15] The ability of a Player to raise new StarFleets is affected by his Civilization Level (Case 14.22).

[12.16] Die rolls on the Fate Table may result in an increase or a decrease in a Player's Civilization Level. (11.2). Each Player keeps track of his current Civilization Level on a separate sheet of paper.

[12.17] If a Player's Civilization Level decreases below "zero" he is eliminated. All StarFleets Friendly to him are removed from the board, and all StarGates Friendly to him are Neutralized.

[13.0] AUTONOMOUS UNITS

GENERAL RULE:

Autonomous Forces are called into being by Fate Table results G, H, I, and J. The first Player to "contact" an Autonomous Force becomes the "Caretaker" for that force and is responsible for controlling all Forces Friendly to that Autonomous Force in accord with the rules governing their actions. Autonomous Forces do not utilize the Fate Table, or keep track of System Points and Resource Points, or construct new StarGates. Autonomous Forces may conduct stellar shifts, utilize the Contact Table, Interaction Matrix, Conflict Table, and Reduction Table, and may raise new StarFleets depending upon circumstances. Autonomous Forces do not utilize explorer StarFleets.

PROCEDURE:

When a Player rolls a result on the Fate Table calling for the appearance of an Autonomous Force, he chooses at random the proper number of Autonomous Force StarGates and StarFleets from among an unused set (color) of Autonomous Force counters. Without looking at or revealing the reverse-side of the counters, he places them on the game-map. (See 13.1) They remain in their original positions until such time as they are contacted, at which point the Caretaker may be called upon to conduct certain actions with them in accord with the Rules governing their employment.

[13.1] PLACEMENT OF AUTONOMOUS COUNTERS

[13.11] An Autonomous Force may only be called into being by a Fate Table result. If such a result is obtained by a Player, he places the called-for Autonomous Force StarGates and StarFleets in and around any hex for which he rolled on the Exploration Table earlier that Game-Turn (see Case 13.15).

[13.12] Place one Autonomous Force StarGate counter on any hex actually explored earlier that Game-Turn. Refer to the Scatter Diagram printed on the map. Starting with the hex corresponding to the hex "one" in the diagram, and continuing in order to the hexes corresponding to hex "two", "three", and so forth, place one additional StarGate counter in each eligible (see Case 13.14) hex adjacent to the original (explored) hex, until all Autonomous StarGates called for have been placed.

[13.13] In the event that the number of Autonomous StarGates to be placed on the map exceeds the number of eligible (see Case 13.14) hexes adjacent to the original (explored) hex, the excess StarGates may be placed in eligible hexes which are not adjacent to the original hex, so long as at least one StarGate is placed adjacent to the original hex and any StarGates not adjacent to the original hex are adjacent to another StarGate which is.

[13.14] A hex is "eligible" to have an Autonomous StarGate placed in it if it does not contain a StarGate counter or a Potential Value chit (except for the original hex, which could contain a Potential Value chit, picked earlier that Game-turn, which is removed). If insufficient eligible hexes are available around any hexes explored by the rolling Player, the Fate Table result which called for the Autonomous Forces is invalidated, and no Autonomous Forces are deployed.

[13.15] A Fate Table result calling for the placement of an Autonomous Force on the board is invalidated if the Player rolling the result did not roll on the Exploration Table that Game-Turn.

[13.16] A Fate Table result calling for the placement of an Autonomous Force on the board is invalidated if there are currently four Autonomous Forces present on the board.

[13.17] Invalidated Fate Table rolls calling for the placement of Autonomous Forces are ignored. There is no substitute roll on the Fate Table.

[13.18] Autonomous Force StarFleet counters are distributed as evenly as possible among the hexes containing the Autonomous Force's StarGates, with any excess StarFleets going to the original (explored) hex.

[13.19] If the Player whose Fate Table roll called for an Autonomous Force has explored more than one hex that Game-Turn which satisfies the requirements of Case 13.16, the location of the Autonomous Force is determined by assigning them numbers on a die and rolling the die to determine the hex.

[13.2] ACTIVITY OF AUTONOMOUS FORCES

Movement, Contact, Interaction, Conflict, Reduction, and Resource activity by an Autonomous Force is determined by its status on the Players' Interaction Matrices. If an Autonomous Force is not represented on any Player's Interaction Matrix, it is a Passive Autonomous Force. Otherwise, it is an Active Autonomous Force, and the "Caretaker" may be required to take certain actions.

[13.21] Passive Autonomous Forces may never move, initiate Conflict or Reduction, or raise new StarFleets. Passive Autonomous Forces may be Contacted (see 7.0, Procedure). Contacted Passive Autonomous Forces always utilize the "No Previous Option" column of the Random Interaction Option Table.

[13.22] Once an Autonomous force has Interacted with a Player it becomes Active. Active Autonomous Forces remain active permanently, unless they are eliminated from the Game or all Players who have Interacted with the Autonomous Force are eliminated from the Game. In the latter case, the Autonomous Force reverts to Passive status.

[13.23] An Autonomous Force is controlled by the first Player to make contact with it. This Player is called the "Caretaker". A Caretaker is the only Player who may examine the reverse side of his Autonomous Force counters. Moreover, only Autonomous Forces which may be examined are those which it is necessary to expose for the purposes of resolving Contact, Conflict, or Reduction.

[13.24] If all the Interaction Options of an Active Autonomous Force are "A's," and/or "B's," the Caretaker may shift those Forces so long as the shift attempted is to a hex which has a Friendly Autonomous StarGate. A Friendly Autonomous Force in hexes not containing a Friendly Autonomous StarGate must be shifted to a hex that does have one. The Caretaker must attempt to concentrate his Autonomous StarFleets in any hexes containing Friendly Autonomous StarGates which are occupied by one or more Player Forces. No Autonomous Force with Interaction Options A and/or B only may initiate Conflict or Reduction resolutions.

[13.25] Active Autonomous Forces participate in Contact resolutions, with the Caretaker calculating the Autonomous Force Contact Index (see 7.0, Procedure).

[13.26] An active Autonomous Force utilizes the Interaction Matrix whenever it is called for, the Caretaker rolling on the appropriate column of the Random Interaction Option Table to select the Interaction Option (see Case 8.19). Exception: whenever a Player initiates Conflict or Reduction resolutions against an Autonomous Force that displays an Option other than "C" with regard to that Player, the Interaction Option of the Autonomous Force with regard to the Player attacking automatically becomes "C" during the subsequent Interaction Segment. It remains so until one or the other is eliminated.

[13.3] HOSTILE AUTONOMOUS FORCES

[13.31] If any of an Autonomous Force's Interaction Options is a "C", the Caretaker must split all of these Autonomous Force StarFleets into two Forces. The first Force, which must be equal in StarFleets to the number of Friendly Autonomous StarGates, is shifted as in Case 13.24. The second Force, which is composed of all excess StarFleets, proceeds to the nearest StarGate in sight (see 15.15) that belongs to the Player for whom that Autonomous Force has "chosen" a "C" Option. The second Force must attempt to eliminate any Force Friendly to that "enemy" Player's StarGate and to Neutralize the StarGate.

[13.32] This second Force must attempt to reach that hex in one Game-Turn, utilizing any Friendly/Allied StarGates within the Autonomous Force's CLR to aid in the Shifting, if possible. If such Conflict is successful in that hex, the second Force then proceeds again to the hex nearest to the previous hex, that can be sighted by any Friendly Autonomous Force or StarGate and which contains a StarGate belonging to a Player for whom the Autonomous Force has "chosen" a "C" option. It then attempts to repeat its success. Any newly-raised Autonomous Force StarFleets (13.34) are used first to bring StarGate equality forces up to full-strength (if necessary); the remainder may then attempt to join the "attacking" (second) Force.

[13.33] If no "C" option Player StarGates are in sight at any time, all Autonomous Forces return to or remain within hexes containing Friendly Autonomous StarGates. An Autonomous Force may always initiate Conflict and Reduction resolutions against Forces owned by a Player for whom that Autonomous Force has "chosen" a "C" option.

[13.34] Any Autonomous Force with at least one "C" Option on an Interaction Matrix belonging to an active Player receives one new StarFleet each turn for each two StarGates deployed on the map. These StarFleets appear during the Resource Allocation Phase in any hex containing a StarGate Friendly to the Autonomous Force. This 2:1 ratio is always rounded down; thus if less than two Friendly StarGates are on the map, no new StarFleets appear.

[13.35] Autonomous Forces may never Interact with or conduct Conflict or Reduction resolutions against other Autonomous Forces. They may not conduct contact resolutions with other Autonomous Forces; if non-Friendly, Autonomous Forces co-exist in the same hex with a Contact Counter they simply ignore each other.

[14.0] RESOURCE ALLOCATION

GENERAL RULE:

Each StarGate has a System Point value. Each Game-Turn each StarGate contributes to the Civilization of its Friendly Player (if any) one Resource Point (RP) for every System Point (SP). During the Resource Allocation Phase of the Game-Turn, each Player allocates RP's to construct new, and/or maintain existing, StarFleets. The Player may also expend StarFleets [sic, as printed] to create or augment the SP value of his StarGates. Players may also expend StarFleets [sic, as printed] to make Neutralized StarGates Friendly. Under certain circumstances Autonomous Forces may also raise new StarFleets (See 13.2).

PROCEDURE:

All Players keep track of their current levels of Resource Points on a separate sheet of paper. At the start of each Resource Allocation Phase each Player increases his total accumulated RP's by the value of currently Friendly System Points. Each then subtracts from this total an amount of RP's sufficient to maintain his current number of StarFleets (See 14.27). Then, all Players simultaneously determine how each shall expend his remaining Resource Points (and StarFleets), making any consequent adjustments in the number and disposition of their StarFleets on the board, in the deployment of their StarGate counters, and on their record of accumulated RP's. Each Player then replaces any (face-down) Neutralized StarGates that have been de-Neutralized with face-up StarGate counters of his own.

[14.1] CREATION, AUGMENTATION, AND DE-NEUTRALIZATION OF STAR-GATES

CASES:

[14.11] Players may construct StarGates only on Spiral Access [printed; Spiral Axis is evidently meant], Spiral Fringe or Inter-Spiral hexes. They may not construct StarGates on Galactic Nucleus hexes.

[14.12] A Player may construct a StarGate only in a hex which he has successfully explored and which has no StarGate counter in it.

[14.13] A Player must expend two StarFleets (of any type) in order to create a StarGate. The expended StarFleets must have started the Resource Allocation Phase in the hex in which the StarGate is created. Newly-created StarGates have an SP value of "zero".

[14.14] A Player may augment an existing Friendly StarGate's SP value by expending StarFleets (of any type) at the rate of one System Point of augmentation per StarFleet expended. The expended StarFleets must have started the Resource Allocation Phase in the same hex as the StarGate.

[14.15] A StarGate may never be created and then augmented in the same Game-Turn. The Player must wait at least one Game-Turn to augment a newly created StarGate.

[14.16] The SP Value of a StarGate may never be augmented beyond the Potential Value of the hex in which the StarGate is located (see 3.2). Whenever the SP of a StarGate equals the Potential Value of the hex it is in, remove the Potential Value Chit and place it back among the unpicked Potential Value Chits.

[14.17] Once created, a StarGate is never moved or destroyed (exception, see 10.24). It may be Neutralized (see Section 10.0 and 11.3), and it may also become Friendly to a different Player from the one who created it (Case 14.18).

[14.18] Any Player may "de-neutralize" a Neutralized StarGate by expending a certain number of StarFleets and Resource Points. The number of RP's expended must be equal to the SP Value of the StarGate. The expended StarFleets must have begun the Resource Allocation Phase in the same hex as the StarGate, and there must be no Non-Friendly Force in the hex during that Phase. The number of StarFleets it is necessary to expend depends on the expending Player's Civilization Level: He must expend a number of StarFleets equal to the SP Value of the StarGate minus his Civilization Level, if the resulting number (SP Value minus CL) is positive. If that number is "zero" or negative then no StarFleets need be expended. In any case, however, at least one StarFleet Friendly to the De-neutralizing Player must be present in the hex (even though it may not be expended).

[14.19] A De-neutralized StarGate becomes Friendly to the De-neutralizing Player.

[14.2] CONSTRUCTION AND MAINTENANCE OF STARFLEETS

[14.21] Players may raise new StarFleets only in hexes containing Friendly StarGates that have an SP Value greater than "zero". StarFleets may never be raised in a hex which has been augmented during that same Resource Allocation Phase.

[14.22] A Player may raise one StarFleet for each Civilization Level he has attained for each hex containing a Friendly StarGate. For example, a Player whose Civilization has a Level of "one" may raise no more than one StarFleet in any one hex; a Player with a Civilization Level of "two" may raise no more than two StarFleets in any one hex, and so on. Exception: A Player with a Civilization Level of "zero" may raise new StarFleets as if his Civilization Level were "one".

[14.23] Regular StarFleets cost three RP's each to construct. A regular StarFleet may be raised in any hex containing a Friendly StarGate in accord with Cases 14.21 and 14.22.

[14.24] Dreadnought StarFleets cost eight RP's each. A Dreadnought StarFleet may be raised in any Spiral Fringe or Spiral Axis hex containing a Friendly StarGate, in accord with the restrictions of Cases 14.21 and 14.22.

[14.25] Explorer StarFleets cost five RP's each. An Explorer StarFleet may be raised in any Spiral Axis hex containing a Friendly StarGate, in accord with the restrictions of Cases 14.21 and 14.22.

[14.26] Autonomous Forces may, under certain circumstances, raise new StarFleets. If so, they do so without regard to Resource Points. (See Case 13.34).

[14.27] For each hex in which there is more than one Friendly Player-owned StarFleet at the beginning of the Resource Phase, one RP is deducted from the appropriate Player's accumulated total for each Friendly StarFleet in excess of one. This is called maintenance. Exception: Explorer StarFleets are exempt from this requirement; they never have to have RP's expended to maintain them and they do not count when determining maintenance levels. Example: a Player has six regular StarFleets, two Dreadnought StarFleets, and three Explorer StarFleets in a hex. At the beginning of the Resource Allocation Phase, seven Resource Points (8 StarFleets, excluding Explorers, minus one) must be expended by the Player in order to maintain the force in its entirety.

[14.28] If a Player fails to allocate sufficient RP's to maintain a StarFleet (either by choice, or because sufficient resources are lacking), the excess StarFleets are immediately removed from play. Example: in 14.27, if the Player allocated only 5 RP's, he would have to remove two StarFleets (his choice).

[15.0] BEACON STARS

GENERAL RULE:

A Beacon star is any star that has a name or a number assigned to it. In addition, whenever a Player-owned Force purposefully shifts (does not "scatter") into any hex other than a Galactic Nucleus or Core hex from which there is no unblocked Line of Sight to a Beacon Star, that Force "discovers" a variable number of "new" Beacon Stars as determined by a die roll. These are placed on the map.

[15.1] HOW TO DISCOVER AND PLACE NEW BEACON STARS

[15.11] The Player whose Force is discovering the Beacon Stars rolls the die and adds "two" to the result: that is the number of Beacon Star counters to be disposed on the map.

[15.12] There are two methods for choosing the hexes for the Beacon Star counters. The first is for games with more than one Player: the Player to the left of the Player who made the die roll chooses a hexrow and the Player to the left of him places a Beacon Star counter in a hex in that row and then chooses another hexrow. The Player to his left then places a Beacon Star counter in any hex in that row and then chooses another hexrow...and so on, until all Beacon Star counters called for have been placed. The second method is for solitaire play: the Player chooses a hexrow and rolls the die twice for each hex. For each hex for which he throws a total of exactly "9", he places a Beacon Star counter in it. If necessary (and it should be), pick additional hexrows to roll for until all Beacon Stars have been placed.

[15.13] Hexrows chosen for Beacon Star placement have three requirements:

a) they must contain at least two hexes that are visible from the hex the discovering Force is in;

b) they may not contain a Beacon Star that is visible from the hex the discovering Force is in; and

c) they may not be the hexrow containing the hex the discovering Force is in.

[15.14] Hexes chosen for Beacon Stars must have an unblocked line of sight to the hex that the discovering Force is in.

[15.15] A hex is "visible" from another hex if there is an unblocked line of sight between the two. To determine the line of sight between two hexes, lay a straight edge from the center of one hex to the center of the other. The straight line so defined is the "line of sight". If any of the hex-sides which the line of sight crosses are "blocking hex sides" (see 16.0) the line of sight is considered blocked.

[15.16] "Discovered" Beacon Stars reduce the chances of Scatter for Forces attempting stellar shifts into them in the same way as "printed" Beacon Stars (see Case 5.42).

[16.0] INTERSTELLAR DUST

GENERAL RULE:

Interstellar dust cloud hexsides inhibit stellar shifts (Case 5.73). In addition, Interstellar dust cloud hexsides block lines of sight (Case 15.15).

[17.0] THE GALACTIC NUCLEUS AND WISDOM CHITS

GENERAL RULE:

The Galactic Nucleus is composed of Nucleus hexes. The Nucleus is generally risky to move within, and Players may not construct StarGates within it. However, at the very center are the three Nuclear Core hexes which contain the Wisdom Chits. Otherwise they are identical to other Nucleus hexes. Wisdom Chits may be acquired by Players and utilized for Fate Table die rolls in order to gain an increase in a Player's Civilization Level. There are ten Wisdom Chits. These are kept face-up at all times. Nine of these are blank on the reverse-side; one is marked with an "X" on the reverse side.

[17.1] USAGE OF GALACTIC NUCLEUS HEXES

Galactic Nucleus hexes increase the consequences of Scatter (5.72) and may not be Explored (6.15). StarGates may not be built on Galactic Nucleus hexes (Case 14.11). There is no particular effect of Galactic Nucleus hexes on Contact, Interaction, or Conflict resolutions, which may proceed normally within them.

[17.2] WISDOM CHITS

[17.21] A Player may gain control of any Wisdom Chit by transporting it from a Nuclear Core hex to a Friendly StarGate. This can be accomplished by shifting a Force into that Nuclear Core hex and then shifting a particular StarFleet (with the Wisdom Chit) from that Force into a hex containing a Friendly StarGate.

[17.22] In transporting a Wisdom Chit, a Player must "assign" a particular StarFleet to "carry" the Chit. That StarFleet must successfully reach a Friendly StarGate in order to use the chit. If the StarFleet is destroyed before reaching a Friendly Stargate, the Wisdom Chit is placed with the undeployed Wisdom Chits off the board (See 3.31).

[17.23] If more than one Force begins a Game-Turn in a Nuclear Core hex, the first Force to shift away (see 4.2) has the option of taking along the Wisdom Chit.

[17.24] Whenever a Wisdom Chit is removed from a Nuclear Core hex, another Chit is immediately chosen at random from among the undeployed Wisdom Chits (if any) and placed on that hex. This new chit may be taken by a second player on that hex (See 17.23).

[17.25] Wisdom Chits are either undeployed, deployed on the map, or under the control of a Player. Only a Player controlling a particular Wisdom Chit may look at the reverse side of that chit.

[17.26] A Wisdom Chit is considered to be under the control of a Player when that Player has successfully shifted it to a Friendly StarGate. At that point, it is removed from the board and held aside by that Player until he chooses to expend it (Case 11.16). A Player may not Control more than three Wisdom Chits simultaneously. (Exception—see 18.56).

[17.27] If a Player gains control of the "X" Wisdom Chit, certain consequences and/or restrictions may result. See the individual Scenarios and Victory Conditions for these effects (18.0).

[18.0] SCENARIOS

GENERAL RULE:

Each Scenario is self-contained, having separate Victory Conditions and game-length, etc. StarFleets are abbreviated as r=regular; d=dreadnought; and e=explorer.

[18.1] CONFLICT OVER SCORPII [Two-Player scenario]

Any civilization which finds itself spanning thousands of light years and still maintaining an appetite for expansion will inevitably be drawn out beyond the confines of its original spiral arm. If cohesion between settlements spanning the Galaxy is to be maintained, and if the nature and riches of the Galactic Nucleus are to be revealed, the control of certain "crossroads" regions could become critical.

[18.11] Forces at Start:

CEPHEIDS

HexStarGate ValueHex Potential ValueStarFleets
1212551/d
1213341/r
1313331/r
1314341/r
1211—4none
1312—52/e; 1/r

Resource Points Available: 3 Civilization Level: 1

WEZENS

HexStarGate ValueHex Potential ValueStarFleets
1118441/r
1119341/r
1018451/r
101913none
111714none
0918—24/e 1/r
09190

Resource Points Available: 5 Civilization Level: 1

[18.12] Victory Conditions: A Player wins a marginal victory if he retains all the Friendly StarGates with which he began the game; in addition, he must have a Friendly StarGate on hex 1816 at the end of the Game. A Player wins a Substantive Victory by fulfilling the conditions for a Marginal Victory plus capturing and maintaining, in a Friendly status at the end of the game, at least one of the StarGates which began the game Friendly to the other Player.

[18.13] Game Length: 25 Game-Turns.

[18.14] For this Scenario, players should ignore Rules 15.0, 16.0 and 17.0, Section 11.3, and Fate Table results A, B, C, D, E, F, K, and L, if they occur.

[18.2] ROUTE TO THE NUCLEUS [Three-Player Scenario]

No one on Earth (at least, no one who was talking to us) knows precisely what is to be found in the Nucleus of close-packed, ancient stars which lie at the center of the Galaxy. However, it can be supposed that if indeed something of value can be found there that it may well be protected in some manner by those who know of it, or their agents.

[18.21] Forces at Start:

GUARDIANS

HexStarGate ValueHex Potential ValueStarFleets
1118332/d; 5/r; 1/e (2nd Star Navy)
1212442/d; 4/r; 1/e (3rd Star Navy)
1215553/d; 7/r; 1/e (1st Star Navy)
121644none
131455none
131533none
1316

Resource Points Available: 12 Civilization Level: 3

CENTAURIANS

HexStarGate ValueHex Potential ValueStarFleets
112412none
122311none
122412none
1323331/r
1324451/r
1024—02/r; 2/e
1325—

Resource Points Available: 8 Civilization Level: 1

PERSEITS

HexStarGate ValueHex Potential ValueStarFleets
0310441/d; 1/r
0410221/r
0510332/e
051133none
0513001/d, 1/r
0714241/r
08132

Resource Points Available: 6 Civilization Level: 1

[18.22] Victory Conditions: The Centaurians or Perseits win by constructing and maintaining for five consecutive Game-Turns a chain of Friendly StarGates, no more than four hexes apart from each other, from one of the StarGates which was Friendly at the beginning of the game to a hex adjacent to the Galactic Nucleus. If either succeeds in this endeavor, the game is over immediately. The Guardian Player wins by avoiding such an eventuality.

[18.23] Game-length: 50 Game-Turns.

[18.24] Special Rules

The Guardian Player must operate under certain strictures. He may not construct new StarGates or augment the value of any existing Friendly StarGates. He may not de-neutralize any StarGate that did not begin the game Friendly to him. Finally, he must attempt to maintain the four "Star Navies" as distinct, cohesive Forces, and as near to full strength as possible. "Full Strength" is defined as ten Dreadnoughts, and one Explorer StarFleet. (Replace the regular StarFleets in the Navies with dreadnoughts as the latter are constructed.) The Guardian Player may retain a reserve of Resource Points of up to 20 RP's.

[18.25] The Guardian Player ignores Sections 11.3 and 17.0 of the Rules, as well as Fate Table results A, B, C, D, E, F, K and L.

[18.26] The Centaurians and Perseits may not build or maintain more than one Dreadnought StarFleet for every ten System Points owned. These Players ignore Section 17.0 of the Rules as well as Fate Table result "K".

[18.3] PSL OUTLEAP [Solitaire Scenario]

In SPI's first science fiction game, StarForce, the history of humanity was traced up through "first contact" with space-faring non-human telesthetics and the subsequent formation of the "Pan-Sentient League", which included two such extra-terrestrial races. An area some forty light-years in diameter (contained completely within hex 1316 on the Outreach map) comprised the map for that game. Each hex in Outreach is some 1200 Light years in diameter. Therefore, this scenario picks up a distant, and hugely expanded, PSL-descendant Civilization, occupying an area some 10,000 times its original size, and still dynamic and growing...

[18.31] Forces at start:

HexStarGate ValueHex Potential ValueStarFleets
1316451/e; 1/r
1216241/r
121524none

Available Resource Points: 5 Civilization Level: 1

[18.32] Victory Conditions: The Player wins if he manages to raise the Civilization Level of the PSL to "two" at the end of the game.

[18.33] Game Length: 25 Game-Turns.

[18.34] If the Player gains control of the "X" Wisdom Chit, (see Case 17.27), it signifies the discovery of the fact that the Nuclear Core has exploded, and that the explosion is spreading outwards in a gargantuan chain reaction at the speed of light. The game is automatically lost, and the Player has about forty million years to entirely evacuate the Galaxy. (Give or take a few hours).

[18.4] STRUGGLE FOR CYGNUS-CARINA [Four-Player Scenario]

This Scenario posits the existence of four distinct groupings of space-faring telesthetics within the near confines of the spiral arm in which Sol is located (hex 1316). (These "confines" include several thousand light years.)

[18.41] Forces at Start:

AURIGAEN

HexStarGate ValueHex Potential ValueStarFleets
081433none
081345none

Available Resource Points: 10 Civilization Level: 1

RIGELIAN

HexStarGate ValueHex Potential ValueStarFleets
131644none
121635none
121522none
131544none

Civilization Level: 1

Available Resource Points: 25

WEZENI

HexStarGate ValueHex Potential ValueStarFleets
111844none
101833none
111925none

Civilization Level: 1

Available Resource Points: 19

REGNAD-KCIN

HexStarGate ValueHex Potential ValueStarFleets
131234none
141122none
141212none

Civilization Level: 1

Available Resource Points: 11

Prior to the first Game-Turn, each Player may utilize available Resource Points to construct any StarFleets desired. These may be deployed on hexes containing Friendly StarGates.

[18.42] Victory Conditions: A Player may win the game in any of several ways:

  1. A Player who establishes and maintains for five consecutive Game-Turns a Friendly StarGate on any four of the following hexes wins the game: 0814, 1118, 1212, 1215, 1314.

  2. A Player whose Civilization Level exceeds the combined (total of) Civilization Levels of all other remaining Players wins the game.

  3. A Player who is the sole remaining active Player in the game—the others having been eliminated (see 10.25, 12.17)—wins the game.

If no Player has fulfilled any of the above-listed victory criteria by the end of the game, then the System Point totals of all Players are multiplied by their Civilization Levels, and the Player with the greatest resultant total wins the game.

[18.43] Game length: 50 Game-Turns.

Special Rules

[18.44] A Player who gains control of the "X" Wisdom Chit is consequently subject to the following restrictions: such a Player may not construct any new Dreadnought StarFleets, nor may he choose Interaction Option "C" vis-a-vis any other Player of Autonomous Force unless that other's most recent Interaction Option vis-a-vis the "X" Player had been "C". The "X" Wisdom Chit may not be expended in a normal fashion (Case 11.16) during the Fate Phase; however, possession of the "X" Chit automatically counts as the expenditure of a Wisdom Chit towards any Fate Table roll by that Player. For example, if the Player controlling the "X" Wisdom Chit determined to expend one (other) Wisdom Chit on a Fate Table roll, the roll would be considered to have had two Wisdom Chits expended on it; if that Player had controlled only the "X" Chit, then his Fate Table roll would automatically count as a roll with one Wisdom Chit having been expended.

[18.45] If the Player controlling the "X" Wisdom Chit succeeds in raising his Civilization Level on a particular Fate Table roll, the "X" Chit may then be considered to have been expended and returned to among those undeployed off the board (Case 3.31). In this instance, all restrictions and bonuses as listed in Case 18.44 cease. Alternatively, the Player may choose to retain the "X" Wisdom Chit, and thereby retain all the above-enumerated restrictions and bonuses. In the latter case, the Player must retain the "X" Wisdom Chit until once again successful at raising his or her Civilization Level, at which point the choice is again open to either expend the Chit or retain it.

[18.46] The Player gaining control of the "X" Wisdom Chit is not required to announce that acquisition, except whenever the possession of the Chit results directly in an increase in Civilization Level. Of course, due to the actions that possession of the Chit force on a Player, it will often become obvious when someone is in possession of it.

[18.5] LUCK OF THE DRAW SCENARIO

This Scenario is playable by any number of Players. Before the first turn of the game each Player rolls on the Seed Winds table. These rolls determine the general region of origin of each's Civilization. In game terms, the table yields the number and location of StarGates that each Player begins the game with.

[18.51] Seed Winds Table

Each Player rolls the die twice. The first die roll yields the vertical result; the second roll is the horizontal result. Example, a 1, 4 would give a G result. These are cross-indexed to determine the Seed Winds Table result. If two or more Players obtain the same result, then rolls are invalidated and each must re-roll again on the Seed Winds Table.

First Die RollSecond Die Roll: 123456
1AHFGHK
2GBIJLJ
3FKCMKI
4EJA

[18.52] Seed Table Results

ResultOne StarGate each in Hexes:
*A0707, 0706, 0607
*B0510, 0409, 0410
×C0814, 0813, 0714
D1709, 1708, 1609
E1110, 1111, 1209, 1210
F1314, 1313, 1213, 1214
G1215, 1115, 1116, 1216, 1316
H1118, 1117, 1017, 1018
I1816, 1815, 1916
J1324, 1323, 1423
K1726, 1625, 1826
*L4903, 4802, 4803

[18.54] Victory Conditions: A Player wins the game either when there are no non-Friendly StarGates remaining on the board, or at any time that his Civilization Level exceeds the combined total of the Civilization Levels of all other Players and Autonomous Forces (that have any StarGate Friendly to them deployed on the board) (Exception, see 18.57). If at any point all Players remaining in the game maintain more than 100 System Points for ten consecutive Game-Turns, the game is declared a draw. (Exception, see 18.57.)

[18.55] Game Length: there is no set limit to the number of turns in the game.

[18.56] Any Player gaining control of the "X" Wisdom Chit is consequently subject to certain restrictions: such a Player may not expend Wisdom Chits to increase Civilization Level and may not win the game except by neutralizing all non-Friendly Player-owned StarGates on the board. By the same token, such a Player gains some advantages. The restrictions on the number of Wisdom Chits which one Player may hold at once (case 17.26) is waived; the Player controlling the "X" Wisdom Chit may hold an unlimited number. Secondly, any Force (including both Dreadnought and Explorer StarFleets) friendly to the Player controlling the "X" Wisdom Chit may conduct Stellar Shifts as if the Civilization Level of the Player were one Level higher than it actually is.

[18.57] Special Solitaire rules: Ignore Cases 18.54 and 18.55. The Player wins by maintaining a level of 100-plus System Points for five consecutive Game-Turns, during which time no non-Friendly StarGate counters must be on the board. If the Player draws the "X" Wisdom Chit, then the restriction on the recurrance of Fate Table results A, B, C, D, E, and F is waived; and these results may apply to the Player an unlimited number of times (exception to Case 11.32).

COUNTER SHEET ERRATA

Due to a printer's error, twenty of the StarFleet counters do not have a "C" backprinted on them as they should. These are counters 406-425.

[The final printed page of the scan reprints the Sequence of Play summary; its text duplicates Section 4.2 above and is not repeated here. The Charts referred to as "separate sheet" (Scatter, Contact, Interaction Matrix, Random Interaction Option, Conflict, Reduction, Fate tables) are not part of the rules scan.]

StarSoldier

[1.0] INTRODUCTION

StarSoldier is a tactical level simulation of man-to-man combat in the 25th Century. Each Player controls from three to a dozen StarSoldiers, which he deploys and conducts in combat, attempting either to accomplish, or prevent his opponent from accomplishing a particular mission. The game features simultaneous movement and combat, and thereby portrays realistically the swift and/or rapid problematical pace of tactical level operations. Each Player pre-plots all activity for his Soldiers before any movement or combat is actually executed on the map; therefore, one Player never knows what the other will be doing. The Rules are divided into three parts, or "sub-games."

The Basic Game (Sections 4.0 to 13.0) is presented first. It concerns the first military interspecies conflict to involve Humans, the First Contact with the L'Chal Dah in 2451. It is intended to serve as an introduction to the mechanics of play.

The Standard Game (Rules 14.0 to 27.0) adds a more refined Sequence of Play and rules for specialized weaponry, tactics, and other species besides the Humans and the L'Chal Dah. Except for the specifically noted changes, the rules for the Basic Game apply for the Standard Game as well. It is composed of several scenarios drawn from the military conflicts which marked the 25th Century as described in the Future History of SPI's companion game of strategic level interstellar conflict, StarForce. Typical scenarios simulate patrols, assaults, base defence, etc.

The Link Game (41.0) allows Players owning SPI's StarForce game (which concerns the strategic inter-stellar situations on which StarSoldier is based) to play the games in tandem, systematically linking actions in one to the other. Hence, Players can resolve with StarSoldier tactical situations that are brought about by the resolution of conflicts in StarForce.

[2.0] GENERAL COURSE OF PLAY

StarSoldier is a two-player game. The Players select a Scenario to play. Following instructions, they assemble their respective forces from the die-cut counters provided. They then proceed to conduct the movement and combat of each of their soldiers with a view toward accomplishing their overall mission as set forth in the Scenario instructions.

Each Scenario is played in successive Game-Turns. Each Game-Turn is subdivided into Stages, Phases, and Segments. These subdivisions are arranged in a structure (called the Sequence of Play); it provides a systematic scheme by which the Players execute the activities of their respective forces in the course of the Game-Turn. When following this Sequence of Play, the Players will be simultaneously plotting and then executing the fire and/or movement for each of the soldiers under their command.

[3.0] GAME EQUIPMENT

[3.1] THE GAME MAP

The terrain printed on the mapsheet included rough terrain, mountains, forests ("organic cover"), bodies of (not necessarily) water, as well as settled ("urban") areas. Most conflicts will be over inhabited, or, at least, habitable planets. However, it is likely that especially resource-rich planets with hostile environments (or even barren ones in strategically located systems where control of the StarGate could be crucial) might be militarily garrisoned and require force to secure. Some scenarios, therefore, call for certain terrain-areas to be treated as if they were something else.

A hexagonal grid has been superimposed over the map to regularize the positioning of the playing pieces and to facilitate distance calculations. Each hexagon (hereinafter referred to as "hexes") represents an area one kilometer in diameter, measured from one edge directly across to the opposite edge.

[3.2] PLAYING PIECES

Four differently colored sets of die-cut counters are provided representing soldiers of the various species in the game. Each soldier has a unique identifying number code, and displays type: Regular, Heavy Weapon or Android. Each soldier's counter is back-printed to indicate either Ground and Airborne Modes (front and back sides, respectively). There are also counters differentiated by species to represent Homing Missiles and to mark targets acquired by each individual Homing Missile, to represent Support Platforms and to mark their Fire Registration and for Strike Commands which may be used in the Link Game with SPI's science fiction game, StarForce. There are counters undifferentiated by species for Free Flight Missiles, Guided Positron Bombs, Opacity Grenades, and so forth, most of which are backprinted with craters, "smoke", and the like, as appropriate. Finally, there are two sets of Game Aid Markers, which are used to record losses (on the Task Point Level Track) and to keep track of the "Preservation Level".

[3.21] Species-Differentiated Counters: There is one set of these each for Humans, L'Chal Dah, the Rame, and the Xenophobes. In some scenarios, where Humans are fighting each other, Players may utilize L'Chal Dah counters to represent one of the Human Forces, as indicated in the Scenarios.

The counter types printed in the game are listed below. Each entry gives the printed front side, and the printed back side where one is shown.

  • Regular StarSoldier: Ground Mode (front); Airborne Mode (back)
  • Heavy Weapons Soldier: Ground Mode (front); Airborne Mode (back)
  • Android: Ground Mode (front); Airborne Mode (back)
  • Homing Missile: dormant (front); active (back)
  • Target Acquisition: Independent
  • Support Platform: Independent
  • Fire Registration: Independent
  • Strike Command: Independent
  • Neutron Bomb: Independent
  • Free-Flight Missile: front; Crater (back)
  • Guided Positron Bomb: front; Crater (back)
  • Opacity Grenade: front; Smoke (back)
  • Orbital Bomb: front; Crater (back)
  • Orbital Opacity Bomb: front; Dense Smoke (back)
  • Base: Independent
  • Civilian Marker: Dummy (back)
  • Civilian Marker: Genuine (back)
  • High Altitude Marker: Independent
  • Dinkblog: Independent

[3.22] Game Aid Markers: Twelve Task Point Allowance Markers and Available Task Point Markers are provided for each side (for use in the Standard Game only). The Players assign each Soldier on their side a number between one and twelve and use the markers in conjunction with the Task Point Level Track to record losses and Task Point expenditure (for the Standard Game only).

The Game Aid Markers are the Task Point Allowance Marker, the Available Task Point Marker, the "Task Points Remain" marker, and the Preservation Level Markers (marked "x1" and "x10").

[3.23] Neutral Game Markers: The following markers are used to represent various launching weapons, the after-effects of detonations of those weapons, civilians, high-altitude markers, and two carniverous "Dinkblogs".

[3.3] GAME CHARTS & TABLES

Most of the tables used in the game are to be found in the center of this rules booklet. Players should tear out this center section and, using a scissors, cut it into two identical 8½" x 11" sheets. Each Player is also provided with a separate Task Point Record Display upon which are deployed the markers used on the tracks to record the status of their StarSoldiers.

Note: The dice in the game are used in connection with the tables mentioned above. Note that some tables use both dice while others call for the use of only one.

[3.4] INVENTORY OF GAME PARTS

Each copy of StarSoldier includes the following:

  • One Rules Booklet
  • One Sheet of Die-Cut Counters (400 pieces)
  • One 22" x 34" Game Map
  • Two Level Record Charts
  • Two plastic dice
  • One Game box

[4.0] BASIC GAME SEQUENCE OF PLAY

StarSoldier is played in turns called "Game-Turns." Each of these Game-Turns is divided into Phases, during which the Players have the opportunity to plan and execute movement and combat by their soldiers. All action must take place in the exact sequence outlined below.

[4.1] SEQUENCE OUTLINE (Basic Game)

This outline should be followed when using the Basic Game Rules.

  1. Plot Phase: Each Player simultaneously and secretly determines and writes down ("plots") the movement and combat activities for the current Game-Turn for each of his soldiers.

  2. Execution Phase: Although all action plotted for each Soldier during this Phase is assumed to be occurring simultaneously, for the purposes of execution it is divided into two Segments.

    a. Fire Segment: All Soldiers plotted to Execute Direct Fire do so. Players should make adjustments on their Task Point Level Charts as appropriate to indicate casualties (which are considered to take effect after the following Segment).

    b. Launch Segment: All Soldiers plotted to launch projectiles do so. Any casualties that may have resulted from combat resolutions during the preceding Direct Fire Segment are then considered to take effect.

  3. Movement Phase: Each Player moves those of his Soldiers who are plotted to do so (casualty status permitting). The counters are physically moved on the map, hex-by-hex, according to the plot which has been written for them. Any Opportunity Fire that has been plotted is resolved by the Players as they determine.

  4. Projectile Resolution Phase:

    a. Scatter/Interception Segment: The range and target Counter-Measure activity (CM) are taken into account to determine whether or not any Guided projectiles that have been launched scatter before reaching their targets, and whether any of the Non-Guided projectiles which were launched are intercepted. The effects of any scattering which occurs are calculated.

    b. Detonation Segment: Execute the detonation of all projectiles launched earlier in the Game-Turn. Assess casualties where necessary, and adjust the Task Point Level Charts as appropriate. Place Stun Markers on stunned Soldiers.

[5.0] "SIMULTANEOUS" MOVEMENT

GENERAL RULE:

During each Plot Segment (see Section 4.1), both Players must plan out and record on a piece of paper all the tasks it is desired to have each soldier perform during the remainder of that Game-Turn.

PROCEDURE:

The owning Player writes the identifying letter of each of his soldiers in a vertical column on the left of a sheet of lined paper. During each Plot Segment, the owning Player writes the corresponding task code (Section 7.1) for any activity he assigns each of his soldiers, next to the appropriate identifying letter. If a soldier is moving or firing, the hexes moved through (one-by-one), or fired upon, are also recorded.

CASES:

[5.1] SECRECY AND HONESTY

The written record ("Plot") of each Player's task assignments is kept hidden from the other Player until after the end of the game. If a Player has any doubt about the other Player's orders during the course of the game, the best thing to do would be to write them down and compare them with the other Player's Plot at the end of the game. A Player discovered to have secretly violated the rules to gain an advantage forfeits the game.

[5.2] SIMULTANEITY OF ACTIVITY

All actions initiated by Soldiers are considered to be taking place at the same time during the Execution Phase during which they occur. Casualties caused by combat resolved during a given Execution Phase do not, therefore, take effect until after all combat occurring during that Phase has been resolved. Similarly, all movement is considered to be simultaneous during the Movement Phase in which it occurs.

CASES:

[5.21] A combat effect suffered by a Soldier in a given Execution Phase does not affect that Soldier's combat ability until after all combat occurring during that particular Execution Phase has been resolved. Such a Soldier must engage in combat during that Phase if ordered to do so by the owning Player's Plot without any consideration of the combat result. Exception—the Command Control rules in the Standard Game amend this slightly to favor Soldiers in Command Control. (See 14.0.)

[5.22] Both Players execute all movement during the Movement Phase. All movement must be executed precisely as plotted (casualty status permitting). Soldiers may never alter their movement in response to Enemy movement.

[6.0] DISTINCTIONS BETWEEN SPECIES

GENERAL RULE:

The differences between the species which are represented in StarSoldier are simulated in the game by three distinguishing characteristics, which tend to determine the ways in which each species can most effectively participate in combat. These characteristics are Task Point Allowance (TPA), Efficiency Rating, and Recovery Rate. Numerical values for these characteristics are listed below on the Species Capacity Chart.

CASES:

[6.1] TASK POINT ALLOWANCE

The Task Point Allowance (TPA) is the number of Task Points which can be expended in a given Game-Turn by an individual Soldier. Each Soldier's TPA is a measure of combat ability, in general terms. Task Points must be expended in order to perform movement, offensive, and defensive tasks. The TPA may vary from turn to turn due to the effects of adverse combat results and /or recovery from them. The current TPA of each Soldier is kept track of on the Task Point Level Track (see 11.0).

[6.2] EFFICIENCY RATING

The Efficiency Rating is a sort of generalized evaluation of "competence" (i.e., co-ordination, initiative, and so forth). The rating for each Soldier depends on that Soldier's Species and never varies due to the effects of combat results, unlike the TPA. The effectiveness of each and every task performed by a Soldier is affected by that Soldier's Efficiency Rating.

[6.3] RECOVERY RATE

Each Soldier has a capacity for recovering from adverse effects incurred in combat (which reduce the TPA). This is the Recovery Rate, which is constant (never varies). During each Recovery Phase, each Soldier's TPA may be adjusted upwards an amount equal to that Soldier's Recovery Rate.

[6.31] No Soldier who has suffered an adverse combat result (i.e., lost any Task Points) during the immediately preceding Execution Phase and/or Projectile Resolution Phase, or incurred a "Stun" result during that Projectile Resolution Phase, may "recover" in a given Recovery Phase.

[6.32] No Soldier may "recover" to a higher TPA than the initial TPA with which that Soldier began the game.

[6.4] SPECIES CAPACITY CHART

(see center pages)

[7.0] STARSOLDIER TASK SUMMARY CHART

GENERAL RULE:

During a given Game-Turn, each Soldier may perform a combination of activities ("Tasks"). The tasks which may be performed are listed below in the Task Chart. Each task that a Soldier attempts costs a certain number of Task Points to execute. The term "Task Point" is a short-hand way of saying "activity per unit of time." Each Soldier has an allowance of Task Points (a Task Point Allowance, or "TPA") available for use in a Game-Turn, as indicated on the Task Point Level Chart. No combination of tasks for any Soldier may be plotted or executed that would cause this TPA to be exceeded in any Game-Turn.

PROCEDURE:

During each Plot Segment of the Game, the Players may assign in writing any of the tasks listed on the Task Chart for a given Soldier. More than one of the tasks detailed may be allocated to a single Soldier in a given Game-Turn, so long as the Soldier has sufficient Task Points to expend to execute all tasks assigned. After the Plot Segment of a particular Game-Turn is completed, all Soldiers must attempt, during the appropriate Phase, to execute all assigned tasks.

[7.1] TASK CHART

Basically, there are four different types of activity which may be plotted: movement, projectile launching, fire combat, and counter-measure. A Soldier or unit may undertake any combination of tasks so long as the total TPA of the Soldier for that Game-Turn is not exceeded. Each Task listed below has a short-hand code of two or three letters which may be used in assigning particular Tasks during the Plot Segment (See 5.0).

CodeTask Points ExpendedDescription
[MV]variesMovement, hex-by-hex, across the map. Task Point expenditures vary with the terrain and movement "Mode."
[GD]3TP or 0TPGrounding. The act of converting to Ground Mode (the Star Soldier equivalent of "hitting the dust").
[NE]3TPNap of Earth. The act of moving to Airborne Mode from Ground Mode, only slightly above the terrain surface.
[HA]3TPHigh Altitude. The act of moving to Airborne Mode from Nap of Earth at a higher altitude (about 5 km).
[LP]3+TPLaunching a Guided Positron Bomb toward a specific target hex.
[LM]3TP

[8.0] MOVEMENT

GENERAL RULE:

There are two Modes of movement: Ground Mode and Airborne Mode. Soldiers in Ground Mode move much slower than soldiers in Airborne Mode, although they are much better off defensively. A soldier is either in Ground Mode or in Airborne Mode at any given instant, and may shift from one to the other during the Movement Phase. Movement per se is considered to be the act of altering a soldier's position in some manner or other—either by changing Modes or moving from one hex to another—in accordance with the soldier's plot. Remaining in Airborne Mode "over" a hex is, therefore, not considered to be "movement." There is no limit to the number of Soldiers, enemy and/or friendly, who may be moved through or into a particular hex.

PROCEDURE:

Movement is an activity; as with all other activities, Task Points are allocated by the Players during the Plot Segment for each Soldier they intend to move. Then, during the Movement Phase, the Players execute the plotted movement of their soldiers as nearly as possible (casualty status permitting) to the orders as written.

CASES:

[8.1] GROUND MODE

[8.11] In order to move from one hex to another, a Soldier moving in Ground Mode must allocate and expend a number of Task Points equal to the Terrain Value of the hex entered. For example, a Soldier moving from hex 0525 to hex 0624 would have to expend three Task Points, as the Terrain Value of the organic cover hex (0624) is three. (See 12.6, Terrain Value Chart.)

[8.12] A Soldier in Ground Mode receives the defensive benefit of the Terrain Value of the hex occupied as outlined in Rules 9.62 and 10.0. (Exception, see Lakes, 12.5.)

[8.13] A Soldier in Ground Mode may shift to Airborne Mode by expending Task Points. It costs three Task Points to move from Ground Mode to Nap of Earth (i.e., Airborne Mode low level); it costs six Task Points to shift from Ground Mode to High Altitude. Shifting from Ground Mode to Airborne Mode does not affect a Soldier's position relative to the ground, only the distance from it. A Soldier shifting Modes would therefore remain in the same hex, unless additional Task Points were specifically allocated for that Soldier to move another hex.

[8.2] AIRBORNE MODE

There are two types of Airborne Mode: Nap of Earth and High Altitude. Nap of Earth is a "tree-top" level maneuver which yields the advantages of quicker movement without greatly increasing a Soldier's vulnerability to combat results. High Altitude puts the Soldier in a more vulnerable position, but yields a superior vantage point; also increases offensive potential.

[8.21] A soldier in Airborne Mode moving from one hex to another must expend ½ Task Point for each hex entered, regardless of the terrain value of such hexes.

[8.22] A Soldier at Nap of Earth receives the full defensive benefit of the Terrain Value of the hex occupied (exception 12.42). A Soldier at High Altitude receives a defensive benefit of "one" regardless of the actual terrain value of the hex (see 9.62).

[8.23] Soldiers who are plotted to spend any portion of a particular Game-Turn in Airborne Mode always have their Efficiency Rating halved when calculating Counter-Measure Strength during that Game-Turn (exception, see 23.2).

[8.24] A Soldier at Nap of Earth must expend three Task Points to shift to High Altitude. A Soldier at High Altitude must expend three Task Points to shift to Nap of Earth.

[8.25] A Soldier at Nap of Earth may shift to Ground Mode without expending any Task Points. Such a shift must, however, be pre-plotted during the Plot Segment of the Game-Turn. A Soldier at High Altitude must expend three Task Points to shift to Ground Mode.

[8.3] MOVEMENT PLOT EXAMPLE

The example lists the actions for two consecutive Game-Turns for Human StarSoldiers. All Soldiers begin in Nap-of-Earth. Soldier 101 moves to hex 3126 in the first turn and goes to Ground; in the second turn, the Soldier puts up two Task Points worth of CM and allocates the remaining three to Opportunity Fire. Soldier 102 moves to hex 3321 the first turn and then to 2921 the second turn, utilizing the remaining three Task Points to put up CM. Soldier 103 moves to 3533 the first turn and then 2629 the second turn and goes to Ground. Soldier 104 moves to 3517 in the first turn and expends four Task Points to launch a Guided Positron Bomb to 2220 and uses the fifth Task Point to put up CM in the second turn.

(The scan's plot example also carries handwritten pencil annotations, which are not transcribed.)

[9.0] FIRE COMBAT

GENERAL RULE:

There are two Fire Combat tasks: Direct Fire and Opportunity Fire. Both require the (pre-plotted) expenditure of Task Points to be performed. Direct Fire is plotted to be shot at a particular hex—the hex which the defender occupies during the Execution Phase (i.e., before any plotted movement is taken into account), the "target hex." It is resolved during the Fire Segment of the Execution Phase. Opportunity Fire is not aimed at any hex in particular; it is resolved during the Movement Phase.

The effectiveness of a particular Fire Combat is measured in terms of an Attack Strength. The value of the Attack Strength depends upon the firing Soldier's Efficiency Rating and the number of Task Points assigned to the attack. The target's vulnerability to Fire Combat is measured in terms of a Defense Strength. The value of the Defense Strength is dependent upon the range of the attack, target CM, amount of Task Points expended by the target on Movement, and terrain considerations. Some terrain impedes Fire Combat under certain circumstances.

PROCEDURE:

During the Plot Phase, each Player plots any Direct Fire Tasks to be assigned to any Soldiers, noting the target hex and effective Altitude Level within that hex of each attack, as well as the number of Task Points allocated to it. Also plotted at that point are any Opportunity Fire Tasks for each Soldier, with the number of Task Points to be expended noted. Then, during the Execution Phase, for each Fire Combat attack, the Attack Strength and Defense Strength are calculated (see 9.6). The Defense Strength is subtracted from the Attack Strength. The resulting number is the Attack Differential. Find the column on the Basic Game Fire Combat Results Table (9.7) which corresponds to the Attack Differential. Roll two dice and cross-index the total with the appropriate column to obtain the result of the Fire Combat attack. The result is the number of Task Points (if any) to be subtracted from the target's total of currently available Task Points on the Task Point Level Track (see 11.0). Immediately apply the results (if any) of the Fire Combat attack by making the appropriate adjustment on the Task Point Level Track (although in some instances, the effects of the combat result are considered to take effect only at the end of the Phase).

CASES:

[9.1] LINE OF FIRE

The firing Soldier must trace a Line of Fire (LOF) to the target hex of any Fire Combat attack. The LOF is traced in a straight line from the center of the hex which the firing Soldier occupies to the center of the target hex. (It is recommended that Players use a straight edge to make this determination.)

[9.11] Urban, mountain, and organic cover hexes impede Fire Combat at ground level. No Soldier in Ground Mode (see 8.1) may be plotted to perform a Fire Combat task if the LOF for that Task passes through any urban, mountain, or organic cover (exception, see 9.13). Soldiers in Ground Mode may be plotted to perform Fire Combat against targets in urban, mountain, or organic cover hexes, so long as the LOF for such combat does not pass through (i.e., in one side and out the other) any hex containing terrain which impedes fire.

[9.12] Urban and mountain hexes impede Fire Combat for Soldiers at Nap of Earth (8.2). Soldiers at Nap of Earth may not be plotted to execute Fire Combat if the LOF for that Task passes through any urban or mountain hex (exception, see 9.13).

[9.13] Soldiers at High Altitude may always be plotted to execute Fire Combat at any hex (exception, see 9.14). By the same token, a Soldier at High Altitude may be fired upon by a Soldier in any hex, regardless of the LOF (exception, see 9.14).

[9.14] No Fire Combat Task may be plotted or executed if the LOF for that task passes through or into a hex containing one or more live Friendly Soldiers (exception, see 9.4). The presence of Enemy Soldiers along the LOF has no effect on a Fire Combat Task; a Friendly LOF passing through a hex occupied by an Enemy Soldier has no effect on that Soldier.

[9.15] Special LOF conditions pertain to Soldiers in Crater and Lake hexes (see 12.4 and 12.5).

[9.2] OPPORTUNITY FIRE

Opportunity Fire differs from Direct Fire in that it occurs during the Movement Phase, and in that it may only be aimed at one target in a hex. The firing Soldier is, in actuality, withholding fire for as long as possible in the hope that a particularly valuable "target of opportunity" will present itself.

[9.21] Opportunity Fire may be plotted by any Soldier that is not plotted to expend Task Points on movement during the Movement Phase. A Soldier may not simultaneously move and perform Opportunity Fire.

[9.22] To plot Opportunity Fire, the owning Player writes that a given Soldier is assigned to Opportunity Fire, designating the number of Task Points to be expended on that Task. Note that it is not necessary, in plotting an Opportunity Fire Task, to designate a specific target hex. The Soldier's "sight" is assumed to be operative in all directions.

[9.23] A Soldier plotted to perform Opportunity Fire may fire at any target which, at any point during the Movement Phase, can be fired upon in accordance with the Line of Fire rules (9.1). Note that no actual movement per se is necessary on the part of the defender in order to be a possible target; a Soldier plotted to Opportunity Fire may fire at any target that is accessible in terms of Line of Fire.

[9.24] There is no limit to the number of targets a particular Soldier using Opportunity Fire may fire at at different points during the Movement Phase. Although each particular Opportunity Fire Combat affects only one target, if the firing Soldier utilizes only some of the allocated Task Points for such an attack, subsequent attacks against other targets (or even the same target) may be made, so long as Task Points allocated to Opportunity Fire remain.

[9.25] During a Movement Phase for which either Player has plotted Opportunity Fire for one or more Soldiers, each Player alternately executes the plotted movement of one Soldier until all possible plotted movement has been executed. At any point during this procedure, any Soldier plotted to perform Opportunity Fire during this Movement Phase may do so if there is an accessible target to be fired at.

[9.26] A Soldier plotted to perform Opportunity Fire may withhold fire, and is never forced to shoot at a given target. A Soldier may, therefore, pass up one possible target in the hope that a better one will show itself. However, a Player is never forced to "take back" the movement or part of the movement of a moving Soldier in order to allow an enemy Soldier a clear Opportunity Fire shot; e.g., if a moving Soldier "Y" moves into and then out of the sights of enemy Soldier "X" who is plotted to execute Opportunity Fire, and Soldier "X" elects to await another target and not fire at Soldier "Y", if no other target appears, Soldier "X" may not fire "retroactively" at the moving Soldier.

[9.27] If at the end of the Movement Phase (after all possible plotted movement has been executed) a Soldier plotted to perform Opportunity Fire who has not fired for one reason or another may now fire at any legitimate target (in accordance with 9.1).

[9.28] If a Soldier plotted to execute Opportunity Fire during a given Movement Phase is affected by Direct Fire during the immediately preceding Execution Phase, the Soldier may be prevented from performing the Opportunity Fire Task (if the combat effect is severe enough). By the same token, any Soldier affected during the Movement Phase by Opportunity Fire may be prevented from completing or performing movement, CM, or Opportunity Fire Tasks (see 11.0).

[9.29] One Soldier's Opportunity Fire Task takes precedence over another's if the owning Player of the first Soldier announces that the Soldier is firing and names the target hex before the other Player announces that his Soldier is firing. If one Opportunity Fire Task has precedence over another, the effects of any casualties resulting from it are applied before the second Opportunity Fire Task is resolved.

[9.3] MULTIPLE FIRE COMBAT

[9.31] Each Fire Combat attack against a particular target is resolved separately. If more than one attacking Soldier plots Fire Combat against one defending Soldier, the total strengths of the attackers are not combined; each attack is considered distinctly and is resolved separately, one by one. The attacks in such an instance may be resolved in any order deemed desirable by the attacker. (Exception, see 23.12.)

[9.32] In the event that a Soldier is plotted to perform Direct Fire against a Soldier that is killed as a result of another Direct Fire attack resolved before, the firing Soldier may not reallocate fire, and must go through with the (useless) attack as plotted.

[9.33] A Player may choose to have a Soldier perform Direct Fire Tasks against any number of different targets during the same Execution Phase. To do so, the Player simply designates the desired targets and the number of Task Points allocated to each attack. The attacks are then resolved separately.

[9.34] No individual Soldier may attack the same target more than once during any single Execution Phase (exception, see 9.24).

[9.35] A Fire Combat attack affects fully and individually all potential targets within the hex it is plotted to effect (exception, see 9.4), so long as they are all at the same Altitude Level. Example: if a Player were to have a Soldier execute Direct Fire at Nap of Earth altitude into a hex which was occupied by three Enemy Soldiers, two at Nap of Earth and one at Ground Mode, the attack would fully and separately affect both Soldiers at Nap of Earth; i.e., the attack would be resolved at full strength against both Soldiers, one at a time. Any CM put up by a Soldier affects Fire Combat against that Soldier only (exception, see 23.11).

[9.4] RESTRICTED FIRE

Restricted Fire is a type of Direct Fire which allows the firing Soldier to designate a specific Soldier as the object of the attack.

[9.41] When plotting Restricted Fire, the Player must designate a particular Soldier as the object of the attack. Regardless of the number of other Soldiers in the hex occupied by the Soldier designated as the target, and their Altitude Levels, only the designated object of the attack is affected by it.

[9.42] Restricted Fire may be plotted to pass through or enter a hex containing a Friendly Soldier, so long as the Friendly Soldier is not designated the object of the attack.

[9.43] Restricted Fire may not be used by Soldiers executing Opportunity Fire.

[9.5] HEAVY WEAPON SOLDIERS

Certain Soldiers (designated "HV") are equipped with augmented Fire Weapons. They are considered to be the same as normal StarSoldiers in all respects, except two:

a. The Efficiency Level of HV StarSoldiers is doubled when computing the Attack Strength for any Fire Combat Task they are plotted to perform.

b. HV Soldiers may never utilize Restricted Fire.

[9.6] HOW TO RESOLVE FIRE COMBAT

Subtract the Defense Strength of the target from the Attack Strength of the given Fire Combat (see 9.61). The result yields the Attack Differential. If the Attack Differential is less than or equal to zero, the attack is without effect. Otherwise, the value of the Attack Differential determines which column of the Basic Game Fire Combat Results Table (9.7) will be utilized to obtain the result of the attack. Roll two dice and cross-index the total with that column. Apply the result as appropriate (see 11.0).

[9.61] How to Compute the Attack Strength

The Attack Strength of Fire Combat is calculated according to the following formula: Firing Soldier's Efficiency Rating multiplied by the number of Task Points expended on the attack. For example, if a Human Soldier expended five Task Points on a Direct Fire attack, the Attack Strength would be ten (5 x 2).

[9.62] How to Compute the Defense Strength

The Defense Strength of a target is calculated according to the following formula: Range Attenuation + Target CM + Movement Effect + Terrain Value = Defense Strength.

Range Attenuation: since fire declines in strength and accuracy as distance to the target increases, the range of an attack has an influence on its effectiveness. To determine the range, count the number of hexes between the hex the firing Soldier is in and the target hex. (Count the hex which contains the target of the attack itself, but do not count the hex the firing Soldier occupies). For every ten hexes (and any fraction thereof) the Range Attenuation total is increased by "one." For example, at a range of nine hexes, the Range Attenuation value would be "one"; at a range of fifteen hexes, it would be "two." Add five hexes to the range if the firing unit is at High Altitude and the defending target is not (or vice versa). If the firing Soldier and the target occupy the same hex, the Range Attenuation value is "zero."

Terrain Value: The Terrain Value addition to a Soldier's Defense Strength is generally equal to the Terrain Value of the hex the Soldier occupies. (See 12.0, Terrain Value Chart). There are two exceptions to this: a) when a Soldier is at High Altitude, the Terrain Value of the Defense Strength against Fire Combat is always "one" regardless of the actual terrain contained in the hex; b) when a Soldier occupies a crater hex or a Lake hex, the Terrain Value addition to the Defense Strength is "one" unless the Soldier is in Ground Mode (see 12.4 and 12.5), in which case the Soldier receives the full Terrain Value benefit ("two").

Movement Effect: A Soldier undergoing Fire Combat adds "one" to the Defense Strength for each Task Point plotted to be expended on Movement during the immediately subsequent Movement Phase. This defensive benefit is never mitigated due to the effect of combat losses suffered during the Execution Phase to which it applies, even if losses result in the loss of Task Points allocated to movement. (The defensive benefit here is calculated on how far and how quickly the Soldier would be moving at the time the high-energy pulse is fired.)

Target Counter-Measure (CM): Represents efforts by the defender to mis-direct Enemy attacks by eliminating or disguising all energy emissions. Target CM = Defender's Efficiency Rating multiplied by the number of Task Points expended. Note that in calculating the CM value, the Efficiency Rating of any Soldier who was not plotted to spend the entire Game-Turn in Ground Mode is halved (8.23). For the purposes of Direct Fire, the CM put up by a Soldier affects attacks against that Soldier only, regardless of the number of Friendly Soldiers in the same hex (exception, see 23.11).

[9.63] How to Calculate the Attack Differential

The Attack Differential is calculated according to the following formula: Attack Strength (of firing unit) Minus Defense Strength (of target unit).

Example: A Human Soldier at Nap of Earth in hex 1325 spends five Task Points to fire at a L'Chal Dah Soldier in Ground Mode in hex 3028. The L'Chal Dah Soldier is not plotted to move and is expending one Task Point for CM (the other five go towards launching a GPB). The attack is calculated and resolved at an Attack Differential of "+3".

Defense Strength = 7. The range is seventeen hexes, so the Range Attenuation total is "two." The L'Chal Dah Soldier is in an organic cover hex in Ground Mode, so the Terrain Value benefit is "three." The defending Soldier is not moving, so there is no Movement Effect benefit. An expenditure of one Task Point on CM yields a Target Counter-Measure value of "two." Two plus three plus zero plus two equals seven.

Attack Strength = 10. The human Soldier expends five Task Points which is multiplied by the Efficiency Rating of two to yield ten.

Attack Differential = 3. Attack Strength (10) Minus Defense Strength (7) = Attack Differential (3).

[9.7] BASIC GAME FIRE COMBAT RESULTS TABLE

(see center pages)

[10.0] LAUNCHED WEAPONS

GENERAL RULE:

There are two types of Launched Weapons ("LW") in the Basic Game—Guided and Free Flight. LW are directed by Soldiers at specific target hexes when launched during the Execution Phase of the Game-Turn. The launching of an LW requires the (pre-plotted) expenditure of Task Points. During the Projectile Resolution Phase, the hex in which each LW which was launched actually explodes is determined, and any Soldiers within the blast radius of each LW are potentially subject to misfortune.

PROCEDURE:

During the Plot Phase, the Players determine and record any intended launchings of Guided or Free Flight LW. It is necessary to plot the target hex and the number of Task Points expended on launching the LW, as well as the type of LW used. During the Execution Phase, all Soldiers plotted to launch LW do so, and Guided Positron Bomb and Free Flight Missile counters are placed in the target hexes as appropriate. During the Projectile Resolution Phase, it is determined whether or not LW that were launched reach their designated target hexes. Free Flight Missiles are subject to being shot down by CM activity, and GPB's are subject to being "scattered" as a result of CM. The direction and distance of any GPB "scatter" is determined. Finally, the LW explode, and the effect of the detonation on any Soldiers (both Friendly and Enemy) within the blast radius of each LW is determined and effected immediately.

CASES:

[10.1] GUIDED POSITRON BOMB

A minimum of three Task Points must be expended in order to launch a Guided LW, although more may be allocated at the option of the Player. Each Guided LW is equipped with extensive, highly sophisticated guidance systems designed to give the weapon the independent capacity to discern and approach any potential target in the general vicinity of its intended impact area. However, these guidance systems can be counter-utilized by astute potential targets to misdirect the LW away from them, by purposefully feeding the guidance system false information.

[10.11] Guided LW are subject to the possibility of landing in a hex other than the one they are aimed at ("scatter"). The chances of scatter occurring are dependent on the Scatter Differential.

[10.12] To determine the Scatter Differential for a Guided LW use the following formula: Launcher's Efficiency Rating multiplied by the number of Task Points expended on the launch, minus Range Effects Rating plus Target CM value (ERxTP)-(R+CM)=SD.

[10.13] In calculating the Scatter Differential, the Range Effects Rating is determined by counting the number of hexes between the launcher and the target hex (not counting the hex the launcher occupies) and dividing that number by five (round any fraction up). Terrain has no effect on range. Example: If the number of hexes between the launcher and the target hex was nine, the Range Effects Rating would be two; if the number of hexes was eleven, the Range Effects Rating would be three.

[10.14] To determine the Target CM value in calculating the Scatter Differential, assume that the LW would explode in the target hex and ascertain which targets would potentially be affected by the explosion (that is, all targets within the blast radius of the explosion). The Target CM (see 9.62), if any, for all such potential targets within the blast radius is added into a single total, and that total is the Target CM value.

[10.15] If the Scatter Differential is equal to or greater than zero, the Guided LW successfully lands (and explodes) in the target hex. If the Scatter Differential is less than zero, there is a chance that the LW will miss. Refer to the Scatter Table (10.4). Each column corresponds to a Scatter Differential value. Find the appropriate column and roll the die. Cross index the die roll to find the scatter result. The hex to which the LW scatters is the hex of detonation.

[10.2] FREE FLIGHT MISSILES

Free Flight Missiles require the expenditure of three Task Points to be launched. They lack extensive guidance and CM systems, but are powerful.

[10.21] The effective range of a Free Flight Missile is ten hexes. No Soldier may be plotted to launch a Free Flight Missile at a hex more than ten hexes away.

[10.22] To determine whether or not a particular Free Flight Missile is intercepted, total all of the CM of any potential targets within what would be the blast radius (see 10.3) of the explosion if it were to occur as plotted in the target hex. Multiply the CM Total by the Range Effects Rating—"one" if the range is 0-5 hexes or "two" if the range is 6-10 hexes—and refer to the FFM Interception Table (10.25); cross-index a die roll with the appropriate column of that Table. If a "D" result is obtained, the LW is considered to have been intercepted and destroyed, and does not detonate.

[10.23] Free Flight Missiles are not subject to Scatter.

[10.24] FFM Interception Table

(see center pages)

[10.3] DETONATION AND ITS EFFECTS

An LW is launched during the Launch Segment of the Execution Phase. Place the appropriate Marker in the target hex. The Game-Turn proceeds through the Movement Phase, until the Detonation Segment, when all surviving LW explode. (The detonation occurs after scatter and—for Free Flight Missiles—possible interception resolutions have been completed during the Scatter Segment.) An LW explosion attacks any personnel, Enemy and/or Friendly, within its blast radius. The blast radius is defined as the hex of detonation and all hexes within two Task Points (of movement at the basic terrain cost of that hex) and is considered to be either at ground level or high altitude. The detonation attacks anything at the same altitude level in its hex with an Attack Strength of 30; it attacks anything in adjacent hexes (if the explosion "reaches" into adjacent hexes) with a strength of 15, and anything it reaches two hexes away with a strength of five. To determine the combat odds, divide the Attack Strength of the explosion by the Terrain Value of the terrain in the hex in question. Roll two dice and consult the appropriate column of the Launched Weapons Combat Results Table (10.5) to determine the effects of the explosion on a target within the blast radius. The result listed is either the number of Task Points (if any) to be subtracted from the target's total of currently available Task Points on the Task Point Level Track, or a Stun ("S") result. (See 11.0.)

[10.31] The Game-Turn is structured so that LW Scatter and detonation takes place "after" Movement, although the Launch Segment precedes the Movement Phase. Hence, it is possible for some Soldiers to move into, and others out of, the Blast Radius of an LW. If a Soldier is plotted to end movement within the blast radius of an LW, the Player must of course carry out that movement as plotted, regardless.

[10.32] Two or more Soldiers in a hex are each attacked separately (roll the dice once for each) with the full Attack Strength of any detonation occurring in that hex.

[10.33] The effects of two or more LW's are not combined in one attack. A Soldier caught in the blast radii of two or more LW's is attacked separately and individually by each.

[10.34] LW's are "blind" and affect all personnel, Enemy and/or Friendly, in the Blast Radius. However, only Soldiers at Nap of Earth or in Ground Mode are considered to be in the Blast Radius (exception, see 10.35).

[10.35] LW's can be detonated at High Altitude. If this is desired, it must be noted on the Plot for that particular LW. The Blast Radius for a detonated LW at High Altitude spreads as normal, but terrain is ignored and only Soldiers at High Altitude are affected.

[10.36] The detonation of an LW other than at High Altitude results in the formation of a crater in the hex at the center of the Blast Radius. A Crater Marker is placed in the hex in question to indicate its changed terrain status (see 12.4). Exception: LW explosions never result in the formation of craters in mountain, lake, or urban hexes.

[10.37] Any Soldier incurring a "Stun" result may not "recover" any Task Points during the immediately subsequent Recovery Phase (case 6.31). That is the only effect of a "Stun" result.

[10.38] A detonation of an LW at High Altitude has no effect on any Soldiers at Nap of Earth or in Ground Mode; a detonation at ground level does not affect any Soldiers at High Altitude.

Examples:

Guided Positron Bomb: A L'Chal Dah Soldier in hex 3405 expends three Task Points to launch a GPB at hex 1430, and an additional three Task Points to launch one at hex 2715. At the end of the Movement Phase, both hexes are occupied by Enemy Human Soldiers. The L'Chal Dah Player first determines "Scatter." The range to hex 1430 is 35 hexes, so the Range Effects Rating is 7 (35÷5=7). The Soldier in 1430 is expending two Task Points on CM and has been in Ground Mode for the entirety of the current Game-Turn, so the CM total is not halved; it is 4. The Scatter Co-Efficient is "-5." [(2x3) minus (7+4)=-5]. A die is rolled, and a "six" results. This is cross-referenced with the "-5" column on the Scatter Table (10.4). The weapon does scatter. The die is rolled again to determine the direction of scatter. A "one" is rolled, so the LW scatters to and detonates in hex 1427. Since the Blast Radius "lacks sufficient Task Points," so to speak, to effect hex 1430, the Soldier in that hex is not affected.

The range to hex 2716 is 14 hexes, so the Range Effects Rating is 3. The Soldier in that hex moved there in Airborne Mode, and the CM total, on which four Task Points are being expended, is halved (to 4). The Scatter Co-Efficient is "-1." [(2x3) minus (3+4)]. A "five" is rolled on the die and the LW scatters. A second die roll of "three" determines that the LW scatters into hex 2817. However, as the Blast Radius does affect adjacent hexes containing terrain with a Terrain Value of "two," the Soldier in hex 2716 is attacked on the "6-1 through 10-1" column (the attack is at 15-2). Two dice are rolled totaling "5" and the Soldier loses three Task Points.

Free Flight Missile: A Human Soldier in hex 3126 launches an FFM at hex 3321. The Enemy Soldier which ends the Movement Phase in that hex has allocated two Task Points to CM activity. Therefore, a die is rolled and the FFM Interception Table consulted. The CM value is four, so the die roll of "one" is cross-referenced with the "1-10" column. Consequently, the LW is destroyed, and no detonation takes place.

[10.4] SCATTER TABLE

(see center pages)

[10.5] BASIC GAME LW CRT

(see center pages)

[11.0] TASK POINTS AND THE TASK POINT LEVEL TRACK

GENERAL RULE:

Each Soldier begins the game with a certain Task Point Allowance (see 6.1, Species Capacity Chart). The TPA of a given Soldier may vary during the course of the game, depending primarily upon the results of combat directed against that Soldier. The current TPA of each Soldier is always indicated on the Task Point Level Track.

CASES:

[11.1] TASK POINT TRACK MARKER

Before the game begins, the Players should assign each of their Soldiers a particular "Track" on the Task Point Level Track. A Task Point Level Track Marker is placed in the box of the appropriate value to mark the Soldier's initial TPA (see 6.1). Each time an adverse combat result is incurred, the marker is adjusted to reflect that Soldier's new (reduced) TPA.

[11.2] TASK POINT LOSSES

[11.21] Any adverse Combat Result suffered by a Soldier always reduces the current TPA and subtracts from any Task Points allocated to be used during the current Game-Turn (exception, see 11.22). Tasks that were to have been performed utilizing those Task Points will, consequently, not be able to be performed. Example: A Terran Soldier with a TPA of five applies two Task Points to CM and three Task Points to launching an FFM. During the Execution Phase, the Soldier is fired upon and suffers a loss of two Task Points. The owning Player reduces the Soldier's TPA on the Task Point Level Track to three, and following the conclusion of the Execution Phase, the CM put up by the Soldier is considered to have been eliminated.

[11.22] A Soldier who suffers an adverse combat result may never lose Task Points allocated to be used during the current Game-Turn for Tasks which "have been completed" (according to the Sequence of Play, 4.0) prior to when that combat result is considered to take effect. If a result is incurred which calls for a Soldier to lose more allocated Task Points than are "available" to be lost because of this rule, the excess allocated Task Points to be lost are ignored. Note, however, that the Soldier's TPA must still be reduced by the full amount called for by the combat result. In the example quoted in Case 11.12, therefore, had the Soldier suffered a loss of three Task Points rather than two, the owning Player would have reduced the Soldier's TPA on the Task Point Level Track to two, and following the conclusion of the Execution Phase, the CM put up by the Soldier would be considered to have been rendered useless. Note that there would have been no additional effect beyond the elimination of the CM, as the effects of a combat result suffered during the Execution Phase are incurred only after the conclusion of that Phase; the launching of the FFM is considered to have happened prior to the Soldier being hit.

[11.23] Whenever a Soldier suffers a loss that must be subtracted from Task Points allocated, and more than one task for that Soldier is plotted in the current Game-Turn, the owning Player may choose the priority for the loss freely, so long as the proper number (or all available) allocated Task Points are lost. For example, a L'Chal Dah Soldier with a TPA of six applies three Task Points to moving six hexes in Airborne Mode and three Task Points to CM activity. During the Execution Phase, the Soldier is fired upon and suffers a loss of four Task Points. The owning Player reduces the Soldier's TPA on the Task Point Level Track to two and decides whether, following the conclusion of the Execution Phase, the Soldier will either put up two Task Points worth of CM and not move at all, put up one Task Point worth of CM and move two of the intended six hexes, or put up no CM whatever and move four of the intended six hexes.

[11.24] Any Soldier which has a TPA level of zero is considered to have been killed. The counter representing such a Soldier is immediately removed from play.

[12.0] TERRAIN

GENERAL RULE:

The terrain features printed on the map have a variety of effects upon movement, fire, and the defensive capacity of Soldiers under attack. Generally, the more "constricted" or "rough" the terrain, the slower Ground Mode movement will be, the less likely it is Fire Combat will pass through effectively, and the better a Soldier's attack resistance will be. This Section summarizes the various effects of terrain and lists the different types with their distinguishing characteristics. Detailed descriptions of the effects of terrain can be found in Rules Sections specifically concerned with movement, Direct Fire, and Launched Weapons, as noted below.

CASES:

[12.1] EFFECT OF TERRAIN UPON MOVEMENT

Soldier's movement is affected by the terrain in the hexes they pass through only when they are in Ground Mode. Soldiers in Airborne Mode ignore terrain for movement purposes. See 8.1, "Ground Mode," and 8.2, "Airborne Mode."

[12.2] EFFECTS OF TERRAIN UPON FIRE COMBAT

It is assumed that there is no terrain on Earth—or, anywhere else, for that matter—which can effectively block the sophisticated detection devices that the Star Soldiers will employ to discern the locations of their opposing counterparts. For this reason, there is no Line of Sight Rule, per se. However, knowing that a target is lodged squarely amidst a mass of mountain peaks and hitting it with a straight-shooting high energy burst are two entirely different propositions. That accounts for the Line of Fire rule (Section 9.1) which limits the terrain which a Soldier may fire through. Additionally, Soldiers at Nap of Earth or in Ground Mode receive a Defensive Benefit from the terrain of the hex they occupy. This Defensive Benefit is equal to the Terrain Value of the terrain in the hex. See Case 9.62, "How to Compute the Defense Strength," for the Terrain Value explanation.

[12.3] EFFECT OF TERRAIN UPON LW DETONATION

In determining the effect of the detonation of an LW on a Soldier in the Blast Radius, the strength of the explosion is matched against the Terrain Value of the hex occupied by the Soldier. See Section 10.3, "Detonation and its Effects."

[12.4] CRATERS

Under certain circumstances, the detonation of weapons may result in the formation of a Crater in a hex (see 10.36 and 20.14).

[12.41] When a Crater Marker is placed in a hex, the terrain that was formerly in that hex is of no account; for the purposes of the game, the hex is considered a Crater hex.

[12.42] Soldiers in Ground Mode in a Crater hex receive full defensive benefit of the terrain against Fire Combat and Launched Weapons. Soldiers in Airborne Mode (including Soldiers at Nap of Earth) receive a Terrain Value defensive benefit of "one" (only) against Fire Combat and Launched Weapons. (Exception to 8.22).

[12.43] Soldiers in Ground Mode in a crater hex may trace (and may have traced to them) a Line of Fire only to (from) enemy Soldiers in Airborne Mode in adjacent hexes.

[12.5] LAKES

Lake hexes are treated as crater hexes except in one respect: A Line of Fire (LOF) may always be traced to or from a Soldier in a lake hex through any number of lake hexsides. Exception: the LOF may not be traced thus to a Soldier in ground mode who is not in a lake hex.

[12.6] TERRAIN VALUE CHART

(see center pages)

[13.0] PLAYING THE BASIC GAME

[13.1] INTRODUCTION

Although Human settlements had been established in a half-dozen systems by the mid-25th Century, it wasn't until 2451 that the First Contact occurred. It came about when two L'Chal Dah Star Forces happened across the newly-established Human outpost in the Eta Cassiopeiae system. There were no Human Star Forces present, and so after both sides recovered from the shock of the Eta Cassiopeiae StarGate adopted a coy, temporizing attitude, hoping to bemuse the L'Chal Dah long enough for help to arrive. Unfortunately, the ploy only succeeded in energizing the intruders, who swiftly neutralized the StarGate, and landed a scouting force on Eta Cassiopeiae II in an attempt to gain information. The scenario concerns the approach of a Squad of the L'Chal Dah to a moderately sized inhabited area. The object of the L'Chal Dah was to capture Humans for the purpose of gaining information. The L'Chal Dah, prudently wishing to avoid unnecessarily provoking the humans, operated under considerable constraints in an effort to avoid bloodshed. However, the Humans, who had partially completed an evacuation of civilians from outlying areas to a more secure central repository, had guarded the area with a Fireteam of StarSoldiers, who attempted to prevent the L'Chal Dah from capturing and removing civilians.

[13.2] ORDERS OF BATTLE AND DEPLOYMENT

The Human Player deploys all ten Civilian Markers (seven "dummies" and three genuine) face-up in urban hexes, without revealing which are which to the L'Chal Dah Player. The Civilians may be placed in any urban hexes, with the following restrictions: no more than one Civilian Marker may be placed in any one hex; nor more than three Markers may be placed in any one "group" of contiguous urban hexes; and no more than two genuine Markers may be placed in any one such "group" of hexes. The Human Player now deploys five StarSoldiers, including one Heavy Weapons Soldier (this is the equivalent of one "Fireteam") on the map.

The L'Chal Dah Player receives seven StarSoldiers including two Heavy Weapons Soldiers (the equivalent of a "Squad"). After the Human Player has deployed all Civilian Markers and Soldiers, two dice are rolled to determine on which side of the map the L'Chal Dah enter. A roll of "2," "6," "7," "8," or "12" results in the L'Chal Dah entering the map between hexes 3901 and 3954 inclusively. A roll of "4" or "5" results in the Soldiers coming in between hexes 3954 and 0154 inclusively. A roll of "3" or "11" [sic: "results in" is omitted in the printed text] and the L'Chal Dah Player may choose any hexes between 0154 and 0101 inclusively. Finally, if "9" or "10" is rolled, the L'Chal Dah enter somewhere between 0101 and 3901 inclusively. Soldiers enter the map on the first Game-Turn with a full complement of Task Points which they begin to expend with the move into the first hex.

[13.3] VICTORY CONDITIONS

The L'Chal Dah Player must attempt to locate and transport off the board a "genuine" Civilian Marker without any Human civilians being killed; the Human Player must attempt to prevent this from occurring. There are five different possible combinations of results which yield various degrees of victory for one side or the other:

  • Substantive L'Chal Dah victory—at least one Civilian Marker off the board; no civilian casualties.
  • Marginal L'Chal Dah Victory—at least one Civilian Marker off the board; one or more killed by Human fire or LW.
  • Marginal Human Victory—No Civilian Markers transported off the board; one or more casualties to Civilians caused by Human fire or LW.
  • Substantive Human Victory—No Civilian Markers transported off the board; no civilian casualties.
  • Decisive Human Victory—Any civilian casualty caused by L'Chal Dah fire or LW, under any circumstances.

[13.4] SPECIAL RULES

[13.41] Human StarSoldiers may launch LW at hexes containing genuine Civilian Markers only if such a Marker has been transported out of the hex in which it was originally deployed by a L'Chal Dah Soldier and if it begins the Execution Phase during which the LW is launched in a hex occupied by one or more L'Chal Dah StarSoldiers.

[13.42] StarSoldiers may plot fire against Enemy Soldiers occupying hexes also containing Civilian Markers utilizing Restricted Fire (only). If a StarSoldier transporting a Civilian Marker is the object of a Restricted Fire attack, any result affecting the Soldier affects the Civilian as well (see 13.47).

[13.43] L'Chal Dah StarSoldiers may "Search" a hex containing a face-up Civilian Marker, thereby discerning the nature of that Marker. The L'Chal Dah Soldier must occupy the hex for one full Movement Phase and have plotted one Task Point to search activities (code "SE") to be expended during that Movement Phase. At the end of any Movement Phase in which these conditions are fulfilled, the Civilian Marker is inverted and if it is a "dummy," it is removed from play.

[13.44] Any Soldier that begins a Movement Phase in the same hex with an inverted Civilian Marker may attempt to "Transport" it by expending three Task Points per Game-Turn that the Marker is transported (code "TR"). The Marker is placed under the counter representing the StarSoldier and is moved along with the Soldier as plotted (if the Soldier utilizes any remaining TP's to move). Should more than one Soldier be plotted to transport the same Civilian Marker, neither of them succeed, and the Task Points allocated to the TR task are automatically shifted to Restricted Fire aimed at the other Soldier.

[13.45] The L'Chal Dah Player may attempt to transport an inverted Civilian Marker off the board utilizing any map-board edge.

[13.46] A Civilian Marker within the blast radius of an LW detonation undergoes an "attack" on the LW Combat Results Table utilizing the appropriate column as determined by the terrain. In the event that there is any effect other than "Stun" (which is ignored), the Marker is inverted (if it has not yet been). If it is a "dummy," it is removed from play; if it is genuine, it is affected by the result (see 13.47).

[13.47] Any genuine Civilian Marker affected by a combat result is considered to have been killed. If L'Chal Dah fire or an LW caused the casualty, the game ends in a Decisive Human Victory (see 13.3); otherwise, play continues.

[13.48] The Human Player receives reinforcements, which enter the game piecemeal, beginning at a randomly determined point in time. Beginning with the second Game-Turn and continuing thereafter, the Human Player rolls one die prior to the Plot Phase. If the number rolled is less than or equal to the number of the Game-Turn, the reinforcements begin arriving that turn. For example, if the Human Player failed to roll successfully for reinforcements on the second and third Game-Turns, a roll of "one," "two," "three," or "four" on the fourth turn would cause the reinforcements to begin entering the game, while a roll of "five" or "six" would mean their arrival would be delayed. One Human StarSoldier comes into the game (entering in any hex along the edge of the map) the turn of the successful reinforcement roll; two Soldiers (including one Heavy Weapons Soldier) the next turn, a fourth Soldier after the next turn, and a fifth the next.

[14.0] STANDARD GAME SEQUENCE OF PLAY

Several things distinguish the Standard Game from the Basic Game. Most of them are simply additions—of species, weapons, and constraints on their use—that build upon the structure of the Basic Game. Except where specifically contradicted, the Basic Game rules apply as stated in the Standard Game. There is, however, one significant alteration that affects the very structuring of the play of the game—in the Standard Game, the Game-Turn is broken down into two identical Stages (see Rule 15.0). This alteration is reflected in the Standard Game Sequence of Play.

SEQUENCE OUTLINE:

A. Initial Stage

  1. Plot Phase

    a] Command Communication Segment: The Players determine which of their Soldiers, if any, are outside the range of Friendly Communications Control. "Ind" markers are placed on all affected ("Independent") Soldiers.

    b] Plot Segment: Each Player simultaneously and secretly determines and plots the movement and combat activities for the current Stage for each Soldier.

  2. Execution Phase: For the sake of convenience, this Phase is divided into four Segments. The first two Segments are for the plotted actions of those Soldiers in Command Communication; the last two are for executing the plots of Soldiers not in Command Communication. All casualties incurred during the first Segment take effect between the second and third Segments. All casualties resulting from actions taking place during the third Segment take effect after the fourth Segment.

    a] Command Fire Segment: All Soldiers in Command Communication who are plotted to execute Direct Fire do so. Players should adjust their Task Point Level Tracks where necessary to indicate casualties (which take effect after the following Segment).

    b] Command Launch Segment: All Soldiers in Command Communication who are plotted to launch projectiles do so. All casualties inflicted during the Command Fire Segment are then considered to take effect.

    c] Independent Fire Segment: All Soldiers not in Command Communication who are plotted to execute Direct Fire do so (casualty status permitting). Players should adjust the Task Point Level Tracks where necessary to reflect casualties inflicted during this Segment (which take effect after the following Segment).

    d] Independent Launch Segment: All Soldiers not in Command Communication who are plotted to launch projectiles do so (casualty status permitting). Casualties inflicted during the Independent Fire Segment are then considered to take effect.

B. Second Stage

Repeat Phases 1, 2, 3, 4, and 5 in order. That completes one Game-Turn.

[15.0] DIVIDING THE GAME-TURN INTO STAGES

GENERAL RULE:

The Standard Game is played with a Game-Turn that is divided into two halves called "Stages." As in the Basic Game, each StarSoldier is granted a Task Point Allowance for the entire Game-Turn (see 6.42). However, instead of allocating the entire Task Point Allowance for the whole Game-Turn in one shot as in the Basic Game, the Player will have to split it between two distinct Stages, during two separate Plot Segments in the course of each Game-Turn (see 14.0, Standard Game Sequence of Play). The allocation of Task Points is, in the Standard Game, therefore a somewhat more subtle exercise, in that the Player must keep in mind the requirements of the second Stage while plotting the first.

PROCEDURE:

During the Plot Segment of the Initial Stage of the Game-Turn, both Players determine and record all activity for the Initial Stage. The Initial Stage then proceeds according to the Sequence outlined in 14.0. During the Plot Segment of the Second Stage of the Game-Turn, the Players allocate any Task Points from each Soldier's Task Point Allowance that were not expended during the Initial Stage to any desired activities for the Second Stage. The Second Stage then proceeds as outlined in Rule 15.0.

CASES:

[15.1] COMBAT RESULTS EFFECTS ON TPA

[15.11] Any adverse Combat Result suffered by a Soldier always reduces the current TPA and subtracts from any Task Points allocated during the current Stage (exception: see 15.2). Tasks that were plotted utilizing those Task Points will, consequently, not be able to be performed.

[15.12] A Soldier that suffers an adverse Combat Result may never lose Task Points allocated to be used during the current Stage for Tasks which "have been completed" (according to the Sequence of Play, 14.0) prior to when that combat result is considered to take effect. If a result is incurred which calls for a Soldier to lose more allocated Task Points than are "available" to be lost because of this rule, the excess allocated Task Points to be lost are ignored. Note, however, that the Soldier's TPA must still be reduced by the full amount called for by the combat result. See Cases 11.13 and 11.14 for pertinent examples.

[15.2] RESTRICTIONS ON TP EXPENDITURE

[15.21] The number of Task Points available to be allocated in an Initial Stage is always equal to the current TPA as displayed on the Task Point Level Track.

[15.22] The number of Task Points available to be expended during the Second Stage is equal to the current TPA (as adjusted for any casualties suffered during the Initial Stage) minus any Task Points expended (not merely "allocated") during the course of the Initial Stage.

[15.23] No Soldier may be plotted to execute in one Game-Turn tasks the total Task Point cost of which exceeds the Soldier's Task Point allowance.

[15.24] No Soldier may be plotted to expend more than six Task Points in any given Stage.

[16.0] COMMAND COMMUNICATIONS

PROCEDURE:

To be in Command Communications ("in Command") a Soldier must be within a certain distance of a Friendly Soldier who has been designated as a Leader. This distance will vary, depending on terrain and the damage state of the units involved. To determine whether an individual Soldier is in Command, add the Terrain Value of the hex occupied by the unit to the Range Effects Rating for the distance between the unit and the leader. If the sum of the two numbers is less than or equal to the current TPA status of the Soldier (as indicated on the TPA track, regardless of the number of Task Points that may have been expended in previous Stages), then the Soldier is in Command. If the sum of the two numbers is greater than the Soldier's current TPA status, then the Soldier is not in Command and must function as an independent Soldier. This determination is made each Plot Phase; Soldiers not in Command are marked with "Ind" markers.

[16.1] EFFECTS OF COMMAND COMMUNICATION

Units that are in Command perform Direct Fire Tasks in the Command Fire Segment of the Execution Phase, and perform LW Tasks in the Command Launch Segment of the Execution Phase. Soldiers not in Command perform Direct Fire Tasks in the Independent Fire Segment of the Execution Phase, and perform LW Tasks in the Independent Launch Segment of the Execution Phase. (This is the only effect of Command Communication; i.e., to see if one Soldier or the other "fires first" in a combat situation.

[16.2] FURTHER CONDITIONS

[16.21] Leaders are always in Command. Note that the TPA status of the leader has no effect on determining Command for other units (except that obviously a leader who has been killed can no longer perform that function). Note also that the terrain in the hex occupied by the leader has no effect on the determination.

[16.22] Rame Soldiers (since they are telepathic) are always in Command, and therefore have no leader units.

[16.23] Players must designate particular Soldiers to be leaders, as per the Scenario order of battle. However, Players need not reveal which of their Soldiers are Leaders during the course of play; there are no special "Leader counters."

[17.0] PRESERVATION LEVEL

GENERAL RULE:

Each side in each Scenario is given a Preservation Level number. This number is the overall number of Task Points lost, beyond which its Preservation Level is reached. A running tally is kept of each side's total cumulative losses in Task Points. Whenever one side exceeds its Preservation Level, its combat effectiveness is reduced considerably. (See 25.0 for a listing of standard unit Preservation Levels.)

PROCEDURE:

On the bottom of the Task Point Level Track is the Preservation Level Track. Each Player records losses in Task Points on this Track. Whenever a Soldier suffers an adverse Combat result, the owning Player adjusts the Preservation Level Track upwards.

CASES:

[17.1] EFFECT ON EFFICIENCY RATING

Beginning with the Game-Turn immediately following the one in which the Preservation Level of a side has been exceeded, the Efficiency Rating of all Soldiers Friendly to that side is halved for the remainder of the game (exception, 17.2).

[17.2] MUTUAL ACHIEVEMENT OF PRESERVATION LEVEL

Once one side has exceeded the Preservation Level, the other side is not effected by subsequently exceeding its Preservation Level. It is theoretically possible for both sides to simultaneously exceed their respective Preservation Levels during the same Fire Segment of Detonation Segment. In such an instance, both sides incur the effect of exceeding the Preservation Level (17.1).

[17.3] The addition of a Support Platform to one side's Order of Battle increases that side's Preservation Level (see 21.4).

[17.4] All Task Points "recovered" during the Recovery Phase are subtracted from the total on the Preservation Level Table.

[18.0] OPACITY GRENADES

GENERAL RULE:

Opacity Grenades are explosive projectiles that, when successfully deployed, impede Fire Combat and movement. Aside from the effects of their detonation, Opacity Grenades behave as Free Flight Missiles.

PROCEDURE:

Precisely as with an FFM, an Opacity Grenade launching is plotted during a Plot Phase and launched during the corresponding Launch Segment. It may subsequently be intercepted by Enemy CM during the Scatter/Interception Segment of the Projectile Resolution Phase, and if not intercepted, it then detonates in the hex plotted. The Opacity Grenade Marker is inverted to reveal an electronic "smoke" counter.

CASES:

[18.1] EFFECTS ON MOVEMENT

[18.11] The Terrain Value of any hex in which an Opacity Grenade explodes is increased by "two." This effect applies both to Soldiers in Ground and Airborne Modes; to enter the hex, a Soldier must expend an additional two Task Points over and above the number that would normally have to be expended.

[18.12] The effect of the detonation of an Opacity Grenade on movement persists for one full Game-Turn (two Movement Phases) after the explosion.

[18.2] EFFECTS ON COMBAT

[18.21] For one full Game-Turn following the detonation of an Opacity Grenade in a hex, no Fire Combat LOF may be traced through (into and out of) that hex.

[18.22] Any Soldier in a hex with an operative Opacity Grenade receives the additional Terrain Value ("two") in computing the Defense Strength for any Fire Combat of which the Soldier is the object. However, there is no extra Terrain Value benefit to such a Soldier in the event an LW explodes in the hex.

[18.3] Any Soldier in a hex during a Detonation Segment in which an Opacity Grenade explodes in that hex is automatically stunned. (See Case 10.37).

[18.4] After one full Game-Turn has passed following the detonation of the Opacity Grenade, the effects are considered to have dispersed, and the electronic "smoke" Marker is removed from play.

[19.0] HOMING MISSILES

GENERAL RULE:

Homing Missiles are a special type of Launched Weapon. A Homing Missile is employed in one of two fashions—either it is launched by a StarSoldier during a Launch Segment or it is "planted" secretly in a hex prior to the beginning of play, to be set off if an Enemy Soldier comes near it. Homing missiles function by "homing in" on a target (a particular Enemy Soldier) and actually zooming towards it during the Movement Phase. If a Homing Missile successfully catches up to its target, it explodes; if it fails to do so, it self-destructs harmlessly.

PROCEDURE:

During the Launch Segment, Launched Homing Missiles are placed dormant-side up in the hex they are plotted to start in. Homing Missiles acting as mines are not deployed on the map; rather their locations are plotted by the Player deploying them to be revealed during the course of play as appropriate. During any subsequent Movement Phase, whenever an Enemy Soldier enters the Acquisition Horizon of a dormant Homing Missile, it is "activated." The Homing Missile counter is flipped over to its Active side (or deployed on the map Active Side-up in the case of a Homing Missile mine). The Target Acquisition Marker with the number corresponding to the Homing Missile is placed in the hex with the acquired target. The Homing Missile is then moved hex-by-hex, alternating with the plotted movement (if any) of the target, along the shortest possible path towards the target. If the Homing Missile succeeds in entering a hex containing its acquired target, it detonates; if it is unsuccessful by the end of the Movement Phase in which it was activated, it is removed from play.

CASES:

[19.1] LAUNCHING A HOMING MISSILE

[19.11] The Launching of a Homing Missile is plotted during a Plot Phase, just as with other launched weapons. It is necessary to record the number of Task Points expended and a hex into which the Homing Missile will be dropped.

[19.12] Launching a Homing Missile requires a minimum expenditure of three Task Points.

[19.13] For each Task Point allocated to the launching of a Homing Missile, it will travel up to five hexes towards the hex into which it is plotted to drop.

[19.14] A launched Homing Missile may never be plotted to be dropped into a hex less than fifteen hexes away from the hex it is launched from. (This is necessary to insure that the Missile has sufficient time to scan all possible targets and avoid locking onto a Friendly one.)

[19.15] Homing Missiles never scatter. When launched, a Homing Missile is simply placed, dormant side up, in the hex it is plotted to be dropped into.

[19.2] TARGET ACQUISITION

At any point during a Movement Phase, a dormant Homing Missile may acquire a target and be activated. In order for that to occur, the target must enter (or be in) the Homing Missile's Acquisition Horizon. Dormant Homing Missiles—both those which have been launched and are deployed on the board and any which may be deployed secretly as mines—are checked for target acquisition at the beginning of the Movement Phase and again as each StarSoldier plotted to move executes that Movement.

[19.21] The Acquisition Horizon of a dormant Homing Missile is variable, depending upon the Defense Strength of any potential target (see Case 9.62). The Defense Strength is calculated as if a Line of Fire were being traced for Fire Combat between the hex occupied by the Homing Missile (considered to be at Nap of Earth) and the target. Any eligible target with a Defense Strength less than or equal to ten is within the Acquisition Horizon of a Homing Missile and causes it to be activated.

[19.22] A particular Homing Missile may never acquire more than one target. If more than one target is within the Acquisition Horizon of a dormant Homing Missile at the beginning of a Movement Phase, the target with the lowest Defense Strength is the one acquired; in the case of a tie, select one target in a random fashion. If no targets are within the Acquisition Horizon of a Homing Missile at the beginning of a Movement Phase, the first target to enter its Acquisition Horizon during the course of that (or any subsequent) Movement Phase is acquired.

[19.23] So long as no target is in/enters the Acquisition Horizon of a Homing Missile, it remains in place, dormant, indefinitely.

STARSOLDIER CHARTS & TABLES

The Charts & Tables sheet of the scan is transcribed here in the order printed. Sections of the rules refer to these as "see center pages" or "see separate sheet".

[6.4] SPECIES CAPACITY CHART

[6.41] Basic Game

SpeciesTPAEff RtngRcvry Rate
Human521
L'Chal Dah621

[6.42] Standard Game

SpeciesTPAEff RtngRcvry Rate
Human923
Human Androids920
L'Chal Dah1221
L'Chal Dah Androids1220
Rame642
Rame Androids640
Xenophobe9

[9.8] FIRE COMBAT RESULTS TABLE (BASIC GAME)

Printed as [9.8]; Section 9.6 cites this table as "(9.7)". Dots (•) are printed as "no effect".

Combat Differential (Attack Strength Minus Defense Strength), columns +1 through +6 and up. Roll two dice and cross index with the Combat Differential to determine the number of Task Points lost by the attacked Soldier (see 9.6, How to Resolve Fire Combat). • = no effect. Attacks at less than "+1" are not possible.

Die Roll+1+2+3+4+5+6 and up
2456666
3345666
4234556
5123

[10.4] SCATTER TABLE

Printed text beside the table: "(see 10.1, Guided Positron Bombs). H = the Guided Positron Bomb lands (and detonates) in the hex it was intended for. S = the GPB will scatter; the number indicates how many hexes the GPB will scatter. To determine the direction of scatter, refer to the Scatter Diagram printed on the map. Each of the numbers from one to six corresponds to a direction away from the intended hex of detonation. Roll one die for each GPB that scatters to determine the direction of scatter. The GPB detonates in the hex scattered two."

Roll one die and cross index the roll with the Scatter Differential (see 10.12).

Die Roll-1-2-3-4-5-6 (or less)
1HHHHHS1
2HHHHS1S1
3HHS1S1S1S2
4HS1S1

[10.5] LAUNCHED WEAPONS COMBAT RESULTS TABLE (BASIC GAME)

Roll two dice and cross index the total with the combat odds (see 10.3). If the result is a number, it indicates the number of Task Points lost by the attacked Soldier; an S = attacked Soldier may not "recover" during the immediately subsequent Maintenance Phase (see 10.37). "•" = No effect.

Dice Roll1-1 thru 5-16-1 thru 10-111-1 thru 15-116-1 thru 20-121-1 thru 25-126-1 plus
2345666
3234566
4123456
5S2

[10.24] FREE FLIGHT MISSILE INTERCEPTION TABLE

Roll one die and cross index the roll with the value obtained from multiplying the CM total of all targets within the blast radius by the Range total (see 10.22). The value obtained is the Interception Value. "D" = missile destroyed; • = no effect on missile.

Die Roll1-1011-1516-2020+
1DDDD
2•DDD
3••DD
4•••D
5••••
6

[12.6] TERRAIN CHART

Terrain Type (and color)Terrain ValueBlocks Soldier's LOF when in...
clear (light beige)1NA
broken (yellow)2NA
organic cover (green)3Ground Mode
mountainous (brown) or urban (buildings)6Ground Mode and NOE
lake (blue)2Ground Mode (see 12.5)
crater (marker)2(see 12.4)

Note: "NA" indicates no effect on LOF. "NOE" is Nap of Earth.

[21.5] SUPPORT PLATFORM DAMAGE TABLE

Roll two dice.

Dice TotalResult
2 thru 7No Effect
8TPA Reduced ½
9TPA Reduced ½
10Laser Cannon Destroyed
11Laser Cannon Destroyed
12Support Platform Destroyed

This table is used only when a result of six or more Task Points lost is obtained against a Support Platform on either the Fire or Launched Weapons Combat Results Chart (see 21.33). In lieu of the result listed, roll two dice and refer to this table. "TPA Reduced ½" = 50% reduction of Platform's TPA. Round any fractions up. A Platform that has already been reduced 50% that incurs this result is Destroyed. "Laser Cannon Destroyed" = Laser Cannon may not be fired for remainder of game. If destroyed previously, treat this result as "TPA Reduced ½". "Support Platform Destroyed" = Support Platform Destroyed.

[26.1] STANDARD GAME COMBAT RESULTS CHART

Combat Differential (Attack Strength Minus Defense Strength)

Die Roll+1+2+3+4+5+6+7+8+9
281012121212121212
36810121212121212
44

Roll two dice and cross index the total with the Combat Differential (see 9.6). The number (if any) indicates the number of Task Points that are lost by the defending Soldier; • = there is no effect.

Attacks at less than "+1" are not possible; attacks at greater than "+9" are treated as "+9".

[26.2] LAUNCHED WEAPONS COMBAT RESULTS TABLE

Dice Roll1-1 thru 5-16-1 thru 10-111-1 thru 15-116-1 thru 20-121-1 thru 25-126-1 plus
26810121212
3468111212
424681012
513

Roll two dice and cross index the total with the Combat Odds (see 10.3). A number result indicates the number of Task Points lost by the defending Soldier; S = defending Soldier is stunned (see 10.37); • = no effect.

[41.3] UNIT ORGANIZATION COST CHART

CostUnit
5 Tac PtsSupport Platform, Base (per hex)
4 Tac PtsSquad
2 Tac PtsHeavy Section, Fireteam, Android team
1 Tac PtFive individual Homing Missiles usable as mines.

[41.6] ORBITAL GROUND SUPPORT AVAILABILITY CHART

The following charts the number of Friendly StarForces orbiting a planet occupied by at least one Enemy Strike Command against the Civilian Density of the system, as explained in Case 40.51.

StarForcesCivilian Density 3 (or zero)Civilian Density 6Civilian Density 8
1FullHalfHalf
2FullFullHalf
3+FullFullFull

[19.24] Whenever a Homing Missile acquires a target, it is flipped over to its active side (or deployed on the map for the first time, active side up, in the case of a Homing Missile acting as a mine). The acquired target is marked with the Target Acquisition Marker with the number corresponding to that of the Homing Missile.

[19.3] MOVEMENT OF HOMING MISSILES

During the Movement Phase in which it is activated, a Homing Missile will move towards its acquired target. The movement of the Homing Missile and its target (if any) are resolved on a hex-by-hex basis, with the target considered to move "first."

[19.31] An activated Homing Missile is considered to have a Task Point Allowance of "six," and to be at NOE (hence, it can move up to twelve hexes). It must always move by way of the shortest possible path towards its target.

[19.32] At any point in time at which an activated Homing Missile is in the same hex as its acquired target, the Homing Missile detonates and any consequential results are applied immediately (exception, see 19.33).

[19.33] Opportunity Fire, which is executed during the Movement Phase, is considered to be Movement if plotted by an acquired target. Therefore, a Soldier acquired by a Homing Missile as a target always has the opportunity to execute Opportunity Fire (if any has been plotted) in an attempt to destroy the approaching Homing Missile (see 19.4, Homing Missile Vulnerability). Note that this is always the case; i.e., even if a Homing Missile were to be activated by a Soldier in the same hex, the Soldier would have the opportunity to execute Opportunity Fire prior to the detonation of the Homing Missile. (A Soldier in such a situation would also have the opportunity to move out of the hex before the Homing Missile could detonate if plotted to move, although, of course, the Homing Missile would immediately catch the Soldier in the first hex moved to.)

[19.34] If at the end of the Movement Phase in which it acquired a target a Homing Missile has failed to "catch" its target, it self-destructs with no effect and is removed from play.

[19.4] VULNERABILITY OF HOMING MISSILES

A dormant Homing Missile may be destroyed at any time during the Game-Turn by Fire or the detonation of other LW; an active LW may be destroyed during the Movement Phase by Opportunity Fire at any time prior to its detonation. The Defense Strength of a Homing Missile is determined in the same fashion as that of StarSoldiers (see Case 9.62). A Homing Missile is destroyed if any combat result other than "No Effect" is achieved against it, including "Stun."

[20.0] ORBITAL BOMBARDMENT

GENERAL RULE:

There are three types of Orbital Ground Support. These are Orbital Bombardment, Orbital Laser Barrage, and Orbital Opacity Bombs.

CASES:

[20.1] ORBITAL BOMBARDMENT

Orbital Bombardment is plotted during the Plot Phase and explodes during the Detonation Segment just as LW. It is resolved on the Standard Game LW Combat Table (26.2). The amount of Orbital Ground Support varies from scenario to scenario.

[20.11] Orbital Bombardment is plotted to impact in a given hex. The plotting Player always rolls for Scatter for Orbital Bombardment, utilizing the "-4" column of the Scatter Table (10.4) and doubling the number of hexes of any scatter result obtained.

[20.12] Orbital Bombardment detonation results in a Blast Radius precisely the same as that for a Guided Positron Bomb (see 10.3), except that the strength of the explosion is triply powerful such that any Soldiers in the hex of impact are attacked at ninety, and Soldiers one hex away at thirty, and any two hexes away at 15.

[20.13] "Range" and CM allocations have no effect on Orbital Bombardment.

[20.14] An Orbital Bombardment detonation results in the formation of craters in any hexes in which an attack strength of thirty or greater obtains. A Crater Marker is placed in any affected hexes. Exceptions: Craters are never formed in mountain, lake, urban, (or crater) hexes.

[20.2] ORBITAL LASER BARRAGE

Orbital Laser Barrage is simply a form of especially potent Direct Fire. In all respects it is treated so, except that the Range Attenuation Total is always zero (see 9.62), and the Attack Strength of an Orbital Laser Barrage is always twenty-four.

[20.3] ORBITAL OPACITY BOMBS

Orbital Opacity Bombs are plotted during the Plot Phase and deployed on the map during the Detonation Segment, as with LW. Invert the Opacity Bomb Markers in the plotted hex of impact to obtain a "smoke" counter.

[20.31] Orbital Opacity Bombs are plotted to impact in a given hex. The plotting Player always rolls for Scatter for Orbital Opacity Bombs, utilizing the "-2" column of the Scatter Table (10.4).

[20.32] Orbital Opacity Bombs add six to the Terrain Value of the hex in which they detonate for movement and combat purposes.

[20.33] Any Soldiers in a hex in which an Opacity Bomb detonates are Stunned. Soldiers subsequently moving into a hex containing a smoke counter are not affected.

[20.34] The effects of the detonation of an Opacity Bomb may disperse. Prior to the first Plot Phase of each Game-Turn, a die is rolled for every Opacity Bomb that has been detonated and has not dispersed, by the Player who caused it to be detonated. Rolls of "one" or "two" result in dispersal; the "smoke" counter is removed from the board.

[21.0] SUPPORT PLATFORMS

GENERAL RULE:

Support Platforms are manned heavy vehicles with the capacity to assist Friendly Soldiers in the performance of military tasks. Support Platforms behave in a manner similar to individual Soldiers, with several exceptional advantages and restrictions. There are Human, L'Chal Dah, and Rame Support Platforms; each type has a TPA, Efficiency Rating and Repair Rate equal to the regular values for a StarSoldier of that species (see 6.42). The TPA of Support Platforms must be kept track of on the Task Point Level Track.

[21.1] MOVEMENT OF SUPPORT PLATFORMS

Support Platforms are perpetually at High Altitude in Airborne Mode (no High Altitude Marker is necessary to indicate this). Support Platforms may be plotted to move as is done with Soldiers; since they are at High Altitude, it costs them ½ Task Point per hex to move.

[21.2] OFFENSIVE ABILITIES OF SUPPORT PLATFORMS

[21.21] Support Platforms have all the offensive abilities of a regular StarSoldier, and are plotted to allocate Task Points between such tasks as Direct and Opportunity Fire, launching Guided Positron Bombs, Free Flight Missiles, and so forth, movement, and Counter-Measure activity up to the limit of their Task Point Allowances.

[21.22] Support Platforms have an additional weapons system, the Laser Cannon. The Laser Cannon may fire up to once per Stage. The firing of the Laser Cannon must be plotted; however, firing the Laser Cannon expends zero Task Points. A Support Platform that had expended its entire TPA in the Initial Stage of a Game-Turn could still fire the Laser Cannon in the Second Stage. Laser Cannon fire is a form of Direct Fire and is resolved on the Standard Game Fire CRT (26.1).

[21.23] The Laser Cannon fires with an Attack Strength of 24.

[21.24] Instead of firing, a Laser Cannon may be plotted to spend a Stage "registering" on a particular hex. A Registration Marker is placed in that hex. In any subsequent Stage, that Laser Cannon may fire at any target in the hex and in resolving that Fire Combat, any Enemy CM in the hex is ignored.

[21.25] Each Laser Cannon may be simultaneously "registered" on up to two hexes at any one time. If a Support Platform's Cannon that is already registered on two hexes registers on a third, it must surrender registration on one of the original two.

[21.3] SUPPORT PLATFORMS ON DEFENSE

[21.31] A Support Platform always defends as if it were in a hex at Nap of Earth with a Terrain Value of ten. The detonation of any LW (at High Altitude) in a hex containing a Support Platform is always resolved as an odds reduction of the Attack Strength of the LW compared to "ten" when determining the effect on the Support Platform. Similarly, when computing the Defense Strength of a Support Platform against any Fire Combat, the Terrain Value is always considered to be "ten." Note that as Support Platforms are at High Altitude, their Efficiency Rating is halved when computing the CM total (exception: see 23.2).

[21.32] Attacks against Support Platforms are resolved on the Standard Game LW and/or Fire Combat Tables as appropriate. However, Support Platforms do not have their TPA's reduced by the requisite number of Task Points as listed there.

Instead, if the listed result calls for the loss of six or more Task Points, Players refer to the Support Platform Damage Table (21.5). If the listed result calls for the loss of five or fewer Task Points (including a "Stun" Result) it is ignored.

[21.33] If an attack against a Support Platform calls for a loss of more than six Task Points, the corresponding roll on the Support Platform Damage Table is increased (over the actual total of the dice) by the difference between six and the result obtained from the attack. So if the original result called for the loss of eight Task Points, the roll on the Support Platform Damage Table would be increased by two. Adjusted results greater than "twelve" are treated as "twelve."

[21.4] EFFECTS ON PRESERVATION

The addition of a Support Platform to the Order of Battle of a side adds to that side's Preservation Level (see 25.0 for standard Preservation Levels). Human Platforms add three to the Preservation Level (each); L'Chal Dah Platforms add four; Rame Platforms add four also.

[21.5] SUPPORT PLATFORM DAMAGE TABLE

(see center pages)

[22.0] ANDROIDS

[22.1] RESTRICTIONS ON ANDROIDS

There are Human, L'Chal Dah, and Rame Androids. Each has a TPA and an Efficiency Rating equal to the regular values for a StarSoldier of that species. Except as noted below, Androids behave in all respects precisely as regular StarSoldiers.

[22.12] Androids may never repair; they have a Recovery Rate of "zero".

[22.13] An Android may never be designated as a Leader in any battle where that side has at least one organic StarSoldier present.

[22.14] Rame Androids may not form "Killer Swarms" (i.e., ignore Rule 23.1).

[23.0] THE RAME

GENERAL RULE:

Unlike the Humans and L'Chal Dah, the Rame are a non-humanoid species. The Rame possess a "joint mind" and have no concept of individual identity. The outlines of their bionic-based technology has vague similarities to that of the other species, but there are enough significant differences, that when combined with the physiological contrasts result in a particularly distinctive style of tactical combat.

[23.1] RAME KILLER SWARMS

[23.11] Whenever two or more individual Rame occupy a single hex at the same altitude, any CM produced by any of those Rame apply for defense against Fire Combat for all. Should more than one Rame put up CM, the combined total applies for all against any Fire Combat. (Exception to 9.35.)

[23.12] Whenever precisely three Rame occupy a single hex at the same altitude, they may pool Task Points allocated to Direct Fire into one attack. To accomplish this, each Soldier must be plotted to expend precisely the same number of Task Points on a Direct Fire task against one particular hex.

[23.2] EFFICIENCY RATING

The Efficiency Rating of Rame plotted to spend some portion of a particular Stage in Airborne Mode is not halved when computing the CM value. Rather, the Efficiency Rating of Rame plotted to spend any portion of a particular Stage in Ground Mode is halved when determining the CM value. This is the opposite of the way it works with Human and L'Chal Dah Soldiers, and is an exception to Case 8.23.

[23.3] COMMAND COMMUNICATIONS

Rame are always in Command Communications; there are no Rame "Leaders."

[24.0] XENOPHOBES

[24.1] RESTRICTIONS ON XENOPHOBES

Xenophobes move and utilize Fire Combat as regular StarSoldiers. They may not utilize any LW other than Neutron Bombs. They may not use Homing Missiles.

[24.2] EFFECTS OF NEUTRON BOMBS

Neutron Bombs behave as Guided Positron Bombs so far as launch and scatter are concerned, except that on the Scatter Table (10.4) the roll is always made one column to the right (worse) than it would be for a GPB.

[24.21] Neutron Bombs may be plotted to detonate either at High Altitude or Nap of Earth. When detonated at Nap of Earth, they always create Craters, regardless of the terrain in the hex. Any Soldier, Android, or Support Platform in the same hex as a Neutron Bomb which detonates is vaporized (removed from the game; killed) if at the same Altitude Level. Soldiers and Androids in the same hex but at the other Altitude Level are stunned; Support Platforms in a hex in which a Neutron Bomb at ground level detonates are not affected.

Preservation Levels and the presence of Civilians are always ignored in scenarios involving the Xenophobes; both sides consider it a fight to the death.

[25.0] UNIT ORGANIZATIONS

The Unit Organization Chart illustrates the way in which the Humans, L'Chal Dah, and the Rame construct their tactical formations.

[25.1] UNIT ORGANIZATION CHART

(see page 20)

[25.2] EXPLANATION OF UNIT ORGANIZATION

The numbers listed are the number of Soldiers that make up the composition of the unit. Leaders are in all cases identical to regular StarSoldiers, except as noted in the Command Communications Rule (16.0). The Preservation Levels listed are the standard values for each unit. They are additive in instances where a combination of different units are on one side. (See Rule 17.0, Preservation Level).

[26.0] COMBAT RESULTS TABLE

(see center pages)

[26.1] STANDARD GAME FIRE COMBAT CRT

[26.2] STANDARD GAME LW CRT

[27.0] GENERAL GAME SITUATIONS

And their use in creating scenarios.

The Standard Game is composed of scenarios. These scenarios are drawn from the interstellar conflicts occurring between the years 2400 and 2785 as described in the Scenario Background and Order of Battle Sections (28.0 to 29.0). Most of the scenarios are composed by the Players themselves. This is done by combining a General Situation with a specific Order of Battle.

There are three General Situations into which most of the tactical combat simulated in StarSoldier can be classified. These are the patrol, reconnaissance, and assault situations. They are described in this Section.

There are twelve different Orders of Battle sets taken from a variety of conflicts. These are Sections 28.0-39.0. The specific Orders of Battle may be combined with the General Situations to create three dozen game set-ups.

[27.1] PATROL SITUATION

25th Century-style ground combat features mobile, extremely independent troops and highly sophisticated data-gathering and data-dispersing systems. Given that, the classic territorial-oriented 20th Century infantry patrol activity will be unheard of, based as it is on the concept of a "front." There will be no "front" when individual soldiers, with only intermittent and minimal logistical dependency, can transport themselves at speeds in excess of 4000 km/hour.

Nevertheless, relatively immobile ground bases will be present. These bases will perform a multitude of functions: shield selected key civilian personnel from the effects of the invader-induced Heissen Field, provide repair and equipment stations for StarSoldiers in the field, perform tracking functions, provide planetary defense against the Invaders' orbiting Teleships (or against the defender's orbiting satellites), and so forth. To some extent, the bases will be concealable from off-world detection, so long as energy emissions are effectively shielded. Actual surface searches will be necessary to pin down the locations. Much of the ground combat will center around the search for, protection and defense of and assaults against these bases. The Patrol Situation represents an outer-perimeter defense of such a base pitted against a probing search/patrol. The probing force will hereinafter be referred to as the "Alpha Force," the defending force as the "Bravo Force."

Depending on such factors as the size and purpose of the base and the availability of orbital intelligence info, the Alpha Force will have a more or less vague knowledge of the location of the base. The purpose of the patrol will be to determine the location within a specific sector of the planet's surface.

In the Patrol Situation, the base itself is either off the East or West edge of the map. The Bravo Force is deployed on the map; the Alpha Force enters from the edge opposite the base and attempts to exit as many men as possible off the edge closest to the base.

[27.11] Set-Up

The Players determine which one will control the Alpha Force and which the Bravo Force. An Order of Battle is selected from among those listed in the Scenario Sections (28.0 to 39.0). It is determined in a random fashion which edge (East or West) of the map the Bravo Force's base is considered to be off of. Each Player plots all Initial Stage activity, with the Bravo Player's forces entering the map from the edge which the base is located off and the Alpha Player's forces entering from the other side. The first Game-Turn then proceeds according to the Sequence of Play.

[27.12] Game Length

The game proceeds an indeterminate number of Game-Turns, until the Alpha Player has no live troops left on the map (including Androids and Support Platforms).

[27.13] How Victory is Determined

At the end of the game, the Player with the most points is the winner. Points are awarded as follows:

  • Alpha receives 2 points for every Task Point loss recorded on the Bravo Preservation Level Track.
  • Alpha receives 10 points for every StarSoldier and/or Android exited off the opposite side of the map from the one entered.
  • Bravo receives 3 points for every Task Point loss recorded on the Alpha Preservation Level Track.

The greater the margin of difference in points between the Players, the greater the margin of victory:

Victory Point MarginVictory Level
12 or lessMarginal
13 to 25Substantial
26 and upDecisive

For example, if Alpha had 54 points and Bravo had 67, then Bravo would win a Victory.

[27.14] Alpha Forces may enter the map in any Mode (except for Support Platforms, if any, which must be at High Altitude), and in the Stage they enter the map, may be plotted to expend Task Points on movement and CM only.

[27.15] In some scenarios, one or both Players may receive reinforcements. The restrictions outlined in Case 27.14 apply to any reinforcements in the Stage in which they enter the map.

[27.2] RECON SITUATION

The question at issue in this situation is the location of a surface installation/base. One force ("Alpha") is attempting to determine the exact location of the base, which is known to be in the vicinity, in preparation for an assault. The other force ("Bravo") is attempting to prevent the discovery of the base.

In the Recon Situation, the Bravo Player deploys all forces, including the Base, on the map. The Alpha Player's forces enter the map and attempt to locate the Base.

[27.21] Set-Up

The Players determine who will control each Force and choose an Order of Battle. The Bravo Player deploys all initial forces secretly, noting the hex locations on a sheet of paper only; except for any Support Platforms, which must be openly deployed on the map. These "initial forces" include at least one Base, which is also deployed secretly. Meanwhile, the Alpha Force Player plots all Initial Stage activity, as does the Bravo Player. The first Game-Turn then proceeds according to the Sequence of Play.

[27.22] Game Length

The game continues until the Alpha Player discovers the location of the Base or Bases, or until no live Alpha Force StarSoldiers or Androids remain on the map.

[27.23] How Victory is Determined

The Alpha Player wins if the location(s) of (all) the Base(s) on the map is (are) discovered. If he fails, the Bravo Player wins. If more than one Base is present, all must be discovered for the Alpha Player to fulfill the condition of victory.

[27.24] All Bravo forces, with the exception of Support Platforms, if any, are deployed in secret at the beginning of the game. The Bravo Player has the option of keeping the location of any Soldiers or Androids secret indefinitely, so long as they are a) deployed in Ground Mode and b) expend no Task Points whatsoever. At the end of the first Plot Phase in which any Bravo Force Soldier is plotted to expend any Task Points, that Soldier is placed on the map. Soldiers with "secret" locations are subject to the effects of an explosive weapon detonating in such a manner as to place them within its Blast Radius.

[27.25] Alpha Forces enter the map in the first Game-Turn, and any reinforcements for either side enter the map when called for, in accord with the restrictions listed in Case 27.14.

[27.26] Each Base has a TPA of six and an Efficiency Rating equal to that of the Bravo Force Species. The Base may perform any Task allowable to a regular StarSoldier of that species, except movement. For the purposes of determining damage, a Base is treated as if it were a Support Platform; use the Support Platform Damage Table (treating "Laser Cannon destroyed" results as "TPA ½ Reduced"). For multi-hex Bases, each hex is treated independently for all purposes. Hidden Bases may be damaged by the detonation of explosives.

[27.27] Bases remain hidden from the Alpha Player until a) they expend Task Points for any purpose (which normally would not occur in the Recon Situation) or b) an Alpha StarSoldier or an Android passes within four hexes of the hex the Base occupies while at NOE or in Ground Mode.

[27.28] If the Alpha Force should exceed its Preservation Level, the range for discovering a Base is reduced to two hexes beginning with the immediately subsequent Movement Phase.

[27.3] ASSAULT SITUATION

This situation concerns an attack on a pinpointed base. One Force ("Alpha") attempts to destroy the Base while the other ("Bravo") attempts to prevent that from occurring. There are two versions to the Assault Situation which have substantial differences in set-up; the significant factor is whether or not the Alpha Force is on the strategic offensive (the invading force) or the strategic defensive (defending the planet).

[27.31] Set-Up for Attack on Invader's Base

In this case, the Alpha Force is on the strategic defensive, attempting to drive off the invaders. The Players determine who will control each Force and choose an Order of Battle. The Bravo Player deploys secretly all forces, including the Base(s), and excluding any Support Platforms, which must be placed openly on the map. Both Players then plot all Initial Stage activity and the first Game-Turn proceeds in accordance with the Sequence of Play.

[27.32] Set-Up for Attack on Defender's Base

With the Alpha Force on the strategic offensive, the assault can be launched directly from orbiting TeleShips. The Bravo Force Player deploys as in Case 27.31. The Alpha Player simultaneously allocates (secretly) ten Orbital Bombardment Explosives and three Orbital Opacity Bombs (see 20.0) and plots the entry of his forces (see below). After the Bravo Player is finished deploying, the Alpha Player places the Orbital Ground Support paraphernalia on the map. The Bravo Player has the equivalent of one Stage to move any mobile forces, and any that move are revealed and placed on the map. The Alpha Player then rolls for scatter and the Bravo Player resolves any attacks against deployed forces, without revealing the location of or exact effect on any hidden forces. All Alpha Forces are now deployed on the map as plotted previously by the Alpha Player. They are deployed in whatever hex(es) the Alpha Player has plotted for them to appear in, at High Altitude. All Bravo Forces (with the exception of Bases) are also deployed openly on the map. Both Players then plot all Initial Stage activity and the first Game-Turn proceeds in accord with the Sequence of Play.

[27.33] Game Length

The game continues until all Bases on the map are destroyed or until no live Alpha Force Soldiers/Androids/Support Platforms remain on the map.

[27.34] How Victory is Determined

The Alpha Player wins if, by the end of the game, all Bases on the map are destroyed. Otherwise, the Bravo Player wins.

[27.35] Any Alpha reinforcements that may be called for enter the map as the original Alpha Forces did (see Case 27.32). Any Bravo reinforcements enter the map as described in Case 27.15.

[27.36] Bases are treated as in Cases 27.26 and 27.27, with the addition that if a Base hex is destroyed, it is revealed.

[28.0] THE EPSILON ERIDANI CAMPAIGN/SKIRMISHES ON EPSILON INDI, 2405 AD

[28.1] BACKGROUND INFORMATION

Sol had colonized three star systems. One of them, Epsilon Eridani, made a move to split from the Solar Hegemony. Forces from Epsilon Eridani attempted to seize a newly accessible habitable system, Epsilon Indi. Solar Hegemony troops, lacking any support from a StarGate (there wasn't one) or StarForces (none were present) attempted to hold out on Epsilon Indi I.

[28.2] ORDERS OF BATTLE

Patrol Situation (only)

  • Solar Hegemony (use Human counters) as Alpha or Bravo Force—one Squad (PL = 54)
  • Epsilon Eridane (use L'Chal Dah counters) as Alpha Force—one Squad plus one HW Section (PL = 63)
  • Epsilon Eridane (use L'Chal Dah counters) as Bravo Force—one Fire Team plus one HW Section (PL = 32)

[28.3] SPECIAL RULES

[28.31] Treat all urban hexes as organic cover hexes.

[28.32] The Epsilon Eridani Player (as either Alpha or Bravo) may utilize Orbital Ground Support. Up to four Orbital Bombardment Explosives, two Orbital Laser Barrages, and two Orbital Opacity Bombs may be plotted/utilized per Game-Turn.

[28.33] Neither side may employ Homing Missiles.

[29.0] RISE OF THE HUMAN LEAGUE/BATTLES ON EPSILON INDI, 2415 AD

[29.1] BACKGROUND INFORMATION

The success of the Epsilon Eridani defiance in 2405 spelled the end for the Solar Hegemony, and a new Pan-Human Hegemony supplanted the older order. However, the PHH was still Sol-oriented, and a more radically frontier oriented society, the Human League, arose and challenged the PHH by the time-honored tactic of seizing Epsilon Indi (which had begun to be developed, but still lacked a genuine indigenous population and a StarGate of its own). PHH forces attempted to regain control of the system and full scale fighting broke out on the planet after the guarding HL StarForce was defeated.

[29.2] ORDERS OF BATTLE

Patrol Situation

  • PHH (use Human counters)
    • as Alpha Force—one FireTeam and one HV Section (PL = 32)
    • as Bravo Force—one FireTeam (PL = 23)
  • HL (use L'Chal Dah counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 FT and 1 HV Section (PL = 32).

Recon Situation

  • PHH (use Human counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 FT (PL = 23), 2 Base hexes
  • HL (use L'Chal Dah counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 FT and 1 HV Section (PL = 32), 1 Base hex

Assault Situation

  • PHH (use Human counters)
    • as Alpha Force—1 Squad and 1 HV Section (PL = 63)
    • as Bravo Force—1 FT and one HV Section (PL = 32), 2 Base hexes
  • HL (use L'Chal Dah counters)
    • as Alpha Force—1 Squad and 1 HV Section (PL = 63)
    • as Bravo Force—1 Squad (PL = 54), 1 Base hex.

[29.3] SPECIAL RULES

[29.31] Treat all urban hexes as clear terrain.

[29.32] The PHH Player may utilize Orbital Ground Support in any Scenario. Up to two Orbital Bombardment Explosives, one Laser Barrage, and one Orbital Opacity Bomb may be utilized per Game-Turn.

[29.33] The PHH Player (only) may use Homing Missiles. They may only be used as mines (see 19.0), and only in Scenarios where the PHH Player is the Bravo Force. Up to two may be deployed in the Patrol Situation, three in the Recon Situation, and four in the Assault Situation.

[30.0] PHH-HL SHOWDOWN/ATTACK ON TAU CETI, 2430 AD

[30.1] BACKGROUND INFORMATION

The antagonism between the PHH and the HL grew worse, in the wake of the latter's successful establishment in 2415. Essentially, the PHH wanted centralization on Sol and expansion limited to already-inhabited planets. The HL desired more independence from the Home System and the terraforming of systems not naturally habitable. When the struggle erupted into open fighting in 2430, the PHH forces attempted to carry the war home to the HL, and mounted an attack on Tau Ceti, the largest (in population) of the HL systems.

[30.2] ORDERS OF BATTLE

Use the same Orders of Battle as are listed for the "Battles on Epsilon Indi" Scenario (see 29.2).

[30.3] SPECIAL RULES

[30.31] Prior to the start of the game, and starting with the Bravo Player, each Player places alternately one Civilian Marker in an urban hex. No Civilian Marker may be placed in the same hex or in a hex adjacent to the hex in which another Civilian Marker has already been placed. Six Civilian Markers are placed on the map.

[30.32] Civilians are considered to be "in Ground Mode." They may be affected by any Fire Combat (excepting Restricted Fire that is not aimed at them) that is directed into that hex unless the Fire is directed at a target at High Altitude. Civilians may also be affected by any explosive weapons which detonate in such a manner as to encompass the hex they occupy in the Blast Radius. Civilian Markers are attacked as normal Soldiers on the appropriate Combat Results Table; any result calling for a loss of Task Points is considered to cause that many "points" worth of Civilian casualties ("Civilian Casualty Points," or CCP's).

[30.33] The number of CCP's caused by each combat is kept track of and "credited" to the account of the Player whose weapon caused them. At the end of the Game, if one Player has more than five more CCP's accumulated than the other, the first Player automatically forfeits the game, regardless of any other considerations.

[30.34] Civilian Markers are never destroyed. Each Civilian Marker may produce an unlimited number of CCP's.

[30.35] The PHH Player may utilize Orbital Ground Support in any Scenario, in accordance with the conditions outlined in Case 29.32.

[30.36] Either Player may utilize Homing Missiles. They may be utilized whether as mines or as LW. Only the Bravo Force Player in a given Scenario may utilize them as mines, however, with a limit of two in the Patrol Situation, four in the Recon Situation, and six in the Assault Situation.

[31.0] L'CHAL DAH CONTACT, 2451 AD

[31.1] BACKGROUND INFORMATION

See 13.1 for background information.

[31.2] SET-UP

Patrol Situation (only)

  • PHH (use Human counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 FT and 1 HV Section (PL = 32), plus two Homing Missiles deployed as mines.
  • L'Chal Dah
    • as Alpha Force—1 Squad (PL = 50)
    • as Bravo Force—1 FT and 1 HV Section (PL = 36).

[31.3] SPECIAL RULES

[31.31] Six Civilian counters are deployed prior to the Game start as described in Case 30.31. They are treated as explained in Cases 30.32, 30.33, and 30.34.

[31.32] The PHH Player (only) may utilize Homing Missiles.

[32.0] SECOND PHH-HL WAR, 2462 AD

[32.1] BACKGROUND INFORMATION

Although the Human League had been defeated in 2430 AD, the basic cause of the conflict had yet to be resolved. Both sides strengthened themselves as much as possible, and tightened control over other systems. Hostilities broke out again in 2462, but it was a brief and inconsequential struggle. The HL did mount one expedition to Alpha Centauri and succeed in gaining control of local space long enough to land troops on Lauren, but they were swiftly repulsed.

[32.2] SET-UP

Patrol Situation

  • PHH (use Human Counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 FT and 2 HV Sections (PL = 41), plus two Homing Missile mines.
  • HL (use LCD counters)
    • as Alpha Force—1 FT and 1 HV Section (PL = 32)
    • as Bravo Force—1 FT and 1 HV Section (PL = 32), plus two Homing Missile "mines."

Recon Situation

  • PHH (use Human counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 FT and 1 HV Section (PL=32), plus three Homing Missile mines, 3 Base hexes.

Assault Situation

  • PHH (use Human counters)
    • as Alpha Force—1 Squad and 1 HV Section (PL=63)
    • as Bravo Force—same plus four Homing Missile mines, 1 base hex
  • HL (use LCD counters)
    • as Alpha Force—1 Squad plus one HV Section (PL=63)
    • as Bravo Force—1 Squad (PL=54) plus four Homing Missile mines. One 3 hex base (must be contiguous).

[32.3] SPECIAL RULES

[32.31] Seven Civilian Markers are deployed prior to the Game's start as described in Case 30.31. They are treated as explained in Cases 30.32, 30.33, and 30.34.

[32.32] Both Players may utilize Homing Missiles.

[32.33] The HL Player (only) may utilize Orbital Ground Support as outlined in Case 29.32.

[33.0] REVOLT OF EPSILON-INDI, 2465 AD

[33.1] BACKGROUND INFORMATION

Soon after the PHH-HL War of 2462 AD, which had ended with an indecisive Pan-Human Hegemony victory, Epsilon Indi revolted against PHH control. Most of the old HL members rallied to support the newest insurgent, while the L'Chal Dah remained neutral, intervening on the side of the PHH only when victory became apparent.

[33.2] SET-UP

Patrol Situation

PHH vs. HL [Choose either PHH or LCD vs. HL]

  • PHH (use LCD counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 FT and 2 HV Sections (PL = 41), plus 2 Homing Missile mines.
  • LCD
    • as Alpha Force—1 FT and 1 AD (PL = 50)
    • as Bravo Force—1 FT and 1 AD (PL = 50), plus two Homing Missile mines.
  • HL (use Human counters)
    • as Alpha Force—2 FT (PL = 46)
    • as Bravo Force—2 FT (PL = 46), plus two Homing Missile mines.

Recon Situation (Choose either PHH or LCD vs. HL)

  • PHH (use LCD counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—1 Squad (PL = 54), plus three Homing Missile mines, 2 Base hexes.
  • LCD
    • as Alpha Force—2 FT and 1 AD (PL = 68)
    • as Bravo Force—1 FT and 1 AD (PL = 50), plus three Homing Missile mines, 2 Base hexes.
  • HL (use Human counters)
    • as Alpha Force—1 Squad (PL = 54)
    • as Bravo Force—2 FT (PL=46), plus three Homing Missile mines, 2 Base hexes.

Assault Situation (Choose either PHH or LCD vs. HL.)

  • PHH (use LCD counters)
    • as Alpha Force—1 Squad and 1 HV Section (PL = 63)
    • as Bravo Force—1 Squad (PL = 54), plus four Homing Missile mines, 2 Base hexes.
  • LCD
    • as Alpha Force—1 Squad and 1 AD (PL = 82)
    • as Bravo Force—1 Squad (PL = 50), plus four Homing Missile mines, 2 Base hexes.
  • HL (use Human counters)
    • Same as PHH.

[33.3] SPECIAL RULES

[33.31] Four Civilian Markers are deployed prior to the Game start as described in case 30.31. They are treated as explained in Cases 30.32, 30.33, and 30.34.

[33.32] Both Players may utilize Homing Missiles.

[33.33] The Player controlling the PHH or LCD forces may utilize Orbital Ground Support as outlined in Case 28.32.

[34.0] WAR WITH THE RAME, 2476 AD

[34.1] BACKGROUND INFORMATION

After the absorption of the L'Chal Dah into the PHH on an Associate basis, the combined leagues made contact with yet a third, more alien species, the Rame, originating from 70 Ophiuchi. After some years of relatively peaceful contact, the PHH attempted to subjugate the Rame. Despite an evident lack of experience, the Rame acquitted themselves well in tactical combat, where the "community mind" was a distinct asset.

[34.2] SET-UP

Patrol Situation (only)

  • Rame
    • as Alpha Force or Bravo Force—1 Killer Swarm (SW) (PL = 13)
  • PHH
    • as Alpha Force—1 FT and 1 HV Section (PL = 32)
    • as Bravo Force—1 FT (PL = 23), plus two Homing Missile mines.
  • LCD
    • as Alpha Force—1 FT and 1 AD (PL = 50)
    • as Bravo Force—1 AD (PL = 32), plus two Homing Missile mines.

[34.3] SPECIAL RULES

[34.31] The PHH and LCD (only) may utilize Homing Missiles.

[34.32] Three Civilian Markers are deployed according to the procedure described in Case 30.31. They are treated as outlined in Cases 30.32, 30.33, and 30.34.

[35.0] L'CHAL DAH EXPANSION, 2480 AD

[35.1] BACKGROUND INFORMATION

The L'Chal Dah continued their new policy (which had been instituted in 2465) of expansion and activity in stellar politics by attempting to strengthen their power base at the expense of the Rame. They discovered that the Rame had adjusted quickly to the need for military prowess on the ground.

[35.2] SET-UP

Patrol Situation

  • LCD
    • as Alpha Force—1 FT and 1 AD (PL = 50)
    • as Bravo Force—1 AD (PL = 32), plus two Homing Missiles (as mines)
  • Rame
    • as Alpha Force—1 SW and 1 AD (PL = 30)
    • as Bravo Force—1 SW (PL = 13), plus two Homing Missile Mines.

Recon Situation

  • LCD
    • as Alpha Force—1 FT and 2 AD (PL = 82)
    • as Bravo Force—2 AD (PL = 64), plus three Homing Missile mines, 1 Base hex
  • Rame
    • as Alpha Force—1 Squad (PL = 26)
    • as Bravo Force—1 SW and 1 AD (PL = 30), plus three Homing Missiles, 3 Base hexes

Assault Situation

  • LCD
    • as Alpha Force—1 Squad and 1 AD (PL = 82)
    • as Bravo Force—1 FT and 2 AD (PL=82) plus four Homing Missile mines, 1 Base hex
  • Rame
    • as Alpha Force—2 Squads (PL = 52)
    • as Bravo Force—1 Squad (PL = 26), plus four Homing Missile mines, 3 Base hexes.

[35.3] SPECIAL RULES

[35.31] Three Civilian Markers are deployed according to the procedure described in Case 30.31. They are treated as outlined in Cases 30.32, 30.33, and 30.34.

[35.32] The LCD Player may utilize Orbital Ground Support as outlined in Case 29.32.

[35.33] Both Players may utilize Homing Missiles.

[36.0] WAR OF THE DEFENSE LEAGUE, 2482 AD

[36.1] BACKGROUND INFORMATION

After the L'Chal Dah defeated the Rame in 2480 AD, the two formed the L'Chal Dah-dominated Defense League. Renouncing their associate status in the PHH, the L'Chal Dah attempted to free themselves from Human interference, with the ultimate goal of defeating the Humans entirely. The Rame were more or less unenthusiastic partners in this venture (due more to bad feelings vis a vis the L'Chal Dah than any love of Humanity) and refused to commit troops to the attempt to subjugate PHH planets.

[36.2] SET-UP

Patrol Situation

  • LCD
    • as Alpha Force—1 FT, 1 HV Section, and 1 AD (PL = 68)
    • as Bravo Force—1 FT and 1 AD (PL = 50), plus two Homing Missile mines.
  • PHH
    • as Alpha Force—1 FT, 1 HV, and 1 AD (PL = 56)
    • as Bravo Force—1 FT and 1 AD (PL = 47), plus two Homing Missile Mines.

Recon Situation

  • LCD
    • as Alpha Force—1 HW Section and 2 AD (PL = 82)
    • as Bravo Force—1 FT and 2 AD (PL = 82), plus four Homing Missile mines, 1 Base hex
  • PHH
    • as Alpha Force—2 FT and 1 HV Section (PL = 55)
    • as Bravo Force—1 Squad (PL = 54), plus four Homing Missile mines, 2 Base hexes

Assault Situation

  • LCD
    • as Alpha Force—1 Squad and 1 AD (PL = 82)
    • as Bravo Force—1 Squad and 1 AD (PL = 82), plus six Homing Missile mines, and 1 Base hex.
  • PHH
    • as Alpha Force—1 Squad (PL = 60), plus two Support Platforms
    • as Bravo Force—1 Squad (PL = 60), six Homing Missile mines, 1 Base hex.

[36.3] SPECIAL RULES

[36.31] Six Civilian Markers are deployed according to the procedure outlined in Case 30.31. They are treated as outlined in Cases 30.32, 30.33, and 30.34.

[36.32] The LCD Player may utilize Orbital Ground Support as outlined in Case 29.32.

[36.33] Both Players may utilize Homing Missiles.

[37.0] WAR FOR IDENTITY, 2487 AD

[37.1] BACKGROUND INFORMATION

After several years, the PHH, despite the victory of 2482, collapsed. Three factions emerged: the Pan-Sentient League (advocating complete freedom for all biologic and cybernetic sentients); the shrunken Human League; and the resurgent Sol-based PHH rump.

[37.2] SET-UP

Orders of Battle for all three factions are given below. All sides fought both offensively and defensively in this war.

Patrol Situation

  • Pan Sentient League (LCD and Rame)
    • LCD (same as 36.2)
    • Rame
      • as Alpha Force—1 SW and 1 AD (PL = 30)
      • as Bravo Force—1 SW and 1 AD (PL = 30), plus two Homing Missile mines.
  • PHH
    • as Alpha Force—1 FT, 1 HW Section, and 1 Support Platform (PL = 35)
    • as Bravo Force—1 FT and 1 AD (PL=47), plus two Homing Missile mines.
  • HL (use LCD counters if deployed against PHH)
    • as Alpha Force (same as PHH)
    • as Bravo Force—(same as PHH)

Recon Situation

  • LCD
    • as Alpha Force—1 Squad, 1 AD, and 1 Support Platform (PL = 86)
    • as Bravo Force—1 FT, 2 AD (PL = 82), plus four Homing Missile mines, 1 Base hex.
  • Rame
    • as Alpha Force—1 Squad and 1 AD (PL = 42)
    • as Bravo Force—1 Squad (PL = 26), plus four Homing Missile mines, 3 Base hexes
  • PHH
    • as Alpha Force—1 Squad plus 2 Support Platforms (PL = 60)
    • as Bravo Force—1 FT, 1 HW Section, and 1 Support Platform (PL = 35), plus two Base hexes.
  • HL
    • (same as PHH)

Assault Situation

  • LCD
    • as Alpha Force—1 Squad, 1 HW Section, and 2 Support Platforms (PL = 76)
    • as Bravo Force—1 Squad, 1 AD, and 1 Support Platform (PL = 86), plus 1 Base hex.
    • Rame
      • as Alpha Force—1 Squad, 1 AD, 2 Support Platforms (PL = 46)
      • as Bravo Force—1 Squad, 1 AD (PL = 42), plus 2 Base hexes (contiguous)
  • PHH
    • as Alpha Force—(same as Recon Situation)
    • as Bravo Force—1 FT, 1 HW Section, 1 AD, 1 Support Platform (PL = 59), plus 2 Base hexes
  • HL
    • (same as PHH)

[37.3] SPECIAL RULES

[37.31] If the action is taking place on a PHH world, deploy seven Civilian Markers; on a HL world, deploy five Civilian Markers, on an LCD world, deploy six counters, on a Rame world deploy three counters.

[37.32] If the action is taking place on a PHH or LCD world, the attacker gets Orbital Ground Support on the order of that listed in Case 29.32. If the action takes place on any other planet the attacker gets the benefits as described in Case 28.32.

[37.33] All sides may employ Homing Missiles.

[38.0] DEFEAT OF THE XENOPHOBES, 2785 AD

[38.1] BACKGROUND INFORMATION

See Section 24.0 for background.

[38.2] SET-UP

The Xenophobe Scenarios do not use the General Situations. Rather, there are three separate Xenophobe Scenarios, pitting 12 Xenophobe StarSoldiers (the Xenophobe military organization is not known) against Humans, L'Chal Dah, or Rame (choose one).

  • Xenophobes—12 StarSoldiers
  • Humans (vs. Xenophobes)—1 Squad
  • L'Chal Dah (vs. Xenophobes)—1 Squad
  • Rame (vs. Xenophobes)—1 Squad.

[38.3] SPECIAL RULES

[38.31] Civilian counters are not deployed in the Xenophobe scenarios.

[38.32] Humans, L'Chal Dah, or Rame receive Orbital Ground Support, as outlined in Case 28.32.

[38.33] There are no Preservation Levels for either side. Both accept it as a struggle to the last "man." The first Player to eliminate all Enemy StarSoldiers is victorious.

[39.0] PROTECTING SETTLERS FROM THE LOCAL FAUNA

[39.1] SET-UP

The Human Player deploys ten Civilian Counters in city hexes on the map. No Civilian Counter may be within six hexes of another. The Human Player also deploys three StarSoldiers. After the Human Player has set up, the Dinkblog Player plots his move for the first Stage (which will be to teleport somewhere onto the map). At the same time, the Human Player plots the moves of his StarSoldiers. The Initial Stage of the first turn then proceeds according to the Sequence of Play.

[39.2] SPECIAL RULES

[39.21] Civilians are treated as in Cases 30.32, 30.33, and 30.34.

[39.32] The Dinkblog moves directly by teleportation from hex to hex. It has no TPA, and automatically attacks with a strength of thirty on the LW CRT (26.2), regardless of terrain, any Human in its hex (including StarSoldiers) at any altitude. It may move once per Stage, with no restrictions on range whatsoever.

[39.23] The Dinkblog is always considered to be in Ground Mode and defends with the terrain value of the hex occupied. For all purposes of undergoing attacks, the Dinkblog is considered to be a Support Platform (see 21.0). Any combat result on the Support Platform Damage Table other than "Destroyed" is considered to "wound" the Dinkblog; a second "wound" kills it.

[39.24] Wounded Dinkblogs may move only once per Game-Turn.

[39.3] HOW TO WIN

If one Player accumulates in excess of one point more than the other, that Player wins the game. Any other result is a draw. The Human Player receives one point for driving the Dinkblog off the map, and either one point for wounding the Dinkblog or five points for killing it. The Dinkblog gets one point for each Civilian eaten (that is, any result other than "stun," which is ignored), and 2 points for each StarSoldier killed.

[40.0] OTHERWORLD ENVIRONMENTS

[40.1] PLANET SIZE

Since Fire Combat needs a "Line of Fire," it is not possible to employ it "over the horizon." Hence, the size of a planet is an important consideration. Earth, with a diameter of 12742 kilometers, has a horizon at sea level of about 20 KM. This limit rises rapidly as the observer gains altitude, so that only units firing from the ground (or, perhaps, NOE) would be affected—but they would be affected, such that the range at which one could fire would decrease as the size of the planet decreases.

[40.2] ATMOSPHERE

The density of the atmosphere also have an effect on Direct Fire. The range attenuation value of "one" for each ten hexes is predicated on an atmosphere roughly as dense as that on Earth. A Vacuum (such as in space) would have no range attenuation; a dense atmosphere would have a greater effect.

[40.3] BACKGROUND INTERFERENCE

That is, more or less, the amount of ambient radiation in the environment. Increases in this would decrease the range of Command Communication.

[40.4] GRAVITY

Gravity has very broad effects; so broad, in fact, that they are rather easily factored out. Generally, a planet with a high gravity would alter the game scale, with each hex representing a smaller area and each Game-Turn a longer period of time.

[40.5] ASSAULT ON ZULU STATION

A tremendous variety of environments are possible. Players are encouraged to experiment. For example, in 2482, in the course of beating back the L'Chal Dah bid for independence from the Pah-Human [as printed] Hegemony, Human StarSoldiers found it necessary to assault a cylindrical asteroid. After capturing the StarGate at 61 Cygni, it was necessary to secure the outer ring of debris which ringed the system to protect it from low velocity counter-assaults, which could have been staged from any one of several of the larger pieces of debris. One of the largest of these, a cylindrically-shaped hunk of rock dubbed "zulu" was defined by a FireTeam of L'Chal Dah.

[40.51] SET-UP

In order to visualize the following rule, pick up the map off of the table and bend the east and west edges back to the point where they touch—the map forms a cylinder. This is what the map will be representing, even as it lies flat on the table. Replace the map flat on the table and determine which Player will play which side. The L'Chal Dah Player deploys his FireTeam. The Human Player deploys his FireTeam at High Altitude (simulating an Orbital Assault). Players then proceed to plot the Initial Stage of the first Game-Turn.

[40.52] There is no range attenuation for Direct Fire, as there is no atmosphere.

[40.53] No LOF for Fire Combat may extend more than five hexes when traced between two points on the ground (or at NOE). No LOF for Fire Combat may extend more than ten hexes when traced from a point on the ground (or at NOE) to a point at High Altitude. No LOF for Fire Combat may extend more than twenty hexes when traced from one point at High Altitude to another such.

[40.54] Imagine that the Eastern and Western edges of the map are connected. Soldiers may move off the Eastern edge of the map and re-enter (at the corresponding North/South latitude) on the Western edge, and vice versa. Soldiers may shoot or launch grenades "over" the map edge.

[40.55] The Humans have a PL of 23; the LCD PL = 18. The first Player to force the other over the PL wins the game.

[41.0] THE LINK GAME

It is possible for Players owning a copy of SPI's StarForce game (which concerns the strategic interstellar situation on which StarSoldier is based) to "link" the two games together in a systematic fashion, such that the results of actions taken in one game influence the course of events in the other and vice versa.

GENERAL RULE:

The basic unit of ground combat troops for the purposes of the "Link Game" is the "Strike Command." The Order of Battle Chart (41.7) lists the number of Strike Commands available for each Scenario in StrikeForce. Each Strike Command represents some 100,000 individual StarSoldiers with concomitant supporting equipment, logistical cargo, and so forth. The Strike Command is the precise number of troops which can be most efficiently transported by one StarForce (four TeleShips). In cases where one side retains control of the planet(s) in a system without the benefit of the presence of a Friendly StarForce or StarGate (as defined in StarForce), the other side may attempt to gain control of the planet (and of the system) only by utilizing one or more Strike Commands to seize it bodily. Comparing the relative number of opposing Strike Commands gives one a "translation" into the tactical-scale StarSoldier game, which is used to determine the outcome of the battle for the planet.

PROCEDURE:

In any LiteZulu (as defined in StarForce) containing a system occupied by one or more Friendly Strike Commands but lacking a Friendly StarGate or other Friendly StarForces, and containing Enemy StarForce(s) which are transporting one or more Strike Commands, at the initiative of the Enemy Player, the Assault procedure may be initiated. For each Strike Command present in the LiteZulu, a Player receives ten Tactical Points. Each Player expends his Tactical Points to "purchase" a mix of forces from his available Strike Commands. Each Player then allocates his forces between three Scenarios that will be contested—one each of the three General Situations described in Section 27.0. The outcome of these scenarios is then translated back into results affecting all the Strike Commands present in the LiteZulu, and perhaps determining the outcome of the dispute for control of the planet.

[41.1] TRANSPORT OF STRIKE COMMANDS

[41.11] It takes one StarForce to transport each Strike Command. A StarForce may transport one Strike Command (only).

[41.12] It takes one entire Stellar Game-Turn to embark or disembark a Strike Command. Both the Strike Command and the StarForce involved must begin and end the Stellar Game-Turn in which the embarkation or disembarkation occurs in the same LiteZulu.

[41.13] A Strike Command may embark from or disembark to a Friendly system (including planets in it), to another Friendly StarForce, or to an Enemy controlled planet (this is considered to be an Assault, see 41.2).

[41.14] Embarkation or Disembarkation may not occur in a LiteZulu containing an unneutralized Enemy StarGate, or Enemy StarForce.

[41.15] The positions of Strike Commands on the Stellar Display are revealed to the opposing Player only to a limited extent. A Strike Command counter is placed on every system which contains at least one Strike Command. The exact number of Strike Commands garrisoning a given system is never revealed to the opposing Player until he enters the LiteZulu containing them. The fact that any StarForce or group of Strike Commands is transporting one or more Strike Commands is only revealed when opposing units are actually in the same LiteZulu; at which point the exact number of Strike Commands involved is revealed. See Case 7.4, in the StarForce rules, "Semi-Hidden Unit Display."

[41.2] ASSAULT PROCEDURE

[41.21] Whenever the Assault Procedure is initiated, Players determine the number of Strike Commands involved on both sides. For each Friendly Strike Command, the Player receives ten Tactical Points. These Tactical Points are utilized to obtain a mix of Forces according to the schedule of costs listed on the Unit Organization Cost Chart (41.3). Players expend Tactical Points to "purchase," in effect, a mix of Forces. There are no restrictions on the numbers or types of Soldiers, Androids, Support Platforms, or whatever a Player may "purchase," so long as no more Tactical Points are expended than are available.

[41.22] Players will engage in three scenarios, using the rules to the three "General Situations" in Section 27.0. These are a Patrol Scenario, a Recon Scenario, and an Assault Scenario. The Player who initiated the Assault Procedure will field the "Alpha" Force in each of these scenarios; the Player in control of the planet will field the Bravo Force. Player must divide the mix of forces they have selected between these three scenarios, in secret, before contesting them one-by-one. This division must be written down; it may not subsequently be altered.

[41.23] No more than 50% of the force mix and no less than 20% of the force mix (as measured in Tactical Point cost) may be allocated to any one Scenario. No more than twelve individual units (Soldiers, Androids, Support Platforms, whatever) may be allocated to any one scenario. Only the Bravo Player may purchase Bases and Homing Missiles to be used as mines. The Bravo Player receives (gratis) three-hex bases for the Recon and Assault Scenarios. The Base must be three contiguous hexes.

[41.24] Once the force mixes are allocated, the Players contest the scenarios. Each Player loses a fraction of his Strike Commands present in the LiteZulu equivalent to the fraction lost in the scenarios (which are considered to be representative actions). For example: If a Player loses all three scenarios, all Friendly Strike Commands in the LiteZulu would be considered eliminated (and no Enemy Strike Commands would be lost). If the Player had lost two out of three, two-thirds of all Friendly Strike Commands would be eliminated (rounded up to the nearest Strike Command) and one-third of all Enemy Strike Commands would be eliminated. Fractions are always rounded up.

[41.25] In the event that only one Player is left with Friendly Strike Commands in the LiteZulu, that Player is considered to have gained (or retained) undisputed control of the planet. If both Players retain Friendly Strike Commands in the LiteZulu after all losses have been extracted, the Assault is considered inconclusive, and the Assault Procedure may be re-initiated (if possible) by the attacker in the next Stellar Game-Turn. In order for a neutralized StarGate to count towards a victory in the StarForce scenario being played, no Enemy Strike Commands may be present in the system.

[41.26] In Assault Procedures where the ratio of Strike Commands is three to one or greater, the larger side wins an automatic victory, and all of the lesser side's Strike Commands are eliminated.

[41.3] UNIT ORGANIZATION COST CHART

(see center pages)

[41.4] CIVILIANS

[41.41] Civilians should be deployed on the map, depending on the population density of the system involved. See Case 16.1 of the StarForce rules, which lists the inhabited systems. The following systems have a Civilian Density of ten Civilian Counters, in any StarSoldier scenario: Sol, Sigma Draconis, 70 Ophiuchi (the three home worlds). The following colonies have a civilian density of six Civilian Counters: Alpha Centauri, Tau Ceti, Epsilon Eridani, 82 Eridani, HR 8832, 61 Cygni, 36 Ophiuchi, and HR 7703. All other listed inhabited systems have a Civilian Density of three Civilian Counters.

[41.42] Civilians are deployed prior to the start of play, by the Players. The Alpha Player deploys one Civilian Counter, and the Bravo Player a second, and so forth alternately until all called for have been deployed. Civilians are deployed subject to the restrictions listed in Case 30.31.

[41.43] Civilians can suffer casualties, as outlined in Cases 30.32 and 30.34. The number of Civilian Casualty Points caused by each combat is recorded and "credited" to the account of the Player whose weapon caused them. At the end of each Stellar Game-Turn, these accounts for each Player are compared; if the difference between the totals is greater than "five," the Player with the greater number must roll two dice one time for each five CCP's extra there are. E.g., if one Player has a CCP total of 3, and the other Player has a total of 13, the second Player must roll the two dice twice. Fractions of five are rounded down. On any die roll of "11" or "12" on the CCP roll, the rolling Player automatically forfeits the game—the telesthetics of the volume have refused en masse to serve policies which result in so much destruction of intelligent life.

[41.5] ORBITAL GROUND SUPPORT

The Alpha Player may employ Orbital Ground Support in all Scenarios if enough Friendly StarForces are present to offset the planetary defense systems. See the Orbital Ground Support Availability Table. "Full" support equals four bursts of Orbital Bombardment Explosives, two Laser Barrages, and two Opacity Bombs maximum per Game-Turn (in StarSoldier). "Half" support halves those support levels.

[41.6] ORBITAL GROUND SUPPORT CHART

(see center pages)

[41.7] ORDER OF BATTLE CHART

The following chart gives the number of Strike Commands and their allegiance in each StarForce scenario for which information is relevant. Where not indicated, Players have the option of assigning starting positions to Strike Commands as they see fit.

  • Scenario 18—Solar Hegemony/3; Epsilon Eridani/2.
  • Scenario 19—PHH/3 on the initial Stellar Game-Turn, 2 on the third, and 2 more on the fifth; HL/5.
  • Scenario 20—Sol/7; AC/2; TC/2; EE/2; EI/1; 82 Eridani/1; DP/1.
  • Scenario 21—PHH/6 initially, 3 on the 3rd turn, 3 on the 5th turn; LCD/4 initially, 2 on the 3rd Stellar Turn, 2 on the 5th Stellar Turn.
  • Scenario 22—PHH/10; HL/6; 82 Eridani/1; DP/1; EI/1.
  • Scenario 23—PHH/9; EI/6; LCD/8.
  • Scenario 24—Rame/6; Humans/5; LCD/6.
  • Scenario 25—Rame/6; LCD/10.
  • Scenario 26—Rame/3 (May not be embarked onto StarForces—remain on Rame systems); LCD/16; PHH/12 initially, 2 on the 3rd Stellar Turn, 1 on the 5th Turn, 1 on the 7th Stellar Game-Turn.
  • Scenario 27—Rame/8; LCD/12; PHH/16; HL/8.
  • Scenario 28—Rame/8; LCD/10; PHH/10.

[41.8] ADDENDA TO THE LINK GAME

StarGate Capture: At the end of any Stellar Game-Turn in which a StarGate has been "permanently destroyed" by combat (see StarForce Case 9.31), if the assaulting Player has been victorious on the ground, he may attempt to capture the StarGate intact. He rolls two dice; on a die roll of "12" the StarGate is considered to be captured (the Telesthetics have been convinced to switch sides). Replace the Enemy StarGate with a Friendly one (which then functions normally). Increase the die roll for capture by "1" for each five civilian casualties caused by the Enemy Player (that is, follow the same procedure as in Case 41.43).

Low Energy Assaults: Each Friendly Strike Command deployed in a planetary system which contains an Enemy StarGate may attempt to destroy the StarGate by Low Energy Assault. At the end of each Stellar Game-Turn, the owning Player rolls the dice once for each Strike Command deployed in the planetary system. On a dice roll of "11" or "12" the StarGate is permanently destroyed and removed from the game; however, no attempt may be made to capture it. There is no limit to the number of Game-Turns in which a given Strike Command may launch Assaults, and there is never any cost or penalty for doing so.

SEQUENCE OF PLAY SUMMARIES

BASIC GAME SEQUENCE OF PLAY SUMMARY

  1. Plot Phase
  2. Execution Phase
    • a. Fire Segment
    • b. Launch Segment
  3. Movement Phase
  4. Projectile Resolution Phase
    • a. Scatter/Interception Segment
    • b. Detonation Segment
  5. Recovery Phase
  6. Game-Turn Record Phase

STANDARD GAME SEQUENCE OF PLAY SUMMARY

A. Initial Stage

  1. Plot Phase
    • a. Command Communication Segment
    • b. Plot Segment
  2. Execution Phase
    • a. Command Fire Segment
    • b. Command Launch Segment
    • c. Independent Fire Segment
    • d. Independent Launch Segment
  3. Movement Phase
  4. Projectile Resolution Phase
  5. Recovery Phase

B. Second Stage

SUMMARY OF FORMULAS USED IN COMBAT PROCEDURES

Fire Combat Attack Strength (see also, Case 9.61): Firing Soldier's Efficiency Rating multiplied by Number of Task Points Expended.

Defense Strength Against Fire Combat Attack (see also, Case 9.62): Range Attenuation plus Target Counter-Measure plus Movement Effect plus Terrain Value.

Free-Flight Missile Interception Total (see Table 10.24): Range (in hexes) multiplied by Target Counter-Measure.

Scatter Differential (see Case 10.12 and Table 10.4): Launcher's Efficiency Rating multiplied by Task Points Expended (intermediate result) minus (Range Effect Rating plus Target Counter-Measure).

[25.1] UNIT ORGANIZATION CHART

(see explanation page 12)

Soldier TypeHUMAN FTHUMAN SQHUMAN HWHUMAN ADL'CHAL DAH FTL'CHAL DAH SQL'CHAL DAH HWL'CHAL DAH ADRAME SWRAME SQRAME AD
Regular SS36•422•3364
HW SS122••2

FT = Fire Team; SQ = Squad; HW = Heavy Weapons Section; AD = Android Group; SW = Swarm. "•" marks a column with no entry in the printed chart.

  • [19.3] MOVEMENT OF HOMING MISSILES
  • [19.4] VULNERABILITY OF HOMING MISSILES
  • 7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    111234567891011121314151617181920
    222344567891011121314151617181920
    333445678991011121314151617181920
    4444566789101112131415161617181920
    5555667899101112131415161718192021
    66667788910111213131415161718192021
    777788991011111213141516171718192021
    8888999101111121314141516171819202122
    999991010111112131314151617171819202122
    10101010101111121213131415161617181920212122
    11111111111212131314141516161718191920212223
    12121212121313131414151616171818192021222223
    13131313131414141515161617181819202121222324
    14141414141515151616171718181920212122232424
    15151515151616161717171819192021212223232425
    16161616161617171718181919202121222323242526
    17171717171718181819192020212122232324252526
    18181818181819191920202121222223232425252627
    19191919191920202021212122222324242525262728
    20202020202021212122222223232424252626272828
    1
    1
    •
    442,341,240,231,2302221••
    542,441,340,332,331,330111•••
    L'Chal-Dah Player: 2326/+17 (Sigma Draconis)2
    L'Chal-Dah Player: 2626/+7 (61 Cygni)0
    L'Chal-Dah Player: 3223/+17 (HR 8832)1
    L'Chal-Dah Player: Start at 3018/+15 (In the Eta Cassiopeiae LiteZulu)2
    3
    Pan-Human Hegemony Player: 2713/-2 (Epsilon Eridani)2
    PHH Player: 1821/-4 (Alpha Centauri)2
    PHH Player: 3018/+15 (Eta Cassiopeaie)1
    HL Player: 3015/-3 (Tau Ceti)2
    HL Player: 2713/-2 (Epsilon Eridani)2
    HL Player: 3009/-14 (82 Eridani)2
    HL Player: 2427/-18 (Delta Pavonis)1
    12
    70 Ophiuchi (2036/+1)14
    p Eridani (3116/-18)12
    Sigma Draconis (2326/+17)12
    Sol (2020/0)18
    Tau Ceti (3015/-3)16
    38
    1439
    1540
    1642
    1743
    1844
    4
    SV system
    7VRM
    7RM
    7SV
    4
    5worthless12VRM6RM6SV5
    6worthless6VRM6RM6SV6
    7worthless5VRM4RM4SV7
    8worthless3VRM3RM3SV8
    9worthless*1VRM1RM4SV9
    9Full attack on nearest unitChange mode
    0Full attack on nearest unitFull Defense
    5
    1/r
    5
    5
    none
    141601none
    170904none
    171744none
    181544none
    1816332/d; 4/r; 1/e (4th Star Navy)
    192402none
    240301none
    2
    none
    5
    2/r
    0814122/r
    0913123/e; 1/r
    0713—01/e
    D
    C
    H
    5DBIDEG
    6CHGFEF
    *M3827, 3728
    [18.53] Initial Set-up: For each of the hexes listed as a result of a particular Seed Table dice-roll, the Player chooses a Potential Value Chit. The Player then places a Friendly StarGate equal in System Points to the full Potential Value in each hex listed. Each Player may also deploy StarFleets equal in Resource Point Value (see Section 14.2) to two times the number of System Points with which that Player shall begin the game. These must be deployed in a hex with a Friendly StarGate in it. For any result with an asterisk (*) next to it, it is necessary to place additional Beacon Star counters on the map before play begins according to procedure outlined in Section 15.0. In addition, a Beacon Star counter is always placed in the first hex listed in each of the results. Example: in a B result, the player must place a Beacon Star in 0510 and then proceed to section 15.0.
  • Recovery Phase: Any Soldiers that did not suffer any adverse Combat Results during the immediately preceding Execution and Projectile Resolution Phases benefit from Recovery. Stun Markers are removed.

  • Game-Turn Record Phase: Record the passage of one complete Game-Turn and begin the next, repeating Phases 1 through 5.

  • Launching a Free-Flight Missile Cluster toward a specific target hex.
    [DF]variesDirect Fire aimed against a specific target hex.
    [RF]variesRestricted Fire aimed at a specific target soldier.
    [OF]variesOpportunity Fire pre-allocated with no specific target, in the anticipation that one will present itself sometime during the Movement Phase.
    [CM]variesCounter-Measures. A variety of techniques carried out to confuse Enemy detection efforts, in order to weaken or prevent attacks.
    [SE]1TPSearch a particular hex; see Case 13.43.
    [TR]3TPTransport a wounded Soldier or non-combatant; see 13.44.
    [LG]3+TPLaunch Opacity Grenade (Standard Game, see 18.0).
    [LH]3+TPLaunch Homing Missile (Standard Game, see 19.0).
    [LN]3+TPLaunch Neutron Bomb (Standard Game, see 24.0).
  • Movement Phase: Each Player moves those of his Soldiers who are plotted to do so (casualty status permitting). The counters are physically moved on the map, hex-by-hex, according to the plot which has been written for them. In the course of executing these movements, the Players will resolve any Opportunity Fire and Homing Mine Detonation which may be triggered.

  • Projectile Resolution Phase (Identical to the Basic Game.)

  • Recovery Phase (Identical to the Basic Game.)

  • 1
    1
    Ground Base (each hex)620
    3
    4
    4
    6•12334
    7•12233
    8••1223
    9••1122
    10•••112
    11••••11
    12••••••
    S1
    S2
    S2
    5S1S1S1S2S2S3
    6S1S2S2S2S3S3
    2
    3
    4
    5
    6S12345
    7SS1234
    8•S1234
    9•SS123
    10••S111
    11•••SSS
    12••••••
    •
    •
    •
    •
    6
    8
    10
    11
    12
    12
    12
    12
    5246789101112
    613567891011
    7•245678910
    8•13456789
    9••2345678
    10••1234567
    11•••122333
    12•••••••••
    5
    7
    9
    11
    6S246810
    7S13579
    8•S2468
    9•S1357
    10••S233
    11•••SSS
    12••••••
    2
    •
    •
    •
    •
    Team Leader12••1211•••
    Squad Leader•••••1•••••
    Preservation Level235492418501832132617