To move around in the document easily, choose (if it isn’t already there):
Tools → Document Outline
See Ship’s Log Guide for simple steps to help us maintain logs so everyone can participate more easily regardless of their timezone. Thanks!
A sci-fi-themed RPG employing the eponymous Pulse Beacon Relay bot as the main means of communication. See What Do We Know? for a moderately short and inconsistently updated summary.
Help pick our ship's name here!
“Apollo Station” in orbit around a red dwarf experienced some kind of event where the (previously red) star itself turned blue #4. The space station is requesting assistance because the failures they suffered in consequence of that.
The crew works for a company called GDf Futuristics. They stated that their problems began 110 days before their first message to us (Sat, June 03, 2017 ), which was was Mon, Feb 13, 2017, in Earth days #3. Their days are half as long, 12 hours #15. When the problems started, two crew members, Eiffel and Jacobi became irradiated, turned delirious and violent, and had to be stopped #14. They’ve been ‘buried at sea’.
Three remain alive on Apollo Station: The main contact person, Commander Bright; Hilbert, a cosmologist who is able to “float”; and Sam Lambert, a doctor who was in jeopardy from the unusual radiation effects, which our meds seemed to counteract. And who also has a theory as to the reason for the ship losing control, as yet undisclosed #5. Lambert states they have been alone without much contact for years prior to the accident #14. Message 14 has good explanatory material.
We’re not sure yet if the Apollo Station crew are fully trustable or not (this could use some analysis and discussion). Our ship (as yet unnamed) decided to head there to assist, but has been warned by the Apollo crew to not come too close, presumably to avoid the same fate of falling into an inescapable orbit #6. However, a transmission from GDF #7 was picked up stating that the Apollo inhabitants are armed and dangerous criminals GDF is allegedly a large interstellar corporation; Apollo Station mentioned a website, and the fact that GDF may send either a Rescue Team or a Containment Team (which sounds possibly like a security or ‘termination’ squad—scary) #14.
When asked, we recommended that Apollo jettison their damaged medical bay after salvaging materials, and keep the more structurally sound escape pod for use and emergency escape, and they followed our advice #5. While travelling to their sector, we launched a probe which determined that the star actually was emitting blue waves, verifying this part of the Apollo crew’s claims. The probe also delivered emergency supplies, medicine, and music, and may or may not also include secret weaponizable materials #10.
A broken message from Apollo hinted at unusual probes, and possibly solar flares, or something interfering with communication. Apollo seemed to warn us against using the comm until further notice; it’s a bit unclear, though. At the same time, a coded message intercepted from a GDf ship to GDf Command suggests that they are about to attack Apollo. The “Stanton Effect” of the blue star was mentioned, and our Strategist passenger postulated that this could be a GDf experiment of the shady sort that they are willing to protect and keep secret at all costs. The fact that Apollo was caught unawares by this effect suggests they are innocent bystanders, despite belonging to GDf. Or perhaps targets. In any case, in order not to attract undue attention from the GDf ship, “Desperate Measures”, in the area (not to be confused with “Desperate Times”, which was our ship’s probe dispatched to examine the blue star), a !ping-style message requesting a response (and also hinting at danger, limited time, and testing Apollo’s awareness of the GDf ship message) was conveyed, disguised as a spam ad for toothpaste #17.
Much is happening! See Msg #18. Plans for the final showdown are coming to fruition. Update coming soon, see Messages 19 to 23 for more.
We’re on the verge of big action, expected around 10, 11:00 UTC on Sat, Jun 17.
The proposed backstory is a war mothership/shuttle taken by a group of rebels that are escaping from the (galactic) empire.
|Doctor Caesar||@caesar||Medical Doctor, Officer|
|TW-947||@tw947🎸||AI Flight Officer|
|Xyzzy||@Xyzzy||Friend of a friend of a friend|
|Master of Engineering||@PouncySilverkitten||Engineering Officer|
|Ensign bluebird||@bluebird||Crew member, lackey, jackdaw of all trades|
|Strategist Jeremy||@JeremyRedFur||Redfur Strategist|
Beacon connects and requires response in order to deliver message. N.B. These messages sent directly before Message #5:
After that, we can respond with a message on our own.
There’s a short time window for both these actions. Afterwards, the beacon disconnects.
Did anyone note the lurkers this time?
5 min after there are two agent lurkers, one the same as yesterday.
Adding Lurker notes to Raw Logs, and maybe a sub-appendix.
We don’t know. Maybe we shouldn’t know. *cue X-Files Theme*
I do know (at least who the front is) but won’t tell.
> Who says they know? What clues led to this hypothesis?
— Encore to Who is this guy? —
Shortly after a !help @PulseBeaconRelay, the bot disconnected, without a Signal Lost. Whether or not the events are causally related is unclear. Further experiments and tests are needed to find out whether a correlation, in fact, exists.
There was no chance to reply.
repeated 7 times
1 day later
Nothing was attached
1 day later
1 day later
Translating the numbers to the respective letters and deciphering using a Vigenère cipher with a key of TOOTHPASTE yields (after adding spaces for clarity):
We are closing in. Sent probes ahead. Detected Station appears damaged. Confirmed Stanton Effect on star. Weapons armed. In firing range in three STD days.
The message was encrypted using a keyed Caesar shift with keyword “chocolate”.
The message was encrypted using a keyed Caesar shift with keyword “cloudy”:
The message was encrypted using a keyed Caesar shift with keyword “birthdaycake”:
The raw logs are currently missing from this copy of the PBR document... Until they are ready, please use the logs in the google document