| By Steve Cole (Stevecole) on Saturday, October 19, 2024 - 05:41 am: Edit |
The F&E staff and I are currently spinning up notes for a 2026 Andro War release. I will not publicly present the notes until I finish reading this topic, talking with SPP, and doing some reading/research. I do have a good grip on the supposed compot deficit issue, which isn't really a difficult problem to solve. More just a matter of deciding just how many solutions we need to apply.
By the way, there will be a counter for each Satellite ship.
| By Mike Erickson (Mike_Erickson) on Saturday, October 19, 2024 - 08:38 am: Edit |
>> there will be a counter for each Satellite ship
And there was much rejoicing!
--Mike
| By Steve Cole (Stevecole) on Saturday, October 19, 2024 - 10:26 am: Edit |
Note to TB: I said full invasion, capturing territory, and I meant it. We shall have that. Wait for the rules post next year.
Note to RB: The Andros have all the toys they need.
SVC agrees: I don't like changing the combat procedure as significantly as would be needed to allow the andros to ambush the ships not in the battleforce. - I really agree with that sentiment
| By Gary Carney (Nerroth) on Saturday, October 19, 2024 - 07:53 pm: Edit |
I'm very much looking forward to seeing what ADB and the F&E staff have in mind!
Also, I agree that separate satellite ship counters are more than welcome.
| By Steve Cole (Stevecole) on Sunday, October 20, 2024 - 05:40 am: Edit |
I have long thought that the andro production/arrival schedule is going to have to be adjusted from published schedules (which were designed to balance those campaigns) to make the AndroWar work.
| By Steve Cole (Stevecole) on Sunday, October 20, 2024 - 05:43 am: Edit |
GARY CARNEY
Make youself useful please. This is a preliminary list of published historical sources which need to be considered in creating F&EAW. If there are more, please add them to the list. If there is significant data buried in an andro ship rule please note the rule numbers of such ships.
AVAILABLE SOURCE DATA
Andro R10 historical/technical rules in R-section background.
Disdev rules in SFB
Operation Unity scenario, production rates, arrival from Andromeda
Return of the Darwin says Galactics were LOSING until discovery of the RTN.
Captain’s Log 49: A BRIEF HISTORY OF THE ANDROMEDAN WAR.
Captain’s Log 49: THE INTERGALACTIC TRUNK LINE.
(R10.1B), the Roms, Gorn, ISC, Lyrans, Hydrans redcuced to a dozen or so hexes each.
(R14.0) says that the LDR was flat-out conquered, and used as a base of operations.
| By Gary Carney (Nerroth) on Sunday, October 20, 2024 - 11:48 am: Edit |
There are a great many data sources to consider - perhaps too many to post all at once.
So, rather than try to do so, I intend to group them by game system, starting with Federation and Empire itself.
Of course, if there is anything I overlook in this and subsequent posts, apologies in advance...
-----
At this time of typing, the "latest" date covered in an historical F&E scenario is the end of Spring Y188, courtesy of the (625.0) Driving Winds scenario in ISC War. Presumably, this means that the first turn of the Andromedan War in the Alpha Octant is set for Fall Y188 (the Andro attempt at the WYN Cluster potentially notwithstanding).
Or, to put it another way: the last "historical" turn covered in that scenario is Spring Y188; the remainder of the scenario is intended to show what might have happened had the Andromedans not emerged in force to ruin things for the ISC Pacification forces.
This scenario provides many important data points, to the point where I'd advise reviewing this scenario in its entirety. But to give one example: it includes how many survey points the General War belligerents had amassed (and thus, how many "new" off-map provinces they had generated) by the end of the General War [(625.542)]; how these same empires are permitted to "transition" their survey operations to peacetime levels [(625.541)]; and how the ISC is itself permitted to generate survey points (and its own "new" off-map provinces) once the Pacification begins.
Beyond this, ISC War includes the Y186 Orders of Battle for the Inter-Stellar Concordium itself, as well as for the Alliance and Coalition empires. it also includes rules for Tactical Reserve Forces [(543.0)], to include initial and operational dates for the various Alpha Octant empires that are known to adopt this system during the course of the Andromedan War [(543.521)].
And of course, ISC War includes the various rules which ISC players need to operate that empire - with two key exceptions: one, how to replace the placeholder rule in (324.34) with a "formal" rule governing the impact of the WYN Radiation Zone on Echelon formations; and two, to how to replace (324.25) with something governing how Echelons are affected by the use of Andromedan displacement devices.
Between the orders of battle; the base, planet, yard, and other dispositions; survey point levels; and production schedules listed in ISC War, it should be relatively easy to work out how most of the Alpha Octant empires stand as of mid-Y188.
However, there are several key exceptions, as listed below.
-----
Firstly, I turn to F&E Minor Empires.
Since things are fairly quiet for the LDR during the Pacification, the data for that faction in ME should be enough to establish what state the Republic is in as of mid-Y188.
In the case of the Vudar, there is conflicting data as to whether or not the ISC ever got around to extending Cordon Foxtrot [(625.F)] into the pre-war Neutral Zone hexes annexed by the Enclave by the end of the General War (so as to oblige the Vudar to withdraw from the three pre-war Hydran provinces they also held at that time) - or of the onset of the Andromedan invasion prevented any such plans from being carried out. In any case, the "low Vudar" data in ME should mostly help in terms of establishing an historical condition for the Vudar as of mid-Y188.
In contrast, the Seltorians are a bit of a problem - as, for that matter, are the Tholians, plus the ISC forces assigned to Cordon Charlie [625.C]. While ME provides the historical "arrival" order of battle and production schedule for the Burning Torch of Vengeance expedition, there is as yet no historical scenario covering their war against the Tholian Holdfast - to include the dramatic intervention by the X1-squadron Echelon of Judgement to extinguish the Torch itself.
I would strongly recommend that such a scenario be written up for Captain's Log and/or for a pre-Andro War module (perhaps in Civil Wars?) - not just to cover this campaign fairly in and of itself, but also to allow for "post-Torch" OOBs to be established for the Tholians and for the ISC's Cordon Charlie forces through to mid-Y188.
-----
As for Civil Wars, it should also provide rules and scenarios needed for a mid-Y188 snapshot of several Alpha Octant empires.
In the case of the Romulans - as well as those ISC forces assigned to Cordons Alpha [625.A], Bravo [625.B], and Zulu [625.Z] - the Romulan Civil War scenario previewed as 6RCW.0 in Captain's Log #50 and in the CL50 Supplemental File would need to be formally published and accounted for. Not just in terms of the fallout from the Civil War itself, but also from the intervention of the X1-squadron Echelon of Justice at Tibernia IV - to include formally clarifying whether or not the ISC continued to "commandeer" that planet as of mid-Y188, or if their forces had withdrawn from this world by then.
Both the WYNs and Kzintis are set to be heavily impacted by the War of Return, as are the ISC Pacification forces in Cordon Echo [625.E] which historically entered the WYN Cluster itself. Although, it might be necessary to clarify when this intervention took place - not least so that the later Andromedan attack on the Cluster can be accounted for.
By contrast, the Lyran Empire was fairly quiet in this era, as were the territories leased to the Klingons out in the "off-map" Delta Sector. So any "new" Lyran data in this module should not be as much of a factor here.
-----
Speaking of the WYN Cluster, Tactical Operations includes the (634.0) Into the Whirlpool scenario, which includes rules on how other Alpha Octant empires are affected by the WYN Radiation Zone. This data would be needed over in Civil Wars, to cover the intervention by the ISC's Cordon Echo forces; in this module, there'd need to be a formal accounting of exactly what the effects of the Zone are on Andromedan warships attempting to make the crossing.
TO also introduced many new ships that are going to be of major importance during the Andromedan War - not least several "X-raiders" (such as the Romulan SparrowHawk-EX) and other lone units (sch as the Federation GSX) that will be critical in terms of engaging the Andromedan Rapid Transit Network later in the war - and, in the case of one well-known GSX in particular, in taking the fight to the Lesser Magellanic Cloud during Operation Unity.
This is also true for several of the "new" ships that have been added to the recent crop of countersheet revisions for older F&E modules. This includes the various "-Z" configuration units provided for the Federation: in the historical timeline, these units - along with the lone Fed GVX - shall play key roles in helping to find and destroy Andro RTN nodes.
-----
That said, there is still a large number of Alpha Octant units that are not presently in F&E that would be required in order to more fully account for the Andromedan War in this game system.
Specifically, the current crop of counters only cover units that historically existed as of mid-Y188: the cut-off point mandated at the time that Tactical Operations was being assembled.
Exactly what those units are is something I'd have to use later posts to explain. But, for now, I should note that the various HWXs provisionally listed in various Alpha empires' SITs (not least the HWXPs, plus the Federation HWXZ) would be required.
As would the various "wartime construction" hulls to be built and/or converted in ISC home space; the "system" ships hastily converted from pre-war hulls out in the semi-isolated cantonments elsewhere along the former Pacification cordons; and certain new "peacetime construction" hulls that emerged during the war, to include the fast blockade runner variant of the fast light cruiser.
And, lest I forget, the Kzintis are going to have a "Goliath" of a ship to deploy later in the war...
| By Gary Carney (Nerroth) on Sunday, October 20, 2024 - 12:20 pm: Edit |
Next, I'll cover the data points provided as background articles and/or story fiction works in various issues of Captain's Log.
-----
In terms of story fiction, there is Not Good Friends in Captain's Log #23; First Encounter in Captain's Log #25; Battle For Rimworld in Captain's Log #27; and Return of the Darwin in Captain's Log #54. All four stories have corresponding Star Fleet Battles scenarios in their respective issues - except for the Darwin story, which is based on the infamous scenario from Module X1 that is also available here.
In terms of longer-form background articles, there is the aforementioned A Brief History of the Andromedan War in Captain's Log #49, as well as NCC-1821 USS Sakharov: Voyages of Discovery in Captain's Log #51.
Monographs and other, shorter historical datafiles are a bit more prevalent. Beyond the aforementioned Intergalactic Trunk Line article in Cl49, there is A Bridge Between Galaxies in Captain's Log #35; Andromedans and the Lack of Innovation in Captain's Log #43; and Breaking the RTN in CL54.
In terms of Class History articles, the one for Federation Galactic Survey Cruisers in Captain's Log #41 is a key resource, not least since it states in which years the five known Federation GSXs are built. Others make reference to events during the Andromedan War, to include the two for Federation Fast Raiders in CL27 and in Captain's Log #43.
Beyond this, there are several Planetary Surveys which refer to events that take place during the Andromedan War, to include that for Skoleos in Captain"s Log #46 and for Vega IX in CL54.
| By Gary Carney (Nerroth) on Sunday, October 20, 2024 - 01:02 pm: Edit |
So far as Star Fleet Battles references are concerned, there are several sub-categories to consider: background datafiles (some, but not all of which are also to be found in Captain's Log); R-section entries; individual scenarios; mini-campaigns; and other items.
-----
To start with background datafiles, there is The Secret History of X-Ships in Module X1R - a key document upon which many later files (and ship designs) were later created.
In Module C3A, there is A Future Darkly, which breaks down why the Alpha empires were losing the war prior to the Darwin's disappearance; how things went from bad to worse in the "dark future" timeline; and how the return of the Darwin offered fresh hope for the surviving Alpha Octant empires.
To be clear, I should note that this hope by no means manifested overnight: it still took precious time for the Alpha empires to figure out how to destroy RTN nodes faster than the Andromedans could move or replace them - and, by extension, how to shift the momentum of the war away from the invaders overall.
C3A also includes a breakdown of the "dark future" timeline, to include referring to the failed "Operation Codominion" - a grim corollary to the historical Operation Unity campaign. A number of events from this timeline are glimpsed in passing in the Darwin story fiction in CL54.
So far what the Andromedans were up to in the Lesser Magellanic Cloud prior to Operation Unity - not least in terms of how many Desecrator starbases they built in that island galaxy - the history of the LMC from Module C5 is available to review here.
As for the war being waged in parallel over in the Omega Octant, I would refer to the consolidated timeline provided in the 2011 revision to the Omega Master Rulebook. Even if the war in Omega is not being covered here in and of itself, its effect on the forces available to the Andromedans in Alpha and the LMC is worth noting.
-----
As for campaigns, mini- or otherwise: the aforementioned Operation Unity campaign in Module C2 has had several updates and revisions posted Captain;s Log #30, Captain's Log #36, and Captain's Log #43, in order to account for a host of new ships - and new empires - which did not exist in print at the time the original Unity campaign was created.
Again in Module C3A, there is the Fall of Demorak campaign, which provides an in-depth look both on the waves of attacks launched against the LDR capital world in and of itself, but also ties in two other scenarios featuring LDR warships of note that were being fought concurrently with these battles: Sound Recall!, also in C3A, and Charge of the Red Guard, from X1R.
A smaller-scale event is The Run for Home in C2, which might be a useful means of testing how the Andro combat and "off-RTN" movement rules work in F&E terms.
-----
In terms of individual scenarios: X1R includes in Time, or Too Late? - which depicts the dramatic intervention of the Echelon of Judgement at the Korlivala home system in the early phase of the invasion. Note that this was technically the second wave of attacks on the Korlivilar home world: the first one had destroyed most of the pre-existing planetary defences.
There's also the Starbase Sanguinax scenario in Module X1, which depicts the destruction of a Romulan starbase in early Y195. (By my understanding, Sanguinax was itself a relatively "new" installation, not accounted for in pre-existing General War- or Pacification-era scenarios. But I might be mistaken on that front.)
I might need more time to assemble a more in-depth list of scenarios featuring the Andromedans, but there are two others that I'm currently minded of:
Battle of the Five Fleets from Module R9, which depicts the early difficulties faced by the Pacification forces when attempting to withdraw back to ISC home space in the midst of hostile opposition;
and Joint Operations from Module C5, which depicts a battle that took place during Operation Unity involving the two X1-ships from the Klingons' Unity task force. As shown here, there is much more to the LMC than the location(s) of the (second and third) Desecrator(s); this scenario highlights the kind of "side missions" the Unity powers found themselves carrying out within the Cloud, both during and after the Unity campaign proper.
| By Gary Carney (Nerroth) on Sunday, October 20, 2024 - 01:33 pm: Edit |
In terms of rule and R-section data, there is much to consider also.
-----
One aspect which has yet to be confirmed is exactly how fast the Andromedans can go in terms of operational movement - as in, when "off the RTN". All that is known is that it is somehow slower than the six-hex-a-turn standard for "modern" (GURPS Prime Directive Tech Level 12) warships in the Alpha Octant - but, according to (MS1.26) in Module C5, is as fast as operational movement is for the native Magellanic empires, whatever that might end up being.
I tried to address this obliquely in part of the Darwin story in CL54, but took care not to lock in an operational speed that would pre-empt whatever move rate is to be assigned to them here.
(Personally, I would favour setting it at 4 hexes per turn, though I defer to the experts in this regard.)
-----
X1R includes relevant R-section data for a number of Alpha Octant empires, not least of which being the ISC and the Hydran Kingdom.
In the case of the Hydrans, it's noted that they were later than the Alpha Octant average, in terms of deploying a more complete range of first-generation X-ships. Indeed, as for the actual X1-ships themselves, it's worth noting that while there are a number of X-scout carrier and X-PFT options available for them, few of these options are well-armed enough to be effective against RTN nodes. So, in terms of wartime orders of battle, one might need to review the appropriate SSDs in more detail, so as to decide upon which - if any - of them would be best suited to clearing the RTN in Hydran space.
-----
As for the ISC, their problems in this era are legion, due to their Pacification forces bearing the brunt of the invasion early on.
In X1R, there are a number of hull types which are hastily constructed in the early years of the invasion, to include the CAX (R13.206) and CMX (R13.207). It's also noted that, due to the lingering trauma of these events, the Concordium refused to send any of their X1-ships to the LMC as part of Operation Unity.
X1-ships aside, the ISC home fleet yards responded to the invasion by placing the "wartime construction" CW (R13.80) and DW (R13.81)from Module R9 into full production; this was later joined by the HCW (R13.05) from Module R12. I would argue that, with so many new ships of these types being built and/or converted, there would be a need to provide a range of mission variants for them over in SFB - and, by extension, here in F&E also.
Meanwhile, a range of "system" hulls were being hastily converted out in the semi-isolated cantonments that the surviving Pacification forces coalesced into. These offer from the "war" hulls in that they do not add any warp engine power along with their added bulk, thus slowing the ships down in combat. (Actually, it might be worth deciding whether or not this added bulk also impacts these hulls' operational and/or strategic movement.) Examples of "system" hulls include the NCA (R13.67) in Module R9, as well as the NDD (R13.84) in Module R11.
Beyond this, new "peacetime construction" ships emerged in this era. A notable example of this is the fast blockade runner (R13.88) in R11: this hull was intended to deliver critical components from ISC home space out to the various cantonments, so as to keep them alive long enough to enable the Concordium government to eventually negotiate their return home later in the war.
-----
And, to go back to X1R, there are the various HWXs (plus their mission variants) to consider - not least for the Federation, whose "-Z" configuration of their HWX (R2.213) might be called upon to serve as a vital backstop to the GVX and GSXs chasing down the RTN across the vast reaches of Federation space.
-----
One final note for now:
Since there are going to be separate satellite ship counters, increasing the number of Andromedan counters to be printed overall; and since there are so many new Alpha empire counters, for the ISC and others, that are going to be needed; I might wonder if it was best to split them into two products.
As in, to keep the Andromedans together in a single-empire product - akin to ISC War - and then to place the others in a dedicated "[Something] Operations" module to be published alongside it.
If so, how about "Unified Operations"? As a nod to Operation Unity, perhaps.
| By Steve Cole (Stevecole) on Sunday, October 20, 2024 - 01:55 pm: Edit |
Thank you, Gary.
| By Steve Cole (Stevecole) on Sunday, October 20, 2024 - 09:13 pm: Edit |
Note to Randy B: We have no plans for alternate timeline stuff in AndroWar.
Although... there will be some mechanism for the discovery of the RTN. You could simply ignore that rule and go down swinging.
Note to Gary C: The thing doesn't work unless the Andros can build all of their ships in the LMC. They could not phone home with a cool idea for a variant and wait 200 years for it to be delivered.
| By Steve Cole (Stevecole) on Sunday, October 20, 2024 - 11:49 pm: Edit |
This is a seriously incomplete list of discussion participants. If you have participated but are not on this list, post a note here.
Tony Barnes, Randy Blair, Gary Carney, Alex Chobot, Robert Cole, Stephen V. Cole, Geoff Conn, Mike Curtis, Alan De Salvio, Kerry Drake, Richard B. Eitzen, Greg Ernest, Christopher E. Fant, David Fowler, Paul Franz, Stewart W Frazier, Andrew Harding, John Kasper, David Kass, Jimi LaForm, Jeff Laikind, Douglas E. Lampert, David Lang, Tim Losberg, Joseph A Mannino, Thomas Mathews, Ryan Opel, Steven P. Petrick, Mathew Potter, Edward Reece, Nick Samaras, David Slatter, Eric Smith, Eric Stork, Joe Stevenson, Colonel Chuck Strong, Scott Tenhoff, Oliver Dewey Upshaw III, Jeff Wile, Kent Wendel, Donovan A. Willett, John M. Williams.
And if I misspelled your name or didn't use the style you prefer, let me know.
| By Gary Carney (Nerroth) on Monday, October 21, 2024 - 12:23 pm: Edit |
For comparison's sake, the Hive Ship Burning Torch of Vengeance stopped to send a powerful subspace message back to M81, in order to inform the Seltorian Suzerainty that a Tholian Sphere had been located in our galaxy.
On a side note: this signal was also detected by the Tholian exile group that would eventually divert to Draco.
As noted in the Fire in the Deep short fiction in Captain's Log #41, this is also done as a means of communicating with the home galaxy while still in the depths of intergalactic space - to include receiving new instructions from the home government, if so required. However, this requires the Hive Ship to reach a dead stop in space in order to send each signal.
Of course, regardless of what kind of data the Torch would have been able to send back to the home galaxy, it would still take 200 years for reinforcement ships to "slow boat" their way to the Holdfast. Although, it would be an interesting means of introducing certain new technologies to M81 as a setting in and of itself...
-----
On a second side note: once SFB (and/or F&E) establishes more solid data on the Tholians of Draco - to include determining exactly what kind of unit the survey ship Sojourner happens to be - this would have an impact on the Holdfast order of battle here: since, according to the namesake article in Captain's Log #39, the Sojourner itself, plus two other Draco-Tholian ships, arrive in the Holdfast in late Y195.
Indeed, might the Tholians end up deploying the Sojourner as part of their Operation Unity contingent?
-----
In contrast, it might be worth determining exactly what (if any) two-way communications are enabled by the operation of the Intergalactic Trunk Line - as well as to clarify exactly how long it takes for Adnromedan ships being deployed on the ITL to get to the LMC from M31.
Although, if one were to assume that the Andromeda galaxy has an energy barrier comparable to that of the Milky Way galaxy, perhaps the ITL does not run directly through it - but, rather, from one of Andromeda's own satellite galaxies instead? In other words, perhaps the Andromedans have succeeded in conquering the likes of M32 and M110 - and find it more practical to use those as jump-off points in order to run ITL links towards (the satellites of) other target galaxies.
Anyway, what I was thinking is that, once a Desecrator starbase is completed in the target island galaxy, perhaps a part of its functioning as an ITL terminus node includes an ability to use the chain of ITL stations as communications relay points, rather than attempting to send a signal to Andromeda all at once akin to what the Seltorians do.
So, if there was such a means to relay (relatively) active intelligence "back home", then the Andromedans might be in a position to use the ITL itself to deploy "new" variants and/or technologies to the LMC - which, in the "dark future" at least, might include the equipment needed to deploy the four Dissection Beam variant Motherships from Module C3A.
| By Alan De Salvio (Alandwork) on Monday, October 21, 2024 - 02:07 pm: Edit |
Wow. Nice work Gary. SVC - this is the crowning jewel of F&E. I have been looking forward to this since I saw the SSCS SSD a long time ago. And the Darwin story and related scenarios are some of the best in SFB (in my opinion).
I believe we need to be able to set up an F&E battle with Andros and see what is going to happen - we need that "ooooh" moment. Hydran cruiser battleline did this; strong plasma battleline did this; Battleline versus battleline+SB did this; fleet versus a kitted out capital did this. PFs versus no PFs gets close, and lots of X versus no X does this, so I am confident.
| By Steve Cole (Stevecole) on Monday, October 21, 2024 - 02:48 pm: Edit |
Alan: all in good time, but not today, or this year. We're very preliminary here. I know there are plenty of sneaky tricks the staff and I can use the balance the battleline confrontation; I do not know yet how many or those tricks we will have to use.
| By Mike Erickson (Mike_Erickson) on Tuesday, October 22, 2024 - 09:07 am: Edit |
The only thing I hope for in AW is that the implementation of the various Andro technologies is quite simple yet effective, so that play is easy and moves right along, particularly for remote play. No SFG-like complexity Andro rules, please.
--Mike
| By Ahmad Abdel-Hameed (Madarab) on Tuesday, October 22, 2024 - 07:18 pm: Edit |
I don't have it anymore, but Captain's Log #5 (I think.) had a couple of Andromedan vs B10 encounters.
Edit: It was Captain's Log #6. I'm going to buy a PDF version of it from Warehouse 23.
| By Mike Erickson (Mike_Erickson) on Tuesday, October 22, 2024 - 10:35 pm: Edit |
"A MEETING OF GIANTS" starting on page 12 of CL#6. A classic from 36 years ago! Packs a lot of action into just a few pages.
--Mike
| By Ken Kazinski (Kjkazinski) on Wednesday, October 23, 2024 - 09:22 am: Edit |
Here is a listing of SFB scenarios.
MSH4.0 Base Busting (C5)
MSH8.0 A Rational Choice (C5)
MSH9.0 Joint Operations (C5)
OS24.0 To Make a Stand (O4)
SD1.0 Giants Among Men (SFT19)
SG2.0 Fleet Action (BS-1999)
SG10.0 Visitor from Andromeda (C2)
SG26.0 Base Busters (C2)
SG56.0 Disrupted Repair (S2)
SG75.0 Starball (T2012)
SG78.0 The Critical Juncture (R10)
SG80.0 Local Security (R08)
SG86.0 X-Termination? (X1R)
SG89.0 Giants Among Men (T2012)
SH26.0 Andromedan Raid (S1)
SH45.0 Logistics Strike (C2)
SH46.0 Three Against Cortez (C2)
SH74.0 A Tangled Web (R02)
SH75.0 Haste to Make Waste (R02)
SH93.0 Invulnerable for the Defense (R05)
SH94.0 Sibling Rivalry (R05)
SH113.0 Religious Experience (C3)
SH154.0 Interrupted Exchange (S2)
SH164.0 Insatiable Arbitrator (X1)
SH165.0 Starbase Sanguinax (X1)
SH166.0 Return of the Darwin (X1)
SH190.0 Curiosity Kills (M)
SH196.0 Strike Force (R06)
SH208.0 One-Man Band (R07)
SH221.0 Target: Rigellax; Objective Unknown (J2)
SH237.0 An Encounter Unwanted (F2)
SH247.0 In Time, Or Too Late? (X1R)
SH248.0 Charge of the Red Guard (X1R)
SH263.0 Just a Little Time (R12)
SH265.0 Wrong Enemy (R04T)
SJ8.0 Marauders and Snakes (C6)
SJ11.0 New Tenants (C6)
SL97.0 Invulnerable for the Defense (CL06)
SL98.0 A Meeting of Giants (CL06)
SL99.0 Sibling Rivalry (CL06)
SL125.0 Logistics Assault (CL09)
SL140.0 Typhoon On The Rocks (CL12)
SL152.0 A Nest Of Vipers (CL16)
SL177.0 Emergency Base Removal (CL19)
SL179.0 A Rational Choice (CL20)
SL201.0 Not Good Friends (CL23)
SL203.0 Joint Operations (CL23)
SL212.0 First Encounter (CL25)
SL223.0 Battle For Rimworld (CL27)
SL232.0 Do or Die at Breakaway Station (CL30)
SL238.0 An Intruding Situation (CL31)
SL243.0 Network Disruption (CL32)
SL266.0 Home-Wrecking (CL37)
SL267.0 Snake Attack! (CL37)
SL274.0 Wabbit Season (CL38)
SL287.0 Local Defense (CL40)
SL297.0 Previously Unknown (CL42)
SL300.0 Backstabbed By A Thief (CL43)
SL326.0 Help Is Where You Find It (CL47)
SL336.0 Death of the Gryphon (CL49)
SL349.0 Flame in the Deep (CL52)
SP Battle of the Invaders (Future)
SP Cutthroat (Future)
SP First Flight of the Goliath (Future)
SP Infest The Nest (Future)
SP Joint Adventure (Future)
SP Plans Change In Battle (Future)
SP Prime Real Estate (Future)
SP368.0 Starbase Sanguinax (CL14)
SP509.0 Insatiable Arbitration (P2)
SP1063.0 Haste to Make Waste (P3)
SP1064.0 Curiosity Kills (P4)
SP1250.0 Web of the Andros (P3)
SP1281.0 Hey! Those Are Our Freighters (P3)
SP1291.0 Supply Raid (P3)
SP2102.0 Why??? (SFT34)
SP3022.0 Base Busting (E1)
SPN2.0 A Question of Sanity (R107)
T7.0 Run for Home (C2)
T7S1.0 Intercept (C2)
T7S2.0 Rendezvous (C2)
T7S3.0 Between a Roc and a Hard Place (C2)
T12S1.0 Assault on Demoak (C3A)
T12S2.0 Sound Recall! (C3A)
U6.0 Operation Unity (C2)
| By Steve Cole (Stevecole) on Wednesday, October 23, 2024 - 09:57 am: Edit |
thank you, Ken!
| By Joe Carlson (Jrc) on Thursday, June 26, 2025 - 01:02 pm: Edit |
SVC,
Is this a next F&E product?
| By Steve Cole (Stevecole) on Thursday, June 26, 2025 - 04:48 pm: Edit |
No, civil wars will be next.
| By Joe Carlson (Jrc) on Thursday, June 26, 2025 - 05:43 pm: Edit |
SVC,
Thank you.
| Administrator's Control Panel -- Board Moderators Only Administer Page | Delete Conversation | Close Conversation | Move Conversation |