The Expanding Frontier

Creating Sci-fi RPG Resources

  • Home
  • Order a Map
  • Order Miniatures
  • Supporters
  • About
  • Bio

Category Archives: Background

Detailed Frontier Timeline – FY61.357 to FY61.381

This post is only a bit over a year late. These are the events that I posted to twitter back in February of 2021 just before I stopped blogging. I’m finally getting them online. I also plan on resuming the daily Twitter posts of the events. starting on day FY61.382. If you want to get the daily updates, follow the @StarFrontiers account on twitter or the #SFTimeline hashtag. If you want to review everything that has happened, or are new to this series of posts, you can grab the PDF file linked at the bottom of the post that contains every entry in the timeline since I started it. Its up to 81 pages so there’s a bit of reading there.

Also, depending on how things go generating the timeline, I might start posting events using the GST calendar of the Frontier. Which means you’ll get 36 Frontier days worth of events every 30 Earth days as the GST calendar only has 20 hours per day instead of our 24. We’ll see if that actually pans out.

The events in this post include the two battles I posted the detail of early last year which are linked in their appropriate entries. With the conclusion of the Battle of Liberty, the war cools down for a while. The sathar are currently out of ships at the moment although they have dozens under construction. Both sides are now maneuvering to reposition and rebuild forces. Otherwise, not much happening in this post outside of the war events.

Date (FY)Events
61.357– Ten more pilots complete their fast-tracked certifications for the Frontier Fighter Corps.  They immediately depart for Hentz (Araks).

– SBF-J2 (Liberty system) begin calculations for a jump to the Waller Nexus system.Spacefleet holds the space in anticipation of more ships finishing and beginning construction on a new battleship.
61.358– Second Battle of Ken’zah-Kit (K’aken-Kar) – After nearly 2.5 hours of fighting TF Cassidine defeats SBF-J1 losing only a single fighter while the sathar only have a fighter and heavy cruiser surviving. Most of the UPF ships have damage requiring a shipyard to repair.

– The surviving sathar heavy cruiser and fighter from SBF-J1 accelerate for a jump to the K’sta-Kar system.

– The damaged UPF destroyer completes repairs in the Streel shipyards (Pale, Truane’s Star) and the ship that was moved out to make room resumes construction (it will be done in 23 days).

– SBF-E2 jumps into the Zebulon system.  It remains at high speed and begins calculations for jump to Kazak.

– A HS:8 ship completes maintenance in the PGC shipyards (Gran Quivera, Prenglar). Spacefleet moves a couple of small ships in for maintenance to coordinate their completion with more ships finishing and beginning construction on a new battleship.
61.359– Calculations for the jump back to YS07 complete, the HSS History’s Hope begins accelerating for the jump while the astrogators get a day of rest before double checking the figures on the way out.

– Sathar TG-1 jumps into the OFS136 system where SCC#3 is located as they continue on their journey to SCC#4 (OFS111)

– The battleship Admiral Dooltan and accompanying minelayer arrive at Zit-kit (Kisk-Kar) and join up with PG Meteor.  With the addition of the battleship and minelayer, the fleet is now designated Task Force Meteor.

– After spending a day rearming, Task Force Cassidine splits up with the undamaged heavy and light cruiser, now designated Patrol Group Vigilant, departing in pursuit of the sathar heavy cruiser which is headed toward K’tsa-Kar.

– The main force of TF Cassidine, all needing time in a shipyard to fully repair, begin accelerating for a jump to the Kizk-Kar system and then on to Fromeltar.  The Terledrom (Fromeltar) shipyard is notified that they will arrive on FY61.375 and begins making preparations to receive them.

– The Clarion (White Light) militia, at the request of Spacefleet, depart for a jump to K’sta-Kar to join up with PG Vigilant and patrol that system.  The saurians send 3 of their 6 Battle Rays to assist.
61.360– Calculations complete, SBF-J2 (LC & FF) begin accelerating from the Liberty system for a jump to the Waller Nexus system.  PG Liberty detects the departure almost immediately and subspace radio the intel back to Spacefleet.

– Stationing 8 of the fighters at Fortress Pale as the first official squadron of the Frontier Fighter Corps, the second assault carrier currently with Strike Force Nova is designated as Shuttle Group Alpha and departs back to Triad (Cassidine) to start moving more fighters around the Frontier.
61.361– PG Liberty are authorized to engage the outbound SBF-J2 if conditions are favorable.  Several Mhemne Belter ships offer to assist although their outdated engines mean that they will only be able to make a single pass at the sathar vessels.  The ships all boost for intercept.

– Four fighters are completed at the Hentz (Araks) shipyard.  They are put into storage awaiting the arrival of the Spacefleet pilots. Construction beings on four more fighters.

– Two fighters are completed at the Minotaur (Theseus) shipyards for the Frontier Fighter Corps but are currently manned by the militia.  Construction begins on two more fighters.
61.362– SBF-E2 jumps into the Kazak system and begins calculations for a jump to OFS019 and SCC#5.

– Battle of Liberty – PG Liberty, augmented by Mhemne ships, engage the sathar in the outer system. The fight does not go well for the UPF who lose their frigate and an assault scout although they do manage to destroy the sathar frigate.

– After fighting the UPF in the Liberty system, the surviving sathar light cruiser of SBF-J2 continues on its course to jump to the Waller Nexus system.
61.363– CDC staff arrive back on Alcazzar (Rhianna) in anticipation of the new mining season. (SF4)

– SBF-J1 jumps into the K’sta-Kar system.  They remain at speed and begin calculations for a jump to FS33.
61.364– The HSS History’s Hope successfully jumps back into the YS07 jump completely charting that route.  They begin decelerating to turn around and jump back to YS08 to continue their journey forward.

– PG Vigilant and the Clarion militia both jump into the K’sta-Kar system from opposite directions.  Keeping an eye on the retreating SBF-J1, they start deceleration toward Kwadl-Kit.

– TF Cassidine jumps into the Kizk-Kar system and begin calculations for the jump to Fromeltar.  They transmit details of their recent battles to TF Meteor to share their experiences.
61.365– SBF-E2 jumps back into the OFS019 system and begins decelerating toward SCC#5.

– SBF-J2 enters the Void and like the frigate before it, misjumps, this time ending up in the OFS196 system.

– Enough space has cleared in the CDC shipyard (Triad, Cassidine) to allow Spacefleet to begin construction on another battleship to replace one of the two lost in the Second Battle of New Pale.
61.366– SBF-J1 jumps into the FS33 system and begins calculations for a jump to OFS166.

– Eight more fighters are completed at the PGC shipyards (Gran Quivera, Prenglar) and shuttled to Gollwin Academy. Spacefleet delays the start of construction of more fighters as production of the ships is outpacing training of pilots and they want to use the space for construction of another battleship.
61.367– As OFS196 is a system in the sathar charts, being on the route to OFS203 and SCC#1, SBF-J2 determines it position after just two days.  It decides to take the known route back to Liberty and try again.

– Enough space opens up in the PGC shipyards (Gran Quivera, Prenglar) for Spacefleet to begin construction on the second battleship to replace the second one lost in the Second Battle of New Pale.
61.368– The HSS History’s Hope arrives in the inner system of YS07 where they will rest for a day before they begin accelerating for the jump back to YS08.

– Task Force Cassidine jumps into the Fromeltar system and begins a slow deceleration toward Terledrom and the shipyard there.  They radio ahead that they are a few days early.

– Spacefleet resumes fighter construction in the PGC shipyards (Gran Quivera, Prenglar) but only producing five at a time instead of eight.  The other 3 HS worth of space is dedicated to constructing an assault scout.  Additionally, 3 more assault scouts are started in the CDC shipyards (Triad, Cassidine).
61.369– PG Vigilant and the Clarion militia, together with the saurian battle rays, arrive in orbit around Kwadl-Kit (K’sta-Kar).  They set up a patrol schedule to watch for new sathar threats.

– SBF-J1 jumps into the OFS166 system and begins calculations for a jump to OFS167.

– SG Alpha arrives back at the CDC shipyards (Triad, Cassidine).  The fighters in storage are transferred to the carrier while they await the arrival of their pilots, scheduled to graduate from Gollwin Academy tomorrow.
61.370– SBF-E2 arrives back at SSC#5 (OFS019).  The heavy cruiser under construction is moved out of the shipyard to make room for the damaged one to receive the necessary repairs.

– Nine more pilots graduate in the accelerated cadet class at Gollwin Academy.  They immediately depart to take command of the fighters currently sitting in storage at Triad (Cassidine).
61.371SBF-J1 jumps into the OFS167 system and begins calculations for a jump to OFS169.
61.372An attempt to explode a bomb at the Council of Worlds building while the council is in session is foiled by Star Law agents and local law enforcement.  Unfortunately, none of the perpetrators survived.  An investigation is launched immediately to track down the origin of the plot.
61.373TF Cassidine arrives in orbit around Terledrom. There is currently 6 HS of open space in the shipyard and the heavily damaged frigate and fighter are moved in for repairs.
61.374– The HSS History’s Hope jumps back to the YS08 system.  They begin decelerating and working on the jump calculations for the next system, a binary system 5 ly away.

– SBF-J1 jumps into the OFS169 system and begins calculations for a jump to the OFS170 system.

– The K’aken-Kar militia assault scout, also in OFS169, happens to detect the heavy cruiser just hours after it jumps into the system.  Realizing they are in sathar controlled space, the ship goes into as stealthy a mode as possible to avoid detection as they monitor the sathar vessel.

– SBF-J2 jumps back into the Liberty system.

– The TF Cassidine fighter in the Terledrom (Fromeltar) shipyard competes its repairs.  The space is held in reserve for the larger ships needing repairs.
61.375– Princess Leotia’s 35th birthday. Major celebrations are held all over Clarion (White Light) in commemoration of her coming of age.  While her father had planned to step down and hand the government over to her during the ceremonies, this has been delayed due to the ongoing sathar conflict.

– SBF-J1 jumps into the OFS170 system and begins calculations for the final leg of their jump back to SSC#10 in the OFS228 system.

– PG Liberty detects the returning light cruiser and radios its presence back to Spacefleet.

– The damaged sathar heavy cruiser at SCC#5 (OFS019) completes repairs and construction is resumed on the new heavy cruiser.
61.376Three UPF fighters are completed at the Terledrom (Fromeltar) shipyards.  They are transferred to Task Force Cassidine.  The shipyard space is held in reserve to fit the larger ships needing repair.
61.377– SBF-J1 jumps back into the OFS228 system and begins decelerating toward SSC#10

– An assault scout is completed in the Outer Reach (Dramune) shipyards.  It sets off immediately for the Fromeltar system to join TF Cassidine.  Construction begins on a new assault scout.
61.378– SBF-J2 arrives back in orbit around Snowball.  After rearming, it sets off once again to try to jump to the Waller Nexus system.

– Calculations complete, the HSS History’s Hope begins accelerating to the next system on their route, which they designate as YS11.

– A UPF assault scout is completed at the CDC shipyards (Triad, Cassidine). This is the first of the replacement ships larger that a fighter to come out of the shipyards since the conflict began.  5 fighters are also completed and work begins on another AS and 5 fighters.  The completed ships join SG Alpha.

– The first damaged frigate from TF Cassidine emerges from the shipyard at Terledrom (Fromeltar) fully repaired.  The other frigate enters and work begins on it.
61.379– The Frontier Fighter Corps pilots arrive at Hentz (Araks) to take command of their fighters there.  There is some initial tension between the UPF and militia forces as the latter do not want to turn over control of the ships.

– The Spacefleet pilots arrive at Triad (Cassidine).  They are immediately transferred to the carrier in SG Alpha where their ships are awaiting them.  SG Alpha departs immediately for a jump to Dramune and then on to Fromeltar where the fighters are to be delivered.

– The Yazira Dome completes its second year of operation.  With the on-going sathar conflict, travel has been curtailed and off-world yazirian visitors diminished but the Dome is still wildly popular with on-planet visitors.

– Detecting SBF-J2 outbound once again, PG Liberty sends a subspace message informing Spacefleet and continues to monitor the sathar ship.

– Calculations complete and checked, the HSS History’s Hope begins accelerating for the jump to the next system on their route, designated YS11.
61.380– Sathar TG-1 arrives at SCC#4 (OFS111), joining the other ships there.

– After several back-and-forth communications, including a threat by Spacefleet to dispatch TF Prenglar to the Araks system to eliminate or take control of the militia, the Hentz militia turns over control of the Frontier Fighter Corps fighters to the UPF crews.

– The second damaged frigate from TF Cassidine completes repairs at the Terledrom (Fromeltar) shipyards.  A new UPF assault scout, along with an assault scout for the local militia are also completed.  This frees up enough space that TF Cassidine’s assault carrier can move in for repairs.
61.381TF Cassidine’s assault carrier completes repairs at the Terledrom (Fromeltar) shipyards.  There is not enough free space to move the battleship in, but that space will free up in three days.  With 30% of the shipyard empty, the work crews can each get a full day off to rest over the next few days.

Full timeline file:

DetailedFrontierTimelineDownload
May 6, 2022 Tom Leave a comment

Detailed Frontier Timeline – FY61.326 to FY61.356

This is only a week later than I had planned. I’ve gotten behind on updating the timeline entries and am still trying to catch up. I’ve had some big battles to play through and I just haven’t had the time to do so. There will be another battle coming in a few days as soon as I get it played out.

The timeline this month, like last, focuses almost exclusively on the maneuvering, battles, and logistics of the Second Sathar War. There are a few entries on the HSS History’s Hope but that is really the only not war related thread I’m tracking right now. This month saw a couple of battles. There was originally going to be one more but the UPF withdrew seeing as they faced almost certain destruction.

This month also sees the fast-track completion of pilots in the current class in the Gollwin Academy to service as pilots for all the new fighters coming out of the starship construction centers for the newly formed Frontier Fighter Corps. This is a process that will continue of the next several months until all the pilots are graduated or the class completes their current training.

There might be a bit of other, non-war stuff next month but not much. The next two posts after this one will be battle reports that I’ll get up as soon as I can. Depending on how those play out, there might not be much in the way of ships left to fight for a while so things will probably quiet down.

Date (FY)Events
61.326– Sathar SCC#4 (OFS111) completes 5 fighters.

– The K’aken-Kar assault scout jumps into its home system and begins decelerating toward Ken’zah-Kit.

– RG One settles into orbit around Zik-kit and joins up with the rest of PG Meteor already in orbit.
61.327SG Alpha jumps into the Fromeltar system and begins calculations for the jump to the Kizk-Kar system.  The pilot of the recently completed fighter takes on extra life support and begins boosting to join SG Alpha as it transits the system.
61.328– SBF-J1 arrives at SCC#3 (OFS138).  After a rapid reprovisioning, during which orders are issued to all existing sathar vessels, SBF-J1 departs the SCC and begins accelerating for a jump to the OFS137 system.

– Sathar EG-1 jumps out of the Liberty system but does not end up in the Waller Nexus system as expected.  Rather it overshoots and arrives in the Padda (FS11) system instead.  The astrogators begin working out where they are at.
61.329– SBF-J3 jumps into the OFS168 system and begins calculations for a jump to the OFS167 system.

– SBF-E3 arrives at Stenmar (Kazak) and merges with SBF-E2.

– The fighter in the Fromeltar system joins up with RG Alpha as it crosses the system for its jump to Kizk-Kar.
61.330– The HSS History’s Hope makes the jump and ends up in a binary system but it is not the two stars of YS07.  While the engineers start to work on the engine overhauls, the astrogators try to figure out where they are.

– The lone K’aken-Kar militia assault scout arrives back in its home system and the crew stands down for some leave but remain on alert for rapid recall if needed.
61.331– SG Alpha jumps into the Kizk-Kar system and begins deceleration toward Zik-Kit and PG Meteor.

– SBF-J3 jumps into the OFS167 system and begins calculations for a jump to OFS166.

– 2 UPF fighters are completed at both the Minotaur (Theseus) and Hentz (Arak) SCC and 2 more go into production in each location.  The fighters are temporarily manned by the local militias until UPF pilots and be dispatched to the system.
61.332Realizing that they need pilots for all the new fighters being produced, the current cadets at Gollwin academy are polled for volunteers for the Frontier Fighter Corps.  Those that volunteer are put on a fast completion track to get their Pilot and Rocket Weapons certifications.
61.333– SBF-J1 jumps into the OFS137 system and begins calculations for a jump to the OFS136 system.

– SBF-J3 jumps into the OFS166 system and begins calculations for the jump to FS33 to join up with SBF-B2.

– 11 UPF fighters are completed at the CDC shipyards (Triad, Cassidine).  With no pilots ready, they are put into storage and Spacefleet temporarily gives the space over for commercial ship maintenance.
61.334– A fighter and assault carrier are completed at SCC#10 (OFS174).  Instead of starting another AC and fighter, construction begins on 2 destroyers and a frigate.

– The new sathar assault carrier at SCC#10 (OFS174) collects the 3 fighters in the system and begins a transit to SCC#4 (OFS111). The ships are designated Transit Group (TG) 1.

– Astrogators aboard the HSS History’s Hope work out their position and discover that they went nearly twice as far as they intended.  The system is designated YS09 and they decide to take two smaller jumps to get back to YS07 to reduce the chance of error.  They begin working on jump calculations for an 8 ly jump to the next system.

– 3 more fighters are completed at the Hentz (Araks) SCC for the Frontier Fighter Corps, 2 more go into production, the other slot being given over to commercial ship maintenance for now.
61.335Initial calculations complete, the HSS History’s Hope begins accelerating for a jump to the first system on their way back to YS07, another binary system 8 lightyears away.
61.336– SBF-J1 jumps into the OFS136 system and begins calculations for a jump to the FS56 system.

– SG Alpha arrives at Zit-Kit (Kizk-Kar).  The fighters are stationed on the planet’s surface while the assault carrier begins preparations for a trip back to Prenglar to pick up more fighters.

– SBF-J3 jumps into the FS33 system and begins decelerating to join up with SBF-B2.

– 8 fighters are complete for the Frontier Fighter Corps at the PGC shipyard (Gran Quivera, Prenglar).  They are shuttled over to Gollwin academy to serve as trainers for the accelerated pilot classes.  Construction begins on 8 more.
61.337– The astrogators in sathar EG-1 are able to localize their position.  Being only a single jump from Theseus, they begin calculating a jump to that system first.

– SBF-E2 leaves orbit around Stenmar (Kazak) and begins accelerating for a jump to the Zebulon system and Strike Force Nova.

