5 replies to this topic

[musekissing]

It seems that I always am the victim of strange dialogue loopings ...
This time it's Coran who repeats his 'let-us-finally-go-wyvernhunting'-sequence over and over.

Strange as it is also NO VALID REPLIES OR LINKS appears as an answering option,
although there shouldn' be anything.

[Thauron]

I think this is caused by the following block of code in X#JFIX.D from BG1NPC:

//Adding Globals to Coran's Wyvern Misadventure:

ADD_TRANS_TRIGGER CORANJ 6 ~Global("X#CoranWyvernWarning1","LOCALS",1)~

ADD_TRANS_ACTION  CORANJ BEGIN 6 END BEGIN
END
~SetGlobal("X#CoranWyvernWarning1","LOCALS",2)~

ADD_TRANS_TRIGGER CORANJ 5 ~Global("X#CoranWyvernWarning2","LOCALS",1)~

ADD_TRANS_ACTION  CORANJ BEGIN 5 END BEGIN
END
~SetGlobal("X#CoranWyvernWarning2","LOCALS",2)~

I don't know why ADD_TRANS_TRIGGER is used here, cause there are no transitions in this dialogue file, hence the 'no valid...'

If I am not mistaking, both ADD_TRANS_TRIGGER should be replaced by ADD_STATE_TRIGGER

This should also prevent the dialogue from looping, since the globals which prevent this from looping aren't set because of the erroneously created transition.

Edited by Thauron, 22 April 2006 - 11:48 AM.

[musekissing]

If I change the D-file it is still the same ...

Or mustn't I change it that way?

[Sir BillyBob]

Changing a D file only works in the game if you compile it back into the game (using DLTCEP). In the game, the file is actually a .DLG file. So you need to change that file (both DLTCEP and NI can do this).

The ADD_STATE_TRIGGER command adds a condition to a dialog. You don't need an actual response from the player. This command will add:

Global("X#CoranWyvernWarning1","LOCALS",1)

to the condition of that dialog. The second part is the action to take after Coran says that dialog. That way, he doesn't repeat this dialog.

The only problem would be if CORANJ does not have a dialog number 6 (you see this in the D file as BEGIN 6). It does, so the corrected action should work.

I agree that the problem here is that the ADD_TRAN is not working as needed. Does anyone know if this has already been mentioned over at G3? That would be a typo in their original Tutu package, not something that I would have changed. They may already have it noted for the next version.

[Thauron]

If I change the D-file it is still the same ...

Or mustn't I change it that way?

If you want a quick workaround for this problem, I think the easiest way would be to CLUAConsole a Wyvern (simply WYVERN) in - so Coran will be happy.

An other way would be to set Coran LOCALS (not a GLOBAL!) variables 'X#CoranWyvernWarning1' and 'X#CoranWyvernWarning2' both to 2, if you know how to do that.

EDIT: @ Sir BillyBob: I didn't find any reference to this bug in the bug thread over at G3.

Edited by Thauron, 23 April 2006 - 11:34 AM.

[Sir BillyBob]

I just asked about it on G3.