The following illustrates a problem I’m running into. Basically, a certain event (in the example, examining a whoozeewhatchamacallit) triggers a sequence of events to occur a certain number of turns later. When that time comes, I want an NPC to arrive and immediately initiate a conversation (using Eric Eve’s conversation package and its constituent extensions). What happens is that the NPC arrives on schedule, but the conversation is not actually initiated until the following turn. I surmise that the problem has something to do with the order in which the various instructions are processed, but I don’t know how to fix it.
I know that in the example (which is simplified to illustrate the point), I could avoid the issue entirely by having the text of Fred’s greeting printed as a “say” statement (which is how the text announcing his arrival is handled) rather than through a node introduction rule. This would not do what I need in the actual game (I need to set up a conv-node so that when Fred arrives, he is immediately set to give certain responses which are specific to this stage of the game, and I also want to set a list of suggested topics to talk to him about).
Given my own lack of sophistication in these matters, I’m afraid of tinkering much with the innards of the extensions, so I’m trying to find a solution which avoids the need to do that.
Any suggestions would be appreciated.
[code]“TimingTest” by Me
Include Conversation Package by Eric Eve.
Anywhere You Like is a room. A whoozeewhatchamacallit is in Anywhere You Like.
Fred is a man.
FredsHere-Node is a convnode.
Node-introduction for FredsHere-Node:
Say “‘Hiya, old buddy,’ Fred says, slapping you on the back.”.
After examining the whoozeewhatchamacallit for the first time:
FredReturns in 3 turns from now.
At the time when FredReturns:
Say “Your old pal Fred enters the room.”;
Initiate a conversation with Fred at FredsHere-Node.[/code]
Robert Rothman
