All Five Minigames and the Quick-Time Events

Why five minigames in a half-hour game

Helping Your Boyfriend is short. The English script runs to more than 8,000 words and a single run takes roughly half an hour, so you will finish it in one sitting — but you will not spend that half an hour reading. Five separate activities break it up, and those activities are where most first runs actually end. This guide exists because the failure rate of this game is almost entirely concentrated in about ten minutes of interactive play, and almost none of it sits in the 8,000 words.

The design is deliberate. The first activity, the doll disassembly, is tactile and slow: you point, click and drag with the mouse and pull an old teddy bear apart piece by piece into the bins. The last one is the opposite. The quick-time events ask for arrow keys and a spacebar, in the frantic sequences where the tension peaks and where most first runs fall apart. Between them sit three activities that each turn one small decision into a mechanic. The contrast between the warm, slow half and the cold, sudden half is the whole point, and the game does not soften it anywhere.

There is also a structural reason the activities matter more than they look. Five of the story's biggest decisions happen inside them: what you name the doll Adrian brings home, whether you swallow the pill, whether you can get the locked door open, whether you get the phone call right, and whether you survive the attack. Each of those is a branch, not a cutscene, and each of them leaves a flag behind that the script reads later. The game does not expose a difficulty selector in the data we extracted, so there is no menu setting to lean on. The pressure comes from the moment itself, and the only lever you have is preparation.

So here is the plan. Start with the full control reference, because most deaths in this game are control deaths. Then take the five activities one at a time, with the exact input each one asks for. Then cover the two habits that cost the most runs: skipping text you should have read, and carrying the previous screen's input into the next one.

The full control reference

The control scheme is small and unusual in exactly one place. Everything in ordinary dialogue is mouse or Enter. Everything inside an activity is something else entirely. That single split explains most of the deaths people report, so it is worth learning the whole table before you start rather than discovering it scene by scene.

The bell at the top of the screen is the one control with no keyboard shortcut, so it is worth opening once early. Click it and you get Save, Load and Settings. Get used to where it sits and where the load slot list is, because on a second run you will want to load a save rather than replay an evening, and the bell is the only door to that menu.

Two more are worth calling out now, because they are the ones players forget and the ones that hurt: L for the dialogue history log and A for auto-play. Both are brilliant tools. Both are actively dangerous on a first run, for the same reason, and both get their own section below.

The one rule that catches everyone out

Space is the control that catches everybody, and it catches them for a good reason: it means two different things. In normal reading it hides or shows the dialogue box, which is a convenience key — the sort of thing you press once while you are looking at the artwork behind the text. During a quick-time event, the spacebar is the confirm key. Same physical key, opposite consequences. Press it to admire a background and you may be answering a prompt you never read, and if the sequence is already running, that mistake can take the run away from you.

The disambiguation is simple once you know to look for it. When a minigame or a quick-time event starts, switch input modality entirely. Do not keep clicking as if the dialogue were still on screen, and do not move your hand to the keyboard until the screen has actually changed. If the activity is a drag, the mouse is the only thing that matters. If the activity is a quick-time event, the arrow keys and the spacebar are the only things that matter. There is no reading, no choosing and no skipping inside an activity, and treating the activity like a conversation is the single most reliable way to lose.

Two habits make the switch automatic. First, rest your non-dominant hand on the arrow cluster and the spacebar from the moment the game says something is starting, so changing input is the lift of one finger rather than a scramble across the desk. Second, read the instruction line before you touch anything. Every activity shows its own instruction, and that line is the only thing telling you which of the two meanings of Space is currently in play.

Doll disassembly

Where: Day 1 and the following nights. How: point, click and drag with the mouse, pulling the old dolls apart piece by piece into the bins. The teddy bear on the table is the first one. There is no timer and no fail state here, because this is not a challenge — it is a chore, and the game wants you to feel exactly how tedious and how intimate that chore is. You are alone in a room in someone else's house, doing something a doctor asked you to do, and it feels completely normal. That normality is the horror working underneath the whole first evening.

The teddy bear is the one to look at closely, and its eyes are the detail the game keeps pointing at. This is not an anonymous plush. Madison is an orphan Adrian talks about, abandoned at an orphanage at two and struggling to talk with the other children. She named the teddy bear Adrian made for her Macaroni and carries it everywhere. She is the emotional anchor of the doll job, and the first hint that these dolls have a purpose beyond Adrian's convenience. When you pull the bear apart on Day 1, you are handling something that belongs to a child the story has not properly introduced yet, and the game never lets you forget it.

