First of all: else Heart.Break() is a very spoiler-sensitive game. It's a game about being curious and playful, about finding mystery and solving it. For that reason it is imperative that you avoid spoilers for as long as possible. Play the game yourself first.

I have played many hacking games, but else Heart.Break() is the most genuine, profound hacking game I have played. It is a hacking game in the true meaning of the work hacking: You are rewarded for being inquisitive, playful and observant. Think outside the box. Realize that the world around you is a system, and that you can interact with that system and even change it in ways that wouldn't be possible in other games.

Originally posted by "Morpheus":

This is a sparring program, similar to the programmed reality of the Matrix.
It has the same basic rules, rules like gravity. What you must learn is that these
rules are no different that the rules of a computer system.

Some of them can be bent. Others can be broken.

The first rule of else Heart.Break() is: Find out yourself. Your main task in this game is to find bits of information, piece it together and find out how to use it for your purpose. This has a couple of implications for us.

Originally posted by "Rule #1":

Find out yourself.

Information is power. In Doom you pick up colored keys. In else Heart.Break(), you pick up pieces of information. For example the name of a computer. A snippet of code showing something you didn't think of yourself. The daily routine of a Dorisburg citizen. Everything you know can help you.

Information must be acquired. Make a habit simply of finding things out. How does this code work? Experiment. What is the name of this computer? Find a way to find out. And the most important question of all is the meta one: How can I find out how to find out?

Information must be stored. You absolutely need a way to store the pieces of information you come across. Whether you use a physical notebook, a text document or speak to a parrot is up to you, as long as you can keep and organize the things you find out. Write lists. Keep a list of player names. Of sound effects. Of consumables. Of computer names. Of doors. Write down snippets. Store information.



The second rule of else Heart.Break() is: Break the rules. Just like Neo in The Matrix, you can alter the flow of the world around you to fit your needs. You have probably figured that out yourself (see: Rule #1) by now. However, breaking the rules doesn't just mean to change things. It means to think outside the box. Experiment with everything. Ask yourself, "How is this supposed to work?" and then do something completely different. Look for the unobvious approaches. Be creative, playful and don't be afraid to break things. In fact: Try to break things.

Originally posted by "Rule #2":

Break the rules

The extension of this is to see the system as a whole. Don't just change single things, change the ways they work together. Use one thing to change another to change a third. Exploit how one item can do something but another can't.

An important way of making your life in else Heart.Break() easier, is to find a small set of tools that can help you in your daily life. Identify a problem, and then try to find a way to fix it. What's the best way to unlock a door? How can you stay awake? When going about solving these problems, look at what you have at disposal and identify their key properties and functions. Being portable and having a specific function available is extremely helpful, so look for carryable items with helpful functions.

Some items that help out immensely can be hard to find. Make sure to thoroughly search rooms, especially those that can be harder to get into, to ensure that you don't miss an invaluable tool.

Learning and using SPRAK is an important aspect of the game. When you are done playing with the world in the game, start playing with the world outside the game. There is another language, called GRIMM, that controls much of how Dorisburgs functions on a day-to-day basis. Start exploring the file structure of the game itself. I recommend, however, that you finish the game at least once before you do so.

Another part of the meta is to find replay value in the game. While the world around you is pretty much the same, you can still do different things on a second playthrough. Find the fastest way to find a modifier (without resorting to external help). Try not being (or being) a soda salesman. Again: Experiment, and find clever solutions.

WARNING: This section contains vague spoilers. Rule #1: Don't read it. Rule #2 (for experts only): Don't read it yet. Remember rule #1 of the game and Find Out Yourself. Only come back here after you've found your own helpful tricks, and then compare them. Getting a solution handed to you ruins the fun. Trust me!

• Certain [REDACTED] have very helpful functions that you want to call from anywhere. What if you could invoke those [REDACTED] remotely...
  
  
• The [REDACTED] function can open a door without using a combination. [REDACTED]
  
  
• GetName() helps you [REDACTED].
  
  
• [REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED][REDACTED]

Be a keymaster:

Step 1: Find a computer in a secure location that has an Unlock() function. You can use one of the computers in the hotel. Write your own function to interface Unlock(), or you might be able to simply use Unlock() directly. Write down the name of the computer.

Step 2: Use the extractor to GetName() a door. Change the code of for example a soda can to Connect() to the computer from step 1, then call computer.Unlock(doorName). When you drink from the can, the door unlocks.

I'd like to sum things up with a great comment by MrMuse:

Originally posted by "MrMuse":

My personal feeling if you get stuck is that you have missed clues that the game constantly throws at you. Start over and think about what is initially odd in Dorisberg. Think about why the game shows you the things it does, how and why people do the things they do - talk to everyone - sometimes repeatedly even if they seem to not be saying much.

else Heart.Break() is a brilliant game if you will let it. Avoid spoilers, pick its mysteries apart on your own and you will have a wonderful adventure. Have fun!


(And remember, if you liked this guide, make sure to rate and favorite to make it more visible to the new Heart.Break() adventurers out there. <3 )