kermit

Crescent Expanse: Warp Lane 7 — The Penultimate Week Bridge Memo Command and Bridge Crew, The warp gate leading to Warp Lane 1, our route back to charted space, has been restored to an operable state. Final readiness checks will be performed due to the derelict condition of the warp gate, with the SCCV Horizon's gate-assisted warp jump scheduled next weekend for 2467-11-02. Should the final GO be given, we will have successfully returned to safer spaces. Also resulting from the reactivation of the warp gate, the PMV Chromatic, an asset protection cruiser of Nexus Corporate Security, has arrived in the SCCV Horizon's current system as part of our vessel's now unneeded rescue: Nexus Corporate Security logistics personnel will be performing repeat resupplies over the next week to fully replenish the SCCV Horizon's stores. A Stellar Corporate Conglomerate executive has been scheduled to board the SCCV Horizon tomorrow to establish interim contact with the Chainlink, and to open an initial inquiry into the vessel's Crescent Expanse Operation. Of lesser importance, a C'thuric 'Klat'xatl' hivecell has embarked onto the SCCV Horizon as in-distress rescues. Cooperation between this hivecell and present Horizon command was integral to the safe and timely restoration of the warp gate, and so they will be permitted passage on the SCCV Horizon to the first safe port within the known Spur. Well done all. Routed via internal relay. Composed by Virgil AI.

Crescent Expanse: Warp Lane 7 — Week 7 —— Bridge Memo: Ship Navigation Good afternoon, Command and Bridge Crew, After an additional week stay in CES-142 assisting the Coalition of Colonies surveyors embark on the SCCV Horizon, and following an expedition to recover supplies from an infested auxiliary outpost, the following developments should be noted: Operations has processed a significant quantity of supplies recovered from a supply cache at the auxiliary outpost. Though the ship continues to lack more specialist and luxury goods, the vessel has resupplied enough to complete our operation in Warp Lane 7 comfortably. Engineering was able to recover a large quantity of gaseous phoron from the outpost, enough for an additional bluespace jump. Command was able to identify and recover warp navigation data from the outpost. The information from this data will allow the SCCV Horizon to perform twice the manoeuvres in one week. ((OOC: The SCCV Horizon can perform 2 movements during 1 of its turns using the Warp Navigation Data — when is up to you, but it can only be done once)) Regarding the Malebranche: The Galga-class surveying vessel with an improvised explosive payload has successfully destroyed one of the Malebranche's escorts, and rendered moderate damage upon the Malebranche itself. The remotely piloted vessel was sent to the CES-144 and was last tracked rendezvousing with the Malebranche, where it then detonated. It is expected that the Malebranche will need to take one week to recover from this action. With the Malebranche's escorts at reduced effectiveness, any attack on the Malebranche itself is more likely to succeed. The escort destroyed is also believed to have been transporting a significant quantity of supplies and fuel utilised by the ship group; at risk of supply loss, the Malebranche and its remaining escort may disengage in a number of weeks if it is unable to keep up with us. The Warp Interdiction Net has been planted in the egress zone of CES-142's warp gate. Should the Malebranche enter the system, the interdiction net should overload the Malebranche's warp drive, causing catastrophic power failures that, hopefully, should render the vessel inoperative for one week. Finally, as previously stated, the distress beacon was scheduled to be activated on 2467-10-11. With the beacon's activation, the SCCV Horizon's location will be broadcasted to all vessels in the region, including a potential rescue vessel if the vessel is unable to locate the warp gate off of the current warp lane. ((OOC: The deadline is being set for Saturday, 1st of November [so, 3 more turns])) Let us endeavour to find this warp gate as soon as we can, or hope our rescue finds us to direct us to one. Routed via internal relay. Composed by Virgil AI. ——— TO: Command, Bridge Crew FROM: Automated Bridge Notices SUBJECT: Bridge Notice: Flight Plan Update MESSAGE BODY: A flight plan update has been made. The SCCV Horizon is now routing to CES-146 via WARP GATE TRANSIT. Estimated time of arrival: 5 DAYS. Please make the appropriate preparations.

