Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
Bug |
Completed |
Medium |
Wed 27th Jan 2016 |
1 vote
 |
|
Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
5.0.34.1 |
Thu 17th Mar 2016 |
5.0.35 |
Thu 17th Mar 2016 |
Log In |
|
ElliotM | | Wed 27th Jan 2016 03:07 |
I recently created a conversation topic that was of type 'general command' and 'introduction' with the idea that the character would ask you a question if you greeted them and that the player could respond with a yes or a no to that question.
The problem is that the "character ignores you" response is triggering when the player tries 'say hi' or 'say hi to character', which prevents the player from answering the question attached to the introduction topic.
However, I did find a scenario where you could get around this. I had made a 'greet character' task that had two conversation task actions: 'enter conversation' with referenced character and 'say hi' to referenced character. Using this task to start a conversation instead of using the say task got around the ignore bug. |
|
ElliotM | | Wed 27th Jan 2016 09:31 |
Can confirm a working solution: adding 'enter conversation' with 'reference character' to the task actions for 'ask character about subject', 'tell character about subject', and 'say something to character' solved this issue for me when I had conversation branches coming off of an introduction topic. With that change made, the player was able to answer the question I had made from the introduction topic without the 'ignores you' response appearing. |
|
ElliotM | | Wed 27th Jan 2016 18:58 |
Thread with demo showing bug without the solution applied to the standard library tasks: http://forum.adrift.co/viewtopic.php?f=14&t=11386 |
|
ElliotM | | Mon 1st Feb 2016 07:05 |
Unfortunately my changes caused a new problem - introduction only topics will fail to trigger with this idea applied. Demo in thread listed in the previous post. |
|
Campbell | | Thu 17th Mar 2016 12:38 |
Conversation node was not being set when entering an explicit intro. Fixed. |