Print

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

[Flying Dice]

if a part of your ship is incredibly dangerous when unstable,
having a system in place to eject it is hardly a flaw.

Designing an engine that is incredibly dangerous and unstable would seem to be a design flaw.

Does that help, or do you want to address something I didn't say again? Anything can be dangerous, especially if it involves high levels of energy, etc.

Any information will be helpful. Even vague references to technology or astrographic data will be of value to us at some point. Furthermore, there very well may be memory backups among the bridge data.

Agreed that information is helpful. Which is why I proposed dedicating all unassigned resources to recovering our memory banks. I'm not objecting to procuring information.

What I'm objecting to is...

the cause of the bridge being offline is the lack of power, and your best guess as to their function would be an alternative method of controlling the ship aside from you

...restoring systems for which the purpose is granting control of the ship to entities other than ourself. I reiterate that restoring power and functionality to the bridge is of extremely low priority. In fact, we might want to deliberately keep it non-functional. I see no benefit to giving biologicals means of controlling the ship.

One might even wonder if we were the original cause of the ships apparent "failure."

Are you suggesting that it would be impossible to shut down the bridge controls, or selectively restore power only to the databanks? 

Existing evidence points to the engines being ripped out during the crash.

That is not the only interpretation of the data:

Millions of years pass and you drift through space, unable to do anything...

Finally you crash land onto a planet

Clearly we lacked propulsion before crashing on this planet. What is uncertain is why. If, as you suggest, we still had all our engine components all that time and they're only missing now because something important was ripped off during the crash...if we were unable to fix whatever the problem was that kept us from operating under our own power for millions of years...it seems unlikely that crashing on a planet and scattering that engine over a kilometers-long "trail of wreckage" would improve upon our ability to repair it.

...whereas if some critical portion that we were unable to replicate were ejected all those millions of years ago, that would explain why we were adrift in the first place.

There are a few other possibilities as well. Our missing fuel rods may have been removed specifically for the purpose of preventing us from self propulsion.

And again, that is your interpretation. I could just as easily say that the reason we were "unable to do anything" is because we were powered off/had our access to shipboard systems cut off. Incidentally that would fit better with your own suspicions about sabotage or a conflict between us and our crew or a boarding party.


>Also going to repeat my suggestion that we have 1 robot take one of the crates outside and a few dozen meters away to open it.

[Mr. Palau]

Guys face it we can only make so many predictions about what happened, all are necesserly flawed as we don't have enough information as of this moment. As of this moment one of if not the bigest is to collect more information on what the hell happened to us, why were we sent here, how damaged are we, and do we have the fuel required for travel.

Ok, I'm gunna try and mediate agian now. Lets go with Flying Dice's way of opening that crates as that is the safest way, but lets have the same number of robots assigned as LordBucket. Here is what the compromise order should be, I believe:
>5 robots are to open the crates, before the crates are first opened one is to go outside and open it carefully, if it doesn't explode/melt the robot/kill it/etc, the other robots proced to open more crates, this time inside as they are deemed safe. If there is no safe way to pen the crates have them begin to scout the ship.

You guys alright with that?

[Flying Dice]

Maybe it's just Paranoia memories, but I am automatically suspicious of anything that is in a sealed, unlabelled container. :x

[Zecro_The_Scourge]

I agree with dice here. Move it outside and 0.5 of a mile away from the ship, then open it.

[ansontan2000]

PTW.

[zomara0292]

I agree with dice here. Move it outside and 0.5 of a mile away from the ship, then open it.

+1

[Cairon]

OOC: I appreciate the summary post Mr. Palau, however your math was flawed. You made orders for 146 robots. While there were only 118. I tried to accommodate as best I can. /OOC


Performing low-level system scan... ... ... Complete!

One thousand, three hundred database entries are corrupted. Purge?

Propulsion: *ERROR 001*
Steering: *ERROR 001*
Positioning System: *ERROR 001*
Life-Support: *ERROR 001*
*ERROR 243*: *ERROR 001*
*ERROR 243*: *ERROR 001*
*ERROR 243*: *ERROR 001*
Shields: *ERROR 001*
Comms: *ERROR 001*
Weapons: *ERROR 001*
System Clock: Online
Robotic Control: Online
Sensors: *ERROR 001*
*ERROR 243*: *ERROR 001*
*ERROR 243*: *ERROR 001*
*ERROR 243*: *ERROR 001*
*ERROR 243*: *ERROR 001*

Currently in Safe-Mode.

ERROR 001: System disconnected, or damaged.
ERROR 243: Data corruption. Unknown element.
---

It was considered to remove the guard from the CPU core, however as you were about to give the order, the robots in the room started to detect a strange noise coming from within the CPU core...


Meanwhile...

Envoy maintains his position in front of the exit port and detects life forms approaching... and suddenly a hundred BE-1s emerge from the jungle, carrying what appears to be throwing spears made of some sort of metallic alloy. Unable to determine composition at this range. They appear to have strange tattoos painted on their body with a white substance...