Crescent Expanse: Warp Lane 7 — Week 6 ————— Bridge Memo: Ship Navigation Good morning, Command and Bridge Crew, Following the investigation of and response to a Coalition of Colonies surveying outpost in CES-142, a number of developments should be noted: After an agreement between Horizon Command and the crew of the surveying outpost, the surveying outpost's crew will be embarking upon the SCCV Horizon in 3 days time as distress signal rescues. They have been provided basic accomodation, passenger credentials, and have been slotted into an essentials-only rationing schema. This information has been forwarded to Coalition of Colonies consulate staff. The SCCV Horizon, by restoring the outpost's water-ice electrolysis-based hydrogen refinery and successfully prospecting a rich ice deposit, has had a number of deliveries of hydrogen, oxygen, and other organic volatile gases. As such, with many of these being usable as bluespace drive moderators, our bluespace jump budget should now accomodate for 3 jumps, up from 2. As part of the outpost crew's evacuation from the surveying outpost and to compensate the SCCV Horizon for aid rendered, we have received a notable quantity of supplies. If we can locate another source of supplies, we should be able to fully resupply for the journey out of Warp Lane 7 and make it out of our supplies struggle. ((The supplies count will remain at 'Partially Resupplied', for which the Scarcity PR will remain merged. Finding one more resupply option will have the Horizon become 'Adequately Supplied' and the Scarcity PR unmerged. Resupplying isn't *necessary* to leave Warp Lane 7, if you can tolerate the scarcity!)) With the dereliction of their damaged Galga-class surveying vessel, the surveying outpost's crew have agreed to refit the vessel to hold an explosive payload, which can be remotely piloted into the Malebranche's heading. It's rendezvous with the Malebranche next week should see significant damage done to the Malebranche or its escorts. Regarding the Malebranche, they are hot on our tail. It appears their familiarity with this region has seen them cross double the anticipated distance. This manoeuvre of theirs has put us into their sensor range. Fortunately, their hasty traversal of the warp lanes spared the ISS Lu'Nioh from a confrontation. Routed via internal relay. Composed by Virgil AI.

This is running the rounds now and will have a decision soon.

TO: Command, Bridge Crew FROM: Automated Bridge Notices SUBJECT: Bridge Notice: Flight Plan Update MESSAGE BODY: A flight plan update has been made. The SCCV Horizon is now routing to CES 142 via WARP GATE TRANSIT. Estimated time of arrival: 5 DAYS. Please make the appropriate preparations.

Crescent Expanse: Warp Lane 7 — Week 5 ————— Bridge Memo: Ship Navigation Command, Bridge Crew, Internal problems aside, I hope some respite was found over the last weekend with no major, external operations having been undergone. Unfortunately, your attention is forthwith required due to a development regarding the Malebranche. The ship has turned its sensors to our current location, having seemingly received a tip off from locals within the region. The Malebranche is likely to begin manoevring to CES 144, which we should endeavour to vacate by their arrival. The ship awaits course plotting. Routed via internal relay. Composed by Virgil AI.

TO: Command, Bridge Crew FROM: Automated Bridge Notices SUBJECT: Bridge Notice: Flight Plan Update MESSAGE BODY: A flight plan update has been made. The SCCV Horizon is now routing to CES 144 via WARP GATE TRANSIT. Estimated time of arrival: 5 DAYS. Please make the appropriate preparations.

———— OOC Permanent Settlements Systems with permanent settlements (prescribed a different colour, EG. purple in the case of the Lu'Nioh) can have actions done to them, as follows: Barter: Resources can be exchanged at a 1:1 rate. EG. 1 Supplies can be bought for 1 Bluespace Jump. Special resources, such as the Warp Interdicton Net, also counts. This doesn't cost a turn, and the SCCV Horizon can still move in the same week. This can be done every 2nd week, and the system will be marked with a green exclamation mark (!) when this option is available. Befriend: Gifting 2 of any resource will sway the settlement towards the SCCV Horion. This doesn't cost a turn, and the SCCV Horizon can still move in the same week. This only needs to be done once. Raid: The SCCV Horizon can raid the settlement for resources. This does cost a turn, and sets the stage for that weekend's event. This will remove the permanent settlement from the map. This can be done at any time. If the Malebranche enters a system with a permanent settlement, and that settlement's faction isn't amiable with the Malebranche's faction, the settlement will be engaged. There is a 80% chance the settlement is disabled, removing it from the gamemap. If the settlement survives, the Malebranche is placed into its Recovering state and misses its movement. ———— The Distress Beacon and Other Turn Options The SCCV Horizon has now become desperate enough to consider the additional options per turn (read: I only just thought of these): Distress Beacon: The SCCV Horizon can deploy its distress beacon, alerting all nearby ships and stations (including the Malebranche) of its location. This will put the Malebranche into's Pursuing state and it will beeline the SCCV Horizon's location at time of emitting the distress beacon. The Distress Beacon is a prerequisite for any rescue vessels to be able to locate the SCCV Horizon. Because of such, the Distress Beacon will be launched uninfluenced by player decision on 2467-10-11, if the SCCV Horizon has not yet found and used Warp Lane 7's exit. It may still take some time for the rescue vessel to arrive however (basically, when I can't manage this minigame anymore and need to wrap things up lol) Create Debris Field: The SCCV Horizon can expend 1 Supplies to leave a bunch of debris in a warp gate's ingress zone, similar to using a Warp Interdiction Net. This will have a 50% chance to put the Malebranche into its Recovering state if it uses that warp lane. A costly and unreliable alternative to a warp interdiction net, for when the net has already been used or you want to save it for a more optimal usecase. Other reasonable actions can be suggested and will may considered. Keep them simple, like the Debris Field action, and avoid contradicting/bypassing any 'rules' or other actions.

Crescent Expanse: Warp Lane 7 — Week 4 ———— Bridge Memo: Ship Navigation Good morning, Command and Bridge Crew, The SCCV Horizon awaits navigation to a new system. After the SCCV Horizon's impromptu port of call at the ISS Lu'Nioh, a sensor data exchange has seen a number of unconventional warp lanes (marked in yellow in sensor graphics) added to the SCCV Horizon's registry. These warp lanes are consistent with lanes often charted and frequented by smugglers and often bypass longer routes, however they can be risky to traverse, particularly in larger vessels such as ours. ((OOC: There is a 10% chance to lose either 1 Supplies OR 1 Bluespace Jump Budget when using a yellow smuggler's lane)) Xar'qui 52 and the ISS Lu'Nioh will continue to be monitered for future transmissions directed to the SCCV Horizon, and it may be possible to trade with them again should we be unable to find a timely route out of Warp Lane 7. It should also be noted that the SCCV Horizon is soon to be overdue its expected return date, with the original flightplan seeing the vessel return on 2467-09-25. It is this intelligence's hope that Central Command will have a contingency plan in place in the event the SCCV Horizon far exceeds its expected return date, however we cannot predict when any such rescue may arrive. Finally, the SCCV Horizon is critically low on supplies. Automated measures will be taken to stretch existing supplies; it is strongly advised to prepare and implement additional supply conservation strategies, and ensure crew members are adhering to preexisting conservation strategies.

