hut/outfly
hut/outfly
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

tweak doc

Browse source
This commit is contained in:
yuni 2024-11-18 00:03:05 +01:00
parent 947ef7b69a
commit 7d55e5a9a8
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
src/chats/README.md
View file

@ -5,7 +5,8 @@ Each chat should contain:
- A short introduction - A short introduction
- A main node from which questions can be asked - 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 - 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 - Each node shouldn't exceed 5-6 options
- Don't assume anything about the player, don't imply anything about the player's condition. It's up to them to make up their own story
- 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) - 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 # Chat System Documentation