Inside ARG
| Inside ARG | |
|---|---|
| The Inside ARG revolved around mysterious codes being printed and deciphered. | |
| Type | Official |
| Creator | Playdead |
| Discovered | 2016-06-29 |
Main Page > List of Investigations > Inside ARG
INSIDE is a puzzle platforming game created by Playdead. After the game launched on June 29th, 2016, players noticed a printer in the background of one of the game areas. This printer was quite notable - on PC, the printer prints sequences of characters that are referred to in the game files as "Morse", despite the fact that these messages do not form legible Morse code. On other platforms, the printer forms other messages, some of which have already been deciphered.
Throughout this article, information has been taken from this Google doc.
Contents
Printer Strings
If you load the 12th last checkpoint and head to the left, you'll see a printer in the background. Normally, it will print nondescript pages, but if you walk in front of it and then wait roughly 10 seconds, it will begin to print a sequence of pages with large, visible symbols, which vary by platform. These are not randomized strings, but turn out to be chosen from a list of predetermined strings. Each platform prints from a different pool of strings.
PC/PS4
On PC and on the PS4, the printer will display one of the following 41 strings, composed entirely out of dots dashes and slashes, apparently at random. We haven't made any progress in understanding how they are to be understood. Of these strings, 32 of them are 32 characters long, and 9 are various shorter lengths. This was the first set of printer codes discovered, and were present in the game at release.
-------------------------/-///-/ ----------------------//-//----/ ------------////-----//-///----- ---------//-/////////-///------- --------/----/-////-////--////-/ --------//--//////-/////-/-//--- --------//-//-//-----//-/-//---- --------///-/-///-///--////----/ --------////-//--//-////-------/ ------/----/-----///--//-///-/-/ ------/---/------/-//////-/-//-- -----/--/------/-----//./-./..-- ----.-//////////-------/-/-//--/ ----/--/------/----...///.//.--/ ---.-///../---////-..--/-/--/--- ---/-/.-----/----.-/..--/.--.--/ ---//-.----/----.-/--.--/----.-- --.....-.--.-.--------/.--.---.- --./-...//--.--/.--..//-/.-.-.-/ -.-.././----..----./.--.--...--/ -...//..----.---..//.--.-..----- /----------------------///------ /---------////-///--//-///-----/ /--------/////--//-////-/////--/ /-------/-//---//-///////------- /------/----/---///-//--////-/-- /----..-//////---------///--/--- /----/---/------/---/////////--/ /---/-/------/------.---/.-...-- /---//----//-..-///-----.------/ /--/----.-/-----..-...//..--..-/ /--/.-......--.------//....----- -------. --/. -.-.- -.-.-.-.-.- -.-.-./// -.-./ .-.--..-.-.-.-/ .-.-.-.-./// /.-.
Xbox One
On Xbox One, the printer will display one of the following 47 unique strings. Of these strings, 35 of them are 36 characters long, and the remaining 12 are a variety of lengths, shorter than 36. At this time, their meaning has yet to be determined. These codes were discovered in June 2018 and it is unknown whether they have always been present or if they were added at some later date. Note that one of the strings was observed to occur about exactly twice as often as the rest. Additionally, including it in the list brings it up to 36 strings that are 36 characters long each, similar to how the PC strings have 32 strings that are 32 characters each.
--------------////////-------------- --------------////////-------------- -----------///---..-..///---------/- ---------///-//////////////------/-- -------//-../---//-//--//////---/-/- -------//...--.......--.--.//------- ------/...-...---.--...-.-.../------ -----/...--..-....---.......-./----- -----/......-.///////////-/-///----- ----/------//////////////-------/-/- ----/.-.....--.-/////-//////-///---- ----/.......-.......--.-...-.../---- ---/-----//..--...-..--..//--------- ---/..-..--...-.//--/////////////--- ---/..-...-.--.-..-..-.....--.--/--- ---/...-.--....--.--...-.......//--- ---/........--.../////-/--////-//--- --/---/..--..//--/--/////-////------ --/..-.-.--....--.--....-......../-- --/...--.-......-.-///////////////-- --/...-.---.-..-..///--////--/--//-- --/..........-......-..-.-..-.-.//-- -/...--..--.-..-...-.--....-..--.//- -/....---......-..--....--.....////- -/....--.--.--.--.-../-////---/////- -/....--.-.....--..-..//--/////////- -/..........-......./-//-////--////- -/....................-.--.--.--///- /.....--.--...-...--....-...//////// /.....--..-..-.....-.--...-//---//// /.....-..-..----.....--.///-/-////// /......-.-..--.-......-...---./-//// /......-..-...-.-..-...../////////// /...........--.......-...-..-/-///// /...........-.........-.--/-//-///// /............-........./-//-//-///// ---.-.--------.-.--.----.--- -..-.--..----..-.... .-.--.....-.-.-------..-.- .-.-.-.------------ .-..---....--.-.--- .-..-.-.-.-- .-..-.-.-.-............... ..-.------..-.- ..-.-.--.-....-- ..-.-.-.-.-... ...-.-.-.-....... .......--------
We have made a bit of progress understanding the scheme of these, but haven't completely cracked it yet. After looking carefully for patterns, it was discovered that they could be arranged to form an ascii circle which serves as a scheme to give every code a definite position in the order. This reveals unknown information encoded as dashes overlaid on top of the circle. This also explains why the reoccurring line occurs twice as often: the top and bottom of the circle happen to be perfectly identical.
--------------////////-------------- -----------///---..-..///---------/- ---/-----//..--...-..--..//--------- -------//...--.......--.--.//------- ------/...-...---.--...-.-.../------ -----/...--..-....---.......-./----- ----/.......-.......--.-...-.../---- ---/...-.--....--.--...-.......//--- ---/..-...-.--.-..-..-.....--.--/--- --/..........-......-..-.-..-.-.//-- --/..-.-.--....--.--....-......../-- -/...--..--.-..-...-.--....-..--.//- -/....................-.--.--.--///- -/....---......-..--....--.....////- /......-.-..--.-......-...---./-//// /...........--.......-...-..-/-///// /.....--.--...-...--....-...//////// /.....--..-..-.....-.--...-//---//// /...........-.........-.--/-//-///// /......-..-...-.-..-...../////////// /.....-..-..----.....--.///-/-////// /............-........./-//-//-///// -/....--.-.....--..-..//--/////////- -/....--.--.--.--.-../-////---/////- -/..........-......./-//-////--////- --/...--.-......-.-///////////////-- --/...-.---.-..-..///--////--/--//-- ---/........--.../////-/--////-//--- ---/..-..--...-.//--/////////////--- ----/.-.....--.-/////-//////-///---- -----/......-.///////////-/-///----- --/---/..--..//--/--/////-////------ -------//-../---//-//--//////---/-/- ---------///-//////////////------/-- ----/------//////////////-------/-/- --------------////////--------------
iOS
On iOS (iPhone and iPad), the printer will display one of the following 24 strings. The string chosen is determined by the iPhone's local system time - they are ordered below in terms of when they'll appear on the printer. For instance, the first line will appear from 00:00 to 00:59.
⬛⬜⬜⬜⬛⬛⬛⬜⬛⬛⬛⬜⬛⬜⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛ ⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬜⬛⬛⬛⬜ ⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬛⬛⬛⬛ ⬛⬛⬛⬛⬛⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜ ⬜⬛⬛⬛⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬛⬛⬛⬜ ⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜ ⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬛⬛⬛⬛ ♻203 ⬛⬛⬛⬛⬛⬛⬜⬜⬜⬜⬛⬛⬛⬜⬜⬛⬜⬜⬜⬜⬛⬛⬛⬛⬛ ⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜ ♻206 ⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛ ⬜⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬜⬛⬛⬛⬜ ⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜ ⬛⬛⬛⬛⬛⬛⬜⬜⬜⬜⬛⬛⬛⬜⬜⬛⬜⬜⬜⬜⬛⬛⬛⬛⬛ ♻208 ⬜⬛⬛⬛⬛⬛⬜⬜⬜⬜⬜⬛⬛⬛⬜⬜⬜⬜⬜⬛⬛⬛⬛⬛⬜ ⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜ ⬜⬛⬛⬛⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬛⬛⬛⬜ ♻205 ⬜⬛⬛⬛⬛⬛⬜⬜⬜⬜⬜⬛⬛⬛⬜⬜⬜⬜⬜⬛⬛⬛⬛⬛⬜ ♻214 ⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜ ♻206 ⬜⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬛⬛⬛⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛ ⬛⬛⬛⬛⬛⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜⬜⬜⬛⬜⬜ ♻204 ⬜⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬜⬜⬜⬜⬛⬜⬜⬜⬛⬜⬛⬛⬛⬜ ⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬛⬛⬛⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛ ⬛⬛⬛⬛⬛⬛⬜⬜⬜⬜⬛⬛⬛⬜⬜⬛⬜⬜⬜⬜⬛⬛⬛⬛⬛ ♻208 ⬛⬛⬛⬛⬜⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬜⬜⬜⬛⬛⬛⬛⬛⬜ ♻215
Solution
Each string is comprised of 25 characters, and can be divided into 5 segments of 5 characters each. For instance, the first string can be split up as follows:
⬛⬜⬜⬜⬛ ⬛⬛⬜⬛⬛ ⬛⬜⬛⬜⬛ ⬛⬜⬜⬜⬛ ⬛⬜⬜⬜⬛
Stacking these segments into a 5 by 5 grid yields the letter 'M' in the form of the following pattern:
⬛⬜⬜⬜⬛ ⬛⬛⬜⬛⬛ ⬛⬜⬛⬜⬛ ⬛⬜⬜⬜⬛ ⬛⬜⬜⬜⬛
Repeating this process for each string yields the following message:
MULTIPLEPROBESDISPATCHED
This phrase, when entered on the main Playdead page, turned out to be a valid passcode. See "printer button" for more information.
Switch
On Nintendo Switch, the printer will display the following string (NOTE: there may be more!)
⬛⬛⬜⬛⬜⬛⬛⬜⬛⬜⬜⬛⬛⬜⬜⬛⬜⬛⬛⬜⬛⬜⬜⬛⬜⬛⬛⬜⬛⬜⬛⬜⬜⬜⬛⬛⬜⬛⬜⬛⬛⬜⬛⬜⬜⬛⬛⬜⬛⬛⬜⬛⬛⬜⬜⬛⬛⬜⬛⬜⬜⬜⬛⬛⬜⬛⬜⬛⬜⬜⬛⬜⬛⬜⬜⬛⬜⬛⬜⬛⬜⬜⬛⬛⬜⬛⬜⬛⬛⬜⬛⬜⬜⬛⬛⬜⬛⬛⬜⬛⬛⬜⬜⬛⬛⬜⬛
The Nintendo Switch string can be translated to Morse code as follows:
⬜⬜⬜ -> / (a long pause between words) ⬜⬜ -> (a shorter pause between letters) ⬛⬛ -> - (long Morse character) ⬛ -> . (short Morse character) ⬜ -> (pause between Morse characters)
Decoding this Morse yields the following message:
CTRL CON DISCON
However, this hasn't led to any valid password accepted by the Playdead website. Either there are more strings left to be found (although seemingly everything has been tried) or there is something more to it.
Printer Button
On June 4th, it was noticed that a printer button had been added to the Playdead website, next to its social media icon links. Clicking this button allows you to print the page. On the main page, the printout contains added text not present on the webpage. If the 'Subscribe' field is empty when the button is pressed, the message says "no message received". Any other input returns the message "incorrect message received". When the iOS printer codes were cracked to produce the string "MULTIPLEPROBESDISPATCHED", it turned out that entering that string into the website returns a printout of this image:
Subsequently clicking the printer button again will bring up the same printout as normal, except with the above image appearing on the second page. Shortly after the same time that this new code was entered into the website, the breachlog.html page on the terminal41.link website was updated with a reference to the new pages printreqstatus_005 and printreqstatus_006.
If an email address is entered into the subscribe field before hitting the printer button, sometimes an email will be sent to that email from the address "[email protected]". This is very inconsistent and it doesn't seem like anybody is getting these emails any more.
Youtube Stream
The address "[email protected]" belongs to a gmail account with the name "Anthony T. Setrinamairé". Googling the last name, at the time it was first discovered, returned a single google result: this youtube stream. This stream has been offline ever since it was first found. There was a theory that having 20 people waiting on stream could cause the stream to start. This was disproven when 20+ people gathered at once and nothing happened.
Terminal41
Googling the string "terminal41" from the youtube string led to [terminal41.link this webpage]. When it was first discovered, the base page terminal41.link led to a redirect trail that eventually landed you on [this page.](http://terminal41.link/comms_main_viewgate.html) Around that time, we made sure to check the source of every page along the redirect trail, but there was nothing to find.
On the 24th of June, the following pages were batch modified. The following are the page sources as they were at this time:
terminal41.link/loadSys/__.html
terminal41.link/loadSys/___________DONE.html
terminal41.link/loadSys/LOAD_COMPLETE.html
Before these pages were modified, they were the same except everything in the "pre" tags weren't there. The unusual text in these pages is still a mystery.
The "__.html" page led to the discovery of two additional valid pages:
terminal41.link/sys/
terminal41.link/dat/
Both pages redirect to the main page, and their source is identical. The only notable thing about them is that their title differs from the rest of the pages: "/emergency terminal link [41]/ comms redir - aux. dir conf."
On the 25th of June, the last page in the redirect chain was modified:
view-source:terminal41.link/loadSys/LOAD_COMPLETE.html
Everything in the "pre"> section was removed, and the page now redirected to this previously unseen page:
terminal41.link/comms_main_viewgate_002.html
This page contained references to another new page:
terminal41.link/dat/breachlog.html (this page has been modified several times since. at the time it ended at the entry dated 25062018)
Which in turn contained a reference to this new page:
terminal41.link/sys/printreqstatus.html
Notably, this page contains a reference to the date June 28th 2018. Also, it turns out the two seemingly useless links found earlier were super-directories of these new pages.
On the 27th of June, the breachlog was updated with another entry pointing to: terminal41.link/sys/printreqstatus_002.html
On the 28th of June the breachlog was updated again with a entry pointing to: terminal41.link/sys/printreqstatus_003.html
The 28th of June is also the day that the Nintendo Switch was released.
When the iOS puzzle was solved and its solution entered into the Playdead website, it seemingly caused the printreqstatus_006.html document to appear. This document seems to be telling us that we did indeed solve one of the four puzzles.
It might be worthwhile to note that as far as we know, we didn't do anything to cause these websites to be updated.
Interpretations: breachlog.html seems like it MIGHT be a counter for every time the printer button was pressed on the playdead website. However, this doesn't quite make sense because of these two entries:
>log(25042018)//breach attempt status//......[4] >log(11062018)//breach attempt status//......[4]
which suggest that nobody touched it between april 25 and June 11 which is demonstrably false. This might just be because the counter is kind of funky, but it's hard to say. Whatever it's counting, it's something that really spiked since June 11.
The printreqstatus pages appear to be describing a format for several required passwords/keys. In earlier versions of this page there were three different "auth. schem."s. They also refered to the date June 28 and on that day, a fourth "auth. schem."" was revealed. The fact that this coincides with the release of the Switch almost sounds like the 4th "auth. schem." is related to it, but we can't say for sure. We would really like someone to give us eyes on the Switch port to see if anything of interest is happening there, like the printer printing something new.
it's worth mentioning that the change between viewgate and viewgate_002 seems to suggest that there was some sort of success gaining access, but as far as I am aware nobody has actually figured anything out, or at least if they have, they haven't told us about whatever they did.
All known pages, and their modification dates as of July 3rd:
:Fri, 01 Dec 2017 15:07:52 GMT /loadSys/:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/_.html:Fri, 01 Dec 2017 15:10:08 GMT /loadSys/__.html:Sun, 24 Jun 2018 18:42:47 GMT /loadSys/___.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/____.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/_____.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/______.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/_______.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/________.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/_________.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/__________.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/___________DONE.html:Sun, 24 Jun 2018 18:39:19 GMT /loadSys/LOAD_____.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/LOAD_COM.html:Fri, 01 Dec 2017 15:10:07 GMT /loadSys/LOAD_COM_____.html:Fri, 01 Dec 2017 15:10:08 GMT /loadSys/LOAD_COM-----.html:Fri, 01 Dec 2017 15:10:08 GMT /loadSys/LOAD_COMPLETE.html:Mon, 25 Jun 2018 11:06:44 GMT /comms_main_viewgate.html:Thu, 07 Dec 2017 15:40:23 GMT /comms_main_viewgate_002.html:Mon, 25 Jun 2018 11:05:57 GMT /sys/:Sun, 24 Jun 2018 18:35:57 GMT /sys/printreqstatus.html:Mon, 25 Jun 2018 11:08:05 GMT /sys/printreqstatus_002.html:Wed, 27 Jun 2018 08:29:42 GMT /sys/printreqstatus_003.html:Thu, 28 Jun 2018 15:03:49 GMT /sys/printreqstatus_004.html:Sun, 01 Jul 2018 13:04:20 GMT /sys/printreqstatus_005.html:Sun, 01 Jul 2018 13:30:15 GMT /sys/printreqstatus_006.html:Sun, 01 Jul 2018 14:10:48 GMT /sys/printreqstatus_007.html:Tue, 03 Jul 2018 09:13:32 GMT /dat/:Sun, 24 Jun 2018 18:35:43 GMT /dat/breachlog.html:Tue, 03 Jul 2018 09:14:27 GMT
 | This page is a work in progress and will be updated as new developments emerge. If you have information you think should be added, please create an account to enable page edits or contact a Wiki Editor. |
