.. | ||
fastravel.yaml | ||
phone.yaml | ||
README.md | ||
serenity.yaml | ||
thebe.yaml |
Guidelines for chats
Each chat should contain:
- A short introduction
- A main node from which questions can be asked
- Questions may lead into sub-nodes with more sub-questions, which have an exit option that takes you back into the main node
- Each node shouldn't exceed 4-5 options
- AVOID hiding questions until the player gains more knowledge about the NPC. While it makes things more realistic, the user experience sucks, since the user will always worry that there are some hidden conversation options that one is missing because knowledge hasn't been unlocked yet. It also makes the definition file convoluted and hard to read/understand. Open up everything from the start. Share vital info in the introduction (of the NPC or of the sub-node)
Chat System Documentation
For now, see chat.rs for the source code and the individual YAML files for examples.
Known bugs
Only Ifs
- some choice:
- if $a:
- answer 1
- if $b:
- answer 2
This is currently broken. Instead do this:
- some choice:
- if $a:
- answer 1
- goto: somelabel
- answer 2