Skip to content

Romance and Relationships in Interactive Fiction

Craft guidance for writing romance—mechanics, pacing, tropes, and player agency.

Relationship Mechanics

Tracking Affection

1. The Love Meter (0-100)

  • Standard "dating sim" mechanic.
  • Pro: Clear feedback.
  • Con: Gamifies relationships ("I need 5 more points to kiss").

2. Flags (Boolean States)

  • met_at_party, shared_secret, kissed_in_rain.
  • Pro: Organic feel. Specific events trigger specific dialogues.
  • Con: Harder to visualize progress.

3. The Two-Axis System

  • Friendship vs. Romance: You can be high Friendship/low Romance (Best Friend) or low Friendship/high Romance (Rival/Fling).
  • Approval vs. Respect: They might hate you but respect your skill.

The "Lock-In" Point

When does the player commit?

  • Soft Lock: Dialogues flavor changes, but other routes remain open.
  • Hard Lock: Distinct branch where other romances become unavailable.
  • Design Note: Clearly signal Hard Locks to avoid player frustration.

Romance Tropes and Pacing

Pacing Arcs

  • Insta-love: Rare in modern IF; often feels unearned.
  • Slow Burn: High tension, delayed gratification. heavily favored in text games.
  • Enemies to Lovers: High conflict converting to passion.
  • Fake Dating: Forced proximity trope.

The "First Move" Problem

Who initiates?

  • Allow player choice: "Lean in" vs "Wait for them."
  • Shy characters shouldn't initiate usually, but bold ones might.

Conflict in Romance

A relationship without conflict is boring.

  • External Conflict: War, family, duty keeps them apart.
  • Internal Conflict: Trust issues, secrets, incompatible goals.

The NPC's Agency

NPCs shouldn't be vending machines (Put in Kindness coins -> Get Sex).

  • Rejection: NPCs should reject players if stats/flags aren't met or if the player's personality clashes with theirs.
  • Breakups: If the player acts against the NPC's core values, the NPC should end it.
  • Clear Signals: "Can I kiss you?" options.
  • Fade-to-Black vs. Explicit: Establish tone early.
  • Opt-Out: Always allow players to remain single or aromantic.

Writing the "Date" Scene

Structure

  1. Invitation: The context (mission downtime, festival).
  2. Conversation: Learning new depth about the character.
  3. The Choice: A moment of vulnerability or escalation.
  4. The Outcome: Relationship status shifts.

Dialogue

  • Avoid generic "flirt" options.
  • Tailor flirting to the character (Witty banter vs. Earnest compliments).

Common Mistakes

"Ninjamancing"

Accidentally triggering a romance by being polite.

  • Fix: Distinct "Flirt" icons or clearly romantic dialogue tags.

The "One Right Answer"

NPC only likes you if you agree with everything they say.

  • Fix: NPCs should respect players who challenge them (sometimes).

Lack of content for non-romancers

Punishing players who choose to be single by giving them less content.

  • Fix: "Friendship" routes should be just as rich as romance routes.

Quick Reference

Trope Mechanic Match
Soulmates High Destiny/affinity flags
Rivals High Respect / Low Friendliness
Slow Burn Gated progression (Chapter locked)
Love Triangle Mutually exclusive flags

See Also