CG_SBCrumb has become known to create event teasers when announcing new events. These teasers have become more intricate and have used cipher's to decode them.
Jango Fett[edit | edit source]
Chewbacca[edit | edit source]
Jedi Knight Revan[edit | edit source]
A Road Ahead was announced on October 5th, 2018. In it contained a teaser, 2 images written in Aurebesh.
The pyramid and the other image is a cipher. The teaser used the Playfair cipher which is translated to OTXYMNONOEUQOZTMOCXGVRHNXIEUTMCKUMKYDMUKBATK. Which is ultimately converted to THEROADAHEADISCOMINGSOXONTHEWAITWILXLBEWORTHITBITLYNAVERIDEJ.
Part of the conversion is a URL - bit.ly/naveridej (jedi revan backwards). This ultimately linked to a Jedi Revan trailer.
C-3PO[edit | edit source]
This teaser started with two clues from forums posts.
The bottom left of CB_SBCrumbs photo had a color bar. If you convert that color bar from hexadecimal to ascii, it produces this URL - https://goo.gl/4HXR42. When you go to that URL, it'll download a JPG, however the format of the file isn't an image. If you take the binary from the file and convert it to ASCII, you get a lot of numbers and letters with "[K:C major clef=alto] [L:1/16] [M:none]" at the beginning. This was discovered to use the Solfa Cipher which is used to encode a message into music. The song from the YouTube video was actually the encoded message. The Solfa Cipher requires a key to decrypt it and one way to set the key is with a date. Using the date in the title of the forum post - 12/14/2018, the key was found to be Clef:Treble Tonic:A Mode:Dorian Unit:1/16th.
With this, you can begin to decode the cipher. The output from the cipher was more numbers and letters that had a pattern of a number, followed by an X, followed by hexadecimal. It was discovered that you repeat the hex for the number in front of it, and covert the hex to color, it would start to draw a picture. Parts of the image started appearing to look like C-3PO
This was solved in just under 3 hours.
Millennium Falcon[edit | edit source]
Episode 1: The original post[edit | edit source]
Found here, the original post contained a body of text, a table and a file which had a deconstructed dial in Aurebesh.
Filling out the table was completed very quickly, as was translating the dial. After that, using the table to read the dial was the obvious route but as it involved printing the dial (or finding some good editing software?) and doing some solving manually, this took some time. Thanks to one member on the forums, it was solved to be "Scoundrels4life".
By this point many had guessed it meant the OT Falcon would be coming and require scoundrels to unlock, but we needed to find the solution to the main body of text.
The main issue with decrypting the main body of text was that we didn't have any clue on how it had been encrypted. Some of it read like a poem that was introducing the challenge but some of it was clearly nonsense. Lots of people tried lots of things such as looking for anagrams, different ciphers, taking out names of scoundrels and their ships, reversing the dial to find a string of numbers for some code, but it wasn't until Crumb gave us another clue that we found out the next step.
Episode 2: What's cooking?[edit | edit source]
Crumb posted a picture of a piglet with the accompanying clue: I've just woke up and having my breakfast but all I can think about is getting more of this guy.
The hint was taken and people began to look for a solution using Bacon's cipher. Using this, each letter in a body of text is replaced by an A or a B which gives a string of As and Bs, these are grouped up into sets of 5 and using the chart for the bacon cipher, turned back into lettters (e.g. a set of ababa would become L). The issue for this was finding what criteria we needed to use to turn the text into As or Bs. We initially looked at many different possibilities such as changing letters from Scounderlsfourlife to As and the rest to Bs but eventually Crumb took pity on us and told us it was much more simple than we were trying to find.
After this second clue, someone tried using A-M = A, N-Z = B which gave a string of As and Bs which was decrypted Lone_Starr to give: N E V E R T E L L M E T H E O D D S T H R E E S E V E N T W O Z E R O O N E A T G M A I L D O T C O M D
Note: whilst we were still working on the bacon's cipher criteria, Crumb also posted :More Bacon then I get to the weekly word search in the newspaper (https://forums.galaxy-of-heroes.starwars.ea.com/discussion/192073/new-clue/p12) which hinted that a future element would be a word-search.
Episode 3: The bugged account[edit | edit source]
After solving the bacon's cipher and the table/dial we had [] and Scoundrels4life. Someone quickly found out we could use these to log into the official forums which came up with an account with which Crumb had posted in the bug report section.
Title: I haz bugs. Text: You are free to use any methods necessary, but I want them alive! File: 102chars.txt (https://us.v-cdn.net/6025736/uploads/editor/ko/qyyzca0odp7e.txt)
The text seemed to refer to Bounty Hunters (scoundrels) and the title of the post made us think the clue might have errors in it.
By this point, the discord channel was going into overdrive as we tried to work out how we could decrypt the text. After analysing it we found that it could be split up into strings of characters with some key points:
- Strings were 5 or 6 characters long.
- Each string would start with either L, D or C.
- The strings always had 'x' as the 4th character
- After L/D/C was always a number, 1-9 (but C only went up to 8)
- After the first number was always a letter, A-G.
- After X, there was always a number, 1-21
We also found that there were 841 sets of data which we worked out was 29^2 which suggested each set would translate to a letter which would then form a 29x29 word search.
This part was tricky as there were a lot of possibilities. We looked to see if it could be colours, or ASCII code using Hex/Oct/Dec based on C/D/L. We even started looking at using Latin, thinking C,D,L could be 100,500,50 and there are only 21 letters in the Roman alphabet.
Eventually though, someone suggested using C=cantina node, L=light side node, D=darkside node.
From there it was only a few steps to get CDL = type of node, 1-9 and A-G were the specific node in that area, and x1-21 was the number of the letter of the shard it rewarded. e.g. C7Ax4 would be Cantina node 7A, 4th letter of the reward shard character's name ('S' in Mission Vao in this case).
Someone clever wrote a program to convert the 841 sets into letters which ended up giving us the basis for the word-search grid.
Episode 4: The word-search of doom[edit | edit source]
We created the grid using the letters from solving the clue, but there were a few errors to begin with as a few spaces were blank or seemed wrong. This was due to us not knowing whether to use the shard character names with or without spaces.
A google spreadsheet was created (final result here) to open up the word search to everyone. We thought that the title of the original file (102 chars) meant we had to find the names of 102 star wars characters so we needed all the help we could get.
To begin with we coloured the names we found in red and used different colours where we thought there were letter errors (turned out to be our mistake in translating the code) but we eventually began to change the letters to what they should be and turned everything we found to red.
At this point MobileGamer (https://www.youtube.com/channel/UCKjqnZEvjlf4TPtt9dmqhYw), who had been watching it for a while (along with Crumb and EVS-469 unbeknownst to us) started a live stream to tell everyone about the breakthrough and the puzzle in general. This was both a blessing and a curse as the document became flooded with people solving it (I shared the document with edit access but it seemed to lock people out after a while, necessitating re-sharing. Not sure what was going on with it - possibly too many users - but sorry about that!). We began to list all the names we found, along with where they were located (L4 down, or AB19 back down for example) so we could check nothing was missed.
Due to all the people finding names we quickly coloured in a lot of the grid but as it started to get messy and a small number of people started trolling we had to restrict access to only a few trusted people. At this point things slowed down as we had to check all the letters in the grid against what the were meant to be (thanks CG_EVS_469 for the confirmation reference table) and check that the correct boxes had been filled in. It took a long while and there a still possibly a couple of minor errors but eventually we found the names. Finding the correct names was tricky as CG_EVS_469 and CG_SBCrumb informed us there were a few we had found that weren't meant to be included (hazards of a large grid with so many unusual names) but we eventually confirmed all the correct names (again thanks CG_EVS_469 for providing the reference of character names).
Episode 5: Wait. There's more?[edit | edit source]
After finding all the names there were a number of characters left unshaded. Looking at these we identified the names of a number of ships. After being told there were 121 characters (thanks again CG_EVS_469 for the checkpoint) we figured these would fit into an 11x11 grid. We created the grid and populated it to move onto....
Episode 6: The last piece of the puzzle[edit | edit source]
In the end we had a second word search where the names were all star wars ships.
After colouring in all the letters we were left with an anagram which everyone worked out very quickly unscrambled to give MILLENNIUM FALCON.
We got confirmation on the official forums - "Congratulations - y'all got it! Hope you guys had fun with this one - I've already got some Ideas for next time. >:) - EVS-469"