– SBF-B2 leaves orbit in the inner FS33 system and begins accelerating for a jump to the K’sta-Kar and Task Force Cassidine.  SBF-J3 changes course to meet them enroute.
61.338– After another 100 days of exploiting their secret jump route between Truane’s Star and Cassidine, Obar Enterprises has grossed another 1.47 million credits.  In the year since charting the route they have grossed over 6.8 million and paid off the loan on their new freighter.  Given the current crisis, they turn over the details of the jump route to Spacefleet.

– Initial jump calculations complete, sathar EG-1 starts accelerating for a jump to the Theseus system.
61.339– SBF-J1 jumps into the FS56 system and begins calculations for a jump to the Kizk-Kar system.

– SBF-J3 meets up with SBF-B2 enroute to K’sta-Kar and merges into that battle group.

– Another UPF fighter is completed at the Hentz (Araks) shipyard.  The extra capacity in the shipyard will be used for the next six days to accelerate construction on two of the other fighters to get all four fighters on the same schedule.
61.340– The HSS History’s Hope successfully jumps into their target system which they designate YS10.  They immediately begin working on engine overhauls and calculations for the 6 ly jump to return to YS07.

– The initial group of more advanced students at the Gollwin Academy (Morgaine’s World, Prenglar) complete their fast-track certification for the Frontier Fighter Corps.  The ten of them are dispatched to Triad to take command of some of the fighters there.
61.341SG Alpha jumps back into the Fromeltar system and begins calculations for a jump to Dramune.
61.342– SBF-J1 jumps into the Kisk-Kar system and begins decelerating to engage PG Meteor.

– SBF-E2 jumps into the Zebulon system and begins decelerating to engage Strike Force Nova.

– SBF-B2 jumps into the K’sta-Kar system and begins decelerating to engage Task Force Cassidine.

– The sathar battle fleets are detected within hours of their arrival in their respective systems and alerts go out across the Frontier.  Spacefleet is out gunned in nearly every case but is determined to stop the worms.

– Sathar EG-1 jumps into the Theseus system.  They immediately begin decelerating to stay in the outer system and begin working on calculations for a jump back to the Padda system.
61.343– Construction of the Spacefleet battleship, Admiral Dooltan, at the Pan Galactic starship construction center orbiting Gran Quivera (Prenglar) complete.  With the new sathar offensive, Spacefleet starts construction of a light cruiser, frigate, and assault scout.

– 2 assault scouts of the Theseus militia detect the sathar frigate of EG-1 and immediately begin boosting to intercept the ship.  An alert goes out and the other ships of the militia boost to intercept as well although they will be two days behind.

– Suspecting FS33 to be the origin of the sathar fleets jumping into the K’sta-Kar system, the K’aken-Kar militia assault scout starts working on calculations to chart a jump route to that system.
61.344– Construction of the Spacefleet battleship, the Admiral R’kazk’tar, at the Cassidine Development Corporation starship construction center orbiting Triad (Cassidine) completed.  The crew takes command of the ship and begins a short shakedown cruise in the system as they await the arrival of the fighter pilots and SG Alpha.

– With the completion of the Admiral R’kazk’tar, Spacefleet uses the space in the shipyard to begin construction of two destroyers and two assault scouts.

– With plans to send the Admiral R’kazk’tar to Truane’s Star, the Admiral Dooltan is ordered to the Fromeltar system and then on to Kisk-Kar to take command of Task Force Meteor if the patrol group survives the coming attack.

– Detecting the incoming militia assault scouts, sathar EG-1 change their deceleration profile to try to avoid the ships while they change direction for the return jump to Padda.

– Realizing that they have an opportunity to exploit the new jump route provided by Obar Enterprises, Spacefleet HQ orders Strike Force Nova and supporting militia ships to fall back to the Truane’s Star system and expect reinforcements.
61.345– The HSS History’s Hope successfully jumps back into the YS07 system.  They begin working on engine overhauls and calculations for a jump to return to YS08.

– SG Alpha jumps into the Dramune system and begins calculations for a jump to the Cassidine system.

– SBF-E2, detecting the departure of SF Nova, vector to follow them to the Truane’s Star system.
61.346– Unable to avoid intercept by the 2 Theseus assault scouts, the sathar frigate turns to engage them. They transmit all their jump data back to SBF-J2 before engaging. 

– Battle of Theseus – In a short, 20-minute battle, the sathar frigate managed to damage one of the assault scouts before being destroyed by a single volley of assault rockets and laser batteries from the 2 militia ships. The damaged assault scout heads to Minotaur for repairs.

– Calculations complete, the K’aken-Kar assault scout begins accelerating for a jump to FS33.

– Three more fighters for the Frontier Fighter Corp are completed in Theseus. Construction begins on 3 more.
61.347– Second Battle of Kwadl-Kit – Though outgunned by the sathar, Task Force Cassidine put up an amazing defense and over the course of 1.5 hours completely destroys the sathar fleet.  While almost no ship goes unscathed, they only lose 3 fighters and 3 assault scouts.

– SG Alpha jumps into the Cassidine system and begins vectoring for a jump to the Truane’s Star system using coordinates provided by battleship Admiral R’kazk’tar.

– After a detailed assessment of the strength of SFB-J1, PG Meteor and Spacefleet command decided that they cannot hold the Kizk-Kar system and the jump capable ships start accelerating for a jump to the Fromeltar system.  The fighters go into hiding on the planet’s surface.

– Seeing PG Meteor departing, the sathar forces vector to intercept but the acceleration of the UPF ships is such that only the smaller sathar vessels could intercept which would give the advantage to Spacefleet.  After a few hours of pursuit, they reverse course and settle into orbit once again around Zit-Kit.
61.348– Sathar SCC#1 (OFS203) completes construction of a light cruiser.

– Arriving back at Minotaur (Theseus), the damaged militia assault scout is immediately put into the shipyard.  A HS:7 ship under construction is moved out to make room.

– 5 fighters are completed at the CDC shipyards (Triad, Cassidine).  Work begins on five more.  These fighters are put in storage until crews can be obtained for them.
61.349– SF Nova and its supporting militia ships jump into the Truane’s Star system and begin decelerating toward Pale.

– The group of 10 FFC pilots arrive at Triad (Cassidine) and take command of their fighters. They immediately take on extra life support and begin a high-g boost, together with the battleship Admiral R’kazk’tar, to join SG Alpha.

– After a day rearming, Task Force Cassidine begins acceleration for a jump to the K’aken-Kar system and then on to Kizk-Kar to engage the sathar forces there.

– The Theseus militia assault scout completes its repairs and the HS:7 ship is moved back in to resume work.

– The battleship Admiral Dooltan jumps into the Cassidine system, it remains at high speed to transit to Dramune.
61.350– Joining up with SG Alpha, the fighters are quickly taken aboard the carrier and stowed for jump.  The battleship, assault carrier, and fighters are designated Task Force Relief and prepare for level 2 risk jump to the Truane’s Star system.

– SBF-E2 jumps into the Truane’s Star system and begins decelerating toward New Pale.  SF Nova and the local militia begin maneuvering to intercept.

– SBF-J1 departs orbit around Zit-Kit (Kisk-Kar) and begins accelerating for a jump to the K’aken-Kar system to intercept TF Cassidine.

– Detecting the departure of SBF-J1, PG Meteor puts its jump on hold and drifts in the outer system to observe.

– The UPF minelayer, currently in the Fromeltar system, begins accelerating for a jump to the Kisk-Kar system.  It will join up with the Admiral Dooltan as it transits the Fromeltar system before making the jump.
61.351– TF Relief jumps into the Truane’s Star system and begins a hard deceleration toward New Pale.

– The K’aken-Kar militia assault scout misjumps and instead of reaching FS33 ends up in an unknown star system (OFS169).  They begin working on determining their location.

– With a HS:12 ship completing maintenance in the CDC (Triad, Cassidine) shipyards, Spacefleet starts work on 3 new assault scouts to replace those lost by Task Force Cassidine.  The remaining space is used for civilian ship maintenance.

– The battleship Admiral Dooltan jumps into the Fromeltar system.  It begins vectoring and performing jump calculations to take it to Kisk-Kar.
61.352– The HSS History’s Hope makes the return jump to YS08 and begin decelerating toward the inner system as they once again overhaul engines and try to plot the route back to YS07.

– Seeing that SBF-J1 seems to be committed to jumping out of the Kisk-Kar system, PG Meteor changes course and starts to decelerate back toward Zit-Kit.

– A fighter is completed at the PGC shipyards (Gran Quivera, Prenglar).  It is transferred to Gollwin Academy (Morgaine’s World, Prenglar) for use in training the accelerated cadets.

– Detecting TF Relief, the sathar reassess their position and despite being out gunned nearly two to one, press on toward New Pale and the UPF forces.
61.353– Strike Force Nova and the Truane’s Star militia ships arrive back at the armed station orbiting New Pale (Truane’s Star).  Just hours later, they are joined by TF Relief.  The incoming sathar ships are only a day away.

– The UPF minelayer in the Fromeltar system joins up with the Admiral Dooltan and then continue on their way to the Kisk-Kar system to join with PG Meteor.
61.354– Second Battle of New Pale – The UPF destroy or drive off most of SBF-E2 but both battleships, including the newly constructed Admiral R’kazk’tar, are destroyed in the fighting.

– The fleeing sathar ships accelerate for a jump back to the Zebulon system.

– The UPF destroyer damaged in the Second Battle of New Pale heads to the starship construction center on Pale for repairs.

– TF Cassidine jumps into the K’aken-Kar system.  Alerted that SBF-J1 is headed their way, they begin decelerating toward the inner system instead of continuing on the Kisk-Kar.

– Another UPF fighter is completed at the Terledrom (Fromeltar) shipyard.  It is temporarily manned by militia forces until Spacefleet can get fighter pilots to the system.
61.355– SBF-J1 jumps into the K’aken-Kar system and begins decelerating to intercept TF Cassidine.

– The UPF battleship and minelayer jump into the Kisk-Kar system and start decelerating toward Zit-kit.

– The damaged UPF destroyer arrives at the Streel shipyard (Pale, Truane’s Star).  A HS:6 ship under construction but nearly complete is temporarily moved out to provide priority access for the Spacefleet vessel.
61.356– PG Meteor arrives back in orbit around Zit-Kit (Kisk-Kar).

– A HS:5 ships complete maintenance in the CDC shipyard (Triad, Cassidine). Spacefleet holds the space in anticipation of more ships finishing and beginning construction on a new battleship.

Full timeline file:

DetailedFrontierTimelineDownload
February 9, 2021 Tom Leave a comment

Detailed Frontier Timeline – FY61.294 to FY61.325

A new year and here’s the recap of the details happening in the Frontier over the past month.

The beginning of the month was the final battle of the initial sathar foray into the Frontier. There could have been a couple more but the sathar, being significantly outgunned, decided to fall back and retreat. Another sathar starship construction center joins the war effort and this month sees a lot of repositioning of ships as well as reclaiming control of the Liberty system. The sathar are getting ships into position for another major push in the coming month.

Early in the month, I started reporting all the movement of ships in and out of the UPF starship construction centers as Spacefleet took control of their operations. By mid-month, I realized that was a little much and scaled it back only reporting ships completed or started for Spacefleet and the militias. All the commercial construction and maintenance will not be mentioned.

Date (FY)Events
61.295– The HSS History’s Hope safely arrives in YS06 and begin working on a jump to the YS07 system.

– The CMS Osprey arrives back at Clarion and is quickly admitted into the shipyards for repair.

– TF Cassidine jumps into the K’aken-Kar system and begins decelerating toward Ken’zah-Kit.  Once again they won’t make the initial engagement arriving a few days too late.  However, they are determined to stop the sathar here if PG Meteor and the militia ships cannot.

– 15 HS of space opens in the CDC shipyards (Triad, Cassidine). Spacefleet starts construction on another light cruiser to finish filling the holes in their ranks and allows the Truane’s Star militia to begin construction of a final assault scout.
61.296– With the loss of the Liberty system, and the massive losses in the initial foray into the Frontier, sathar forces and production from SCC#10 are committed to war effort against the Frontier.  This adds 9 fighters, 3 FF, 5 DD, 3 LC, 2 HC, and 2 AC to the sathar roster in addition to the SCC’s production capacity.

– The CMS Osprey emerges from the Clarion shipyards fully repaired and ready for action once again.  A small HS:4 yacht is moved in the SCC for maintenance.

– Battle of Ken’zah-Kit (K’aken-Kar) – The sathar obliterate the station with a single concentrated barrage but then are quickly destroyed by the combined UPF and militia forces.  Besides the station, only a single militia assault scout was lost with damage to three other ships that will require time in a shipyard to repair.

– Sathar SCC#4 (OFS111) completes construction of a new frigate.

– Realizing that SF Nova will reach New Pale in time for the battle, and having a nearly 2:1 hull disadvantage against SF Nova, PG Virgo, and the remaining Truane’s Star militia, SBF-E2 reverse course and start plotting a jump back to Zebulon.

– 12 HS of space opens up in the CDC SCC (Triad, Cassidine).  Construction is begun on two new assault scouts to replace those lost by the Kizk-Kar militia.  The remaining space is given over to a HS:6 ship for annual maintenance.

– 22 HS of space opens up in the PGC shipyards (Gran Quivera, Prenglar).  With Spacefleet’s immediate needs being met, they move two HS:11 ships in for maintenance.
61.297– SF Nova arrives in orbit around New Pale.  The crew spends the day resting from their hard trip as they watch the sathar begin to fall back.  The remaining ships of PG Virgo are absorbed into the Strike Force.

– The White Light militia jumps back to their home system and begins deceleration toward Clarion.

– The UPF minelayer jumps into the Fromeltar system and begins decelerating to join up with the militia forces holding that system.

– With the loss of SBF-C1 in the K’aken-Kar system, and recognizing that they are out gunned by the UPF forces there, SBF-B2 does not jump to K’aken-Kar but begins decelerating back toward Kawdl-Kit in the K’sta-Kar system.

– With its engines repaired, SF Nova’s assault carrier, together with its four surviving fighters, begin a high-speed jump to catch up with the main group.  At the same time PG Virgo’s carrier, leaving its 3 fighters behind, begins a transit back to Prenglar.

– The newly constructed sathar frigate at SCC#4 (OFS111) begins a transit to SCC#5 (OFS019)

– SBF-J1 (1 AC, 1 HC, 2 LC, 1 DD, 1FF, & 8 fighters) departs SCC#10 and begins a high-speed transit that will eventually take it to K’sta-Kar.

– SBF-J2 (1 HC, 1 LC, 3 DD, 2 FF) departs SCC#10 and begins a high-speed transit to the Liberty system.

– 8 HS of space opens in the Hentz (Araks) SCC for a total of 9 HS of open space.  A small HS:9 freighter is moved in for maintenance.

– SBF-E1 jumps back into the Kazak system.  They do not slow down and start plotting a jump back to SSC#5 in the OFS019 system.

– An additional 13 HS of space opens in the Hentz (Araks) SCC.  A HS 11 mining ship is moved in for annual maintenance.
61.298– After rearming the ships in the K’aken-Kar system, TF Cassidine and PG Meteor begin accelerating for a jump to the K’sta-Kar system to confront SBF-B2 or drive it out of the system.

– The damaged ships (a frigate & assault scout from PG Meteor and the surviving K’aken-Kar assault scout), designated Repair Group (RG) One are ordered to Fromeltar for repairs. They begin accelerating for a jump to Kizk-Kar.

– 13 HS of space opens in the PGC shipyards (Gran Quivera, Prenglar).  A HS:12 ship is moved in for maintenance.
61.299A small group of 8 civilian privateer vessels, hailing from the yazirian worlds of the Frontier and calling themselves the Yazira Squadron, arrive in orbit around Morgaine’s World (Prenglar) and request permission to assist Starfleet in the fight against the sathar.
61.300– The HSS History’s Hope arrives in the YS07 system and begins decelerating toward the inner system.  Back at the last system explored, they plan to spend a few days resting here before starting to chart new routes toward their destination.

– SBF-E2 jumps back into the Zebulon system and starts decelerating toward Volturnus.

– SBF-B2 settles back into a high orbit around Kawdl-Kit (K’sta-Kar).

– SBF-E1 jumps back into the OFS019 system and begins decelerating toward the starship construction center there for repairs.

– 8 HS of space opens in the PGC shipyards in Gran Quivera (for a total of 9 HS of space available).  A HS:9 ship is moved in for maintenance.
61.301– Worried that since the sathar have a route into Prenglar they may also have one to Gruna Garu, Spacefleet sends the Yazira Squadron back to Gruna Garu to bolster the defenses there.

– With the sathar mostly on the retreat at the moment, and based on the success of the fighters and assault scouts in the recent engagements, Spacefleet announces the creation of the Frontier Fighter Corps with a plan to station multiple squadrons of fighters in every system of the Frontier.

– As the first step of implementing the Frontier Fighter Corps, all currently available space in the Type I and II shipyards around the Frontier are used to start construction of new fighters.  At the moment that means 2 are started in Hentz (Araks) and 2 in Minotaur (Theseus).
61.302– The White Light militia arrive back in orbit around Clarion.

– The UPF minelayer arrives in orbit around Terledrom, joining up with the Fromeltar and Dramune militias.

– SF Nova’s Assault carrier jumps into the Dixon’s Star system and starts working on calculations for the jump to Truane’s Star.  The carrier leaving PG Virgo also arrives in the system and starts working on calculations for the jump to Prenglar.

– The lone sathar frigate jumps into OFS110 and begins calculations for a jump to OFS022.

– SBF-J1 jumps into the OFS170 system and begins calculations for a jump to OFS169.

– SBF-J2 jumps into the OFS177 system and begins calculations for a jump to the Dayzer system (OFS178).

– Sathar SCC#5 (OFS019) completes construction of a cutter.
61.303– SBF-J1 jumps into the OFS169 system and begins calculations for a jump to the OFS167 system.

– Task Force Cassidine and PG Meteor jump into the K’sta-Kar system and begin decelerating toward the sathar forces orbiting Kawdl-Kit.

– RG One arrives in the Kizk-Kar system and begin engine overhauls and plotting a jump to Fromeltar.

– 11 HS of space open up in the Triad (Cassidine) SSC.  Work is begun on 11 fighters for the newly formed Frontier Fighter Corps.  There are complaints that over half the SCC’s capacity are being used for Spacefleet but Spacefleet points out that some of that usage if for planetary militias as well.

