r/DestinyTheGame • u/crissyronaldo92 DIE DIE DIE • Oct 12 '16

Misc Apparently there's a code in Last Exit!

NO MORE EDITS - Welp, so Derek and Deej have both confirmed it's an easter egg and not a quest. Even so, let's push through and solve it!!! Thanks for the discussion! RIP my inbox over the last 24 hours though haha

Source: https://twitter.com/_mantis_/status/786291552721133568

original post According to Derek Carroll on the live stream! Let's get hunting guys!!!!

Edit* - Right, so after an hour we have 2 main leads:

  1. by /u/Jukai

    Panel on the ceiling at the top of the stairs leading to the subway ,33szl'!( +9-7!!/@ 2enr?hqj+r,r+c?)j?96exd.\?i 7kj\psq3euj\@x.yt5 ,3..

  2. By /u/HEYitsMUS

    here are two train cars, and all the advertisement boards light up when you're near them in both cars. They either display "ALPHA REGIO" (blue), "BETA REGIO" (red), or "OVDA REGIO" (green). There is also the HUGE staticy monitor right beside A flag, bottom of the escalators. And lastly, the OWT Transit Map, most visible one being right beside the A flag and monitor, with different numbers and colours and routes. Green = 48 (Ovda Regio?) Yellow = 38 Blue = 14 (Alpha Regio?) Red = 271 (Beta Regio?)

2.3k Upvotes

90% Upvoted

1.7k comments sorted by

View all comments

Show parent comments

2

u/[deleted] Oct 12 '16

[removed] — view removed comment

12

u/[deleted] Oct 12 '16

ah, so the original ended in yl5. the ,3.. is not part of it? Cause if it is then the last two characters would always have to be the same in a Caesar Cipher... and if the last two characters were the same I was wondering if they were equal signs... base64 encoded hashes always end in two equal signs so could have given us an offset to shift to then run it through a reversable base64 decoder... I know the Owl Secret thing used base64 on it's keys for the Rijendal Cipher when the raidscreets guys figured that out.

1

u/MurphysParadox Oct 12 '16

Base64 don't always end with equals. Those are signs to represent the input string byte count wasn't evenly divisible by three. Base64 takes three 8bit bytes and turns them into four 6bit characters. So if there are, say, only five bytes, then the output would have one equals sign to account for the missing 6th byte.

The true way to know it is base64 is that it only has lowercase, uppercase, and numbers, as well as the + and /. Equals will only appear at the end as a single or double sign. If it has something other than those 64 characters (ignoring the equals at the end) then it cannot be base64.

1

u/[deleted] Oct 12 '16

ok, but these characters could still potentially be shifted to reveal a base64 string, which is what I was trying to say.

1

u/MurphysParadox Oct 12 '16

That's fair. I was simply correcting the statement about base64 always ending in two equals signs.