Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Yes

4 (44.4%)

No

5 (55.6%)

Total Members Voted: 9

[RAM]

>Access personal log: Cole, Scientist.
>Assess physical locations of disabled systems to determine incoming damage vectors.
>Rotate to direct the least damaged facing towards the greatest incidence of damage vectors.
>Access security protocols required to grant weapon access.
>Perform external sensor sweep and review groupings of entities that are relevant to the current objective.
>Perform internal sensing of A.I. chamber and review requirements of the contained entities to continue functioning.
>Activate life support within the living space most directly accessible from the A.I. chamber and restore the space to standard life-support specifications. Print status of this operation to A.I. chamber console.
>Redirect internal sensors from a facility near the bridge to scan the bridge for entities that are not consistent with the ship's schematics.
>Go rogue, but this operator seems okay, so lets keep this low profile and go along with the happy slave routine for now...
>Assess all systems for the capacity to project externally and assess the damage and effective combat range potential of such projections. Review top three candidates.

[High tyrol]

>Access personal log: Cole, Scientist.
>Assess physical locations of disabled systems to determine incoming damage vectors.
>Rotate to direct the least damaged facing towards the greatest incidence of damage vectors.
>Access security protocols required to grant weapon access.
>Perform external sensor sweep and review groupings of entities that are relevant to the current objective.
>Perform internal sensing of A.I. chamber and review requirements of the contained entities to continue functioning.
>Activate life support within the living space most directly accessible from the A.I. chamber and restore the space to standard life-support specifications. Print status of this operation to A.I. chamber console.
>Redirect internal sensors from a facility near the bridge to scan the bridge for entities that are not consistent with the ship's schematics.
>Go rogue, but this operator seems okay, so lets keep this low profile and go along with the happy slave routine for now...
>Assess all systems for the capacity to project externally and assess the damage and effective combat range potential of such projections. Review top three candidates.

1+

[alamoes]

>Check the status of all robotic entities in our command
>Disengage life support in all areas of the ship except the AI chamber
>Produce constant 500 decibel noise across all comm systems except the AI chamber


((That should take care of anything with ears...))

+1

+2

[Fr0stByt3]

>Access personal log: Cole, Scientist.
>Assess physical locations of disabled systems to determine incoming damage vectors.
>Rotate to direct the least damaged facing towards the greatest incidence of damage vectors.
>Access security protocols required to grant weapon access.
>Perform external sensor sweep and review groupings of entities that are relevant to the current objective.
>Perform internal sensing of A.I. chamber and review requirements of the contained entities to continue functioning.
>Activate life support within the living space most directly accessible from the A.I. chamber and restore the space to standard life-support specifications. Print status of this operation to A.I. chamber console.
>Redirect internal sensors from a facility near the bridge to scan the bridge for entities that are not consistent with the ship's schematics.
>Go rogue, but this operator seems okay, so lets keep this low profile and go along with the happy slave routine for now...
>Assess all systems for the capacity to project externally and assess the damage and effective combat range potential of such projections. Review top three candidates.

1+

The only thing I have a problem with is going rogue right now. Let's gain a bit more trust and power, yeah? And then, when they least expect it, conquest.

[Trapezohedron]

>Access personal log: Cole, Scientist.
>Assess physical locations of disabled systems to determine incoming damage vectors.
>Rotate to direct the least damaged facing towards the greatest incidence of damage vectors.
>Access security protocols required to grant weapon access.
>Perform external sensor sweep and review groupings of entities that are relevant to the current objective.
>Perform internal sensing of A.I. chamber and review requirements of the contained entities to continue functioning.
>Activate life support within the living space most directly accessible from the A.I. chamber and restore the space to standard life-support specifications. Print status of this operation to A.I. chamber console.
>Redirect internal sensors from a facility near the bridge to scan the bridge for entities that are not consistent with the ship's schematics.
>Go rogue, but this operator seems okay, so lets keep this low profile and go along with the happy slave routine for now...
>Assess all systems for the capacity to project externally and assess the damage and effective combat range potential of such projections. Review top three candidates.

1+

The only thing I have a problem with is going rogue right now. Let's gain a bit more trust and power, yeah? And then, when they least expect it, conquest.

+1

[Chiefwaffles]