– Deciding not to wait any longer, two HS:6 ships under construction in the Pale SCC (Truane’s Star) are moved out of the shipyard by Spacefleet to make room for the damaged light cruiser.
61.304– The crew of the HSS History’s Hope start working on the next jump in their journey to a small red dwarf star.  It’s a long one, just under 12 light years long jumping a big void of stars in this region of space.  They designate their target system YS08.

– Detecting the inbound UPF forces, and recognizing that they are still outgunned, SBF-B2 decides to abandon K’tsa-Kar. They break orbit from Kawdl-Kit and begin accelerating to jump out of the system.

– 13 HS of space opens up in the Hentz (Araks) shipyard.  Two HS:5 ships are moved in for maintenance and work begins on constructing 3 new fighters.

– 4 HS of space opens up in the Clarion (White Light) shipyard and a small HS:4 ship is moved in for maintenance.

– The sathar SCC#10 (OFS174) completes construction of a fighter.
61.305– SF Nova’s assault carrier jumps into the Truane’s Star system and begin deceleration toward the rest of the Strike Force.

– The lone sathar frigate jumps into OFS022 and begins calculations for jump to OFS018.

– SBF-E1 arrives back at SCC#5 (OFS019) and is disbanded.  The work halts on the heavy cruiser currently under construction and the damaged frigate and destroyer enter the shipyard for repairs.

– 6 HS of space opens up in the CDC SCC (Triad, Cassidine), with another 17 HS opening up tomorrow, the space is held to allow some larger ships to move in for maintenance.

– 9 HS of space opens in the Terledrom (Fromeltar) SCC.  With RG One only a few days away, the space is held for those ships so that battle repairs can begin immediately when they arrive.
61.306– SBF-J1 jumps into the OFS167 system and begins calculations for a jump to the OFS166 system.

– SBF-J2 jumps into the Dayzer system (OFS178) and begins calculations for a jump to the OFS179 system.

– 11 HS of space opens in the PGC shipyards (Gran Quivera, Prenglar).  Spacefleet begins construction of 8 fighters and an assault scout using the available space.
61.307– The lone sathar frigate jumps into OFS018 and begins calculations for jump to OFS019.

– The damaged sathar destroyer under repair at SCC#5 (OFS019) is finished and emerges from the shipyard ready for battle.

– SF Nova’s assault carrier arrives in orbit around Pale and rejoins the fleet.  It collects the fighters left by PG Virgo as part of its compliment.

– The assault carrier from PG Virgo arrives back at Morgaine’s World (Prenglar).  The crew is debriefed on their trip to the Rim and recent battle at New Pale (Truane’s Star).

– After four days of round-the-clock work by the engineers from the Pale SCC and SF Nova, the light cruiser emerges from the Streel shipyards fully repaired and ready for action.  The two ships that were moved out to make room resume construction.
61.308– SBF-J1 jumps into the OFS166 system.  Upon arrival, their orders are changed, and they are ordered to proceed to SCC#3 (OFS138) instead of heading into K’tsa-Kar.  They begin plotting a jump to OFS157.

– RG One arrives in the Fromeltar system and begins deceleration toward the shipyards at Terledrom.

– Task Force Cassidine and PG Meteor arrive in orbit around Kawdl-Kit, much to the relief of the planet’s populace.

– The damaged sathar frigate under repair at SCC#5 (OFS019) is finished and emerges from the shipyard ready for battle.  The damaged heavy cruiser is moved in to begin the extensive hull repairs it needs.
61.309– SBF-J2 jumps into the OFS179 system and begins calculations for a jump to the Liberty system (FS30).

– SBF-B2 jumps into the FS33 system and begins decelerating.

– After two days rest, the assault carrier at Morgaine’s World (Prenglar) is ordered to Triad (Cassidine) to await completion of the first fighters for the Frontier Fighter Corps and then to shuttle them to the Kizk-Kar system.  It is designated Shuttle Group (SG) Alpha.

– 18 HS of space opens in the Hentz (Araks) SCC.  A HS 14 ship is moved In for maintenance.  Another fighter is started for Spacefleet and the remaining space is held for an upcoming ship maintenance.
61.310– Jump calculations complete and verified, the HSS History’s Hop starts accelerating for the jump to YS08.

– Yazira Squadron arrives back in the Gruna Garu system where they join up with the local militia to coordinate the defense of that system.

– Strike Force Nova, together with the remaining ships of the Pale militia, leave Fortress Pale and begin accelerating toward the Zebulon system to engage the sathar forces now orbiting Volturnus.
61.311– The lone sathar frigate jumps into OFS019 and begins decelerating toward SCC#5.

– SBF-J1 jumps into the OFS157 system and begin calculations for a jump to the OFS156 system.

– With the sathar apparently gone from the system, PG Meteor is ordered to the Kizk-Kar system where they will be supported by the fighters being delivered by SG Alpha and joined by their flagship, the battleship Admiral R’kazk’tar which will be completed in 33 days.
61.312SBF-J2 jumps into the Liberty system and begins decelerating toward Snowball.
61.313– PG Liberty and the Mhemne belters detect the sathar ships that have arrived in the system.  An alert is immediately sent out to Spacefleet alerting them of the sathar presence.

– RG One arrives at the Terledrom shipyards (Fromeltar).  The militia assault scout and UPF frigate are immediately moved into the shipyard to begin repairs.

– SBF-J1 jumps into the OFS156 system and begins calculations for a jump to the OFS155 system.
61.314– SBF-B2 arrives in the inner system of FS33 where they await orders from the sathar high command.

– Recognizing that they are no match for the inbound sathar forces, PG Liberty, with the assistance of the Mhemne belters, go into hiding in the Liberty system to watch the sathar’s movements.  Evacuations begin immediately on the L4 and L5 stations.

– Receiving the alert from PG Liberty, the Theseus militia ships in the White Light system depart Fortress Redoubt and begin accelerating for a jump home.
61.315– The HSS History’s Hope successfully jumps into the YS08 system.  They begin decelerating toward the inner system and working on engine overhauls.

– SBF-J1 jumps into the OFS155 system and begins calculations for a jump to OFS150.

– SF Nova and the Pale militia jump into the Zebulon system and begin decelerating toward Volturnus and the sathar forces.

– The K’akan-Kar militia assault scout completes its repairs in the Terledrom (Fromeltar) SCC.  As it emerges the UPF assault scout is moved into its place.
61.316– The sathar frigate arrives at SCC#5 (OFS019) joining up with the other ships there.

– SBF-J2 arrives in orbit around Snowball and finding the L4 station abandoned settle back into the berths there. 

– Detecting SF Nova, SBF-E2 decides to avoid engagement and departs Volturnus and begins accelerating for a jump to the Kazak system.

– PG Meteor jumps into the K’aken-Kar system and begins working on calculations for the jump to Kizk-Kar.

– The UPF frigate and assault scout complete their repairs in the Terledrom shipyard and emerge once again ready for combat.  A HS:6 ships is moved in for maintenance and Spacefleet begins construction of 3 fighters.
61.317RG One, now fully repaired, departs Terledrom for the Kizk-Kar system.  The  Spacefleet vessels will remain in that system to await the arrival of the rest of PG Meteor while the militia ship will return to its home system.
61.318– SBF-J1 jumps into the OFS156 system and begins calculations for a jump to the OFS146 system.

– SG Alpha arrives in orbit around Triad (Cassidine) just in time to pick up the five fighters completed in the CDC shipyards.  The fighters are taken aboard the assault carrier which prepares to depart for the Kizk-Kar system the next day.  Construction begins on five more fighters.

– After two days in the Liberty system, with no indication of any UPF presence, the heavy cruiser and 3 destroyers of SBF-J2 split off (now SBF-J3) and begin accelerating for a jump back to OFS179 leaving the light cruiser and 2 frigates in the system.
61.319– Arriving at the inner system of YS08, the crew of the HSS History’s Hope begin working on calculations for the return jump to YS07.

– Taking several days longer than expected, the damaged sathar heavy cruiser emerges from SCC#5 (OFS019) fully functional once again.  The hull of the heavy cruiser whose work was paused is moved back into the shipyard to resume construction.
61.320– SBF-J1 jumps into the OFS146 system and begins calculations for a jump to SCC#3 (OFS138).

– SF Nova arrives and settles into orbit around Volturnus (Zebulon).

– PG Meteor arrives in the Kizk-Kar system and begins decelerating toward Zik-Kit.

– SBF-E3 (1 C, 1 FF, 1 DD, 1 HC) departs SCC#5 (OFS019) for a jump to Kazak to join up with SBF-E2.
61.321SBF-E2 jumps into the Kazak system and begins decelerating toward Stenmar.
61.322– RG One arrives in the Kizk-Kar system and the Spacefleet vessels start decelerating toward Zik-Kit while the militia assault scouts remains at speed and prepares for a jump back to its home system of K’aken-Kar.

– A fighter for the Frontier Fighter Corp is completed in the PGC shipyards (Gran Quivera, Prenglar) and construction begins immediately on another.
61.323– The Theseus militia arrive back in orbit around Minotaur.

– SG Alpha jumps into the Dramune system and begins calculations for a jump to Fromeltar.

– SBF-J3 jumps into the OFS179 system and begins calculations for a jump to the OFS168 system.

– One of the sathar frigates in the Liberty system begins accelerating out from the inner system and appears to be on a course to jump to the Waller Nexus system. It is designated EG-1. PG Meteor could intercept from their hiding place in 2 days.

– Detecting the outbound sathar frigate, PG Liberty notifies Spacefleet and are told to let it pass but take it out if it returns to the system.
61.324– SBF-J1 jumps into the OFS138 system and begins deceleration toward SCC#3.

– PG Meteor arrives in orbit around Zik-Kit (Kizk-Kar).

– A UPF fighter is completed in the Terledrom (Fromeltar) shipyards and construction begins immediately on another.
61.325– Calculations complete, the HSS History’s Hope stars accelerating for the jump back to YS07.

– SBF-E2 arrives in orbit around Stenmar (Kazak).

– SBF-E3 jumps into the Kazak system and begins decelerating toward Stenmar and SBF-E2.

Here’s the full timeline PDF for download:

DetailedFrontierTimelineDownload
January 5, 2021 Tom 1 Comment

Thoughts on the Second Sathar War

Obviously, as I’ve been playing through the battles and coordinating the movements of the UPF and sathar forces for the Detailed Frontier Timeline, the events and conditions surrounding the Second Sathar War have been on my mind. A lot.

While the rules in the Knight Hawks Campaign Books are really geared around a balanced war game, I’ve been porting the scenario over more to the RPG side and looking at it from that perspective. In this post, I thought I’d collect some of the ideas I’ve had along the way. The topics are not necessarily connected or in any particular order but all relate to the how the Second Sathar War would impact or play out in the Frontier. So let’s get started

The Rim

I already mentioned this in one of the battle reports, but I’m not really considering the Rim in my narrative beyond the two battles I’ve already reported. I’ve never sat down and worked out the starship construction capabilities of the Rim, the order of battle for the Flight (the Rim’s version of Spacefleet), or any of those logistical considerations.

When I set this scenario up, literally decades ago, I didn’t have a copy of Zebulon’s Guide so the Rim was never in my considerations. Since I’m really just playing out that setup from so many years ago, and I never did the background work necessary for the Rim, they just weren’t part of the plan. I’m really just assuming that their fortunes go the same as in the Frontier.

Civilian and Megacorp Ships

I think handling these other Frontier ships is the biggest issue that moving this from a war game over to the RPG side of things needs to consider and I’m not sure how I’m going to address it completely yet.

In looking at starship construction based on the listed starship construction centers in the Frontier, I’ve estimated that without any changes to the SCCs, there are probably about 2300 ships flying around the Frontier, which is probably low. But let’s use that number to start.

There are 23 worlds in the Frontier (including Volturnus), so if you just divide those ships out, that’s about 100 ships per world. That probably shifts around a bit, for example, Laco, in Dixon’s Star, is an outpost world with very low population, so it probably doesn’t have as many ships. Neither would Volturnus. And the more heavily populated worlds probably have a little more. Morgaine’s World in Prenglar is also an outpost but since that’s the home of Spacefleet, I give them just as many ships as at least a medium population planet and say that those are all the Spacefleet ships.

Plus there are the ships that the megacorps own. We know that Streel and Pan Galactic have military ships, it stands to reason that WarTech and CDC do as well and I even gave some to Trans Travel in my timeline. So some fraction of those 2300 ships are going to be military vessels owned by the megacorps. All of which could do some damage to sathar ships invading a system.

Finally, and what I really want to focus on, is that given that piracy is a concern for ships in the setting, even the “non-military” ships are going to be armed to some extent or another, even if it is just a laser battery or three on any ship HS 6 or larger.

Let’s assume for a minute that every ship in the Frontier has at least a laser battery. Now some won’t have any weapons but others will have more than one so it probably all averages out. What happens if 50 of these ships decide to not sit idly by while Spacefleet dukes it out out with the sathar but join the fight?

First, lets just look at the “average” hull damage done by a laser battery. On the damage table, there is a 10% change of double hull damage, a 35% chance of regular hull damage and a 55% chance of damaging some other system. The laser battery does 1d10 damage for an average of 5.5 hull points of normal damage and 11 points when double damage is called for. Multiplying that out by the percentage that they occur means that on average, ignoring the damage from system hits, a hit by a laser battery does 3 HP of damage (11 points 10% of the time, 5.5 points 35% of the time and 0 points 55% of the time).

At an average of 3 HP of damage per hit, 14 hits kill a frigate, 17 kill a destroyer, 24 kill a light cruiser, 25 kill an assault carrier, and 27 kill a heavy cruiser. Do you see where this is going?

The next question is how often do these laser batteries hit? The base “average” chance to hit with a laser battery is 50%. But since laser batteries suffer from range diffusion, it’s only that high if the ships are within 10,000 km (1 hex on the game map) of each other. Getting that close means that the sathar can use their rocket batteries and torpedoes against you if they want and since these are civilian ships, we’ll assume they try really hard to stay out of the range of those weapons. So they shoot from 50,000 km (5 hexes) away and have a chance to hit of only 25%. Which means that the average laser battery shot, factoring in the miss rate, does a little over 0.75 HP of damage any given round.

That doesn’t seem like a lot, but remember that is an average taking into account of all the probabilities and that is per ship. So let’s look at those 50 ships. If you take 50 ships, each doing ~0.75 HP each time they fire, you have a combined damage output of 37-38 HP. And since the laser battery can fire both offensively and defensively, that doubles to about 75 HP each round of combat. That’s enough damage to take out any single ship expect a heavy cruiser.

And the truth is, that there is a good chance that the HP damage output is actually larger. We have 100 shots (50 ships, 2x each) at 25% to hit. So 25 of those shots hit the target. 11.25 (45%) of those do hull damage while the other 13.75 (55%) do system damage. But if the system damage results calls for a hit on a system already destroyed, you get hull damage instead. Some of those system hits are going to shift over to the hull side and increase the damage. (I really should write a program to analyze this and get the actual numbers.)

The bottom line is that in any give turn, that swarm of civilian ships could take out any one large sathar ship, two frigates, or a swarm of fighters.

From the sathar side, there is really nothing you can do about this. You are looking at 25-50 targets (depending on how you distribute the laser batteries), each with 30 or more HP, and taking out 2 or 3 each round is not going to make much difference in their damage output. They will overwhelm you with sheer numbers. Death by a thousand cuts.

This is something that the war game doesn’t have to deal with but which will definitely come into play in an RPG-level look at the conflict. Maybe the civilian and mega-corps ships won’t get involved. But if their worlds are threatened, I don’t really see them not stepping up, at least a good number of them. And what if Spacefleet calls for a 3rd Common Muster? (There has to be something in the UPF charter about that.) Then they will be involved. The sathar are going to need more ships.

Starship Construction Centers

In the war game, ship construction and replacement is very abstracted. Every 20 days, the UPF get 2 fighters and/or assault scouts for each fortified station on the map and a capital ship for every fortress. The sathar just have a base 35% chance to replace every ship lost in the previous 20 days.

A big part of this project for me was to see how using the starship construction rules, combined with the distribution of UPF starship construction centers, and giving the sathar some SCCs as well, would play out in the logistics of what ships were available for combat. I knew this would drag things out as you couldn’t replace ships that quickly but wanted to see what would actually happen. We’ll find out as this plays out.

But, as the first battles have been fought, and the UPF is looking to replace ships, I started really looking at the distribution of the SCCs in the Frontier. Until now I had just taken them for granted and not though much about it. And for the most part, the type of construction center and its location make sense for the SCCs described in the book. Analyzing that (and maybe reorganizing them) may be another post in the future. But three of the SCCs stood out as a little odd. Let’s look at those from least troublesome to most (in my opinion).

Clarion (White Light)

This is a Type III SCC which means it can have up to 20 hull sizes (HS) of ships under construction but they cannot be military vessels and cannot have atomic drives.

To me, this feels a little bit odd. White Light is the nexus for jumps to four different systems so it’s a major hub system (and the only access to Theseus). Maybe because it is the setting for the Warirors of White Light adventures but it seems to me that there should be a more major construction center here.

However, with the Type II center just a system away in Theseus, and the fact that the main output of the planet is resources, not industrial products, maybe having a small shipyard is okay even if the planet does have a high population and is a major crossroads.

Outer Reach (Dramune)

Like at Clarion, the Outer Reach shipyard is a Type III SCC. There are a couple of things that stand out for me here.

One is the lack of an SCC at Inner Reach. Given the animosity between the two worlds, which is part of the canon background material before you even factor in the events of the Dramune Run module, and the fact that animosity has erupted into fighting in the past, if Outer Reach has a SCC, I would expect Inner Reach to have one as well. I don’t see them being willing to wait for ships to come in from Fromeltar or Cassidine, they would want to be able to build them themselves.

The other issue I have is the SCC class. As a Type III SCC, this shipyard is not supposed to have the capability to produce military vessels or ones that use atomic drives. But since this world is the home of a major crime syndicate, and supplies and supports pirates, I see this shipyard as where many of those pirate vessels, which are assault scouts, corvettes, and frigates, are created. Thus the shipyard can obviously handle military class vessels and atomic drives and should really be a Type II.

Because of this, for the Second Sathar War, I’m classifying this shipyard as a Type II-s (the s is for small). It can still only handle 20 HS of ships total like a Type III SCC, but like a Type II, can build ships with atomic drives and military ships up to HS 6 (i.e. destroyers).

Pale (Truane’s Star)

This is the one that baffles me the most. The rules say that this is another Type III shipyard. Pale is classified as a medium population, which tends to indicate a smaller shipyard, but its main economies are industry and resources, which would lend itself to ship building and therefore a larger SCC. Having a Type III SCC here just doesn’t make sense to me for a couple of reasons.

