"The Stones"
- Thread starter Jmanis
- Start date
i only said what i did as Cannon have decoded things similar before... think that was more morse alphabet
Does anyone actually know how to decode these things. Would be great to learn and not keep getting answers fed to you from other commanders findsLots of mentions about Decoders from many Squads but no info on where to get such decoder. This aint Alphabetical LOL
I tried a few online, I am finding my way with these things too,
First one seems basic but has lots of decrypt "methods" you can try, can paste in the value and click decrypt for each one to see what it spits out: https://tech.pookey.co.uk/non-wp/encoder-decoder.php
The Vignere one seemed more interesting as you can if you want specifiy an optional
key to unlock the code (paste key into the key box), I am 70% sure Frontier have hidden a key somewhere (ie that instagram message or further hint about the cipher used in the other log messages, encryption was mentioned in one), https://www.boxentriq.com/code-breaking/vigenere-cipher
Same for this Ceasar cipher one, but from my basic understanding the Vignere and Ceasar are quite old fashioned and unlikely to be used by Frontier, https://www.boxentriq.com/code-breaking/caesar-cipher
Here is the instagram message someone laid out nicely in google docs https://docs.google.com/spreadsheets/d/1-IVoNbF8vkGfC8D5McX3R9slI3uV5b9JrXPEjY-LLnk/edit#gid=0
I wondered all the time why some code was highlighted brighter than others so possibly an encryption key in there?
Taking the highlighted binary as the key e.g. 01111110_00000101_00000011_00100101_10110110_01101100_00
paste into the Vignere cipher key box, paste in the encrypted log message:
8BFGTY4PLU67-RTYO06.45:GN63-74PHGJI E67-:F563-21-574.9 ER34.6-DER8+WEST U.5 -RTG10 RTH8-4 6T.WR4564-21 +G134.2 RT55.4 GDW THE42.1LY 764.2Y-45TG4.BTJ-Y. 6ORT437.1D341-67.Y5DS 243 45TY-3234
click decode and you get:
8CGHUZ4QMV67-SUZP06.45:HO63-74QIHKJ F67-:G563-21-574.9 FS34.6-EFS8+XFTU V.5 -SUH10 SUI8-4 6U.XS4564-21 +H134.2 SU55.4 HEX UIF42.1MZ 764.2Z-45UH4.CUK-Z. 6PSU437.1E341-67.Z5ET 243 45UZ-3234
probably nonsense but you get the idea, I think the trick is to see patterns to know what type of cipher to use, or just brute force by trying each one, cant be that many common ones?!
Last edited:
Since the word "West" is translated, that might not be in code at all. As the translations change the message length, that probably rules out anything too strongly dependent on that.
Pretty sure they know there is a Listening Post
Standing stones are quite famous in Scotland as we have many in different locations and older than the most famous like Stone henge... My FC is Named Bonnie Tursachan which was named before this LOL... Meaning Beautiful Standing Stones.. Yup, no relation. Ya can't decipher Scottish Gaelic but ED Was origionated in England ( Stone henge ) Supposed to be old portholes but who knows
but ED Was origionated in England ( Stone henge ) Supposed to be old portholes but who knows
Could it maybe be the case that we aren't even supposed to decrypt the message?
Since this operation was meant to stay private and undetected then it could be that we have to unlock something or find something else that can decrypt the message for us (maybe the Adamastor? It had drone docking ports, so maybe these are interactive?).
I'm not sure if this goes into the wrong direction but I am out of thoughts on how to work with this message directly.
We also shouldn't forget that we had other ideas too - like maybe trying to find out where the Adamastor had went if the autopilot hadn't brought it back (although that could get unprecise really fast).
Since this operation was meant to stay private and undetected then it could be that we have to unlock something or find something else that can decrypt the message for us (maybe the Adamastor? It had drone docking ports, so maybe these are interactive?).
I'm not sure if this goes into the wrong direction but I am out of thoughts on how to work with this message directly.
We also shouldn't forget that we had other ideas too - like maybe trying to find out where the Adamastor had went if the autopilot hadn't brought it back (although that could get unprecise really fast).
Or we find the systems it passed through as the 1s stated were just NEAR. better chance of pulling blood out a stone
Just out of my own personal curiosity I've put together a little time line of events surrounding the Ghostship and it's mission based on all the logs and transmissions I've collected myself.
Don't know if anyone else has posted this but it's helped me straighten out the sequence of events in my head.
WARNING: lots of spoilers
Don't know if anyone else has posted this but it's helped me straighten out the sequence of events in my head.
WARNING: lots of spoilers
Ghost Ship Timeline
13 10 3111
Profesor Carvers planetary survey team arrives at (M) MUSCA DARK REGION PJ-P 86-1 3 and establish survey site.
20 10 3111
Carvers team discover Thargoid Barnacle site, begin examinations and sends reports back to Azimuth Biochemicals.
26 10 3111
Megaship Adamastor departs under private licence of Azimuth Biochemicals from CHUKCHAN system.
Route trajectory suggests it passes through systems HIP 39748 & HIP 33386.
27 10 3111
Carvers team discover crashed Thargoid Interceptor and recover "Object".
"Object" creates electromagnetic interference causing equipment malfunctions.
Azimuth Biochemicals orders survey team to cease all transmissions and await arrival of Adamastor for transport to "Secure Facility".
28 10 3111
MISSING MEGASHIP LOG
29 10 3111
Survey team reports sightings of lights in the sky above Thargoid Barnacle site.
Adamastor arrives at (K) SYNUEFE XE-Y C17-7 3.
Receives encrypted message from Listening Post:
8BFGTY4PLU67-RTYO06.45:GN63-74PHGJI E67-:F563-21-574.9 ER34.6-DER8+WEST U.5 -RTG10 RTH8-4 6T.WR4564-21 +G134.2 RT55.4 GDW THE42.1LY 764.2Y-45TG4.BTJ-Y.6ORT437.1D341-67.Y5DS 243 45TY-3234
Updates route to rendezvous with Carvers planetary survey team.
30 10 3111
"Object" in survey site storage activates.
Suspected of emitting infrasonic frequencies as well as electromagnetic interference causing survey teams erratic behaviour & equipment malfunctions.
Adamastor arrives at (M) MUSCA DARK REGION PJ-P 86-1 3.
Mercenary squad lands in Sidewinders to recover "Object".
Thargoids attack and half of the mercenary squad & survey team are left behind in the evacuation.
31 10 3111
Adamastor arrives at HIP 69200
"Object" causing severe shipwide system malfunctions and drastically effecting peoples behaviour.
Carver steals a Sidewinder and abandons ship.
Sidewinder crashes on nearby moon HIP 69200 1 B.
Adamastor route trajectory suggest it passes through systems HIP 65201, HIP 64011 & HIP 61595.
29 10 3306
Adamastor arrives at CHUKCHAN 5 B after drifting for 200 years at sublight speed.
Ship deserted and severely damaged.
All escape pods & secondary craft appear to be launched.
Several air locks manually opened from inside.
All data drives appear to be deliberately erased.
13 10 3111
Profesor Carvers planetary survey team arrives at (M) MUSCA DARK REGION PJ-P 86-1 3 and establish survey site.
20 10 3111
Carvers team discover Thargoid Barnacle site, begin examinations and sends reports back to Azimuth Biochemicals.
26 10 3111
Megaship Adamastor departs under private licence of Azimuth Biochemicals from CHUKCHAN system.
Route trajectory suggests it passes through systems HIP 39748 & HIP 33386.
27 10 3111
Carvers team discover crashed Thargoid Interceptor and recover "Object".
"Object" creates electromagnetic interference causing equipment malfunctions.
Azimuth Biochemicals orders survey team to cease all transmissions and await arrival of Adamastor for transport to "Secure Facility".
28 10 3111
29 10 3111
Survey team reports sightings of lights in the sky above Thargoid Barnacle site.
Adamastor arrives at (K) SYNUEFE XE-Y C17-7 3.
Receives encrypted message from Listening Post:
8BFGTY4PLU67-RTYO06.45:GN63-74PHGJI E67-:F563-21-574.9 ER34.6-DER8+WEST U.5 -RTG10 RTH8-4 6T.WR4564-21 +G134.2 RT55.4 GDW THE42.1LY 764.2Y-45TG4.BTJ-Y.6ORT437.1D341-67.Y5DS 243 45TY-3234
Updates route to rendezvous with Carvers planetary survey team.
30 10 3111
"Object" in survey site storage activates.
Suspected of emitting infrasonic frequencies as well as electromagnetic interference causing survey teams erratic behaviour & equipment malfunctions.
Adamastor arrives at (M) MUSCA DARK REGION PJ-P 86-1 3.
Mercenary squad lands in Sidewinders to recover "Object".
Thargoids attack and half of the mercenary squad & survey team are left behind in the evacuation.
31 10 3111
Adamastor arrives at HIP 69200
"Object" causing severe shipwide system malfunctions and drastically effecting peoples behaviour.
Carver steals a Sidewinder and abandons ship.
Sidewinder crashes on nearby moon HIP 69200 1 B.
Adamastor route trajectory suggest it passes through systems HIP 65201, HIP 64011 & HIP 61595.
29 10 3306
Adamastor arrives at CHUKCHAN 5 B after drifting for 200 years at sublight speed.
Ship deserted and severely damaged.
All escape pods & secondary craft appear to be launched.
Several air locks manually opened from inside.
All data drives appear to be deliberately erased.
knowing Frontier and with the experience we had with previous events.. i think they WANT us to decode that message.
I meant the fact that it wasnt working for most.
Anyway just logged in and it worked so only took me like 18hrs to work
I meant the fact that it wasnt working for most.
Anyway just logged in and it worked so only took me like 18hrs to work
It was a confirmed bug and was fixed just ~6 hours ago
Anyone know if srv giving data ? wasnt earlier
You fly in open, you will get hunted my friend. Lots of pvp players be there to halt us explorerswas there about 20 minutes ago and scanned, no data (while in my SRV my Phantom got blown up by a CMDR who was flying around destroying landed craft), so I have transferred my combat fleet to the system, taking a brief break from puzzle solving
I think it’s worth us picking back up on the wiped log from the 28th.
Two possibilities stand out:
A. Adamastor departs Chukchan on 26th and something happens on the 28th and they then arrive at the Listening Post system on the 29th
B. Adamastor departs it’s base system on 26th. It then goes to Chukchan, and departs there on the 28th.
In terms of distances, the 2nd makes more sense as we’ve either got:
A. 3 days for 370 ly to Listening Post, 1 day for 600ish ly to Coalsack, plus doing all the stuff there, plus departing, 1 day to get to the A class and for people to abandon ship etc.
Or,
B. Same but starts with 1 day to the LP.
The distances don’t definitively mean it’s B though, obviously, and there’s certainly plausible explanations for A.
Possible investigation options:
A. Another system stopped at before the Listening Post. (Could look roughly 2/3 of the distance, but there’s nothing else to go off).
B. Try and work out where the Adamastor originally set out from, and check local Galnet feeds, etc.
Judging from the galaxy map of 'inhabited' systems along the route from Chukchan to the LP System - the last inhabited system is COL 285 SECTOR OS-T D3-99 which is roughly half way between said systems. I will have a little fly around there and see if any local galnet has anything to go off. I doubt it but its worth knocking out of the park. I will also check other nearby systems also
It seems to me 28 they took the "object" to the base of the absence of the object. Spared the aggression of the Tragoids. Not finding the "object" at the crash site, they attack! But the object is loaded onto the Ship! Departure
I also suggest canceling the Arrival and Departure timeline!
Let's know the speed at which the ship was moving!
Then we will look at the data further, by the dates we will try to determine where the "approximately" stop was! And we will search!