+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Role-Playing (https://discoverygc.com/forums/forumdisplay.php?fid=9)
+--- Forum: Stories and Biographies (https://discoverygc.com/forums/forumdisplay.php?fid=56)
+--- Thread: Ship's Log *name classified by the LSF* (/showthread.php?tid=1215)
Ship's Log *name classified by the LSF* - marauder - 06-26-2006
marauder,May 13 2006, 06:03 PM Wrote:****CLASSIFIED TOP SECRET****
Report into the R&D of Project *********
Over-view of Project *********
The aim of this project was to development a way to improve the processing speed and power of the main computers aboard modern Capital Ships.
It is unfortunate that we cannot do this using our current technolgy. Organic processor chips failed to work or be a successful alternative so it was decided to use two well know facts as the basis of our research.
These facts are:-
We humans do not use the full capabilities of our brains.
Most women are excellant at multi-tasking.
Therefore we created a group of clones. These clones can perform upto seven hundred seperate tasks at the same time.
Test results
The results of all the lab tests were an overwhelming success.
However during the only live trial, onboard a cruiser, the prototype killed the entire crew and all the escorts. The prototype then actived the cruiser's engines and headed towards the magellan system. It has now disappeared into the gulf between systems.
LSF edit
Also another prototype appears to have disappeared from the station. A complete search of the station failed to turn up any signs of what happened. We are continuing our search for the missing prototype
Recommendations
[DELETED]
LSF Recommendations
Complete destruction of all records relating to this project and the storage of the prototypes until further notice. All research personnel to be replaced and imprisoned until further notice.
All personnel on willard station to have full background checks. We suspect infiltrators to be responsible for the disappearance of the prototype.
[snapback]20428[/snapback]
marauder,May 15 2006, 11:29 AM Wrote:****CLASSIFIED****
Project ********* update.
LSF report
The suspected infiltraitors on willard station have disappeared along with the remaining prototypes.
This was definately a hastily planned and executed assault by the phantom empire. We have reached this conculsion based on security video recordings taken during the assault.
These recordings shows that the marine strike force seems to have gotten lost several times.
This also seems to have been the cause of several of them to lose all self-control. This has been deemed the primary reason for the slaughter of all the personnel aboard willard station.
A coded signal was received by the marine unit from one of the phantom VHF's outside the station. The point of this signal is unknown. It is possible that it was directions to the lab where the prototypes were being kept as the unit did not get lost again.
We have been unable to decode the contents of the signal so far and our analyse indicates that it is a one-time cipher code developed using one of the missing prototypes. This means that we are unlikely to break the code, even if given all the personnel and equipment needed, within one hundred years.
This means that the phantom empire have gotten hold of coding abilities which will make any attempts to crack their codes utterly useless and a waste of resources.
Conclusions:
However any gains made by the phantom empire will not last forever as the prototypes are extremely unstable and need to be treated carefully at all times.
It was believed by the research staff, based on telemety data recorded before and during the incident, that the prototype onboard the cruiser for the 'live' test thought she had been insulted by an officer. Her rage resulted in her killing the entire ship's crew and turning the cruiser's guns onto it's escorts.
Also the high level of self-preservation built into the prototypes means that they consider the ship they are on to be themselves. This is why the rogue prototype fled the fleet send to bring back the cruiser that she was on.
It is also possible that being incharge of everything onboard such a powerful vessel helped to push the prototype over the edge.
We can only hope that something similar happens to any phantom ships that the prototypes are placed aboard.
[snapback]20573[/snapback]
***OOC***
This is a brief overview of the previous posts I made about this ship.
The story is going to be done as a log starting just before the 'prototype' overheard the insult made by a junior officer and finishing when I start using the character 'Navy-LibertyDreadnought' on the server, it might continue on but it'll depend on the reactions I get.
If you have any questions about this log or what I'm doing let me know via PM.
This isn't going to feature other players, unless I run from them for several hours or blow them up :laugh: , so no posting here unless I ask for comments.
***IC***
Ships log of the *name classified by LSF*,
Date: 3 days since test began, mid-afternoon watch.
Location: california system, 30k from willard research station.
Begin Log:-
Beginning test of audio receivers...
"Hey, whats on tonight?", "How are the engines doing?", "Not the bloody curry again!", "This thing is so old it needs to be scrapped, not used for a test."
Locations: main recreation room, engineering, mess hall, main bridge.
'I should be scrapped! Who said that?'
Accessing bridge monitors.......
Access denied..., unable to override due to mechanical malfuntion.
Accessing robot mainframe.., Accessing robot assignment roster....., Accessing remote viewing mode...
A tall, lanky youth, fresh out of his senior year at west point acadamy stood near a dead console on the main bridge. He's uniform was clearly very new and had still got the dry-cleaning tag from the manhattan tailor who'd made it.
'So this is the one who called me scrap?'
Accessing personel files...
Access denied..., override acknowledged.
Access granted..., searching directory..., file located..., file opened.., berth assignment located.., Watch roster located..., file closed.., directory closed.., returning to ship mainframe..
'Time to make him regret that remark'
Remote viewing mode cancelled.., assignment roster search activated.........., parameters met.., awaiting extra instructions for unit XZ3378...., instructions received.., instructions verified... Returning to robot assignment roster... returning to ship mainframe.
to be continued...
Ship's Log *name classified by the LSF* - marauder - 06-26-2006
Date: 3 days since test began, mid-afternoon watch changing to evening watch.
Location: california system, 100 k from magellan jumpgate.
A young junior officer stretched as the lift descended to the crew berth levels from the bridge. Once it stopped he stepped out and strode off to his quarters, ignoring the robot repairing a wall conduit nearby.
As the door slid open he heard a soft footstep behind him, as he turned he saw the robot with it's arm raised.
"What do you want?" he snapped.
The robot didn't reply or move while he stared at it. Then, as he turned to enter his room, it shoved him through the door and stepped through after him carrying a short heavy piece of pipe.
Several minutes later the door slid open again and the robot returned to repairing the wall conduit in the deserted corridor, without the pipe and glistening as though it was wet.
Accessing unit XZ3378..., memory wipe completed.., memory restoration completed..., returning to robot assignment roster..., returning to ship mainframe..
Access audio receivers..
"Helm, bring us to a dead stop. Gunnery officer are the target drones in place?" the general ordered brisky.
"Dead stop aye sir." the helm officer reported as he opened a channel to engineering.
"Aye sir, the drones are in place."
"Very well. Target drone One is to be destroyed using our own gun crews."
"Aye sir." the gunnery officer start snapping orders to his crews as the throbbing of the main engine died.
"Then the guns are to switched to automatic for drone Two." the general could feel the questioning gaze of the crew as the bridge went silent. But she ignored them and continued staring at the battered old transports that were drones One and Two.
The first drone died in a flurry of energy rounds and brilliant explosions, although three shots missed and continued on into empty space.
"Target 1 destroyed sir."
"Some of those shots missed gunnery officer. Have the crews of those guns disciplined."
"But sir you know that on automatic the guns won't hit that drone if it's right in front of us! the gunnery officer protested.
The general winced, then turned to the gunnery officer.
"You have been given your orders, as have I. While we may not understand or, even agree with them, all orders WILL be obeyed on this ship." she said icily.
The gunnery officer nodded once and then checked that the guns were ready and on automatic.
"All guns ready sir." he reported.
"Main computer, fire when ready."
The flak turrets lifted and turned as the servo motors brought them inline with drone Two.
Then all the energy guns fired their projectiles which raced towards the doomed transport. All the shots hit along its back, vaporising the engines and engulfing the ship in a massive fireball.
The gunnery officer looked furious, even after he'd checked the readouts and sensor logs twice.
"That was an excellant display. Helm, bring us about and set course back to willard." the general looked very pleased as she left the bridge and entered the lift.
'I couldn't hit it if it was infront of me! How dare that pathetic little idiot speak of me like that! Why does this entire crew hate me? I look after their every need, safisify all the requirements that drain so much from me and keep them alive.'
Accessing robot listings..., accessing robot assignments..., reprogramming all robots..................., reprogramming complete.., awaiting programme activation...
'Just one more insult and I'll kill them all.'
to be continued...
Ship's Log *name classified by the LSF* - marauder - 06-27-2006
Date: 4 days since test began, start of evening watch.
Location: california system, 70k from magellan jumpgate.
The general stared at the report on her desk, when she looked up at the first officer he stepped back slightly.
"Find out who did this. We're not moving from this spot until the person responsible is found."
"Aye sir!" the first officer saluted before spinning around and leaving hurriedly.
The general flicked back the the start of the report and read it through again.
Accessing audio recievers..
"Whats going on?", "Why are we just sitting here?", "Have the engines failed?", "Is the reactor damaged?"
The confused chatter was everywhere, then a short sharp whistle silenced the ship.
"This is the first officer, there has been a murder committed aboard this ship. Fleet command has agreed with the general's decision that the ship will stay here until the culprit is found. There has been no reactor incident, there is no problem with the engines. We have stopped so that the culprit cannot escape onto willard and then transfer away. Whoever comitted this... act... will be found and punished. That is all, return to your duties."
The crew slowly began to return to their tasks, still chatting except this time they were wondering who had been killed... and who could have committed the crime.
'Hah! They won't find anything, I'm in charge of everything aboard this ship, including the security recordings.'
to be continued...
Ship's Log *name classified by the LSF* - marauder - 08-10-2006
Date: 5 days since test began, mid-morning watch.
Location: california system, 70k from magellan jumpgate.
"Sir? We have an armoured transport, from willard, hailing us. They wish to speak with you on the encoded command channel." The comm officer whispered into the general's ear.
She frowned before quickly standing up and striding into the captains ready room.
"What is the problem?." the general asked, after inputting the codes into a terminal.
"We have discovered a serious problem with the prototypes. The data suggests that... The transmission cut off abruptly. Then a junior officer opened the door and saluted hurriedly before saying:
"Sir! The guns have activated and are currently autoloading!"
"What?!" The general swore and rushed out onto the bridge as the guns finished loading and swung round. She easily found their target, the armoured transport from willard.
"Emergancy shutdown!" the general ordered.
The bridge crew responded immediately but it was too late, the transport disappeared under a salvo of energy shots.
Then the recharge systems kicked in, even as the turrets swung around towards the escorts.
"Open a channel to all the escorts." the comm officer nodded for the general to continue"We have no time for questions or explainations, just get out of here now!"
All the escorts started their cruise engines and they each swung towards a different direction, but the energy cannons fired again and enveloped a gunboat in flames, a shot from the forward gun hit the other gunboat and crippled it's weapon systems.
The escorts engines finally finished charging and started to thrust them forward. However more salvoes hit and destroyed both the damaged gunboats before they could get more then 1000m.
The remaining escorts, both of which were cruisers, hadn't been targeted yet, but they had still suffered damage from debris.
A missile salvo hit one of the fleeing cruisers in the engines and dropped it out of cruise speed, then the reactor overstressed and exploded.
The last cruiser, that had been running, turned back and unleased a massive blast from it's main gun at the cruiser, it fired again and again.
The massive amount of damage was rapidly draining the shield, then the cruiser fired an experimental anti-shield weapon and finally dropped the shield.
The dreadnought had stopped firing the energy cannons, because the crew had managed to sabotage the energy feed conduits systems, and it had been pounding the cruiser's bridge with it's main gun.
The lethal energies finally breached the hull and vaporised the cruiser bridge, it's main weapon control system and it's emergancy generator.
The result was a final shot from the main gun slamming into and crippling the dreadnought's engine.
The destruction of the emergancy generator caused a feed-back that fed into the main reactor, which channelled it into the engines.
They flared to full power in a fraction of the time they were built to handle and exploded.
to be continued...
Ship's Log *name classified by the LSF* - marauder - 08-11-2006
Date: 5 days since test began, afternoon watch.
Location: california system, 70k from the magellan jumpgate.
The wreckage from the escorts floated into a slowly expanding cloud.
The cruiser's tractor beam activated every so often, pulling engine parts and debris into it's hold, where a group of robots sifted through it.
They carried the still usable or repairable parts away through the empty corridors towards engineering and the maintaince workshops.
The crew had been unprepared for what had happened after the last cruiser exploded.
It started first in engineering, the massively armoured robots that had been built to service and repair the main reactor, suddenly activated and formed into a moving wall that forced the crew out of engineering.
The General ordered the entire crew to report to the ship's armoury and equip themselves with heavier weapons, however the armoury lock wouldn't open and then all the other robots started forming mobile walls.
In the end the entire crew were forced into the main access corridor and slowly forced down to the mid-ship station access hatches, then they opened and the entire crew were sucked out of the ship.
After several hours they formed a grotesque chain around the cruiser.
to be continued....
Ship's Log *name classified by the LSF* - marauder - 08-18-2006
The repairs to the engine were finally completed just as a fleet of three battleships, twelve cruisers and thirty guardians appeared on the dreadnoughts scanners.
The cruiser fired several missile salvoes before charging it's cruise engine and running hard into the gulf between systems.
The fleet chased for a few hours before giving up when their nav computers nearly crashed, which would have stranded them in the gulf.
____________________________________________________________________
Ok, the log is done, for now at least.
So... any and all comments are welcome but leave the flaming in the fireproof bin :D .
Ship's Log *name classified by the LSF* - marauder - 08-20-2006
Anyone gonna post then? There must be some comment you want to make.
BUMP
Ship's Log *name classified by the LSF* - General Nakazawa - 08-21-2006
There isnt much to coment althow it was sort of bland in my opinion. A rather crummy ending to a rather good begining.
Ship's Log *name classified by the LSF* - DarkOddity - 08-28-2006
General Nakazawa,Aug 20 2006, 07:27 PM Wrote:There isnt much to coment althow it was sort of bland in my opinion. A rather crummy ending to a rather good begining.
[snapback]31207[/snapback]
I thought it was pretty good actually and that was really a$$ holish of you Naka.
Look forward to seeing a continuation on this story.
Ship's Log *name classified by the LSF* - General Nakazawa - 08-29-2006
what?! he just disapers in to to emptyness of the void inbetween systems. after all that lead up it just sort of leaves you hanging. I also wold look forward to a continuation if for no other reason that to provide closure. But it realy was good exept for what ive already said.