First, everyone knows that the sathar have a jump route into the Frontier that goes through Truane’s Star. This was the locus of the First Sathar War that resulted in the founding of the UPF. Spacefleet has a fortress here, it would stand to reason that there should be a good shipyard to build up ships here as well.

Second, and more important to me, this is the world where Streel is headquartered. We know they make ships, the corvette is designed by them, and they have a number of ships to fight against the ships of the Pan Galactic Corporation in the corporate wars. Assuming the shipyard at Gran Quivera (Prenglar) is owned by PGC where they have their headquarters, and the one at Triad (Cassidine) is owned by the Cassidine Development Corporation where they have theirs, if the #1 and #3 megacorps have Type I SCCs, then the #2 megacorp should have at least a Type II shipyard, If not a Type I. It’s a matter of corporate pride and sustainability. I mean, if they don’t have their own shipyard, PGC and CDC could just deny building them ships and they’d have to travel even farther afield to Hentz or Fromeltar to get ships build. It just doesn’t make sense.

I’m leaving it as a Type III SCC for the Second Sathar War in the timeline, but if I ever revisit the SCC distribution in the Frontier, I think Pale will be getting a bigger one.

Other Thoughts

It seems I had one more item that I wanted to talk about but it is slipping my mind at the moment and I didn’t write it down when the idea occurred to me to write this post a week or so ago. If it does come back to me, I’ll have a topic for a future post.

Overall, the sathar did not fare too well in their initial foray into the Frontier. In fact, if this was just the war game, they may very well have lost the game as I believe every retreat condition that the sathar players could have chosen have been met. Although if I was using those retreat conditions, I probably would have set things up a little differently and made a few different choices. However, I’m not using those conditions directly and the sathar have another wave of ships coming later this month. After that, however, it might be a while as they rebuild their forces.

This post has given me the idea for a few other posts that may show up in the future. The first looking at the distribution of starship construction centers in the Frontier (and probably the Rim) and another looking at the average damage output by the different ship types. The third one would be a look at exactly what is in the UPF Charter. We’ll see when or if those actually materialize.

Have you ever tried to incorporate, in detail, the Second Sathar War into your campaign? What assumptions did you make and what ideas did you incorporate? What other ideas should I consider? Let me know in the comments below.

December 8, 2020 Tom 3 Comments

Detailed Frontier Timeline – FY61.265 to FY61.294

This months sees the opening battles of the Second Sathar War. Maneuvers and engagement from this conflict overshadow nearly everything else happening in the Frontier as everyone watches the events unfold.

It is this conflict that I originally started this timeline to track so it will be heavily focused on the events of the battles and how the sides react for the next little while. Also things get really busy so there are a lot of entries every day this month. I think there are only 2 or 3 days that don’t have at least two entries and toward the end when the invasion starts, it’s rare to have a day with less than 5 or 6 entries. Links to battle reports on all the ship engagements are linked in the timeline.

On day 61.280, the arrivial of Strike Force Nova in the Prenglar system on the same day as the sathar fleet was pure coincidence. I had planned out the maneuvers of SF Nova separately from the sathar movements without consulting between the two. I was completely surprised when they ended up jumping in on the same day.

Settle in. This one is a bit of a read.

Date (FY)Events
61.265– After eight days of exercises with the crews of Fortress Kdikit, SF Nova departs Kdikit (Madderly’s Star) for a jump to Triad (Cassidine).

– PG Virgo arrives in the Zebulon system and begins work for the jump back to Pale (Truane’s Star).
61.266– Sathar Fleet SBF-C1 (1 HC, 1 LC, 2 DD, & 1 FF) departs SCC#3 (OFS138) and begin accelerating for a jump to the OFS137 system.

– PG Liberty arrives at Snowball (Liberty) and joins up with PG Lancet.  The assault scout in PG Lancet is transferred to PG Liberty, with the UPFS Flying Cloud (frigate), UPFS Eleanor Moraes, and UPF Backdoor (sathar scout ship) remaining attached to PG Lancet.
61.267– The SF Meteor destroyers arrive at Lossend (Timeon).

– The CMS Osprey arrives back at Clarion.  The ship is immediately put into the starship construction center for maintenance, repairs, and refits while the crew is given some much needed leave.
61.268– Sathar Fleet SBF-B1 (1 HC, 1 LC, 2 DD, & 1 FF) departs the rendezvous point in OFS167 and begins accelerating for a jump to the OFS166 system.

– The HSS History’s Hope and escorts jump into the OFS222 system.  They begin work on engine overhauls and jump calculations for the YS01 system.
61.269– The SF Meteor destroyers depart Lossend (Timeon) and begin accelerating for a jump to the White Light system.

– After three days debriefing the commander of PG Liberty and introducing him to the Mhemne contacts, Captain Reider and PG Lancet depart Snowball (Liberty) for a jump back to the Waller Nexus system and a high speed transit to Minotaur (Theseus).
61.270– Sathar Fleet SBF-A1 (2 HC, 2AC, 1 LC, 4 DD, 2 FF & 14 fighters) departs SCC#1 (OFS203) and begin accelerating for a jump to the FS12 system.

– PG Virgo arrives in the Truane’s Star system and begins decelerating toward Fortress Pale (Pale, Truane’s Star).
61.271-= Sathar Fleets SBF-E1 (1 HC, 1 LC, 2 DD, & 1 FF) and SBF-F1 depart SCC#5 (OFS019) and begin accelerating for a jump to the Kazak system in the Rim.

– Sathar fleet SBF-C1 arrives in the OFS137 system.  It maintains its high speed and begins calculations for a jump to OFS136.
61.272– Sathar Fleet SBF-D1 (1 HC, 1 LC, 2 DD, & 1 FF) departs SCC#4 (OFS111) and begins accelerating for a jump to the OFS020 system.

– The HSS History’s Hope and escorts jump into the YS01 system.  They detect transmissions from several other ships in the system.  Hoping to avoid a confrontation, they begin work on engine overhauls and jump calculations for the YS02 system.
61.273Sathar fleet SBF-B1 arrives in the OFS166 system.  It maintains its high speed and begins calculations for a jump to FS33.
61.274– Sathar fleet SBF-C1 arrives in the OFS136 system.  It maintains its high speed and begins calculations for a jump to FS56.

– Strike Force Nova arrives at Triad (Cassidine).  They will spend just 2 days in the system exercising with Task Force Cassidine before heading back to Morgaine’s World (Prenglar).

– PG Lancet arrives in the Waller Nexus system.  They immediately begin work on overhauling the ships’ engines and plotting a jump to Padda.
61.275– Sathar fleet SBF-A1 arrives in the FS12 system.  It maintains its high speed and begins calculations for a jump to Prenglar.

– Another small fleet of sathar ships, consisting of 2 LC, 3 DD, & 1 FF, designated SBF-F2 arrive at SCC#5 (OFS019) from deeper in sathar controlled space.

– PG Virgo arrives at Fortress Pale (Pale, Truane’s Star).  The crews are given a week of leave while the ships go into the starship construction center for repairs and maintenance.
61.276– Sathar fleets SBF-E1 and SBF-F1 arrive in the Kazak system.  SBF-F1 begins decelerating toward the inner system to engage the Rim forces there.  SBF-E1 maintains its high speed and begins calculations for a jump to Zebulon.

– Sathar fleet SBF-B1 arrives in the FS33 system.  It maintains its high speed and begins calculations for a jump to K’tsa-Kar.

– SF Nova leaves Triad (Cassidine) for a jump to Morgaine’s World (Prenglar)
61.277– Sathar fleet SBF-D1 arrives in the OFS020 system.  It maintains its high speed and begins calculations for a jump to Fromeltar.

– Sathar fleet SBF-C1 arrives in the FS56 system.  It maintains its high speed and begins calculations for a jump to Kisk-Kar.

– The sathar fleet (SBF-F1) decelerating toward Stenmar (Kazak) are detected by Rim forces in the system (10 F, 3 AS, 2 FF, 2 DD, 1 LC), alerts go out to systems in the Rim and the Frontier.

– Just hours before the engine overhauls are complete and the HSS History’s Hope is ready to jump once again, the ship and her escorts are attacked by three unidentified vessels. 

– A running battle ensues as the escorts attempt to screen the HSS History’s Hope long enough to make the jump. In the ensuing fight, one of the escort vessels is destroyed along with two of the attacking ships. The last attacker manages to get a hit in on the History’s Hopes engines but it is not enough to stop the ship and it slips into the Void.

– After the HSS History’s Hope jumps out of the YS01 system, the remaining escorts ships finish off the final attacker.  After the fight, the escorts repair what damage they can and begin heading back to Scree Fron for repairs.
61.278– Now in the YS02 system, the crew of the HSS History’s Hope works on repairing the battle damage to their ship and preparing for the next leg of their journey, a jump to the YS03 system.

– The 2 destroyers arrive at Fortress Redoubt (Clarion, White Light).  They join with the other ships of PG Meteor which now consists of the two destroyers and 3 assault scouts.

– With the alert from the Kazak system, PG Virgo’s maintenance is fast tracked and the crews are recalled from leave after only 3 days.
61.279PG Lancet makes the jump to the Padda system.  Work begins immediately on the engines and calculations for the jump to Minotaur (Theseus).
61.280– Sathar battle fleets appear in five different Frontier system within hours of one another and most begin decelerating towards the inhabited worlds in those systems.  SBF-A1 arrives in the Prenglar system, SBF-B1 arrives in K’tsa-Kar, SBF-C1 arrives in Kizk-Kar, SBF-D1 arrives in Fromeltar, and SBF-E1 arrives in Zebulon.

– Unlike the other sathar fleets, SBF-E1 doesn’t slow down in Zebulon but prepares for a jump to the Truane’s Star system.

– Due to the alert sent out by forces in the Kazak system, these fleets are detected within hours of their arrival in system.  Alerts are broadcast all across the Frontier.

– Task Force Cassidine, leaving its minelayer in the Cassidine system, departs on a high-speed risk jump to Dramune.

– PG Meteor is dispatched on a high risk run to reinforce the armed station at K’tsa-Kar as there is no militia in that system.  The Clarion Royal Marines (1 FF, 4 AS) join PG Meteor.

– The two ZKKDA assault scouts, currently in K’aken-Kar also depart on a high risk run to the K’tsa-Kar system per the defense agreement.

– Both of the planetary militias of Dramune independently agree to make a high speed risk jump to the Fromeltar system to assist with the defense of that system, hoping to stop the sathar before they can get  any further into the Frontier.

– Strike Force Nova arrives in the Prenglar system within hours of the sathar fleet appearing.  They begin decelerating to engage the sathar fleet simultaneously with Task Force Prenglar.

– Sathar Fleet SBF-B2 (1 HC, 1 AC, 3 DD, 1 FF, 7 F) departs the rendezvous point in OFS167 and begins accelerating for a jump to the OFS166 system.
61.281– Battle of Stenmar (Kazak) between Rim forces (1 LC, 2 DD, 2FF, 3 AS, 10 F & 1 fortified station) and SBF-F1.  The sathar forces are completely destroyed and the Rim only lose 1 LC, 2 DD, and 1 AS with the station severely damaged. Word of the victory is broadcast across the Rim and Frontier.

– PG Lancet jumps back into the Theseus system and is dissolved. The UPFS Eleanor Moraes and UPFS Backdoor break off from the group and start decelerating toward Minotaur.  The UPFS Flying Cloud remains at velocity and starts working on the jump to White Light.

– The last of the ships of PG Virgo emerge from their maintenance in the Streel shipyards (Pale, Truane’s Star).  The crews go on high alert as they monitor the sathar progress across the Frontier.  While cheered by the news of the Flight’s victory in Kazak, they mourn the loss of friends made while stationed in that system.
61.282– The sathar forces from the Sauria system arrive back at their base, SCC#10 (OFS228) where they stand down to effect repairs from the recent campaign.

– Sathar fleet SBF-E1 jumps into the Truane’s Star system and begins decelerating toward Pale.  The Truane’s Star militia, along with PG Virgo, prepare to meet them.

– Task Force Cassidine successfully jumps into the Dramune system, they maintain the high speed and start working on a risk jump to Fromeltar.

– The Dramune militias successfully jump into the Fromeltar system and begin decelerating toward Terledrom, the apparent destination of the sathar forces in that system.

– PG Meteor and the White Light militia successfully jump into the K’tsa-Kar system and begin decelerating toward the planet and sathar forces approaching it.

– The ZKKDA assault scouts also successfully arrive in the K’tsa-Kar system and race to join the fight.
61.283– Sathar Fleets SBF-E2 (1 HC, 1 AC, 1 LC, 1 DD, 1 FF, & 8 fighters) and SBF-F2 depart SCC#5 (OFS019) and begin accelerating for a jump to the Kazak system in the Rim.  After the initial loss in the Kazak system, the sathar commit their 4 new cutters to SBF-F2 to boost the strength of that fleet.

– Deciding that PG Liberty can provide advanced warning if sathar start to come from that direction, the Theseus militia, together with the remaining saurian forces in Theseus, begin accelerating for a jump to the White Light system.
61.284– The HSS History’s Hope jumps to the YS03 system and begins preparations for a jump to YS05.

– Sathar fleet SBF-B2 arrives in the OFS166 system.  It maintains its high speed and begins calculations for a jump to FS33.

– TF Cassidine makes the jump to the Fromeltar system and begin a hard deceleration.  They won’t arrive in time for the initial battle but can engage any sathar forces remaining in the system if the militias cannot successfully hold the line.
61.285– Battle of Zik-Kit (Kisk-Kar) – Overwhelmed by the forces of SBF-C1 the two militia assault scouts and the armed station are destroyed with only minimal damage to the sathar vessels.

– Battle of Terledrom (Fromeltar) – The combined militias of Dramune and Fromeltar quickly overwhelm the sathar forces in an intense 20-minute battle. The only loss is the Inner Reach destroyer with the 2 Outer Reach destroyers sustaining heavy damage.

– Battle of Kawdl-Kit (K’sta-Kar) With some amazing gunnery by the UPF and militia forces, the sathar fleet is reduced to scrap in just 20 minutes.  However, before they are destroyed, they manage to obliterate the armed station orbiting Kawdl-Kit.  No UPF or militia forces were lost although the CMS Osprey sustained some hull damage that will require a shipyard to repair.

– Battle of Gran Quivera (Prenglar) – Approaching cautiously due to the expected minefield, the sathar’s slow speed limits their maneuverability and they are overwhelmed by the combined forces of TF Prenglar and SF Nova in less than an hour. The UPF only lose 2 F, 5 AS, 1 DD, and 2 LC in the battle. Several other ships will require shipyard repairs.
61.286– The UPFS Flying Cloud jumps into the White Light system.  It maintains its high speed while performing engine overhauls and jump calculations to get to K’sta-Kar and join up with PG Meteor.

– The CMS Osprey leaves Kawdl-Kit and begins accelerating for a jump back to the shipyards orbiting Clarion. The White Light SCC has space for up to a HS 4 ship so space is held for the Osprey.

– A HS 8 freighter completes its annual maintenance at the Terledrom SCC giving a total of 12 HS of space in the SCC.  The two Outer Reach frigates are immediately admitted for repairs.

– Orbiting high above Zik-Kit the sathar ships spend the day rearming but make no move toward the planet. All UPF and militia ships that were in battles the previous day also spend the day rearming and checking that all systems are ready to go.

– With the militias in control of the Fromeltar system, Task Force Cassidine immediately starts calculations and acceleration for a jump to the K’izk-Kar system.
61.287– Sathar fleet SBF-B2 arrives in the FS33 system.  It maintains its high speed and begins calculations for a jump to K’tsa-Kar.

– Battle of New Pale (Truane’s Star) – Sathar target the smaller UPF vessels to great effect destroying 5 fighters, 6 AS, and 1 LC while only losing a DD & LC.  While their remaining ships are damaged, so are the remaining UPF vessels which are unable to purse as the sathar break off the fight.

– After finishing what battle repairs they can, the remnants of SBF-E1 start accelerating for a jump to the Zebulon system.

– SBF-C1 leaves orbit around Zit-Kit (Kizk-Kar) and begin accelerating for a jump to the Kaken-Kar system.

– Spacefleet now has several damaged ships in need of immediate repair and a need to replace ships lost in battles with the sathar. However, there is no space in most SCCs across the Frontier and especially in Prenglar.

– Given the state of the Frontier’s starship construction centers, and expecting things to get worse, Spacefleet addresses the Council of Worlds and requests that the Wartime Construction Control clause of the UPF charter be invoked.  A relic of the original charter, it has never been invoked in the history of the UPF.

– Receiving word of the departure of SBF-C1, PG Meteor and the K’aken-Kar militia, now rearmed, begin accelerating for a jump to the K’aken-Kar system to meet the on-coming sathar forces.
61.288– Sathar fleets SBF-E2 and SBF-F2 arrive in the Kazak system.  SBF-F2 begins decelerating toward the inner system to engage the Rim forces there.  SBF-E2 maintains its high speed and begins calculations for a jump to Zebulon.

– Shortly after their arrival in the Kazak system, the sathar fleets are detected and an alert is sent out.  The Rim forces brace for another battle.

– Space clears in the Outer Reach (Dramune) SCC and construction starts on a new Destroyer for the Inner Reach militia.

– Space clears in the CDC shipyards orbiting Triad (Cassidine), Spacefleet convinces the shipyard managers to start construction of 5 fighters and another assault scout, preempting the regular construction schedule.

– One of the Outer Reach frigates completes its repairs in the Terledrom (Fromeltar) shipyard freeing up 5 HS of space. 
61.289– Receiving the alert from Kazak, Spacefleet realize they only have 10-11 days to reinforce Truane’s Star.  Replenishing SF Nova’s order of battle with ships from TF Prenglar, but having to leave the damaged assault carrier and its fighters behind, it begins a high risk jump to Dixon’s Star and then on to Truane’s Star.

– Betting that Cassidine is safe, the third UPF Minelayer is ordered to Fromeltar.  It begins accelerating for a jump to Dramune as the first leg of its trip.

– Realizing that there is still enough room in the Outer Reach (Dramune) SSC, Spacefleet gets construction started on a new assault scout before anything else can be moved in.

– The second Outer Reach frigate completes its repairs in the Terledrom (Fromeltar) shipyard freeing up 5 more HS of space.  As HS 10 mining ship is moved in to the shipyard for its annual maintenance.
61.290– Two-day end of year celebration on Hum begins. With the events currently happening in the Rim and Frontier, the celebrations are more subdued than normal.