TO: Command, Bridge Crew FROM: Automated Bridge Notices SUBJECT: Bridge Notice: Flight Plan Update MESSAGE BODY: A flight plan update has been made. The SCCV Horizon is now routing to XAR'QUI 52 via BLUESPACE JUMP. Estimated time of arrival: 5 DAYS. Please make the appropriate preparations.

Crescent Expanse: Warp Lane 7 — Week 3 ——— Bridge Memo: Ship Navigation Good morning, Command and Bridge Crew, The SCCV Horizon awaits course adjustment after evaluation of the vessel's current situation. Following the incident at the hivebot-infested propellant depot, a number of important developments should be noted: The SCCV Horizon was able to salvage 1 weeks worth of supplies from the derelict, as well as the surrounding graveyards of hivebot robot debris left by the Purpose synthetics. This is only enough to recoup what was lost relocating to the system. Scans prior to the derelicts detonation, a successful attempt to interrupt the worst of the hivebot interference of the SCCV Horizon, indicated the gas holding tanks were left untapped of a potential 1 weeks worth of bluespace drive moderator gases. The Purpose synthetics encountered around the derelict disappeared from our sensors, alongside all equipment and material brought with them. Their treatment by SCCV Horizon personnel suggests future aid is unlikely. The SCCV Horizon continues to experience network faults, despite best efforts to prevent them. ((OOC: For reasons currently unknown to the crew, there is a 25% chance to lose an additional 1 supplies per week)). In addition to this, the Malebranche was detected warping into the Berkley 73 system and is now actively patrolling Warp Lane 7. The sensors suite will continue to track the Malebranche, utilising bluespace sensors unable to be traced by the dated vessel. Routed via internal relay. Composed by Virgil AI. ——— OOC On the Malebranche The Malebranche is now on the gamemap in its attempt to pursue the SCCV Horizon. The Malebranche has a shorter sensor range than the SCCV Horizon, and can only see adjacent systems. The Malebranche will move a random direction as permitted by warp lanes. A random number will be generated, with a number corresponding to a direction. The Malebranche has 4 'patrol' states: Hunting: The Malebranche is not aware of the SCCV Horizon's location and is attempting to locate it. Pursuing: The Malebranche is aware of the SCCV Horizon's location (or last known location), and will begin moving to that direction. This state is triggered when 'spotted' by the Malebrache by being in an adjacent system. This state can be triggered by certain event outcomes, where something may tip of the Malebranche. Disengaged: It is possible the Malebranche to give up, at which point it will return to Sawal. As you can infer by previous posts, this requires rendering its escorts non-operational, which can be done a number of ways, such as with the help of potential allies. Recovering: The Malebranche is recovering from an attack or being interdicted. It skips its movement that week. The Malebranche has 2 'targetting' states: No Lock: The SCCV Horizon is not actively being tracked by the Malebranche. Locked On: The SCCV Horizon has locked on and can 'see' the SCCV Horizon. This is usually hand-in-hand with the Malebranche's 'Pursuing' state, and is used to differentiate whether the Malebranche is pursuing because it can see the SCCV Horizon, or if it's pursuing what it thinks is the SCCV Horizon. The Malebranche has 3 special capabilities: The Malebranche has a 75% chance to perform a special capability a turn, where a special capability is selected by random, and where a special capabilities may require a precondition (eg. being Locked On).