Welcome to Star Trek Simulation Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Cptn_LoAmi

STSF GM
  • Content count

    243
  • Joined

  • Last visited

Everything posted by Cptn_LoAmi

  1. The away team makes first contact with the repair team. They find that the facility is usually 100% automated, and that, while they don't have warp travel, they have some kind of interplanetary transporter technology. The away team heads with the repair team to the transporter at the bottom of the stairs. chatlog2020-6-28.txt
  2. The Arcadia away team finds the communications center of the complex, which turns out to be sending out monitoring messages. In order to attract attention, they disrupt the communications. A repair team, presumably of Keepers, arrives to fix it. chatlog2020-6-21.txt
  3. The away team finds that the Keepers' complex is full of machines, but find nobody there. chatlog2020-6-14.txt
  4. An Arcadia away team arrives on a surface inside the anomaly and enters an underground structure. They find equipment, but no evidence of habitation. chatlog2020-6-7.txt
  5. Arcadia initiates contact with a space coleoid. They learn that the coleoids are trapped by "The Keepers," who extract something then release them. Given available information, they theorize that the Keepers are humanoids and find where they are probably located. Arcadia launches a shuttle mission. chatlog2020-5-31.txt
  6. Arcadia tries a number of ways to pull out of the trap, but is unable. They get pulled through the anomaly into a higher pressure area of space, filled with space coleoids. Listening in to the gravitational waves, they pick up more language. One of the coleoids seems to have been trapped before. They prepare to initiate a conversation. chatlog2020-5-24.txt
  7. Engineering completes modifying the tractor beam to emit gravitational waves to try to communicate with the space coleoids. Arc comes up with a plan to coordinate with the coleoids in pulling against the anomaly to get out. It looks like it's working but the anomaly compensates and continues to pull Arcadia and the space coleoids inwards. chatlog2020-5-17.txt
  8. The Arc remains stuck in the tractor beam as more space coleoids come in. They translate some of the gravitational waves from the coleoids and find that they are complaining. The crew theorizes that they have been caught in a coleoid trap. chatlog2020-5-10.txt
  9. Arcadia follows a gravitational anomaly and is trapped in what seems like a tractor beam. A number of space coleoids are trapped similarly near them. chatlog2020-5-3.txt
  10. Arcadia continues into a relatively uninteresting area of space on its way to explore in deep space. There are rumors that it is on a migration route of space molluscs, though nobody is really even sure they exist. chatlog2020-4-26.txt
  11. The Arc crew finds out from the holo of the creator of the derelict ship that the ship schematics are in the ship's own library. They use them to rebuild the damaged components. Starfleet agrees to tow the ship back to its origin once it is taken out of the void. Arcadia repairs the derelict ship and tows it out of the void at a maximum speed of warp 2.5. chatlog2020-4-12.txt
  12. The Arc crew listens to the holo, which turns out to be a maverick, Kusim Nole, who developed transporter technology and copied the entire planet, expecting to repopulate it after the planetary disaster tat happened subsided, but instead the ship drifted off. Also, the crew found that the power systems on the ship are degrading. chatlog2020-3-29.txt
  13. Arcadia finds that the data is getting corrupted by a faulty power system on the derelict ship. They find a holo in the data that makes reference to the ship and reconstruct it on the holodeck. chatlog2020-3-22.txt
  14. The crew generates a city from the library ship on a holodeck and finds a book shop. There, they discover that some of the data is also stored on separate indexed pods. chatlog2020-3-15.txt
  15. Arc discovers the origin and potentially the purpose (a scale backup) of the library computer. They decide to find a city from it and recreate it on the holodeck. chatlog2020-3-8.txt
  16. Arcadia reconstructs one pod's data on the holodeck. They find a couple of intelligent beings (rabbit people?) and make contact. chatlog2020-3-1.txt
  17. The Arc engineers filter a sampling of the data pods through the transporters to understand what's in them. Some of the pods operate slower than others. They plan to figure out what's in them by rematerializing it temporarily on the holodeck. chatlog2020-2-23.txt
  18. Arc crew tries their plan to interface with the derelict ship. They are able to install a wireless hardware interface and send signals. chatlog2019-12-1.txt
  19. Arcadia finds a large data port on the derelict ship. While security continues to monitor for other ships in the area (and finds none so far), engineering reverse engineers the data ports from the ship and constructs a wireless transmitter to attach to the data port they found. chatlog2019-11-17.txt
  20. Arcadia's AT lands on the ship and finds rows and rows of electronic memory devices. They try to retrieve one of them. but it starts to lose power. Instead, the team beams back to the ship to find a data port so they can read the data from the ship. chatlog2019-11-10.txt
  21. Arc sends an away team to investigate the derelict ship. It has stale air, minimal power and no identifiable bridge. The only things powered are repeated rows of small book-sized objects. chatlog2019-11-3.txt
  22. Arcadia finds a derelict ship in an otherwise empty area of space. chatlog2019-10-27.txt
  23. The crew is sedated, while only Alice from the planet - who has no secondary neural signature - is kept awake to run the ship. A hole appears in the anomaly, but the ship is too big to make it through. As the computers' bioneural circuitry fails, the hole gets bigger. Alice realizes what is going on and turns off the backup computer's bioneural circuitry, letting the ship get out of the anomaly. She wakes up the crew as the ship falls toward the planet. A last second maneuver to put the ship into orbit prevents the ship from crashing. chatlog2019-10-6.txt
  24. Arc attempts to cut power, but it only produces a small opening in the anomaly. Blasting the opening does not work either. The Arc crew realizes that the secondary neural signatures may be holding them in the anomaly. The only one who does not have one is Alice. They plan to sedate everyone, but leave Alice awake with instructions in case anything goes wrong. chatlog2019-9-22.txt
  25. Arcadia attempts to cut power and "go with the flow" in the anomaly to see if it will allow them to get out. The ship takes damage. The plan does not work. chatlog2019-9-8.txt