– The HSS History’s Hope arrives in YS05 and begin preparations for the jump to YS06.

– Overhauls complete, the UPFS Flying Cloud jumps into the K’sta-Kar system.  It remains at high speed working on calculations for a jump to K’aken-Kar with the rest of PG Meteor.  It will be just a day behind them.

– More space opens up in the CDC shipyards (14 HS worth). However, having just bumped six ships ahead in the queue for Spacefleet, they resist efforts to start more military construction giving the space to a large freighter that has been waiting over a month for its annual maintenance.

– Space opens up in the Minotaur (Theseus) shipyards (6 HS worth).  The Theseus government starts construction of a new destroyer for the militia although they suspect the hull will be assigned to Spacefleet.

– Space opens up (4 HS worth for a total of 6 free) in the Terledrom (Fromeltar) SCC.  The Terledrom government alerts Spacefleet of the availability and starts construction on 2 assault scouts, one for Spacefleet and one for the militia.

– Space (8 HS) opens up in the PGC shipyard at Gran Quivera (Prenglar) as a freighter completes maintenance. After the recent battle, shipyard owners are more than happy to hold the space for Spacefleet. The damaged assault scout and frigate are moved in immediately and begin repairs.

– TF Cassidine jumps into the Kizk-Kar system.  They don’t slow down but immediately begin working on engine overhauls and calculating a jump to  K’aken-Kar.
61.291– Sathar fleet SBF-E2 arrives in the Zebulon system.  They don’t slow down but begin immediate calculations for a jump to the Truane’s Star system.

– Sathar fleet SBF-B2 arrives in the K’tsa-Kar system and starts decelerating toward the White Light Militia ships there. PG Meteor and the K’aken-Kar militia are less than 10 hours from jumping out of the system when the sathar are detected.

– Realizing that the K’aken-Kar militia will suffer the same fate as the K’izk-Kar militia if they return to face the sathar alone, PG Meteor continues with them for the jump to K’aken-Kar.

– SF Nova jumps into the Dixon’s Star system.  Working feverishly on overhauls to the assault scouts’ engines, they begin calculating the jump to Truane’s Star.

– The UPF assault scout and frigate complete their hull repairs after a single day in the PGC shipyard (Gran Quivera, Prenglar) and return to active duty.

– Another 6 HS of space open up in the PGC shipyards (Gran Quivera, Prenglar) for a total of 16 HS of space available.  The damaged assault carrier is moved into the shipyard to have its engines repaired.

– Realizing that they cannot withstand the incoming sathar force, the White Light militia starts plotting a jump back to their home system. They delay departure, however, acting as bait and hoping to draw SBF-B2 deeper into the system so they don’t jump immediately after PF Virgo or straight to White Light.
61.292– SBF-C1 jumps into the K’aken-Kar system and begins decelerating toward the planet.

– PG Meteor and the K’aken-Kar militia jump into the K’aken-Kar system and begin decelerating to meet the sathar.

– The Theseus militia, along with the second saurian Ark Ship arrive in orbit around Clarion (White Light).  The saurians join their sister ships in orbit while the Theseus militia confers with the Clarion Royal Marines and Fortress Redoubt to establish defensive plans.

– SBF-E1 jumps into the Zebulon system and establish contact with SBF-E2 relaying full details of their encounter.  They start working on a jump to Kazak System and then back to SCC#5 (OFS019) for repairs.

– The UPF assault carrier’s engines complete their repairs.  With 16 HS of space available at the PGC shipyards, Spacefleet begins construction on a fighter, an assault scout, and a light cruiser.
61.293– Second Battle of Stenmar (Kazak) – seriously outgunned, the Rim forces are nearly all destroyed with only a single fighter surviving.  They manage to take out a sathar light cruiser and cutter before being overwhelmed.

– The UPFS Flying Cloud jumps into the K’aken-Kar system. It remains at high speed to catch up with the rest of PG Meteor and will execute a hard deceleration to match speed with the group when it does.

– Having succeeded in drawing SBF-B2 into the K’sta-Kar system, the White Light militia, reluctant to abandon Kawdl-Kit, begins acceleration for their jump home.

– Seeing the White Light militia start to leave the system, SBF-B2 changes course and start accelerating for a jump to K’aken-Kar to join SBF-C1.

– The UPF minelayer jumps into the Dramune system.  It doesn’t slow down but begins calculations for its jump to Fromeltar.

– Space (5HS) opens up in the Hentz (Araks) shipyards. It is not immediately filled as there is a larger ship waiting on maintenance.
61.294– SBF-E2 jumps into the Truane’s Star system and begin decelerating toward New Pale.

– SF Nova arrives in the Truane’s Star system just hours after the sathar.  Unfortunately, they arrived much farther out in the system than anticipated.  They begin a fast run and hard deceleration toward New Pale in order to arrive before the sathar forces.

– Seeing more and more sathar ships arriving in the Frontier, the Council of Worlds stops blocking the activation the Wartime Construction Control (WCC) clause in the UPF Charter. Spacefleet is granted complete control of all starship construction centers in the Frontier.

– With the activation of the WCC clause, Spacefleet, with the assistance of Star Law, move to take control of the shipyards. They temporarily suspend any new maintenance work while they sort out the schedule and priorities.

– More space opens in several SCCs across the Frontier: 2 HS at Hentz (Araks) for a total of 7 HS, 18 HS at Rupert’s Hole (Cassidine) emptying that facility, 6 HS at Terledrom (Fromeltar) 12 HS at Gran Quivera (Prenglar), and 5 HS at Minotaur (Theseus)

– Working to replenish their immediate losses, Spacefleet takes control of the destroyer construction at Minotaur, and start construction of 2 assault scouts at Hentz, a light cruiser at Gran Quivera, and a fighter and assault scout at Terledrom.

– Lacking facilities to construct military vessels, the Rupert’s Hole SCC is designated for ship maintenance and two ships are moved in immediately.  The other Type III SSCs at Pale & Clarion are given the same designation.

– Spacefleet also authorizes the start of construction for two assault scouts to replenish some of the ships lost by the Truane’s Star militia with the understanding that they may be deputized by Spacefleet during the conflict. Construction starts in Terledrom and Minotaur

Here’s the full timeline to download:

DetailedFrontierTimeline-1Download

December 1, 2020 Tom 1 Comment

Sathar Starship Construction Centers

I had planned to do an article on an alternate set of astrogation rules, but as I started looking at it, it was going to require more time than I had to get it done properly. So that one will come at some point in the future.

If you’re following the Star Frontiers Twitter feed, you know that yesterday started the main events of the Second Sathar War. A lot of my free time has been spent working on that and staying far enough ahead that I can get the battle posts up, track the ship movements, record and schedule repairs and new ship construction, and figure out strategy and tactics as they shift after each encounter. In fact, if I hadn’t posted it early to get some feedback, the Battle of Stenmar post I did a while back would have been today’s post as the tweet about that battle will be going up at some point today. Tracking all the ship movements and playing out the battles is keeping me busy. Who knew that managing a Frontier-wide battle for both sides would be so much work! 🙂

Given that the Second Sathar War narration is where my focus is right now, I thought I’d do a related post and talk about the Sathar starship construction centers (SCCs) in my version of the setting.

Some Background

Placing the SCCs

If you have looked closely at the Extended Frontier Map, you already know the locations of these SCCs – they are marked on the referee version of the map. And as I mentioned in the posts about the creation of that map, the sathar worlds and jump routes were originally laid down decades ago. I modified them slightly to account for the Zeb’s Guide data and fan material that I included in the map as the latter hadn’t been produced and I didn’t own a copy of the former when I made the original map as a teenager.

On that original map, only the first five SCCs were marked. I had originally created the map to help track the exact project I’m doing now as part of the Detailed Frontier Timeline, namely track the Second Sathar War from a ship construction and movement perspective with the RPG rules rather than the board game rules in in the Campaign Book. It was also made for a exploration campaign where the PC would go out to expand the borders of the Frontier and look for the sathar worlds but that’s a different set of posts. Because of that, I only included the five SCCs that I envisioned participating in the conflict and which is why those five, closest to the Frontier, have the first five numbers and not the ones deeper in sathar controlled space which arguably were created first. If I ever go back and rework everything, I might change the numbering.

When I was setting up the Detailed Frontier Timeline project and making the Extended Frontier Map, I realized that I needed to add in a few more SCCs in the other parts of sathar-controlled space to handle all the other ship construction needed by their empire. That got me up through the ninth SCC. I then realized they needed one to manage the fight against the Saurians and so added in the tenth one. So while they are numbered in order of creation, it was their creation in my head for the setting, not their creation dates in the timeline.

Sathar Ship Hull Sizes

Another item of note relative to the SCCs is the hull sizes I use for each of the sathar ships. These are slightly different than the values I use for the UPF ships but all fall within the range of sizes given for each class of ship on page 5 of the Knight Hawks Campaign Book. The sizes I use for the sathar ships are:

  • Fighter – HS:1
  • Cutter – HS:4
  • Frigate – HS:5
  • Destroyer – HS:6
  • Light Cruiser – HS: 14
  • Assault Carrier – HS:16
  • Heavy Cruiser – HS: 18

In the timeline the cutter is a new ship type that will see action first in the Rim and later in the Frontier. The specs for the ship can be found on page 6 of Frontier Explorer issue 2.

It’s my take that the larger sathar ships are a bit bulkier than the corresponding UPF version. So sathar light cruisers are HS:14 while the UPF ones are HS:12, the sathar assault carriers are HS:16 while the UPF ones are HS: 14, and the sathar heavy cruiser is HS:18 compared to the single UPF heavy cruiser which is HS:16. Even the sathar destroyer is actually HS:6+ being just a bit larger than the standard HS:6 volume but not enough to actually be HS:7.

The reason for this is the role I have for these larger ships. In addition to being mainline fighting ships, the larger capital ships also double as troop transports. You can see this in the Sathar Destroyer Technical Manual. Someday I’ll detail out the light and heavy cruisers similarly. In any case, this makes the sathar ships a bit bulkier and take a bit longer to produce. They aren’t being used for the troop transport role at the beginning of the war but the capability is there. While this doesn’t have any impact on the actual battles, it does impact the starship construction centers and so needed to be spelled out.

The Starship Construction Centers

In this section, we will look at each of those starship construction centers in turn to talk about their capacity, production queues, and main focus.

If you’ve been following along with the Detailed Frontier Timeline and playing close attention, you could probably reconstruct the production queues of SSCs two through five as I’ve been posting the ships that were produced there as part of the timeline. SCC#1 has just come online and only produced a single ship (a light cruiser) so it’s full queue hasn’t been revealed and SCC#10 will soon be shifting from the Saurian conflict, which has ended, to the Second Sathar War. The first ship out of that SCC (a fighter) to participate in the SSW will complete construction in early December (FY61.304).

The production queues for SSCs one to five were specifically set up to try to produce the sathar Order of Battle from page 55 of the Knight Hawks Campaign Book at the time I started up the war in the timeline. I started with an initial semi-random “seed” of ships, modified for the encounters in the Detailed Frontier Timeline (like the fight a Volturnus), and then allowed the SSCs to crank out ships. I came pretty close with only a few more fighters (most of which I destroyed in the fight in the Liberty system) and one extra destroyer. I have a small computer program that allows me to run the production queues and add (and remove) SCCs as needed to produce the ships so I don’t have to do it by hand.

Okay, let’s look at these construction centers. Directions for the locations of the SCCs are given on the Extended Frontier map assuming the top of the map is “north.”

SCC#1

Location: OFS203 (“S” of Prenglar)

Capacity: 48 HS worth of ships

Production Queue:

  • 42 HS of capacity dedicated to the production of light cruisers (3 under construction at any one time), staggered to produce a new LC every 140 days
  • 6 HS of capacity dedicated to the production of destroyers, one every 180 days

Notes: This is the newest of the starship construction centers with its first ship being produced on FY61.208. It is at the far end on the sathar jump routes (without passing through the Frontier). It was constructed specifically to be a jump off and repair point to strike right into the heart of the Frontier at Prenglar.

The recent loss of SSC#2 and the Liberty system has actually isolated this SSC from the others. Ships produced here (or headed here) will have to pass through the Liberty system. This will give the UPF a chance to detect these ships if they try to get into the Frontier anywhere other than Prenglar.

SCC#2

Location: FS30 – now Liberty (“SE” of Theseus)

Capacity: 46 HS

Production Queue:

  • 16 HS of capacity devoted to production of assault carriers, one very 480 days
  • 24 HS of capacity devoted to production of destroyers (six under production at any one time), staggered to complete one every 45 days
  • 6 HS of capacity split between production of fighters and destroyers. Produces 6 fighters in 30 days, then a destroyer 180 days later, than back to fighters.

Notes: This SCC has been operating for a while and is responsible for the production of most of the destroyers seen in the Frontier recently and present in the fleets in the initial attacks in the Second Sathar War and produced some that were used against the saurians. It was also the driving force behind the exploration that established the sathar jump routes over to SCC#1 and in to S’esseu space.

In the notes in the SFKH4 module The War Machine (the Beyond the Frontier series), it said that this SCC was responsible for about 20% of the ships in the second sathar war. This is why I went with five SCCs when creating the original map.

This SCC was lost just recently along with a large number of fighters in the events of the SFKH4 module which wrapped up on FY61.40, only 40 days before the first sathar ships appeared in the Frontier to start the Second Sathar War. It will be interesting to see how things play out with the loss of this system, but that was always intended from the start.

SCC#3

Location: OFS138 (“NE” from Kizk-Kar)

Capacity: 59 HS

Production Queue:

  • 54 HS of capacity devoted to heavy cruiser production (three under production at any one time), staggered to produce one HC every 180 days
  • 5 HS of production dedicated to frigate production, one completed every 150 days

Notes: This is an older SCC as well and originally fueled the sathar exploration on the eastern side of the Frontier that resulted in the discovery of the saurians and the Mhemne.

Now focused on the battle with the Frontier, this SCC is responsible for the construction of the majority of heavy cruisers present in the early days of the conflict.

SCC#4

Location: OFS111 (“N” of Fromeltar)

Capacity: 49 HS

Production Queue:

  • 16 HS of capacity dedicated to assault carrier production, one every 480 days
  • 28 HS of capacity dedicated to light cruiser production (two under production at any one time), staggered to produce one every 210 days
  • 5 HS of capacity dedicated to frigate and fighter production, completing 5 fighters in 30 days, then a frigate 150 days later and then back to fighters.

Notes: This is a older SCC established after the First Sathar War to explore more into the Frontier sector and the Rim. The route to Zebulon has been known for hundreds of years but most of the other routes are fairly new.

SCC#5

Location: OFS019 (“N” of Truane’s Star/Zebulon)

Capacity: 50 HS

Production Queue:

  • 28 HS of capacity dedicated to light cruiser production (two under production at any one time), staggered to produce one every 210 days
  • 18 HS of capacity dedicated to heavy cruiser production one every 540 days
  • 4 HP of capacity dedicate to cutter production, one every 120 days

Notes: This is a newer SCC set up to provide ships for fighting in the Rim and the Frontier and built as part of the preparation for the Second Sathar War.

The cutter is a new ship that the sathar have developed partially in response to the UPF’s assault scout. It is not battle tested and at the start of the Second Sathar War, only 4 have been produced. They will see first blood in the Second Battle of Stenmar (coming on FY61.293).

SCC#6

Location: OFS117 (upper left center of Extended Frontier Map)

Capacity: 200 HS

Production Queue: Random, mostly non-military ships

Notes: This SCC is located in orbit around what in my game is the sathar homeworld. It is larger than even the largest SCC in the Frontier but is not currently involved in the SSW conflict, although that may change. This SCC primarily is responsible for producing “civilian” ships that the sathar use for non-military purposes.

It did, however, supply the ships that comprised SBF-F1 and SBF-F2 that attacked Stenmar (in the Kazak system) in the Detailed Frontier Timeline. Since those battles were outside the scope of the simulation I was working on (I’m ignoring the Rim), I had the ships for the fight in the Rim come from somewhere other than the five main SCCs.

SCC#7

Location: OFS101 (upper right of Extended Frontier Map)

Capacity: 75 HS

Production Queue: random, “civilian” ships

Notes: This is a new SCC and is currently focused on producing “civilian” ships and ships for exploration to the “NE” of the sathar homeworld. Not currently involved in SSW production.

SCC#8

Location: OFS097 (“N” of OFS117)

Capacity: 75 HS

Production Queue: random, “civilian” ships

Notes: This is another SCC that is producing civilian ships for the day-to-day operation of the sathar worlds. Not currently involved in SSW production.

SCC#9

Location: OFS064 (upper center of Extended Frontier Map)

Capacity: 75 HS

Production Queue: random, military and exploration vessels

Notes: This SCC is focused on an active campaign to explore the upper left corner of the Extended Frontier Map. It was ships from this system that many years ago discovered the Tetrach complex on OFS070 that the Discovery Squadron went looking for and which was contacted by the complex on Laco (Dixon’s Star) back at the end of FY59. It was actually this signal, plus the events of Volturnus, that kicked off the Second Sathar War.

The sathar are currently trying to find a way through the large nebula in this region as they have detected signals from another race on the other side of the nebula that they intend to conquer. It is not currently producing ships for the SSW and probably will not be used for that purpose at it is focused on a different threat.

SCC#10

Location: OFS174 (“E” of White Light)

Capacity: 60 HS

Production Queue:

  • 18 HS of capacity dedicated to heavy cruiser production, one every 540 days
  • 16 HS of capacity dedicated to assault carrier production, one every 480 days
  • 14 HS of capacity dedicated to light cruiser production, one every 420 days
  • 6 HS of capacity dedicated to destroyer production, one every 180 days
  • 5 HS of capacity dedicated to frigate production, one every 150 days
  • 1 HS of capacity dedicated to fighter production, one every 30 days

Notes: This SCC is producing some of every type of main-line sathar warship. For the past several years, it has been focused on the war with the saurians and is responsible for producing most of the ships that destroyed their worlds.

Being already focused on military production, and with the campaign against the saurians now ended (finished on FY61.282) and the loss of the SCC in the Liberty system, this SCC will shortly be added to war effort against the Frontier (officially on FY61.296).

Last Thoughts

Those are the sathar starship construction centers scattered about. All told, there are 737 HS of capacity across the 10 SCCs. It’s about 45% more capacity than in the Frontier, although more spread out. It is also more focused on military ships. The UPF has 430 HS of capacity that can produce military vessels and another 80 HS of capacity that can produce civilian ships and do maintenance.

