This is the data I provided to my players regarading the Cause Rampant
Cause Rampant (FI-6412, later CF-6412)
Laid down 360-1002 Gashidda No. 2 Yard
First flight 106-1005
Transferred to fleet auxiliary 1048 and used as a fleet tanker/bulk carrier
Refurbished into frontier cruiser
Conversion begun 321-1084
Returned to duty 005-1086
Refit 135 to 270-1088
Refit included fitting an ISMM Model 7.3 on-board computer system with multiple input stations and limited AI with fibre-optic back-up network.
Refit 014 to 165-1102
Refit included removal of failed black globe generator and strengthening of forward decks to allow for less hazardous fuel-skimming operations.
Data in computer includes data on Solomani Rim, Magyar, Dark Nebula, Ustral Quadrant, Canopus and Hanstone sectors. (Data for Hanstone is incomplete.) This includes navigation and clearance codes for imperial naval bases and the imperial naval depots in the Daibei, Diaspora and Solomani Rim sectors.
Lost on operations in 1103 fate unknown
This is what I decided happened to the vessel
The Cause Rampant was assigned to the 96th Fleet based in the imperial portion of the Magyar sector. The jump-5 capability of the vessel keeping the cruiser in service despite its age. This resulted in the vessel being chosen for a series of missions into the Dark Nebula, Ustral Quadrant, Canopus and Hanstone sectors.
1. Transport the imperial ambassador and entourage to Kusyu in the Aslan Hierate. This route was chosen as the appointed ambassador was coming from the Solomani Rim sector. This involved crossing the Solomani Confederation border and transiting Confederation Space. The Confederation had granted grudging permission for this transit.
2a. Proceed via Aslan space into the Ustral Quadrant spreading imperial good will to both the Aslan client states and independent systems.
2b. Promote pro imperial feeling and support against the Solomani on worlds likely to be receptive.
3. Enter the Canopus and Hanstone sectors, Promote pro imperial feeling and support against the Solomani on worlds likely to be receptive. Particularly the multi-system states of the Trita Brotherhood and Jurisdiction of Nadon in the Canopus sector and the Fteiheiel Oih (Aslan) and the Council of Heads in the Hanstone sector.
4. Investigate the problems the Solomani Confederation is having which are limiting expansion in the Rimward sectors.
The Cause Rampant successfully arrived at Kusyu in the Aslan Hierate, safely delivering the imperial ambassador and entourage.
The vessel also successfully transited through the Ustral Quadrant making a number of potentially valuable contacts.
In the non- Solomani portion of the Canopus sector the Cause Rampant was unexpectedly attacked by the Solomani “High Justice” class battleship “Ultimate Victory” Early in the engagement the Cause Rampant sustained a bridge hit rendering the captain unconscious…(The player sometimes thinks his character is Dillon Hunt of the Andromeda)
...The ships AI (not as limited as its designers intended) decided it would like to survive and engaged the jump drive resulting in a massive misjump. The ship did sustain some damage both because of the combat and the misjump. The ship was found ninety odd years later drifting in an asteroid belt with no crew on board (save the captain who was in a medical cold berth). Its condition when found was - the power plant was still operating at minimal levels fuel almost exhausted. The ships maintenance droids had repaired the bulk of the damage sustained by the jump drive though there was insufficient fuel to activate it again. Some compartments were sealed off because of damage that could not be repaired without more parts (the ships on-board stocks having been exhausted).
The ships computer logs show that the remainder of the crew abandoned ship taking all the small craft and fuel shuttles with them.
The jump drive when examined was found to be operational and Alston does have some TL14 parts available from an old Regal class battlecruiser used as the orbital starport of Alston.