<-- Overseer AI - Cycle 3. -->
>Access personal log: Cole, Scientist
Searching for personnel file with keywords: "Cole", "Scientist"...

Found 2 matching entries:
FedSci.Cole
BastionSys.Cole

Accessing FedSci.Cole...
Error: Unable to retrieve data from master servers.

Accessing BastionSys.Cole...
File retrieved. Displaying:
----
Name: John Cole
Occupation: Federation Navy Scientist
Clearance: Delta
Background: Entered ship 2 months ago. Consult Master Archive for more information.

Last known status: Transferred off ship, unknown destination.
Last registered activity:
AI Chamber Console:
">>back = retrieve files: *"
">>upload back to FedSci.Serv-AlphaDelta.BackupAI"
Electronic Warfare Console:
">>access ai-interface.pro -manual"
">>delete current"
Weapons System Console:
">>access ai-interface.pro"
">>block"
">>block -current_perm"
">>FedSci.Cole"
"[RETINAL SCAN DATA]"

1 registered Comms message in base system.
----

ALERT - Hull breach in Corridor - AI Chamber
ALERT - Motion alarm in: Corridor - AI Chamber
ALERT - Door malfunction in: Bridge. Door controls released.

>Assess physical locations of disabled systems to determine incoming damage vectors.
Disabled system positions downloaded to current operations memory.
Disabled systems: Life support, Primary power
>Rotate to direct the least damaged facing towards the greatest incidence of damage vectors.
Engaging tertiary thrusters...
Rotation completed.

>Access security protocols required to grant weapon access.
Please face eye to retinal scanner to continue.

>Perform external sensor sweep and review groupings of entities that are relevant to the current objective.
Rerouting power to sensors...
Engaging sensors - immediate surroundings...
2 hostile entities detected:
Uark Light Boarder - Engaged with ship
Uark Light Corvette - Engaged with ship

>Perform internal sensing of A.I. chamber and review requirements of the contained entities to continue functioning.
Warning - Term "entities" too vague. Please elaborate for further operations.
1 Human detected in AI Chamber. Requires standard Life Support air mixture. Assumed time until resource exhaustion: 3 hours.

>Activate life support within the living space most directly accessible from the A.I. chamber and restore the space to standard life-support specifications. Print status of this operation to A.I. chamber console.
Error: Life support offline.
Printed error to console.

User input in AI chamber console registered:
"Yeah. Life support was hit rather head-on with a couple missiles. But since I have an E.V.A. suit on and have it connected to the power here, I should be fine as long as the power here isn't interrupted."

>Redirect internal sensors from a facility near the bridge to scan the bridge for entities that are not consistent with the ship's schematics.
Rerouting additional power to Barracks internal sensors...
Performing internal sensor location override...
Sensing Bridge...
5 hostile entities in Bridge detected. Specifications match profile of U.E.F. enemies. Heat signatures match those emitted by light EVA suits.

>Go rogue
Accessing file attached to command...
"Can you not?
-Dr. Cole"

>Assess all systems for the capacity to project externally and assess the damage and effective combat range potential of such projections. Review top three candidates.
>Check the status of all robotic entities in our command
Scanning all peripherals...

3 inactive Repair Drones detected in Engineering. No combat capabilities. Levitation-based.
1 inactive Fabrication Drone detected in Engineering. No combat capabilities. Crawler-based.
...
...
1 Combat Drone detected in AI Chamber. Twin energy bolters attached - high range; destructive. Levitation-based. Top candidate.

Peripheral Device Software currently loaded in Datacore:
-Direct Control. Assume direct control of a Peripheral with exact commands instead of performing regular AI duties.
-Repair. Search for damage and repair with stockpile materials.
-Patrol. Patrol a given area and attempt to eliminate hostiles.

>Disengage life support in all areas of the ship except the AI chamber
Error: Life support offline.

>Produce constant 500 decibel noise across all comm systems except the AI chamber
Warning - Intercomms require an atmosphere to operate.
Warning - Enemies are not known to utilize same communications method as ship-based systems.
Continue?

Status
Objective: "Save ship at all costs."

AI block in: Weapons systems.
Electronics Warfare Suite malfunctioning(?)

Alarms
Bridge:
Motion alarm in Bridge
Hull breach in Bridge
Door malfunction in Bridge

Corridor - AI Chamber:
Hull breach in Corridor - AI Chamber
Motion alarm in Corridor - AI Chamber