As the battles play out, the sathar may shift the production queues to different mixes going forward (e.g. they have lost most of their destroyer production) but we’ll have to see how the upcoming battles play out. Look for the first play report later this week and running into next week as the initial battles occur around the Frontier.

How do you see the sathar starship construction being set up and handled? Have you every attempted anything like this for your game? Or have you been more sensible and just hand-waved it? Share your thoughts in the comments below.

November 17, 2020 Tom 3 Comments

Detailed Frontier Timeline – FY61.234 to FY61.264

This month sees the conclusion of the Beyond the Frontier series of modules (SFKH2-4) with UPF forces driving out the sathar from the FS30 system which is named Liberty. They also destroy a sathar starship construction center which will cripple the sathar efforts in the Frontier in the coming conflict, the wheels of which are already turning.

Also this month, the HSS History’s Hope makes it back to Frontier space for some much needed maintenance and starts back out to hopefully completely their voyage of discovery and the Saurians begin to set up an initial settlement on Clarion in the White Light system.

The last day of the month sees additional sathar ships arriving at their forward posts in preparation for the coming conflict. Next month with see the sathar forces set in motion and the opening shots of the Second Sathar War. If you want to follow along as events unfold, remember that I post the daily updates on Twitter. These posts are just the monthly summaries. As the battles play out, I’ll be doing posts on the day they occur as I described in my State of the Frontier post a couple of days ago. You can see a sneak peek (if you haven’t already) of these battle posts in the Battle of Stenmar post from a couple of weeks ago. That battle actually occurs on day FY61.281 but I provided it early to get feedback on the format.

Here are the most recent events in the timeline.

Date (FY)Events
61.234– Investigating the wreckage of the ships that attacked the HSS History’s Hope points to the involvement of the Family of One but the evidence is inconclusive.  The ships repair what damage they can and resume preparations for the jump to OFS224.

– On-board preparations complete, the first shuttle loads of materials for their new settlement depart the 7th saurian Ark Ship for the surface of Clarion.

– Within hours of their landing, protesters arrive at the saurian settlement site and attempt to disrupt the operations.  However, the Clarion Royal Constabulary, already on-site to maintain order, quickly gets the situation under control.
61.235The HSS History’s Hope jumps to the OFS224 system on high alert.  However, there is no indication of hostile forces and they begin preparation for the jump to Scree Fron.
61.236– Two destroyers, slated to join Strike Force Meteor, are completed in the Hentz (Araks) shipyards.  They begin a shakedown cruise to Prenglar via the Gruna Garu system.

– Strike Force Nova jumps into the White Light System and begins decelerating toward Clarion.

– The UPF ships under Command Reider in the FS30 system initiate Operation Cracker to attack and draw off the sathar ships from the occupied Mhemne L4 station.

– The ensuing battle of Operation Cracker manages to destroy many the remaining sathar fighters in the system which seemed to have very poor pilots.  The sathar LC and AC retreat to the strong defenses of the planet’s moon.

– Simultaneous with Operation Cracker, the CMS Osprey, UPFS Eleanor Moraes and the two captured sathar shuttles lift off from the surface of Snowball and approach the L4 station. 

– Gaining access to the L4 station, the UPF/Mhemne forces wage a running battle with the sathar forces occupying the station in an attempt to capture it before the sathar can destroy the station and kill the inhabitants.

– Having successfully captured the L4 station, the UPF and Mhemne forces brace for a sathar counterattack.

– Instead of attacking, the sathar abandon their positions on Snowball’s moon, the planet’s surface, and head to the L5 station.  All sathar installations are destroyed by nuclear blast.  Surprisingly, the Mhemne installations and cities are not destroyed.

– After collecting fighters at the L5 station, the remaining ships begin accelerating for a jump out of the system. As they leave L5 station, the sathar ships under construction at the L5 station are destroyed by explosions.

– After waiting to ensure the sathar don’t double back, Commander Reider pursues the sathar vessels as they continue to accelerate.  The sathar send their inexperienced fighters after the UPF ships which are destroyed in the ensuing fight.  The UPF remain safely out of range of the sathar ships’ heavier weapons as they trail them out of the system.

– Sathar SCC#4 (OFS111) completes a frigate
61.237After a week of additional patrols in the FS26 system, PG Meteor begins acceleration for a jump back to the Theseus system.
61.238Due to the scrutiny after the rubies deliver, Obar Enterprises takes some lower profile cargos for the next few runs on their secret jump route between Truane’s Star and Cassidine.  While not as profitable as the last few runs, they still gross 1.365 million credits.
61.239News of the events in the FS30 system leak to the public on Gran Quivera (Prenglar).  The Frontier Peace Organization stage a protest outside the Council of Worlds building demanding a cease of hostilities against the sathar and a stop to Spacefleet expansion.
61.240– The HSS History’s Hope and her remaining escorts jump in the Scree Fron system and begin decelerating to Hakosaur.

– Strike Force Nova arrives at Clarion and settles into berths at Fortress Redoubt.  They open communications with the commanders of the saurian vessels to arrange a meeting between the ship captains to discuss sathar tactics observed by both forces.

– The sathar HC and AC from FS30 jump into the OFS179 system, they maintain their high velocity and begin calculations for a jump to the OFS 168 system.  Commander Reider turns his ships around to return to the inner system.
61.241Responding to the activities of the Frontier Peace Organization, the Anti-Satharian League stage a counter protest demanding even greater Spacefleet and Star Law funding.  The two groups clash and the Port Loren police have to intervene to stop the fighting.
61.242– The commanders of the Strike Force Nova vessels meet with their saurian counterparts.  Over the next 6 days, they host each other on the various ships and stations and trade intelligence on the sathar.

– While most of the information on the sathar flows from the saurians to the UPF, the recent experiences of the Discovery Squadron provide some information to flow the other direction
61.243After months of negotiations, the Consolidated Nebula Energy Group has signed on all the independent power distributors on Groth (Fromeltar) and many distributors on Terledrom (Fromeltar) and Inner Reach (Dramune).  They continue to recruit others and begin sending delegates to other systems as well.
61.244The HSS History’s Hope arrives back at Hakosaur and lands at the starship repair facility on the surface.  While the ship goes in for maintenance, the crew take a much-deserved rest and spend time with their families.
61.245The two UPF destroyers arrive at Hargut (Gruna Garu), while the rest of the crew takes a bit of shore leave, the astrogators get to work immediately on the calculations for the long jump to Prenglar.
61.246– The sathar forces in the Sauria system, having finished the cleansing of that system, begin accelerating for a jump to the Tischen system, the first leg of a journey back to their base in OFS228, the site of another sathar starship construction center (SCC#10)

– PG Meteor arrives back at Minotaur Station (Theseus).  They transmit their findings in FS26 back to UPF Headquarters.  The crews are given 3 days of shore leave.

– The sathar HC and AC from FS30 arrive in OFS168.  They begin calculations for a jump to OFS167.
61.247– Initial jump calculations complete, the two UPF destroyers at Hargut (Gruna Garu) leave the station and begin accelerating for their jump to Prenglar.

– Commander Reider arrives back at Snowball with PG Lancet.  The CMS Osprey is released to return back to Clarion (White Light).  It begins accelerating for a jump back to Waller Nexus. 
61.248– Meetings with the saurians complete, Strike Force Nova departs Fortress Redoubt and begins accelerating for a jump to Madderly’s Star.

– Calculations complete, the sathar HC and AC in OFS168 jump into the OFS167 system.  The begin decelerating to join the other ships rendezvoused there.
61.249PG Meteor in split apart once more.  3 Assault scouts, keeping the PG Meteor designation, leave Minotaur station and begin accelerating for a jump to Clarion (White Light).  The frigate and remaining assault scout, designated PG Liberty, start accelerating for a jump to Padda.
61.250– The FS30 system, in consultation with the Mhemne population, is named the Liberty system in UPF records.

– After over a year on patrol, PG Virgo departs the Kazak system to return to the Frontier.  It will make a high-speed transit back to Pale (Truane’s Star).
61.251After a week of ship maintenance and crew leave, the HSS History’s Hope emerges from the starship repair facility with a clean bill of health.  The crew prepares to depart once again into the Yazira sector to continue their voyage of discovery.
61.252The CMS Osprey arrives in the Waller Nexus system.  They maintain their high velocity and begin calculations for a jump to the Padda system.
61.253Preparations complete, and fully restocked with food and fuel, the HSS History’s Hope, along with three other vessels acting as escorts, leave Hakosaur (Screen Fron) for a jump to OFS224.  They plan to make another high-speed transit back to YS07 to continue their exploration.
61.254PG Liberty arrives in the Padda system where they maintain their high velocity and begin calculations for a jump to the Waller Nexus system.
61.255– Sathar SCC#3 (OFS138) completes a heavy cruiser and frigate.  These are the last of the ships that will comprise the initial volley of what will come to be known as the Second Sathar War.

– PG Virgo jumps into the Osak system and begins calculations for the jump to the Capella system.
61.256– The two destroyers designated as part of SF Meteor arrive at Gollwin Station (Morgaine’s World, Prenglar).

– The CMS Osprey arrives in the Padda system and establishes contact with PG Liberty briefing them on the events in the Liberty system.  They maintain their high velocity and begin calculations for a jump back to Theseus.
61.257SF Nova arrives at the new Fortress Kdikit (Kdikit, Madderly’s Star).  They begin a series of maneuvers to fine tune the station’s tracking systems.
61.258– PG Meteor arrives at Fortress Redoubt (Clarion, White Light).  UPF High Command decides to station the patrol group there indefinitely while the remainder of the ships for the strike force are completed.  They will assemble here as they are finished.

– The SF Meteor destroyers are dispatched from Gollwin Academy (Morgaine’s World, Prenglar) with orders to join up with the other ships in White Light.  They begin accelerating for a jump to Timeon.

– PG Liberty jump into the Waller Nexus system.  They begin calculations for their final jump to the Liberty system.

– The CMS Osprey jumps into the Theseus system.  Deciding to head straight home, they continue at high velocity across the system and begin calculations for the jump to White Light.

– The HSS History’s Hope and her escorts jump into the OFS224 system.  They begin overhauling the ships’ engines and calculating their jump to OFS221.
61.259After several weeks of intensive work, the first saurian dwellings on Clarion (White Light) are completed and ready to be occupied.  They just need the power generator to be finished.
61.260PG Virgo jump into the Capella system and begins work for the jump back to the Zebulon system.
61.261PG Liberty jumps into the Liberty system and begins decelerating toward Snowball.
61.262The first power generator at the saurian settlement is completed and brought on-line.  The construction crews can now move into permanent residences and begin working on expanding the settlement.
61.263– The CMS Osprey jumps into the White Light system and begins decelerating toward Clarion and home.

– The HSS History’s Hope and her escorts jump into the OFS221 system and begin work on jump calculations for the jump to OFS222 and work on overhauling the ships’ engines.
61.264A small fleet of sathar ships, consisting of 1 HC, 1 AC, 1 LC, 4 DD, 2 FF, and 8 fighters), designated Sathar Battle Fleet F1 (SBF-F1) arrive at SCC#5 (OFS019) from deeper in sathar controlled space.

The full timeline for download:

DetailedFrontierTimelineDownload
November 3, 2020 Tom 1 Comment

Detailed Frontier Timeline – FY61.204 to FY61.233

Here comes the next installment of the detailed Frontier Timeline. The HSS History’s Hope is returning back home for it’s annual maintenance and gets waylaid, the UPFS Eleanor Moraes and CMS Osprey discover the sathar starship construction center in the FS30 system, and the Saurians start the process of settling into the Frontier.

We are drawing closer and closer to the launch of the sathar attack into the Frontier that will come to be known as the Second Sathar War. As I was starting to work ahead on that I realized that since back in mid April, I had forgotten to post the updates about the sathar ship construction and movement of sathar ships outside the Frontier. All of the craziness that result from COVID-19 resulted in me dropping the ball on these posts. The funny thing is, when I started this project nearly two years ago, these were the very posts and bits of information that I started the project to track. Seeing how the sathar moved ships around in preparation for and during the battle what the inspiration for the project in the first place. It’s kind of ironic that that is what I lost track of. The other stuff was just supposed to be filler around these posts, but these other threads seem to have taken on lives of their own.

I’ve gone back and fixed that error. In the final document at the bottom of the page, the posts (which start on FY61.068) that I missed posting to Twitter and in the monthly updates are highlighted in a blue font. I’ve assembled them into a separate table below so that you can see them all together if you don’t want to search for them in the document and see them in their context. These missed updates include almost all of the positioning of sathar forces before the commencement of the invasion. Going forward, things will be included as regular updates and posts and I won’t have to backfill.

I also realized, as I’m completing the events of the SFKH4 – The War Machine module, that in the time line, the Liberty System, which is the location of that adventure, is still unnamed and only known as FS30 on the star maps. So I’ve gone back through the document and changed all reference to the Liberty system to FS30. The name change actually occurs in the coming month and is an event that will be in the next update.

The Lost Events

Date (FY)Events
61.068A new sathar starship construction center comes on-line and begins producing ships.  This new center is located in a system “south” of Prenglar, OFS203.  It is designated SCC#1.
61.081Sathar SCC#2 (FS30) produces 6 fighters
61.096Sathar SCC#2 (FS30) produces a destroyer
61.105Sathar SCC#3 (OFS138) produces a frigate
61.116Sathar SCC#4 (OFS111) produces a frigate
61.1283 sathar ships (1 DD, 1 LC, 1 AC, designated transit group TG 1) depart SCC#5 (OFS19) and begin accelerating for a high-speed transit to SCC#4 (OFS111).
61.141A destroyer is completed in the sathar SCC#3 (FS30)
61.146The sathar SCC#4 (OFS111) completes 5 fighters.
61.148The ships of sathar TG1 arrive at SCC#4 (OFS111).  The destroyer remains in the system while the remaining ships are joined by 12 fighters (housed in the assault carrier) and another light cruiser.  TG1 begins acceleration for a high-speed transit to SCC#3 (OFS 136).
61.150A sathar frigate leaves SCC#4 (OFS111) and begins a high speed transit to SCC#5 (OFS019)
61.170The sathar frigate arrives at SCC#5 (OFS019)
61.172The ships of sathar TG1 arrive at SCC#3 (OFS136).  They are joined by another assault carrier (with 8 fighters), 3 heavy cruisers, and 3 frigates.  They depart immediately and begin accelerating for a high-speed transit to OFS167.
61.173The Sathar battle fleet arrives in orbit around Edge (Precipice).  They meet no resistance and begin bombing the planet.
61.175Destruction of the saurian world Edge (Precipice) complete, the sathar battle fleet begins acceleration to return to the Sauria system.
61.180Several sathar ships (1 AC, 1 HC, 1 LC, & 6 fighters, designated TG2) leave SCC#2 (FS30) and begin accelerating for a high-speed transit to new SCC#1 (OFS203).
61.182The sathar SCC#5 (OFS019) completes a cutter and light cruiser.
61.184The sathar fleet arrives back at Kischen (Sauria).  They begin an aggressive patrol of the system looking for any survivors or other ships that escaped their initial attack.
61.186The Sathar SCC#2 (FS30) completes a destroyer.  It along with six others, depart the SCC and begin accelerating for a high-speed transit to OFS 167.
61.193Sathar Transit Group 1 arrive in the inner system of OFS167.  They begin patrolling the system and waiting for other ships to arrive.
61.194– Sathar TG1 is reformed consisting of 1 AC (with 6 fighters), 1 HC, 1 LC, and 1 frigate.  It departs OFS167 immediately for a high-speed transit to SCC#1 (OFS203)

– A new transit group (TG3) is formed from the ships at OFS167. Consisting of 1 HC, 1 AC and 7 fighters, it begins accelerating for a high-speed transit to SCC#2 (FS30).
61.200Sathar Transit Group 2 (1 AC, 1 HC, 4 DD, & 8 fighters), arrive at the newly operating SCC#1 (OFS203)

That covers everything I missed in months past. I missed a few events in this month’s activities as I was doing the Twitter posts but they will just be included in the regular update below. The events I missed posting on Twitter will be highlighted in italics.

The Regular Update

Date (FY)Events
61.204After two days of preparation, the UPFS Eleanor Moraes, CMS Osprey, and the sathar scout ship (now named the UPFS Backdoor) lift off from Mahg Mar and begin accelerating toward the FS 30 system using the captured astrogation data. (SFKH4)
61.205After over a week of deliberations, discussions, and subspace communications all of the Frontier, Princess Leotia of Clarions extends a formal invitation from her world to the Saurians to set up an initial settlement there.
61.206– PG Meteor successfully jumps into the White Light system.  They do not slow down but immediately begin calculations for the 10 light year jump to Theseus.

– The second saurian Ark ships joins the first one in orbit around Minotaur and delegates from that ship join the discussions.
61.207– Two UPF Frigates slated for SF Meteor are completed in the Minotaur (Theseus) shipyards.  They begin a short shakedown cruise while they wait for the arrive of the assault scouts in PG Meteor.

– After two days of internal discussions, the saurians agree to send one of the ark ships to White Light for direct discussions about settling on Clarion, at least initially.  Princess Leotia offers to accompany them personally on their vessel as a show of good faith.
61.208– The UPFS Eleanor Moraes, CMS Osprey, and UPFS Backdoor successfully jump into the FS30 system.  They begin decelerating toward the location of the sathar base, codenamed Base Alpha. (SFKH4)

– The first ship, a light cruiser, is completed at the new sathar SCC#1 (OFS203) south of Prenglar.
61.209– The HSS History’s Hope jumps into the YS03 system and begins work on the jump back to YS02.

– Sathar Transit Group 3 arrives at SCC#2 (FS30)
61.210After 3 days of preparation, the 7th saurian Ark Ship leaves orbit around Minotaur and begins accelerating for a jump to the White Light system.
61.211Jump calculations complete, PG Meteor jumps to the Theseus system and begins decelerating toward Minotaur.
61.212– After four days of deceleration, the UPF ships approach the location of Base Alpha in the FS30 system.  They realize that the base is a small assault carrier.  Leaving the other ships behind, the captured sathar scout ship (UPFS Backdoor) approaches the carrier. (SFKH4)

– The UPFS Backdoor is pulled in to a docking bay of the sathar carrier.  After an intense battle through the decks of the sathar vessel, the crew manages to capture the ship and eject its engines before they can overload and destroy the vessel.   (SFKH4)
61.213Several ships, independently dispatched by members of the True Yaziria society, arrive in YS01.  They discover several Family of One vessels in the system patrolling for the eventual arrival of the HSS History’s Hope as it returns to the Frontier.
61.214– The HSS History’s Hope jumps to the YS02 system arriving safely.  They begin work to make the jump back to YS01.

