Abstract
Problem: What are the key differences between topic-based and branching dialogue systems in RPGs, and when should a designer choose one over the other?
Approach: Tim Cain draws on his experience shipping both systems — a hybrid topic/branch system in Fallout 1 and pure branching in subsequent games — to compare their strengths and trade-offs.
Findings: Topic-based systems are simpler to extend and easier for players to navigate, but branching systems feel more natural, better convey NPC personality, and more clearly surface the impact of player skills and choices.
Key insight: Both systems can react to the same game-state triggers (quests, events, stats, choices), but branching dialogue handles multiple simultaneous state changes far less gracefully — every new entry point multiplies complexity, whereas topics just add an item to a list.
Definitions
Topic-based dialogue: Clicking an NPC presents a flat list of topics (single words or short phrases). Clicking a topic produces a response, lore dump, or service (barter, repair, identify). The list grows and shrinks as the game state changes. Examples include the early Ultima and Elder Scrolls games.
Branch-based dialogue: Clicking an NPC triggers a conversational flow. The NPC says something (an "entry point"), the player picks from a set of responses, and the conversation branches from there. This is the dominant model in modern RPGs, especially with voice acting and lip sync.
Hybrid: Fallout 1 used branching dialogue with a side panel where the player could type in any keyword to ask about. Topics weren't displayed — the player had to guess or learn keywords (Brahmin, mutants, ghouls) through exploration. This approach was not continued in later games.
What Both Systems Share
Both topic and branch systems can add or change content in response to the same triggers:
- Game events — something happened in the world and NPCs react
- Quest completion — the player did something for or near this NPC
- Story acts — a major narrative milestone changes available dialogue
- Player choices — killing someone, stealing, selling stolen goods
- Player stats — attributes, skills, perks gate certain options
The difference is how they surface those changes. Topics simply add a new item to the list. Branches may require an entirely new entry point and response tree.
Advantages of Topic-Based Systems
Easy to extend
Adding a new topic in response to any game event is trivial — it's just another item on the list. No need to restructure conversation trees or worry about competing entry points.
No response-count limits
Branching systems typically cap player responses at 4–5 (sometimes up to 8–10) for UI and sanity reasons. Topic lists can scroll or display in a grid, accommodating many more options without friction.
Simple for players to use
Players can jump directly to what they want — barter, repair, crafting — without drilling through multiple dialogue layers. Common actions sit at the top of the list, and unasked topics can be highlighted and sorted to the top, making it easy to see what's new.
The entry-point problem
Branch-based dialogue struggles when multiple state changes happen simultaneously. If the player fended off a goblin invasion, killed a dragon, and the villain Bart arrived in town, what should the NPC's opening line be? Topic systems sidestep this entirely — all three just appear as topics.
Advantages of Branch-Based Systems
Feels natural
Especially in modern RPGs with VO, lip sync, and facial expressions, a flowing conversation feels like the obvious way to interact with an NPC. It mirrors how real dialogue works.
NPC personality shines through
The way an NPC talks, responds to player choices, and reacts to different conversational branches reveals character. Is this person secretive, sarcastic, authoritative, annoying? Branching dialogue makes personality emerge naturally through conversation flow, which is harder to achieve with topic lists.
Skill and perk use is more visible
Branching systems make it easy to label responses — "you're getting this option because of your Intimidation skill" or "this appeared because you took this perk." The limited number of responses means there's room for these labels without clutter.
NPC reactions add depth
Beyond showing that a skill check is available, branching lets you show how the NPC reacts. A powerful NPC might resist intimidation but respond to persuasion or a bribe. This demonstrates the texture of different skills and reinforces NPC characterization simultaneously.
Tim's Preference
Tim states his preference clearly: branching. He's only done topic-based once (Fallout 1's hybrid system) and used branching for everything else. He finds that branching's ability to convey personality, surface player agency, and feel conversational outweighs topic systems' simplicity and extensibility advantages.
References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=aXg3y-OxOsM