Mechanically the activity is simple. Put the cursor on a piece of the doll, hold the mouse down, drag it over the correct bin, and release. The bins are the entire puzzle: pieces go where they belong, and the game is happy to let you take as long as you like. If a piece refuses to move, you have probably grabbed a cramped corner of it — move to a clearer edge and drag from there rather than pulling harder. Dragging in a straight, slow line also reads better than flailing the cursor around, because the game is generous with what counts as a successful grab but not with what counts as a dropped one.

Adrian brings home a green dinosaur and asks you to name it. There are exactly four options and the game records whichever you pick: O'Green, Jeff the dark-lord of the darkness realm, Diny the bed-watcher or Bob. It sounds like a throwaway bit of flavour and it is not. The naming happens on the same evening as the doll job, which is the point the game is making: you are already handling one child's toy before you have been told anything about where the others came from.

The pill

Where: Midnight 1 and Midnight 2. This is the only activity that is genuinely a timed decision, and the only one where the mouse and the keyboard both matter. The rule is the important part, and it is a rule rather than a reflex: a brief press reads, a held press confirms. Most players will never make that distinction until it costs them, because the instinct under pressure is to mash the button as fast as possible, and a fast tap only reads the option you are looking at. Hold it down instead. Do not tap, and do not double-tap.

Here is what is actually happening. A weight settles on you in the dark, a man's shadow falls over the bed, a hand clamps over your mouth and a pill is held in front of your face. The scene's own labels are #OpenEyes, #Take, #Refuse and #Vanish. Taking it sets tookPill to true. Refusing sets tookPill to false and routes into the #Vanish label. Neither choice ends the run — refusing does not get you thrown out of the story, it sends you down a different path — but the game records what you did and reads that record much later.

The second visit is the one that changes the route. Midnight2 is reached from Day2Evening when you spit Adrian's pill out instead of swallowing it, which sets spatPill and turns the story away from Adrian's route. So the pill activity is not a mood piece; it is the hinge the whole story swings on, and it comes back a second time in a slightly different form. Treat Midnight1 as a taste of what is coming and Midnight2 as the choice that actually decides which half of this game you are in.

The basement

Where: after the locked door is opened. How: point-and-click in a dark, narrow space, and the hasKey flag opens the #KeyStub branch. So the dependency is exact: you cannot reach this activity until the locked-door sequence in the escape has resolved in your favour, and the key is what makes the branch open at all. If you are trying to work out why an object in the basement does nothing, check whether you are actually holding the key.

The space itself is doing most of the work. It is a narrow staircase down into the dark with a cold light at the bottom, and Adrian always said not to go down alone. The game does not make this a reflex test the way a quick-time event is a reflex test. It makes it a place where you click things, because clicking things is what you do in a room that frightens you. Expect to move slowly here. There is no reward for speed and the atmosphere is doing the job the mechanics are not.

What actually goes wrong in the basement is impatience rather than technique. Click every interactive object, and give things that look like scenery a fair chance: one click, then step away, rather than five clicks in the same spot. If a click seems to do nothing at all, check whether you are holding the key first, because hasKey is what opens the #KeyStub branch, and a room without that flag is a room with less in it. The full order of checks in the escape sequence, and where the key comes from, are laid out in the secret room guide.

The phone

Where: PhoneOutside1, after the escape. How: dial the right number. This is the only activity in the game that asks you to remember something instead of clicking something in front of you, and it is where a skipped line turns into a dead run.

Two digits of a phone number are written in ink on your arm, and they fade over time, but you remember two of them. You need those two digits to dial Oliver Freeman. The phone screen branches four ways: phoneTried when you try to dial a number, phoneCorrect when you dial the right one, phoneLeave when you leave the phone without calling, and oliverCallDropped when you drop Oliver's call. Dialling the wrong number gets you No signal, and that is the entire feedback system. The game will not tell you which digit was wrong, only that the number did not connect, and it will not give you the number anywhere else. It is on your arm, in fading ink, and that is the only copy.

So the whole activity collapses into one habit: when you see the digits on your arm, write them down. A phone number on a scrap of paper, in your own handwriting, is worth more to you at PhoneOutside1 than every other clue in the game combined. Keep it next to the address from the parcel, because you will need both within the same stretch of the story.

One more thing worth knowing: you are allowed to hang up. phoneLeave exists as a branch, which means the phone screen tolerates being abandoned. That does not make it a good idea. Oliver introduces himself on the phone as "Oliver Freeman speaking", and he is the one who stops Ian's syringe in the rain — he had been parked in the alley by Adrian's house, patrolling day and night because he suspected Adrian. Without his call, you never got out of the house at all, and the endings on the other side of it are the only ones where anybody is still talking to you.