– The True Yaziria ships engage the Family of One ships destroying one, crippling another, and driving off the remaining two.  The FoO ships are trailed until they jump out of the YS01 system.

– Four sathar fighters arrive from the inner system to investigate the explosions of the sathar carrier’s engines.  A battle ensues between the CMS Osprey, UPF Eleanor Moraes, UPFS Backdoor, and the sathar fighters.  The UPF forces win but the Moraes is severely damaged. (SFKH4)
61.215– The 7th saurian Ark Ship jumps into the White Light system and begins decelerating toward Clarion.  Princess Leotia radios ahead to alert her father of their arrival.

– PG Meteor arrives at Minotaur station, the assault scout crews are given two days of rest before they are given their next assignment.  The two frigates join the assault scouts, and the ships are temporarily assigned to the Frontier Expeditionary Force under Commander Reider.
61.216After two days of engine overhauls and repairs, a small chemically propelled rocket approaches the UPF ships in the FS30 system.  Capturing the rocket, they determine that it is a message requesting a meeting from some unknown group.  They radio back to FEF headquarters. (SFKH4)
61.217– The UPF forces in FS30 receive orders from Commander Reider to make contact with whomever sent the rocket and learn as much about the sathar in the system as possible.  He is personally bringing reinforcements.

– PG Meteor is split into two groups.  One (a frigate and 4 AS) are sent to the FS26 system to see if any sathar ships were pursuing the saurians and establish a forward screen there.  The other (a frigate and 2 AS), commanded by Commander Reider, depart for the trip to FS30.

– After completing preparations, the crew of the UPFS Eleanor Moraes depart for the rendezvous point indicated by the map in the rocket.  (SFKH4)
61.218The full White Light Militia, sans the CMS Osprey, boost out from Clarion station to meet the saurian Ark Ship.

– The sathar SCC#1 (OFS218) completes a frigate.
61.219– With everything ready to go, the crew of the HSS History’s Hope prepares to jump back to the YS01 system.  They go on high alert as this is the system they were attacked in before and are worried that there will be trouble again.

– Jumping in to the YS01 system, the crew of the HSS History’s Hope detect radio signals from several different ships. Initially concerned, they soon realize that these ships are there as escorts, not antagonists. Work begins on jump calculations as the ships in the inner system accelerate to join them.

– The Eleanor Moraes crew arrives at the rendezvous point, a small asteroid that has been hollowed out into a space station.  After docking they meet with a new race, called the Mhemne. (SFKH4)

– Two sathar destroyers arrive at SCC#3 (OFS138) and join the forces there.
61.220– The 7th saurian Ark Ship, together with the White Light militia, settle into orbit around Clarion.  Preparations are begun to send a delegation to the surface.

– After a day of negotiations, the UPF forces and the Mhemne reach an agreement to work against the sathar in the system.  They plan to slip to the surface of the planet (Snowball) and contact the resistance there and investigate the sathar factories on the surface. (SFKH4)
61.221– SF Nova prepares to depart the K’aken-Kar system and begins accelerating toward the K’tsa-Kar system.

– UPF forces descend to the surface of Snowball (FS30). After fighting off a Sathar hovercraft, they make contact with the Mhemne resistance on the surface. (SFKH4)

– After consulting with Commander Reider, the UPF forces, assisted by the Mhemne resistance, begin a series of raids on the sathar factories on the surface of Snowball to disrupt sathar operations while they wait for PG Lancet to arrive in system. (SFKH4)

– Descending to the surface of Clarion (White Light), the saurian delegation are met by King Leotus and Princess Leotia as welcome guests.  The next several days are spent in meetings, festivities, and other activities to introduce the saurians to the Clarion culture.
61.222– The larger portion of PG Meteor (retaining the PG Meteor designation) arrive in the FS26 system.  They don’t detect any sathar signals but do detect the saurian beacon.  They begin decelerating toward the inner system.

– The smaller portion of PG Meteor, now designated PG Lancet, arrive in the Padda system.  They begin calculations for a jump to the Waller Nexus system without slowing down.
61.223After two days of discussions, the saurian delegation, escorted by Princess Leotia, begin a multi-day tour of Clarion to look for sites where the saurians could set up a permanent settlement.
61.224– Joined by the True Yaziria escort vessels, the HSS History’s Hope jumps to the OFS222 system.  They immediately begin engine overhauls and plotting the next jump to OFS221.

– The last sathar Transit Group, TG1, arrives at sathar SCC#1 (OFS203).  All ships stand down and complete any maintenance needed after their recent maneuvers.
61.225After training the Mhemne resistance fighters, the combined UPF/Mhemne force make their first raid on a sathar factory.  Catching the factory unprepared, they overwhelm the defenses and manage to capture one of the sathar shuttles. (SFKH4)
61.226PG Meteor arrives in the inner system of FS26.  The ships split up to begin exploring the planets there while remaining alert for sathar vessels.
61.227– After completing engine overhauls and the astrogation calculations, PG Lancet jumps into the Waller Nexus system.  The immediately begin work to jump to the FS30 system, again without slowing down.

– Resting a day after their first assault, the UPF/Mhemne force on the surface of Snowball attack a second sathar factory.  This fight proves to be a bit more challenging as the factory is on alert after the first attack.  The factory is destroyed but the attacking forces are unable to capture another shuttle. (SFKH4)
61.228After 5 days of guided exploration, the saurians decide on a location in the southern hemisphere of Clarion that is about a quarter of the way around the planet from Valencia, Clarion’s capital.  They return to their ships to begin preparations for establishing the settlement.
61.229– After another day of rest, the UPF/Mhemne forces attack the third known sathar factory.  This is the most vicious fight yet and the sathar forces intentionally destroy all the shuttles when it is apparent they will lose the fight. (SFKH4)

– Strike Force Nova settles into orbit around Kwadl-Kik (K’tsa-Kar).  They will remain here for only 2 days before continuing on to Clarion (White Light) to meet the saurians in that system.

– HSS History’s Hope and escorts jump to the neutron star system OFS221. While there was a hint of ship radio signals, it is lost in the natural radio noise from the pulsar.  Work begins on engine overhauls and jump calculations for the trip to OFS224.
61.230After four days examining all the planets in the inner system of FS26, the ships of PG Meteor settle into orbit around one of the two habitable planet in the system to compare notes and prepare for a departure back to Theseus.
61.231SF Nova departs Kwadl-Kik (K’tsa-Kar) for Clarion (White Light)
61.232PG Lancet completes their preparations and jumps into the FS30 system.  They begin decelerating toward the inner system and establish communications with the UPF forces there.
61.233– After four days of searching, the UPF/Mhemne forces on Snowball find another sathar factory.  After a bloody and desperate fight, the UPF/Mhemne forces gain control of the factory and manage to capture an additional shuttle before it can be destroyed by the sathar forces. (SFKH4)

– One day before the ships are ready to jump to OFS224, the HSS History’s Hope and escorts are attacked by 3 unknown vessels (2 corvettes and a Lightspeed Lady class privateer). In the ensuing battle, two of the escorts are destroyed and the History’s Hope is damaged, but they manage to destroy the attackers

Here’s the full file with all the updates:

DetailedFrontierTimelineDownload

October 6, 2020 Tom 1 Comment

Void Jumping, Acceleration, and Other FTL Nuggets

This post is going to get a little bit math heavy toward the middle. Just warning you now.

The idea for this post stemmed from a recent discussion on the Star Frontiers: Alive and Well Facebook group talking about the accelerations involved in faster than light (FTL) travel in that game. I’ve written about this many times over the years on forum posts but since I can’t seem to find those posts (I think some of them at least are on the now defunct forums at starfrontiers.org), I’m going to do it one more time here on this blog as a permanent reference. But before I dig into the details of the math and physics, I’m going to share some links to other posts I’ve made that I do still have.

Other Posts

First up we have a post from 2010 on Void Jumping on my Star Frontiers Network site. I don’t think this article is linked from anywhere anymore so this will help to bring it back to life. This essay talks about some of the issues associated with making a Star Frontiers style void jump for FTL travel. This essay was the basis for the sci-fi novel, Discovery, that I published back in 2011 (has it really been that long!).

Next, in 2015, when I was still writing on the Arcane Game Lore blog, I did a series of posts on Void travel that expanded and refined those ideas a little more in the direction of a personal sci-fi game I work on off and on. The first two of these posts were actually part of the November 2015 RPG Blog carnival.

  • The first is an article on Void Travel Sickness. Not really relevant to this discussion but fun none-the-less and falls under the “nuggets” heading.
  • The second, Your Final Destination – Exiting a Void Jump, talks about variations in your arrival at your destination. The blog carnival topic that month was “Surprises” and both of these articles were things that could add surprises or randomness to your FTL travel. I actually recommend you read this one after the next one as it talks about things at the end of the journey but it can be read first.
  • The third (and final) article in that set was part of my “Designing out Loud” series of articles where I talked about game design decisions and ideas. This one was entitled “Designing Out Loud – Void Jumping” and expanded on the ideas in my 2010 article.

While you don’t necessarily need to read those article to follow along with the following, it definitely wouldn’t hurt.

Void Jumping

The concept of the Void Jump was introduced with the Knight Hawks supplement in Star Frontiers. In the original rules (renamed to Alpha Dawn when the Knight Hawks rules came out), there were no spaceship rules and it just said to treat interstellar travel at the rate of 1 light year per day.

So how does it work? According to the rules, you make a jump by leaving your starting point and accelerating until you reach 1% the speed of light. At that point you “jump” into the Void. To get out of the Void, you just have to slow down slightly. While you’re in the Void, you travel amazingly fast, on the order of 1 light year per second (The rules don’t actually so but imply something close to that so that’s the value I use). Once you jump into your destination system, you swing the ship around and start decelerating. Remember, there is no artificial gravity in Star Frontiers so this acceleration and deceleration is what provides gravity in the ships. Most ships make these trips accelerating at 1g.

So how long does this take? For these calculations, we’ll take 1 g to be equal to 10 meters per second squared (m/s/s) of acceleration. On Earth we define 1 g to be 9.82 m/s/s but rounding up to 10 just makes everything easier and its less than a 2% difference.

Okay, here comes the math.

If you start at rest, your velocity at any given time is just:

v(t) = at

where v is velocity (in m/s), a is acceleration (in m/s/s), and t is time (in seconds). Technically v and a are vectors but we’ll just worry about speed, not direction.

Now, the void jump occurs at 1% the speed of light. We’ll take the speed of light to be 300,000,000 m/s. It’s really 299,792,458 m/s but we’ll again round up to make the math easier. The difference is less than 0.07%. Good enough for this discussion. 1% of that is just 3,000,000 m/s. That’s our target velocity.

Since our acceleration is 10 m/s/s, dividing 3,000,000 m/s by 10 m/s/s gives us 300,000 s of acceleration needed to reach jump speed. That works out to 83 hours and 20 minutes of acceleration. Given that a standard day in Star Frontiers is 20 hours long, that is 4.17 days.

That’s the time to get up to jump speed. It takes that much time to slow down on the other side as well. Which means at a minimum, an interstellar jump takes 8 and 1/3 days, assuming everything lines up perfectly (see the Exiting the Void Jump article for things that might lengthen that).

That’s the time required. What about distances covered? The equation for position is just the integral of the velocity equation above. Again, for starting at rest, and assuming that you measure the distance from your starting point, your position at any given time is given by:

x(t) = \frac{1}{2}at^2

where x is your position in meters. We know what t is from the velocity equation above is 300,000 s. a is just 10 m/s/s. Plugging these in gives us a distance traveled of 450 billion meters or 450 million kilometers. (A lot of people forget that factor of a half and end up with the wrong number.) Now the distance from the Earth to the Sun, called an Astronomical Unit (AU), is 150 million kilometers (again I’m rounding, the actual value is 149,597,871 km so the rounding is less than 0.3%).

So in those 4.17 days of acceleration, you traveled 3 AU. If you started at Earth and headed straight out from the sun, you’d be 4 AU from the Sun. That’s most of the way from Earth’s orbit to Jupiter’s orbit (at a distance of 5.2 AU from the Sun). That distance puts you well beyond the main asteroid belt which ends at 3.3 AU.

Now, these numbers all change if you use a different acceleration. Doing those calculations is left as an exercise for the reader.

ADF and the Board Game Rules

The above all works just fine. The problem comes when you start looking at the rules for the spaceship combat board game and try to rationalize those rules with the math above.

From the board game, we have that one hex is 10,000 km and one turn in the game is 10 minutes of time. Added to that is the ship’s statistic, the Acceleration/Deceleration Factor (ADF) which is described as the number of hexes that a ship can speed up or slow down in a given turn. The fastest ships (fighters and assault scouts) have and ADF of 5.

Let’s look at some numbers. First, what is Void jump speed on the game map. Well, jump speed is 3,000,000 m/s or 3,000 km/s. Since a turn is 10 minutes or 600 seconds, that works out to 1,800,000 km/turn. Given that a hex is 10,000 km across, that works out to a speed of 180 hexes per turn. Since the game map is only 54 hexes wide, you’ll never get to that speed in the game.

The problem comes when people start looking at ADF as acceleration in gees, i.e. that 1 ADF = 1g of acceleration. If you make that assumption, then accelerating at 1 ADF per turn, it would take you 180 turns to get to jump speed from rest. 180 turns at 10 minutes per turn means that it would take just 1,800 minutes, or 30 hours, significantly faster than the 83.33 hours calculated above. Obviously 1 ADF cannot equal 1 g.

So let’s work that out. 1 ADF represents a change of velocity of 10,000 km per 10 minutes in 10 minutes (or 100 km/min/min). That’s an acceleration, just not in the normal units of m/s/s. So lets convert them:

\frac{10,000 km}{10 min * 10 min} = \frac{100 km}{min^2} = \frac{100,000 m}{60 s * 60 s} = 27.778 \frac{m}{s^2} = 2.78 g

So we see that 1 ADF is really 2.78 g of acceleration. You’re not going to sustain that for 30 hours and have anyone in any sort of condition to function unless severe precautions are taken. Heck, even sustaining that for 1 turn (10 minutes) is going to be rough. It’s doable, that amount of acceleration and duration is roughly equivalent of a launch to low Earth orbit with modern rockets, but you wouldn’t want to keep it up for a long time.

That also raises another issue. 5 ADF is actually 13.89 g of acceleration. And Star Frontiers doesn’t have any sort of artificial gravity tech. Pulling those kind of maneuvers is a little unrealistic. (There are discussions about using interia screen tech to help with this but that’s a different article.)

There are a couple of solutions to this. One, which is the one I use and which is probably the simplest, is a willing suspension of disbelief. The board game rules are just that, rules for a board game that simulates (sort of) spaceship combat. There are other issues with the board game physics besides this one, so I don’t expect it to represent “reality”. It’s a fun way to approximately simulate spaceship combat.

