dubiousintent Posted July 14, 2018 Share Posted July 14, 2018 That's too bad that it didn't resolve the problem. But cleaning up code is never wasted effort. As mentioned before, we need to see the code surrounding the skipped line: the one that is supposed to link to the skipped dialog, the result of the skipped dialog that is supposed to link to the following line, and the line that next gets said (with any lines in between) at a minimum. It sounds like you have everything in place, but the results are saying that isn't so. It's common practice at this point to sprinkle liberal numbers of PrintC statements displaying the values of various conditionals between each line of dialog to help trace the flow of the logic. See 'TIP: Debugging Compound Conditionals' and 'TIP: Debugging data to file' under the "Scripting" section of the wiki "Getting started creating mods using GECK" article. -Dubious- Link to comment Share on other sites More sharing options...
Mktavish Posted July 14, 2018 Share Posted July 14, 2018 If you haven't already , try getting rid of the Link To and Link From fields. Just using the result script (end) with the SayTo So in result script (end) of the first topic , which was said by "Actor01Ref" then put ... Actor02Ref.SayTo Actor01Ref MyTopic02 Then in the result script (end) of MyTopic02 ... Actor01Ref.SayTo Actor02Ref MyTopic03 Then in the result script (end) of MyTopic03 ... Actor02Ref.SayTo Actor01Ref MyTopic04 And so on through out the conversation. But this method will not show up in the Dialogue Tree ( guessing anyways ).... so you will have to make your own to know what links to what. But with some careful incrementing , should be able to get it done without needing to look at the tree anyways.Hope that helps , give it a try. Link to comment Share on other sites More sharing options...
Recommended Posts