I've never had this problem before. A conversation keeps starting at the first node even though I set it to "once per game". Here's the situation.
It's an NPC that joins the party. The NPC has just one conversation. The first node on the conversation is the part where you talk them into joining your party. The subsequent ones are for discussion along the way. The problem is, the first node keeps firing.
The odd part is that if I change the node to "once per creature" then it works fine. Any thoughts?
A conversation node keeps firing even though it is set to "once per game"
Débuté par
M. Rieder
, janv. 16 2011 08:22
Retour en haut
#2
Posté 17 janvier 2011 - 05:08
Kaldor Silverwand
-
- Members
- 1 598 messages
Strange. What actions take place on the first node? Are you despawning and spawning in another copy of your npc for some reason?
#3
Posté 17 janvier 2011 - 07:51
M. Rieder
-
- Members
- 2 530 messages
Thre are no actions on the first node. But when the NPC is added to the group, it is added to the global roster and then becomes a compaion. I don't know if that makes a difference. The really strange thing is that I can start the conversation multiple times and it still fires the first node.
#4
Posté 17 janvier 2011 - 11:02
Kaldor Silverwand
-
- Members
- 1 598 messages
To determine what is the cause I would try adding a new first node that has no actions of any kind associated with it and have it set to once per game and see if it works properly. If it does, and it should, then the problem has something to do with what you are doing after the node. I'm not sure what though. My thought was that you were possible spawning in a different creature, which would mean that they had not actually said the line before.