Another option, which immediately removes the 1 ADF not equaling 1 g issues, is to change the size of the hexes in the board game. Simply saying that they are 3,600 km in size instead of 10,000 km, makes 1 ADF = 1 g. If you keep the range of weapons the same (measured in hexes as they are described in the game rules, the only thing that really changes is that any planet counters you put on the map have to take up 7 hexes instead of just 1. And it might tweak the gravity rules a bit, but not significantly. This doesn’t solve some of the other problems, however. That’s a whole different post as well.

How I Apply This In Game

So how do I use this?

Basic Application

For most ships, I assume that they have two astrogators that can work in alternating shifts around the clock to do jump calculations. Since the rules say it takes 10 hours of calculation per light year traveled. And since it takes over 80 hours of travel time to get to jump speed. This means that any jump of 8 light years or less takes the same amount of time, namely 8.5 days, which I typically round up to 9 for maneuvering around the station and slight variations in arrival location (see my linked posts). And actually, since I round this up to 9 days, it play it that jumps of 9 light years or less all take 9 days, regardless of distance. Each light year beyond 9 adds a half of day of travel time to allow for the calculations. This is how I calculate the travel times for ships in my Detailed Frontier Timeline.

Again that assumes that they have two astrogators. If not, jumps take significantly longer, namely one day per light year traveled, plus 4.5 days to slow down at the destination, with a minimum of 9 days total travel. So in this case, jumps of five light years or less take 9 days, and each additionally light year adds a day on to the jump time.

Now I do allow the jump calculations to be started before the ship leaves it’s berth, assuming the crew knows when they plan to leave (to within a day or so). But because the planets and stars are always in motion, and the jump calculations have to be done for each specific jump, no more than half the calculations can be done in advance. The rest must be done “in flight.” For me this represents the tweaking and refining of the ship’s course in preparing for the jump that I discuss in the other articles I linked. But that means that even for a ship with a single astrogator, they can reduce the flight time if the astrogator gets started before they leave on the longer jumps.

Traversing multiple systems in a single trip

Another aspect of this is what I like to call the “high speed transit.” This occurs when the ship wants to traverse several star systems but doesn’t need to stop in each one. In this case, the first jump starts as usual, but once they traverse the Void the first time things change.

In each system after the first, until they reach the final system that they want to stop in, they don’t decelerate, at least not appreciably. But rather remain near jump speed, either drifting or, if they want gravity, decelerating for a few hours, flipping around and accelerating, and repeating until they are ready to jump. During this time the astrogators work on the jump and the engineers do any needed engine overhauls. The amount of time spent in system is just the longest of those two activities. Once that’s done, they nudge into the next system and repeat until they arrive at the destination system where it then takes 4.5 days to slow down.

Let’s look at an example: The UPFS Stiletto, an assault scout, is on patrol in Truane’s Star and has orders to get to Dramune as quickly as possible. This route has 4 jumps:

  • Truane’s Star to Dixon’s Star – 5 light years
  • Dixon’s Star to Prenglar – 5 light years
  • Prenglar to Cassidine – 7 light years
  • Cassidine to Dramune – 4 light years

Using normal jumps, these are all less than 9 light years so each jump would take 9 days for a total of 36 days.

Rather than do this, let’s look at what this takes using the high speed transit option. According to the rules, engine overhauls take 60 hours minus 1d10 hours for each engineer level. The rules also say that Spacefleet ships typically have level 4 engineers. That means that on average, it will take 38 hours to overhaul each engine. We’ll assume that there are 2 astrogators and 2 engineers onboard the Stiletto. This is what a high speed transit looks like in this scenario:

  • Accelerate out from Truane’s Star – 4.5 days – plenty of time to do the 50 hours astrogation calculations
  • Transit Dixon’s Star – astrogation calculations take 50 hours (2.5 days of round-the-clock work), engine overhauls only take 38 hours of work, but since there is only one engineer per engine, they have to sleep. So these are the slow part, taking 4 days – so after 4 days, they jump to Prenglar
  • Transit Prenglar – astrogation will take 70 hours (3.5 days of round-the-clock work). This one is closer but the 4 days of engine overhauls is still the limiting factor. After 4 days they jump to Cassidine.
  • Transit Cassidine – Here the astrogation calculations only take 40 hours (2 days of round-the-clock work) and the astrogators get a bit of a break while the engineers finish up. After 4 days, they make the jump to Dramune
  • Decelerate in Dramune – it takes 4.5 days to slow down and arrive at Inner Reach.

All told, this trip takes only 21 days instead of the baseline 36, saving 15 days of travel. The crew might be a little tired, but they made it without taking any risks.

If you only had 1 astrogator and two engineers, one level 3 and one level 2 (more likely on a merchant ship or PC ship), the transit looks like this:

  • Accelerate from Truane’s Star – 4.5 days, same as before. We assume the astrogator got started before they left.
  • Transit Dixon’s Star – Astrogation takes 5 days, engine overhauls take 43.5 for the level 3 engineer and 49 for the level 2 engineer. The level 3 engineer can help the other engineer once they are done so the total time to do the overhauls is five days – Time in system 5 days.
  • Transit Prenglar – In this case the limit is the astrogation which takes 7 days. Time in system, 7 days.
  • Transit Cassidine – This time the astrogators win and the jump is waiting on the engineers – Time in system, 5 days.
  • Decelerate in Dramune – 4.5 days.

Total time: 26 days. Takes a little longer but still faster than the base 36 hours. If there was only one engineer, it would actually take longer than 9 days per system as one engineer just can’t do engine overhauls on two engines in each system that fast (unless they are level 5 or 6). You might as well stop over in the station each time unless you have a reason not to go into a system.

Final Thoughts

That’s it for this post. There are other aspects of the travel that I could talk about such as vector movement, the process of lining up for a jump, what happens to your calculations and alignment when you have to maneuver for a combat or something else, and a discussion on how long those alignment efforts take anyway. Some of those ideas I touched on in the posts I linked. I might look at these again in a future post or two as well.

What are your thoughts? What questions do you have? Share them in the comment section below.

September 15, 2020 Tom 1 Comment

Detailed Frontier Timeline – FY 61.173 to FY 61.203

This was a rough month for getting the timeline posts out on Twitter. I was doing good and had them all scheduled up through my vacation, but then when I got back, completely dropped the ball for the rest of the month. Mainly do to being swamped by dealing with the loss of my truck and getting it replaced. In fact, I’m still getting caught up and some of the events in this post won’t make it up until later today.

This was another busy month in the timeline with several threads overlapping including the completion of the Dramune Run and Mutiny on the Eleanor Moraes module events, and the beginning of the Face of the Enemy module events. Additionally, the last saurian Ark Ships leaves their home system and the saurians make contact with the Frontier.

Here’s the events of the last month:

Date (FY)Events
61.173– The Osprey departs Minotaur (Theseus) for their jump to the Padda system.

– The sathar vessels overtake the 8th Ark Ship just hours before it is ready to jump.  The escort vessels, combined with the defenses of the Ark Ship, put up a heroic defense. 

– The escort vessels sacrifice themselves to ensure the escape of the Ark Ship and manage to damage the pursuing sathar vessels enough that the Ark Ship, while severely damaged itself, can escape their pursuers and slip alone into the Void.  They arrive safely in OFS191.
61.174– Decelerating toward the inner regions of the OFS191 system, the 8th saurian Ark Ship begins scanning the binary star system. 

– After being sedated and interrogated for 10 days, the crew of the Gullwind is taken to meet with the Malthar.  On the return to their cells, their guards are set upon by chukkahs running free in the station.  They escape to the docking bay where the Gullwind is being held. (SFKH1)

– Next to the Gullwind’s bay, the crew discovers a room with cages of imprisoned chukkahs and transport containers for them.  Loading as many as they can into the transport containers and on to the Gullwind, they then depart the station just as a swarm of combat robots attack the ship. (SFKH1)

– As the Gullwind departs Darkworld station, the Malthar’s ships pursue and attempt to destroy the vessel.  The fight is quickly joined by both the Inner Reach militia and the elements of Strike Force Nova (LC, 2xFF, 4xAS) in the system.   (SFKH1)

– With the Spacefleet ships quickly turning the tide of the battle, the pirate and Outer Reach militia ships scatter.  The Third Dramune War is over. (SFKH1)
61.175– Arriving at Inner Reach, the crew of the Gullwind give a full report to the Inner Reach Government and Spacefleet on their discovery and the events of the Dramune Run.  The crew discovers that Garlus left the Gullwind to them in his will.

– After a quick resupply, the element of SF Nova that survived the battle depart for the Fromeltar system to rejoin the Strike Force.
61.176– Just a few hours before making the jump to the Padda system, the CMS Osprey detects unknown radio signals in the outer system.  The ship’s energy sensors confirm several faint sources in the same direction.  They have passed close to the saurian Ark Ship and its escorts and detected some intership communications.

– The CMS Osprey attempts to contact the unknown radio source but receives no response. They radio the contact back to Minotuar and continue on their way to the Padda system.

– After analyzing the report from the CMS Osprey, the destroyer, frigate, and two assault scouts of the Theseus milita begin boosting toward the location of the contact.
61.177– The HSS History’s hope arrives back in the YS07 system and begins deceleration. Unfortunately, all jumps forward from here are 10-12 light years long.  The team begins weighing which of the five systems would make the most sense for progress beyond it.

– The CMS Osprey successfully jumps to the Padda system.  They immediately begin working on the jump calculations to the Waller Nexus system while not slowing down, only angling their vector toward that system.

– The saurians detect the militia ships traveling toward them. Given their analysis of the radio signals collected so far from the system and the CMS Osprey, they believe the species living here are not allied with the Sathar and decide to risk communication.
61.178– With the militia ships only a day away and now decelerating toward their location, the saurians open communications, attempting to contact the approaching ships.  The Theseus militia receives the communication attempt and responds in kind. They also notify Minotaur of the development.

– While initial communication between the saurians and UPF is difficult, both due to the long light delay as the signals travel between the ships, and the lack of a common language, progress is made as the distance between the ships decrease and the saurians’ computers translate Pan-Gal into saurian.
61.179– The Theseus militia ships arrive at the location of the saurian Ark Ship and its escorts. They are impressed by the design of the saurian Battle Rays and the sheer size of the Ark Ship itself. 

– Rudimentary communications between the saurians and Frontier races are established and the story of the saurians’ flight are related to the crews of the UPF ships.  This information is relayed back to Minotaur.

– The Minotaur government notifies the UPF Council of Worlds via subspace radio of the detection of the saurian vessels and their contact with them.

– The detachment of SF Nova arrives in the Fromeltar system from Dramune.  The remainder of the Strike Force beings accelerating for a jump to the Kizk-Kar system.
61.180– Having found no suitable planets in the OFS191 system, the 8th saurian Ark Ship begins accelerating for a jump to the OFS179 system.

– The Council of Worlds temporarily suspends all other deliberations to discuss and debate what to do about the saurians.
61.181– Having picked a system as their next target, and with deceleration complete, the crew of the HSS History’s Hope begin work on jump calculations for the next leg of their journey, a M5 dwarf 12 light years away.

– The detached ships from SF Nova rejoin the main group as it accelerates toward Kisk-Kar.
61.182– Calculations complete, the CMS Osprey jumps into the Waller Nexus system and begins decelerating toward Mahg Mar.  They radio the UPFS Eleanor Moraes to establish communication with the downed ship.

– The UPFS Elanor Moraes responds to the hail from the CMS Osprey and transmit the survey data they have collected along with coordinates for the Osprey to find the Moraes.
61.183As the Council of Worlds continue discussion, the Minotuar (Theseus) government, under pressure from many of the citizens of their world, invite the saurians to bring their ships into the inner system. 
61.184– While working on jump calculations and surveying the YS07 system, the radar system on the HSS History’s Hope suddenly stops working.

– As the engineers begin to work on HSS History’s Hope’s radar, they realized that they have been out so long that they have missed their annual maintenance.  They discover several other systems that may cause problems in the future.

– With it being about 100 days to make a high speed transit, perform the maintenance, and return to their current location, the HSS History’s Hope crew must decide if they should return or press forward with an increased chance of breakdowns in future jumps.
61.185– After two days of internal debate, the saurians begin accelerating toward Minotaur, escorted by the militia ships.

– The 8th saurian Ark Ship successfully jumps to the OSF179 system.  The immediately detect a beacon left by the 7th ark ship indicating that the system had been surveyed but nothing suitable found.  Deciding that the neutron star in OFS192 is a non-starter, they begin plotting a course to FS58 and shifting their vector for the jump.
61.186– After four days of deceleration, the Osprey settles into orbit around Mahg Mar (Waller Nexus).  After a couple of orbits to orient their mapping systems, they locate the UPFS Elanor Moraes and descend to the planet’s surface, landing just a few hundred meters from the survey vessel.

– With repairs still ongoing on the HSS History’s Hope’s radar system, the crew comes down on the side of caution and decide to return to Scree Fron for maintenance.  The calculations for the jump forward are aborted and calculations are started to jump back to YS06.
61.187With the arrival of the CMS Osprey and the supplies it brought, the repairs on the UPFS Eleanor Moraes begin to progress much quicker.  Captain Dentin takes command of the expedition and begins sending out the survey robots to scout the surrounding terrain.
61.188– SF Nova arrives in orbit around Zit-kit In the Kisk-Kar system.  They will remain here for 6 days.

– The saurian ships settle into orbit around Minotaur (Theseus).  Constant holovid coverage has greatly increased the public interest in these strangely graceful ships.
61.189– The Theseus militia establishes a “no fly” zone around the saurian vessels to keep away all the curious onlookers attempting to visit and observe the ship up close in their small shuttles and private yachts.

– Having discovered what appears to be some sort of village about 30 km away members of the Moraes crew are sent by Captain Dentin to investigate with the Osprey crew continues working on the repairs. (SFKH3)
61.190– The two newest assault scouts for SF Meteor arrive at Gollwin Station orbiting Morgaine’s World (Prenglar).  They are debriefed and join with their fellow assault scouts and formed into Patrol Group Meteor until the capital ship complete construction.

– About 3/4 of the way to the village the crew of the UPF Eleanor Moraes discover a strange, small vehicle containing the bodies of two dead sathar and what appears to be a small, functioning robot.  They radio the find back to the Osprey which sends out another team to collect the vehicle. (SFKH3)

– With about 3 km left to the village, the Moraes crew reaches a tall cliff that their explorer cannot climb.  They need to continue the rest of the way on foot.  They camp at the base of the cliff for the night. (SFKH3)
61.191– The saurians agree to send an envoy to meet with members of the Minotaur government aboard Minotaur station.  They request that the captains of the militia vessels they had met originally be present at the meeting.

– Security is enhanced on Minotaur station in preparation for the historic first meeting with the Saurians.  Several protest groups are dispersed that were threatening to become violent.

– As the crew of the UPFS Eleanor Moraes reach the top of the cliff, a strange, birdlike creature briefly emerges from the underbrush and then disappears again. The crew can see it crouching in the bushes and decide to wait to see what happens. (SFKH3)

– After a several minutes, the creature emerges again from the underbrush and begins trying to talk to the Moraes crew.  Establishing some basic communication with the aid of a polyvox, the creature, Beet-Chest, begins leading them to his village. (SFKH3)

– Meeting with the village elders, the Moraes crew learn that the sathar had arrived on the planet about 3 months ago and 2 sathar attacked a party of the Notui (what the bird-like creatures call themselves) and were killed by the Notui.  The crew spends the night in the village after reporting in.
61.192– Patrol Group Meteor is dispatched to White Light via Timeon.

– The saurian delegation arrives at Minotaur stations.  Large crowds line the passages hoping to catch a glimpse of the visitors, but they are quickly moved away from the crowds.  After several hours of discussion, they return to their ships.

– Having determined the general direction of where the sathar’s ship landed (roughly in the same direction from the village as the UPFS Eleanor Moraes), the Moraes crew return to their ship to confer with Captain Dentin.
61.193– Calculation and course corrections complete, the 8th saurian Ark Ship jumps to the FS58 system.  They again detect a beacon from the 7th Ark Ship and realize they are still following the previous ship.

– Having completed jump calculations and gotten the radar system fixed, the HSS History’s Hope begins accelerating toward YS06, they plan to make a high speed transit back to Scree Fron spending only enough time in each system to overhaul engines and make jump calculations.

– The saurians of the 7th ark ship return to Minotaur station to continue their discussions with members of the UPF and Minotaur governments, returning once again to their ships at the end of the day.  This continues for the next several days.
61.194– After much deliberation the saurians of the 8th Ark Ship decide that jumping through the nebula again (which would take them to the Tristkar system) would not be the best plan, and like the 7th Ark Ship before them, start plotting a jump to the Theseus system.

– Strike Force Nova departs Zit-Kit (Kisk-Kar) for the K’aken-Kar system.
61.195After three days of detailed survey by the robots, no trace of the sathar ship can be found on land and Captain Dentin suspects that it landed in the water of the nearby river.  The Moraes’ crew sets out to try to find some trace of it along the river.
61.196A delegation from White Light, including Crown Princess Leotia Valentine Leotus, arrives at Minotaur station and joins the deliberations with the Saurians. 
61.197– Jump calculations complete, the 8th saurian Ark Ship begins accelerating toward the Theseus system.

– After two days of careful search along the riverbanks, the Moraes crew discover a metal cable attached to a stake in the ground, partially buried in the sand, and extending out into the river.  Investigation shows some sort of small craft submerged in the river at the other end of the cable.
61.198– HSS History’s Hope jumps into the YS06 system and begin immediately working on the engines and jump calculations for a jump to YS05.

– Using spacesuits with improvised weight belts, the Moraes crew investigate the submerged vessel.  It is a hull size 2 ship of sathar design never seen before.  They locate the airlock at the other end of the cable but do not attempt to enter.
61.199Descending again to the sathar ship, the Moraes crew breach the security system on the airlock and enter the ship.  Fighting through the ship’s defenses, they gain control of the ship with only minor damage to the ship and no serious injuries to the crew.
61.200After a day of examining the sathar vessel, the Moraes crew discover what appears to be a sathar base of operations for the ship located in the FS30 system and astrogation data to get there.  They send a report back to the Frontier Expeditionary Force HQ on Clarion.
61.201PG Meteor arrives in orbit around Lossend (Timeon).  They plan to spend two days here before continuing on to Clarion (White Light).
61.202– The 8th saurian Ark ship successfully jumps into the Theseus system and immediately detect radio signals from the inner system.  A few hours later they detect the 7th Ark Ship and establish communications.

– The UFPS Eleanor Moraes and CMS Osprey receive orders from the Frontier Expeditionary Force commander to select a crew to man the sathar scout ship.  The three ships are to jump to the FS30 system and attempt to capture the sathar base.

– PG Meteor’s time in Timeon is cut short and their orders are changed to proceed immediately to the Theseus system to support Frontier Expeditionary Force operation in the FS30 system.  They leave immediately for the White Light system.
61.203– Strike Force Nova arrives at Ken’zah-Kit in the K’aken-Kar system.  They will remain in this system for 18 days patrolling the outer system.

– Engine overhauls and jump calculations complete, the HSS History’s Hope jumps back to they YS05 system and begins working on the jump to YS03.

And here’s the full timeline file:

DetailedFrontierTimelineDownload

September 8, 2020 Tom 1 Comment

Posts navigation

1 2 … 5 Next →
Become a Patron!

Recent Posts

  • Detailed Frontier Timeline – FY61.357 to FY61.381
  • Back to Blogging
  • Moonbright Stinger Miniature and Model (aka The Gullwind)
  • State of the Frontier – April 2021
  • Battle of Liberty – FY61.362
  • Second Battle of Ken’zah-Kit (K’aken-Kar) – FY61.358
  • Detailed Frontier Timeline – FY61.326 to FY61.356
  • Second Battle of New Pale (Truane’s Star) – FY61.354
  • State of the Frontier – Jan 2021
  • Spacefleet Naming Conventions

Categories

  • 3D Models
  • Adventures
  • Background
  • Creatures/Races
  • Deck Plans
  • Equipment
  • General
  • Locations
  • Maps
  • NPCs
  • Optional Rules
  • Patreon-only
  • Project Overviews
  • Reviews
  • Setting Material
  • Starships
  • System Brief
  • Vehicles
  • Writing

Recent Comments

  • Frank Patnaude on Thoughts on the Second Sathar War
  • Frank Patnaude on Thoughts on the Second Sathar War
  • Detailed Frontier Timeline – FY61.357 to FY61.381 – The Expanding Frontier on Second Battle of Ken’zah-Kit (K’aken-Kar) – FY61.358
  • Back to Blogging – The Expanding Frontier on HSS History’s Hope Deck Plans – part 1
  • Dominic Pelletier on Maps and Counters
  • Cian Shay on A New Starship Construction System – part 5 – Engines Revisited
  • ANDREW LAWTON on Moonbright Stinger Miniature and Model (aka The Gullwind)
  • Aemon Aylward on Moonbright Stinger Miniature and Model (aka The Gullwind)
  • ANDREW LAWTON on Freighter Model and Miniature
  • ANDREW LAWTON on Moonbright Stinger Miniature and Model (aka The Gullwind)

Archives

  • May 2022 (2)
  • June 2021 (1)
  • April 2021 (1)
  • February 2021 (4)
  • January 2021 (6)
  • December 2020 (5)
  • November 2020 (11)
  • October 2020 (4)
  • September 2020 (5)
  • August 2020 (4)
  • July 2020 (6)
  • June 2020 (5)
  • May 2020 (8)
  • April 2020 (5)
  • March 2020 (5)
  • February 2020 (5)
  • January 2020 (5)
  • December 2019 (7)
  • November 2019 (4)
  • October 2019 (6)
  • September 2019 (5)
  • August 2019 (6)
  • July 2019 (7)
  • June 2019 (5)
  • May 2019 (6)
  • April 2019 (7)
  • March 2019 (4)
  • February 2019 (5)
  • January 2019 (7)
  • December 2018 (5)
  • November 2018 (10)
  • October 2018 (4)
  • September 2018 (4)
  • August 2018 (5)
  • July 2018 (4)
  • June 2018 (4)
  • May 2018 (12)

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
Powered by WordPress | theme Layout Builder