What your choices change
Choices in I Have Known You do three jobs: they set the protagonist's personality, they move relationship counters up or down, and the developer states that decisions carry weight into the full game. The demo is where that accounting starts.
Every visual novel says your choices matter. The useful question is what a game actually does with them, and I Have Known You is unusually open about its machinery: a named protagonist whose personality you shape, visible relationship scoring, and a developer promise that the decisions carry into the full release.

Three kinds of choice
Reading the store page and the demo together, choices in this game do three distinct jobs.
| Kind of choice | What it changes | Where you see the result |
|---|---|---|
| Character choice | The protagonist's name and personality | My Profile in the character screen |
| Relationship choice | A tracked value with one character | The counter over the dialogue box |
| Story choice | Which scenes and information you reach | The scenes themselves, and Memories |
Most games blur these into one "choice system". Separating them makes the demo easier to read: when a line changes something, you can usually tell which of the three it changed.
The protagonist is a choice
"You customize the protagonist's name and shape his personality through your choices" is the store page's phrasing, and it is a bigger statement than it looks. A named, shappable protagonist is not a silent avatar. The game is committing to reflecting who you have been, which means the writing has to branch on personality, not just on romance.
In practice, this is what the My Profile entry is for: the game keeps a file on you, the same way it keeps one on everyone else. The choices you make about how to respond to people accumulate into a character rather than disappearing into a hidden variable.
Relationship scoring, visible
The counter over the dialogue box is the most legible consequence system in the demo. It fires on scored lines, shows the character's name and the change, and then gets out of the way.
Visible scoring is a design philosophy, not a shortcut. It tells the player: this line mattered, this person noticed, and the game is keeping track. That transparency makes replaying more interesting, because you know which moments to revisit.
It also creates a specific kind of tension. Once you can see the counter, you start reading for it — choosing the line that moves the number rather than the line you would actually say. Whether that is a feature or a trap depends on whether the game ever punishes optimisation. The demo does not answer that; the full release will.
What "consequences" means in a demo
The honest answer is: the demo can only show the beginning of the accounting.
| What the demo can show | What needs the full game |
|---|---|
| A scored line changing a counter | Whether the counter changes the ending |
| A dossier recording what happened | Whether the record is ever used against you |
| A branch inside a scene | Whether branches reconverge later |
| A personality being built | Whether the story acknowledges it |
That is not a criticism. A demo that showed the payoff would spoil the game. What the demo does is prove the systems exist and are wired to the story, which is the part players actually need to judge before spending money.
The choices worth paying attention to
If you want to see the consequence design rather than just play through it, watch for four things:
- Lines that offer two versions of the same sentiment. One will usually score, one will not. That is the writer telling you which reading of the protagonist is canonical.
- Moments where a character reacts to something you did earlier. Those are the callbacks that make a branching story feel authored rather than assembled.
- The relationship counter moving down. A system that can only go up is a gift; a system that can go down is a game.
- Scenes that change depending on who is present. In an ensemble cast, presence is often the consequence.
Betrayal is the interesting promise
The store page names three possible outcomes for a relationship: friendship, love or betrayal. Betrayal is the one that requires real consequence design, because it implies a threshold you can cross without noticing.
A game that can betray you is a game where the counters are not purely positive, and where the dossier's Memories field matters — because betrayal is a narrative event, not a number. If the full game delivers that, the choice system will be doing more than sorting players into romance routes.
How to approach a first run
Play it once without optimising. Take the lines you would take, watch the counters, and let the dossiers fill in. Then, if the demo has grabbed you, replay one scene with a Q.Save and take the opposite line to see what the system was measuring.
That two-pass approach is the cheapest way to judge a choice-driven game, and it is exactly what a demo is for.
For the scoring layer in detail, read relationships and routes. For the personality side, read character profiles. For what carries forward, read demo versus full game.
The quotes on this page are from the Steam store description of I Have Known You, and the counter behaviour was observed in the demo, checked on 3 November 2026.