BONDS/RIVALRY
Relationships between characters accrue mechanical weight — units who fight together gain support bonuses, rivals remember defeats and grow stronger, affinities unlock story scenes and combat synergies.
- SOLO-DEV COST HIGH
- TIMING REAL-TIME / TURN
- COMMON IN TACTICS · RPG · ACTION-ADVENTURE · NARRATIVE
Fire Emblem: Three Houses builds its support system into both tactics and narrative: paired units gain hit and avoid bonuses while friendship ranks unlock character-defining conversations. Middle-earth: Shadow of Mordor's Nemesis system creates rivalries dynamically — the orc who killed you gets promoted, remembers, and taunts you about it next encounter. Designers use bonds and rivalry to convert repeated proximity into attachment (players protect units they've invested relationships in, raising permadeath stakes), and rivalry to give failure narrative dividends: dying to a named enemy authors a story instead of just reloading one. Both make a roster feel like a cast. Key decisions: how relationships build (adjacency in battle, shared meals, scripted scenes), what they pay out mechanically versus narratively, and whether negative relationships exist with real teeth. Pitfall: relationship grinding — when bonds come from repeating trivial actions, players optimize the friendship system like a spreadsheet, and the emotion the mechanic exists to produce is exactly what gets ground away.