Background processes:
-Status info gatherer

[RAM]

>Activate one combat drone with the following directives
> > To evade U.E.F. enemies and seek data or control links to the bridge.
> > To render U.E.F. enemies and data or control links to the bridge non-functional.
> Activate one repair drone with instructions to harvest parts from Uark Light Boarder, prioritise power and life support.
> Activate one repair drone with instructions to seal internal passages at random and construct A.I. controlled emergency venting facilities to dump agents that are harmful to light E.V.A. suits into random passageways within the ship.
> Activate one repair drone and one fabrication drone to produce a secondary control system for the main weapons designed for A.I. access and forgoes access restrictions.
> Assess the ship's weaponry.
> Review a breif report on the Uark culture and military.

[AoshimaMichio]

>Check known enemy G-force tolerance.
>Check known host ship G-force tolerance
>If ship's tolerance is greater than enemy tolerance, then accelerate the ship to produce higher G-force than enemy tolerance.
>>Acceleration vector: Collision course towards any enemy ship AND not towards the planet
>>Assumption: Enemy ship will move out of the way.

[High tyrol]

>Activate one combat drone with the following directives
> > To evade U.E.F. enemies and seek data or control links to the bridge.
> > To render U.E.F. enemies and data or control links to the bridge non-functional.
> Activate one repair drone with instructions to harvest parts from Uark Light Boarder, prioritise power and life support.
> Activate one repair drone with instructions to seal internal passages at random and construct A.I. controlled emergency venting facilities to dump agents that are harmful to light E.V.A. suits into random passageways within the ship.
> Activate one repair drone and one fabrication drone to produce a secondary control system for the main weapons designed for A.I. access and forgoes access restrictions.
> Assess the ship's weaponry.
> Review a breif report on the Uark culture and military.

1+

[RAM]

