Open omegabytes opened 6 years ago
We can make some changes to make the skill stateful. For example, we can set a FIRST_LAUNCH state that gives the user a more in-depth rundown of how to use the skill. After that, we can have a RETURNING_USER state that cuts out a lot of the excess chatter.
Another example would be separating features into states to provide targeted help messages. There would be a SPELLS state that triggers whenever the user is asking about spells. The user could get specific, spell related help prompts ("Ask about spell attributes, etc"). Likewise, there would be a FEATS state where we provided help messages that deal with the attributes of feats. This allows us to reduce the amount of time the user is listening to stuff that isn't relevant to what they're trying to accomplish.
see #99 - make a branching help menu to reduce speech output time and better respond to questions.