Let me say that this point blew our mind when we found the solution. I think you’ll see why below. I was also really excited that we were able to get this point without really anything in the way of clues from the CM after the initial tweets.
This point started simply enough:
Start transmission #thegintercode
— Ginter Code (@TheGinterCode) March 11, 2015
I immediately spotted that this tweet happened at exactly noon (plus 14 seconds). That was then followed by 28 more tweets over the next 5 and a half hours, all of which consisted simply of a number, like so:
— Ginter Code (@TheGinterCode) March 11, 2015
I'll save you some scrolling and skip the rest of the tweets, but they were all similar to this one, with some positive and some negative numbers. I spent my afternoon waiting for the next tweet and entering it into a spreadsheet. I also had a hunch that the time the tweets came out would be important, so I recorded that into the spreadsheet as well.
And Finally:
End transmission #thegintercode
— Ginter Code (@TheGinterCode) March 11, 2015
Once the tweets were all recorded into the spreadsheet, Jason and I started trying to make something work. We played around with a few different methods using the time and the text. We tried taking the number of minutes after noon. We tried summing all the tweeted numbers. We came up with several lists of numbers. We tried matching those numbers to card numbers and also set up an alphabet table with 1=A, and continuing several times through the alphabet.
The winning combination ended up being the minutes since the last tweet, plus the number in the current tweet. Add them together to get a number, which corresponds to a letter in the alphabet, where A=1:
In case it’s hard to read, that spells “Do This backwards for the hashtag.”
After a major adrenaline rush, we tried to figure out how to do it backwards. The solution was to start with the “end Transmission” and then did the same thing backwards, so minutes between the end transmission and the last tweet, plus the number in the last tweet.
Read this one from bottom to top, it spells:
— Bosun Knows Best (@BosunKnows) March 13, 2015
So you can see why this one blew our mind. the code was designed so that you could do it forwards and backwards and get a message both directions. This was a case where we realized how much time and effort the Codemaster had to put into designing some of these points. We were really impressed with this one. The excitement of finding a readable message was followed by the excitement of finding the solution. We had a lot of fun with this one.
These are definitely the kind of pre-planned things that I love. Nicely done.
ReplyDeleteGrant worked on this point, so I can't comment on what we tried. I don't recall much of it.
I'll just say that, for obvious reasons, this was by far the most nerve-wracking point for me. I had absolutely no backup plan if I missed one of the 29 tweets' assigned minutes. Thankfully, I didn't need one.
ReplyDeleteThere was a moment of sheer, abject terror when Twitter wouldn't let me send the same tweet twice, but fortunately a simple extra space circumvented that.
Yep, this point gets more amazing the more I think about it. Well done!
DeleteI had assumed you were using a tweet scheduler like tweetdeck or hoot suite. If you were watching the clock all afternoon, that's dedication. I'm even more impressed.
DeleteWhen I saw our account post the hashtag it was one of the greatest moments during hug the code. This one was all Adam and with this answer we had just scored three in a row and were up 9-8! Couldn't hold on but it was a good run.
ReplyDeleteI can't stop thinking about going back to see the level of difficulty on designing this one.....maybe after I solve the poem point
ReplyDeleteIt's actually not as hard as you might think, once you know what you're trying to do. Here's one you can solve for fun:
ReplyDeleteTime of tweet:: Text of tweet
12:00 :: Start Transmission
12:01 :: 1
12:23 :: -7
12:35 :: 7
12:46 :: 10
13:06 :: -6
13:26 :: -9
14:02 :: 4
14:28 :: -11
14:48 :: 3
15:00 :: 7
15:07 :: 21
15:13 :: 25
15:32 :: 26
15:33 :: 19
15:56 :: End Transmission
Nicely Done!
Delete