The conversation system has been one of those features that looked simple until I started paying attention to how often it appears.
If every NPC gives the same answer structure, the character disappears and the dialogue becomes a menu.
At first, talking to a character could have been a list of questions and a response. Functional, but not especially alive. The more I played with it, the more obvious it became that conversations needed memory and shape.
I have been rebuilding the system around portraits, speaker names, new-topic sorting, optional hiding of questions that have already been asked, and follow-up choices that can create actual decision-tree conversations. If Ethan asks something important, the next response should be able to open a more specific line of questioning instead of dropping the player back into the same generic list.
The developer side is just as important. I want to be able to see the conversation tree, edit follow-up responses, understand which branch leads where, and add new material without hunting through unrelated code. That is why the conversation editor has become part of the larger Dev Workshop rather than remaining hard-coded dialogue.
Character voice is another concern. Liam, Maya, Margaret, Elias and the rest of the cast should not sound interchangeable. The same ridiculous player action can produce different reactions depending on who is present. That gives optional dialogue a reason to exist beyond dumping information.
I am also planning voice carefully. I like hearing characters when they speak, but I do not want every thought, menu option and piece of interface text narrated until the game feels exhausting. Spoken character dialogue and a controlled narrator can add personality without turning the experience into an audiobook with buttons.
The end goal is simple: when you click TALK, I want you to feel like you are dealing with that particular person, not opening a database record.