S.P.L.I.T WALKTHROUGH

this guide is for those who didn’t really know how to do the console bits & couldn’t figure it out for the life of them (because I get it). This guide will not have story spoilers, but it will give you direction for the actual hacking bits if you don’t know how to get through it!

It makes me really sad to see people unable to experience this game because they don’t know what to do, so if any of you guys want help , hi ! :-}
I apologize if any of the steps in this guide are incorrect or sloppy, or overexplained. I tried to make it as simple as possible to understand !

This guide is not for speedrunning intentions, and aims to help players understand the games mechanics instead of just doing the required actions as quickly as possible. I’ll be providing the steps I took (in a more direct form, because I was all over the place when I played this). If you do want to speedrun, the 100% necessary steps will be marked with a star ★. Keep in mind that all codes in screenshots from my game are not the actual codes, because all codes are randomly generated. You will have to find them in your own games!

After the initial opening dialogue, you’re told to boot up the console and get the files from the field kit onto it.

your controls:

• A & D = TURN HEAD
  
• ALT = UNFOCUS WINDOW/DISTANCE SELF
  
• You can use the print command ingame to write yourself notes, like small codes or brief information.

Hold ALT to distance yourself, and then turn to the field kit to your right. Enable it with the typing prompts, and then distance yourself again, and turn to the console.

Here is where you’re left with a mostly empty console and no real direction. Type “help” for a list of commands.


Your goal is to connect the field kit to the console. Focus on the bottom prompts for this, for right now. ★ Type “probe” into the console, and have a look at the result.



The field kit’s information is at the very bottom. The Unique Machine Number is what you’ll use to refer to it. Use the connect command, and type your field kit’s Unique Machine Number. In my case, it would be 6585.
★ Grab your field kit’s Unique Machine Number, and print it with the print command (or write it down, or just memorize it!).


Right now, your goal is to copy the local files. But when you try to do this, an error occurs.


So, we have to go into the trusted devices data. Back out of this menu by typing a 5 into the console.

The game shows us where the trusted devices data is: in the tools directory, and then the HoleMounter directory. Type ls into the console to see the directories.



We want to go to tools.



★ Type cd tools to get into the tools directory. From there, we can do ls again to see all of the directories in the tools one. Then, we type cd HoleMounter to get into that one.



If you try to open the trusted devices data, you get an error message telling you to edit the file with the nano command instead.
★ Do nano trusted_devices.data to get this page. From here, we just put in our field kit’s Unique Machine Number. Keep in mind; my number is 6585, but yours will be different (it is auto-generated).





Once you do that, press CTRL + X to exit, and make sure to save your changes. Make sure to back out of the HoleMounter directory by typing in cd .. twice.
Then, ★ use the connect command to connect back to your field kit. Now that it’s on the trusted devices list, you’ll be able to get the files from it.

After you do that, ★ Type in 3 to copy the files onto the console.


Press ALT to distance yourself, and head back to your friends. Get through that conversation, get the updates, and see what they need you to do next.

They ask for the ID, and you don’t have the option to reply yet. Go back to the console. Let’s take a peek at those new files! Scroll up a bit on the console, and look at it in udder befuddlement. What next?

In your earlier conversation, Sarah told you that the ID you’re looking for would be in the config folder. Looking over, you can see where the config directory got dropped.




★ Navigate to config. type in cd emulated, and then cd [FIELD KIT NUMBER]. When you type in ls, you’ll see it!


★ Type in cd config and then boot up the system config. Type in open system_config.json. You’ve found your ID (Low-latency file streaming ID).



Get back to your friends. You’ll have new dialogue for them. When the dialogue finishes, you’ll have two new files and a whole new can of worms. Your goal now is to get your auth key generated. But before that, you’ve got a few steps to get through. Sarah will give you the REF number, write that down. In my case, it’s 13660.



Type in cd .. three times this time to navigate back to the main directory. This time, you’re going to want to go to your downloads, per Viktor’s suggestion.



If you boot up the AuthKeygen, you’ll see options to generate an authorization token, but you’ll notice you don’t have the access to. You have to set up pre-requisite arguments first. You try to do that, and you need to look at the documentation. So, let’s start there.

Type in 3 to get to documentation.
To get a pre-requisite argument, you need three codes. Documentation will tell you where you get said codes. Because the console is running K-COM, we’re going to be looking at that one. Ignore the (Deprecated) label, because that doesn’t mean anything.

Navigate back to your downloads. Type 4 to exit Authkeygen to get back to downloads.
★ Open up the Schematic 09 that Viktor sent. Get your server address.
The server address has to be one without an x on it. Print or write one (or both in case one somehow doesnt work) down.

It will be a full number, no spaces. for me, it would be 96381024, or 62487492.

★ This time, open up the AUI 2068 document that Sarah sent you. Get your unregistered inmate number. To figure out which number you’ll use, find an inmate with N/A under their “REG. NR” category.

In my case, it would be 316687.

This is the code that Sarah sent you. Go back to the console, and it should be the last message she sent you. Again, for me, it’s 13660. :-)

Now, you should have those all written down together. You have your numbers. Let’s go back to the Authkeygen.

★ Open Authkeygen.exe and then press 2 to get to the setup for pre-requisite arguments. This is where you put in your codes. Make sure to separate them with commas!



★ And finally, generate your authorization token.


★ Press 4 to exit out of the Authkeygen, and then connect back to your field kit.

Type in connect [field kit number] again. When you connect back, you’ll be able to connect to a remote K-COM server using the authorization token you just got.
★ Press 1 to connect to the remote K-COM server. Then just wait for all the text to fly by, and then go talk with your friends again. It should be fine from here, with no more hacking required! Sit back, and enjoy the show!

This should get you to ending 1, and earn you the Trust achievement. :-)

To get ending 2, and earn the other achievement, simply do not type "POTENTIAL BETRAYAL" at the start of the ending sequence. This should get you what you're looking for! You should see the induced achievement pop up after you exit back to the menu.

that should be everything! apologies for if this was scuffed and I hope it was helpful (and thank you to the comments for telling me how to get the other ending - I dont know why I thought id be more convoluted than that LOL) <3 have a good one !