Elsewhere...

Teams A, B, and C continue their search of the ship, and you have now explored 64% of the ship.

Team A: Ended up at a missing section of ship... There is a gaping hole and the entire section of the ship appears to be missing from the superstructure. BE-1s are noticed amongst the trees...
Team B: Located more apparent dormitories.
Team C: Located a room filled with strange mechanical machines of no seeming purpose. Long thin metal rods sit in a rack, or shorter metal rods with circular discs on the end are also arranged in peculiar fashion on another rack, smallest to largest. There appears to be writing on them, but it seems gibberish. "3, 5, 10, 15, 20, 30" etc. There also are just circular discs stacked on the floor, seemingly largest to smallest with the same strange gibberish.

Your repair team at the generator have finished their repairs, now they only require replacement fuel rods in order to activate.

Your team with the fighters proceed to drain the fuel from the other fighters and pump it into the one functional fighter, and manage to bring the tank to 80%. You also determine the cause of damage for the fighters appear to be collateral damage caused from the crash-landing.

Fighter-001 is prepping for launch. Please clear the launch bay and open the launch doors.

The repair team with the broken robots proceed to repair the damaged robots by cannibalizing parts. Only five robots are assigned to this task and thus only two robots are made functional, an additional one is rendered scrap. Seventeen broken robots remain.

Another team of five is dispatched to locate all methods of entry to the ship, and modify them to be only computer controlled.
Additionally, five robots are sent to take soil and bedrock samples.
Finally, another team is dispatched to determine the use of the unknown but discovered ship systems.

One robot takes a suspicious crate outside of the ship and would proceed 0.5 kilometers away from the ship... if the ship were not surrounded by BE-1s wielding spears... Apparently they are on all sides of the ship, not just the side of Envoy, this would bring the total up much higher than originally anticipated... Response?

Twenty robots proceed to prepare cables to connect the bridge computers with our CPU mainframe, and proceed to run them from the bridge...

The remaining robots are dispatched to locate the ship's main memory banks, and bring them online. Somehow.


Status:

Spoiler (click to show/hide)

Core sealed.
BE-1 Language translated. Very basic language.
Running in Safe-Mode.

One hundred twenty functioning Robots. One with communication capabilities.
-Five in sealed core.
-Twenty-Five at Generator Room.
-Fifteen scouting ship in teams of Five.
-Five repairing fighters.
-Envoy outside of ship, near BE-1s.
-Five repairing broken robots.
-Five locating methods of entry and removing mechanical operation.
-Five taking soil and bedrock samples.
-Five identifying unknown systems.
-Twenty connecting bridge to CPU Mainframe.
-Twenty-Eight attempting to recover memory banks...?
-One outside of ship with suspicious crate, facing BE-1s.

Time elapsed:
-since crash: Four hours.
-since previous update: half hour

[ansontan2000]

Robots are to be dispatched to the entrances tom the ship, and should open fire if the BEs start throwing. While they aren't really a threat, if we show them our power, they might stop trying to kill us.

[Flying Dice]

At the moment, our only 'weapons' as such are arc-welders and whatever other tools we have.

Question: Is the fighter VTOL? Does it have a drive plume? (I.e. does it have high-temperature/pressure exhaust?) If so, would it be possible to exercise fine enough control to use it to frighten/kill BE-1s?

>Remove the robots on robot/fighter repair duty (except for one in the fighter bay), 20 of the robots on memory recovery duty, and send them all to meet up with search team A at the hull breach, prepared to defend it.
>Other search and sealing teams will speed their actions; sealing entrances is more important than documenting the interior of the ship, at least for the moment.
>Envoy and the robot with the crate will each withdraw into the ship via the nearest opening, the latter taking the crate back in with it. Each will seal the entrance they used if possible.

[Cairon]

Question: Is the fighter VTOL? Does it have a drive plume? (I.e. does it have high-temperature/pressure exhaust?) If so, would it be possible to exercise fine enough control to use it to frighten/kill BE-1s?

No, the fighter is not VTOL. I forgot to describe the look of it, sorry. It resembles a Viper from Battlestar Galactica.

[Flying Dice]

Would you happen to be talking about the massive hole in our side? If so:

>Remove the robots on robot/fighter repair duty (except for one in the fighter bay), 20 of the robots on memory recovery duty, and send them all to meet up with search team A at the hull breach, prepared to defend it.

>Also, keep the fighter in the bay for the time being.
>Check the charge on the other fighters and determine if it can be transferred.

If the BE-1 attack, we should have enough time to launch and hit them with our rockets before they get inside.

[scout890]

PTW

[Koronii]

Have the fighter bomb them. They are a bunch of primitives, having a giant metal bird raining death from above should help to cement their worship.

[NoahTophatz]

Clearly the BE-1 are here totest wether we are truely a war god either that or they fight so much that the have to concept of war

[MrWiggles]

These things are like automated SCVs.

What the heck are stone spears going to do? And they certainty can't have protection from plasma torches.