Quick-time events

Where: the frantic moments, including the attack sequence. How: arrow keys plus the spacebar. These are the sequences where the tension peaks and where most first runs fall apart, and they are the only part of this game that asks for reaction speed rather than care.

The attack sequence is the biggest one. Day3_Act2 is the act two decision point and it splits on useKnife: with the flag set the scene routes to Attack1, and without it you go to ICanFixHim. Attack1 carries its own #A1_after label and leads into Attack2, which leads to FinishHim. The script also contains three game over variants, GameOver1, GameOver2 and GameOver3, which is how failure in the frantic stretches gets expressed. A missed input does not nudge the story along, it can take the run somewhere you did not want to go.

The practical fix is to fight the instinct to repeat. The game never asks for the same input twice in a row, and it will not ask for the same key twice in a row either. When a prompt calls for left, pressing left twice is a guaranteed miss. Watch the shape of the prompt rather than reacting to the sound of it, because the arrow you see is the arrow you need, and the sound is almost never a reliable guide to which one it is.

If you do fail, treat the failure as information rather than as a verdict. Look at which prompt you actually missed before you restart, because the run is cheap to repeat and the read is free. And if you want to know exactly which ending a particular failure pushes you onto, the endings guide has the routes mapped out flag by flag.

Read the prompt, do not muscle-memory it

Here is the single most common failure mode, and it is not a mechanical skill problem. It is carrying your input from the previous screen into the next one. Every activity in this game shows its own instruction line, and the game is not in the habit of repeating an input pattern — because it does not need to. The doll screen wants a mouse drag. The pill wants a held press. The quick-time event wants arrow keys and a spacebar. Three activities, three different input types, and the transition between them is where people fumble.

The rule that makes it click: after every screen change, spend a quarter of a second reading the instruction before you touch anything. Not the whole line, just the input it names. Then answer with that input and nothing else. Do not keep clicking as if the dialogue were still on screen, and do not press space to find out what space does this time.

A quieter version of the same mistake is doing the right thing too early. Players who learn that a quick-time event wants arrow keys will sometimes start throwing arrows the moment a scene turns tense, before the prompt is actually up. That does not help you, and in the wrong moment it will not be forgiven. Wait for the instruction line. It is the only reliable signal that the game has switched modes, and it is always there before the input matters.

Skip, auto and the history log — and when not to use them

The controls make it very easy to outrun your own story. Hold Ctrl or Tab and the game skips text you have already read. Press A and it plays itself. Press L and it opens the dialogue history log, which keeps what has been said so you can go back and read it properly. All three are excellent tools. All three are dangerous on a first run, and they are dangerous for the same reason: the clues this game depends on are delivered in ordinary dialogue, in the middle of a conversation, in exactly the places a skip key would eat them.

There are four clues you need, and every one of them is spoken rather than shown as an objective. The first is the two digits of the phone number written on your arm. The second is the address on the parcel Adrian brings home, 742 Silverwood Creek Lane, Silverwood Springs, CA 95401, which you have to give to Ian before the escape door will open at all. The third is the family photograph in Adrian's room: four smiling members, and the boy in the middle is Adrian, except his hair is black. The fourth is the newspaper headline in the living room, about a recent murder case, which you are interrupted before you finish reading. Skip past any one of those on a first playthrough and you are carrying a hole into the second half of the game.

Auto-play has the identical problem, with the added disadvantage that it takes the clicking away from you as well, so you cannot stop it at the moment a clue appears. The history log on L is the honest compromise: it skips nothing, it just lets you go back and check. Use it after the fact to confirm what you read, to recover anything you skimmed in a hurry, and to look up a scene name when you are checking a route against a guide. It is the safety net that makes skipping survivable rather than fatal — but only if you actually open it afterwards.

On a replay, all of this inverts. If you are chasing a specific ending, skipping and auto-play are exactly right: you have already seen the text, and the only thing you need is to reach the branch point. Hold Ctrl through the scenes you have read, let auto-play carry the quiet stretches, and stop skipping before the scene where the choice matters. The same key that ruins a first run is the best tool you have on the third.

First run or chasing an ending

Two very different jobs, two very different setups. If this is your first run, the game is a reading game with five interruptions, and the interruptions are where you will lose it. If you are chasing an ending you have not seen, the game is a set of decision points and you already know where they are. The table below is the short version of how to play each one.

Whichever run you are on, keep the history log within reach. It costs nothing, it breaks no tension, and it is the difference between "I think it said four" and knowing. The game is short enough that being wrong about a clue is never a small mistake.

Frequently asked questions