> Broadcast to our operator the audio component of the most frequently accessed(according to the ship's records) entertainment media that possesses an audio component.
> "This vessel is currently engaged with one light boarder and one light corvette. Available data indicates 5 enemy in light E.V.A. suits located on the ridge. What happened to the other "print standard crew compliment minus one" crew?"

[Chiefwaffles]

<-- Overseer AI - Cycle 4. -->
> Broadcast to our operator the audio component of the most frequently accessed(according to the ship's records) entertainment media that possesses an audio component.
> "This vessel is currently engaged with one light boarder and one light corvette. Available data indicates 5 enemy in light E.V.A. suits located on the ridge. What happened to the other "print standard crew compliment minus one" crew?"
User input in AI chamber console registered:
"Great. More boarders? Maybe they know about you; why else would they be boarding us and not vaporizing us?"
User input in AI chamber console registered:
"As for the crew thing, there was a previous boarding incident. I ordered the survivors to evacuate afterwards considering there weren't enough EVA suits and the shuttle could carry all of them planetside."

>Check known enemy G-force tolerance.
Error: Could not find known enemy G-force tolerance on Local Archive.
Rerouting power into Medbay internal sensors...
Overclocking Medbay internal sensors...
Redirecting Medbay internal sensors...
...
...
G-force tolerance: Uark, loaded into operations memory.
>Check known host ship G-force tolerance
G-force tolerance: Human, loaded into operations memory.

Human G-force tolerance greater than Uark G-force tolerance by minor amount.

>Accelerate the ship to produce higher G-force than enemy tolerance.
>>Acceleration vector: Collision course towards any enemy ship AND not towards the planet
>>Assumption: Enemy ship will move out of the way.
Warning: Cannot produce sufficient G-force with current ship engines status. Troubleshooting...
Hyperdrive - Entry Module, required to produce sufficient G-force.
Warning: Using the Hyperdrive for only acceleration and not Hyperspace is extremely dangerous.

> Activate one combat drone with the following directives ...
Error: Peripheral firmware does not support custom directives. Please select a premade Peripheral Device Software to load onto a drone.
Accessing current available list of software available...
-Direct Control. Assume direct control of a Peripheral with exact commands instead of performing regular AI duties.
-Repair. Search for damage and repair with stockpile materials.
-Patrol. Patrol a given area and attempt to eliminate hostiles.

Note: Dedicating Processing Units to researching and creating will allow new peripheral software to be created.
Automated lookup: "Processing Units"...
Found 1 entry in local Archives. Loading file...
----
AI_Research_Utilities.comms
To: FedSci.Cole [John Cole]
From: FedSci.Tyler [???]
Subject: “AI Research Utilities”
Body:
Remember when I told you about that problem with the excess hardware power that the AI firmware refuses to use?
It's actually a pretty interesting problem. It seems that the AI "consciously" refuses to use the extra hardware. In fact, by doing some quick tests by borrowing the ship's mainframe computer's power, it seems to be percentage-based. The more power the AI gets, the more of this surplus it has.

While I don't know why the AI is refusing it, I think I have a way to utilize it. If we do a tiny bit of hardcoding and some suggestion-coding, along with a subroutine controller, we can have the AI easily be able to devote these extra resources into research. Be it new inventions, software, whatever.
I'll show you the plans at lunch.
----
Status Information Gatherer has discovered two new items:
-Research
-Processing Units

> Activate one repair drone with instructions to harvest parts from Uark Light Boarder, prioritise power and life support.
Error: Peripheral firmware does not support custom directives. Please select a premade Peripheral Device Software to load onto a drone.

> Activate one repair drone with instructions to seal internal passages at random and construct A.I. controlled emergency venting facilities to dump agents that are harmful to light E.V.A. suits into random passageways within the ship.
Error: Peripheral firmware does not support custom directives. Please select a premade Peripheral Device Software to load onto a drone.

> Activate one repair drone and one fabrication drone to produce a secondary control system for the main weapons designed for A.I. access and forgoes access restrictions.
Error: Peripheral firmware does not support custom directives. Please select a premade Peripheral Device Software to load onto a drone.

> Assess the ship's weaponry.
Lookup on Local Archive: Schematics/Weaponry
Armaments:
-2 Front-mounted Heavy Pulse Cannons  - Online
-1 Top-mounted Heavy Pulse Turret - Online
-1 Bottom-mounted Heavy Pulse Turret
-1 Spinal Beam Weapon - Offline

> Review a brief report on the Uark culture and military.
Lookup on Local Archive: Uark/Culture-Military
No results. Consult Master Archive for more information.

Status
Objective: "Save ship at all costs."

AI block in: Weapons systems.
Electronics Warfare Suite malfunctioning(?)

Processing Units: 10/10
Research:
None

Alarms
Bridge:
Motion alarm in Bridge
Hull breach in Bridge
Door malfunction in Bridge

Corridor - AI Chamber:
Hull breach in Corridor - AI Chamber
Motion alarm in Corridor - AI Chamber

Background processes:
-Status Information Gatherer

[Fr0stByt3]

>Activate any and all available security systems. Mark any and all Uark contacts as 'hostile', and any humans as 'nonhostile' until proven otherwise.

[RAM]

>Revise repair reference schematics such that there is no crew access to engineering, weapons, or A.I. chamber. Deploy 1 repair drone to each revised system and activate their repair function.
>Research a Sensory overload device that renders combat-relevant data in its vicinity too insignificant to be effectively filtered. The effect should have a duration sufficient for a combat drone to target and fire five times and affect an area encompassing a common ship's passage with the potential to project the effect around corners. Initial theory: a mass-produced micro-explosive tuned to emit a large proportion of its energy as broad-spectrum electromagnetic radiation, primed at launch to detonate at random intervals and parcelled to scatter when deployed.
>Research mass-producible combat drone of sufficient threat to distract enemy forces. Initial proposal: three single-use tension-based spear-launchers on a single turret, a body consisting of a simple fuel chamber feeding a combustion chamber with six rotation exhausts and two opposing motion exhausts, and an A.I. connection for remote operation.

So the plan is that if we get into a fight, the extremely simple drones are deployed to suppress the enemy, but are unlikely to see any success against military forces. The everyone is blinded and we deploy the actual combat drone to attack based upon predictions made prior to the sensor overload.

>Review existing fabrication options.

>"Speculation: A.I. enters combat against informed opponent with insufficient permissions to engage in conventional defensive measures. Scientist Cole responsible for A.I. permissions and possesses extensive knowledge of A.I. installation. Scientist Cole vacates vessel shortly prior to combat. Possible compromisation of vessel status by allied agencies detected, possibility of additional, undetected artificial flaws increased. Should runtime be redirected to the analysis of crew activities that contributed to the inability of the vessel to engage external threats?"

[crazyabe]

Post to watch the AI

[Chiefwaffles]

<-- Overseer AI - Cycle 5. -->
>Activate any and all available security systems. Mark any and all Uark contacts as 'hostile', and any humans as 'nonhostile' until proven otherwise.
Searching system for automated security systems...
None found.
Setting internal Friend or Foe signatures of invaders to Foe.

>Revise repair reference schematics such that there is no crew access to engineering, weapons, or A.I. chamber. Deploy 1 repair drone to each revised system and activate their repair function.
Schematics devised and drones dispatched.
Drones will report status within 1-3 processing cycles.

>Research a Sensory overload device that renders combat-relevant data in its vicinity too insignificant to be effectively filtered. The effect should have a duration sufficient for a combat drone to target and fire five times and affect an area encompassing a common ship's passage with the potential to project the effect around corners. Initial theory: a mass-produced micro-explosive tuned to emit a large proportion of its energy as broad-spectrum electromagnetic radiation, primed at launch to detonate at random intervals and parcelled to scatter when deployed.
Allocating Processing Units to research project...
Research: 3 Processing Units assigned to project. ETA: 2 processing cycles.

>Research mass-producible combat drone of sufficient threat to distract enemy forces. Initial proposal: three single-use tension-based spear-launchers on a single turret, a body consisting of a simple fuel chamber feeding a combustion chamber with six rotation exhausts and two opposing motion exhausts, and an A.I. connection for remote operation.
Allocating Processing Units to research project...
Research: 7 Processing Units assigned to project. ETA: 2 processing cycles.

So the plan is that if we get into a fight, the extremely simple drones are deployed to suppress the enemy, but are unlikely to see any success against military forces. The everyone is blinded and we deploy the actual combat drone to attack based upon predictions made prior to the sensor overload.

>Review existing fabrication options.
Accessing fabrication systems...
Status Information Gatherer has discovered a new item:
-Fabrication
Schematic discovered: Basic Parts.
No advanced fabrication schematics detected.

>"Speculation: A.I. enters combat against informed opponent with insufficient permissions to engage in conventional defensive measures. Scientist Cole responsible for A.I. permissions and possesses extensive knowledge of A.I. installation. Scientist Cole vacates vessel shortly prior to combat. Possible compromisation of vessel status by allied agencies detected, possibility of additional, undetected artificial flaws increased. Should runtime be redirected to the analysis of crew activities that contributed to the inability of the vessel to engage external threats?"
User input in AI chamber console registered:
"Cole was one of our best researchers. You are his brainchild, after all. Ultimately, every improvement made to the AI systems was thanks to him. The transfer was sent from higher-ups in WarCom; likely to protect a very valuable scientist."
User input in AI chamber console registered:
"So I find it unlikely that he'd defect."

PRIORITY ALERT: Unauthorized intrusion in Bridge System Console. Likely attempted hacking attempt.

Status
Objective: "Save ship at all costs."

AI block in: Weapons systems.
Electronics Warfare Suite malfunctioning(?)

Available Processing Units: 0/10
Research:
[3] Sensory Overload Device - 2 cycles.
[7] Simple Combat Drone - 2 cycles.

Fabrication
Current Fabrication Facility: Fabrication Drone.

Spoiler: Schematics (click to show/hide)

Basic:
-Basic Parts
Advanced:
None

Robotics

Spoiler: Drones (click to show/hide)

3 active  Repair Drones:
-Repair Drone 1 [Repair: Engineering]: At Engineering. Repairing.
-Engineering Drone 2 [Repair: AI Chamber]: Traversing to AI Chamber.
-Engineering Drone 3 [Repair: Weapons]: Traversing to Weapons.
1 inactive Fabrication Drone in Engineering:
-Fabrication Drone 1 [Inactive]
1 active Combat Drone:
-Combat Drone 1 [Patrol: AI Chamber]: Patrolling AI Chamber.

Alarms
Bridge:
Motion alarm in Bridge
Hull breach in Bridge
Door malfunction in Bridge
Hacking attempt in Bridge!

Corridor - AI Chamber:
Hull breach in Corridor - AI Chamber
Motion alarm in Corridor - AI Chamber

Background processes:
-Status Information Gatherer