13 replies to this topic

[Intox]

Hi. I'm experiencing a problem with Coran, who after joining in Cloakwood works fine until we kill our first wyvern (clua summoned or otherwise). He then goes into an infinite loop saying "Can't stick around to talk, I have some wyverns to kill" - until I force-talk to him, at which time he continually bugs me every few seconds with that talk menu.
  
I've seen some very similar bugs mentioned in relation to Coran and the wyverns, including something now supposedly fixed mentioned in the BGT 1.0 version history (but it might be the source of my problem is with BG1NPC not BGT).
  
Can anyone suggest a SetGlobal or other fix for this problem? Summoning another Wyvern to kill doesn't help the problem. (I'd hate to have to dump this cool character. I've never had him in my party before. )
  
  My WeiDU log is attached.
Thanks.

Attached Files

•  WeiDU.txt   10.39K   252 downloads

Edited by Intox, 26 May 2006 - 01:56 AM.

[Intox]

Well I've been able to semi-solve this problem by removing the BGT-Tweak component "Coran responds to the death of a Wyvern". I'm not very familiar with BG scripts, but it seemed to me that little bit of code added by BGT-Tweaks (below) checks for a condition which may be continually true as soon as you kill a Wyvern, hence the infitite loop I was getting. I'm sure you good folks wouldn't have made this mistake so if someone more knowledgeable in this area could explain what went wrong I'd much appreciate knowing.

IF
	  CombatCounter(0)
	  Dead("Wyvern")
	  InParty(Myself)
	  Global("CoranReward","GLOBAL",0)
	THEN
	  RESPONSE #100
		Dialogue([PC])
	END

Edited by Intox, 28 May 2006 - 10:25 PM.

[Ascension64]

Sorry, I'm a bit busy at the moment with RL, but you can easily check whether this script block you mention is the problem by using the CLUAConsole:SetGlobal("CoranReward","GLOBAL",-1). That would quell the problem if indeed this was the cause. Be sure to let us know what happened.

[Intox]

RL? That sounds like a fun mod! Anyhow, tried your suggestion and it fixed the problem (as did removing the component I mentioned as well). Might be there's a problem with that BGT-Tweaks component. Thanks for your help.

Edited by Intox, 03 June 2006 - 04:46 AM.

[Ascension64]

RL? That sounds like a fun mod! Anyhow, tried your suggestion and it fixed the problem (as did removing the component I mentioned as well). Might be there's a problem with that BGT-Tweaks component. Thanks for your help.

That's good news. It means I know where the problem is. RL = real life, a very good 'mod' indeed.

[Autar]

Had same problem:


While walking around:



When he reaches party member:



When he reaches CHARNAME:



Answering to the "flirt"-dialogue - whatever option - had no change to this happening again.

It starts when I piked him up. I already had killed a Wyvern (random encounter) befor joining Coran. Bringing head to temple or killing other Wyvren does not fix this problem.

After uninstalling "Coran responds to the death of a Wyvern" BGT-Tweak component it seems to work fine.

[berelinde]

You've got BG1 NPC Project, don't you?

Make that script block

IF
	  CombatCounter(0)
	  Dead("Wyvern")
	  InParty(Myself)
	  Global("CoranReward","GLOBAL",0)
	  Global("DeadWyvern","GLOBAL",0)
	THEN
	  RESPONSE #100
		SetGlobal("DeadWyvern","GLOBAL",1)
		Dialogue([PC])
	END

And that would fix it, too.

[Autar]

The "Coran responds to the death of a Wyvern" wasnt so important for me so I uninstall it

I just post to fix the BGT-tweaks or the BG1 NPC project in future versions

Anyway thanks for the reply

[pro5]

Well, the first thing to fix at this moment is incorrect detection of BG1NPC by BGTTweaks, which is supposed to skip those components if BG1NPC is installed:

FORBID_COMPONENT ~Setup-BG1NPC.tp2~

should be

FORBID_COMPONENT ~BG1NPC.tp2~

everywhere.

[Ascension64]

Well, the first thing to fix at this moment is incorrect detection of BG1NPC by BGTTweaks, which is supposed to skip those components if BG1NPC is installed:

FORBID_COMPONENT ~Setup-BG1NPC.tp2~

should be

FORBID_COMPONENT ~BG1NPC.tp2~

everywhere.

This was changed during which version?

[berelinde]

pro5, may I respectfully suggest that a different file be used for BG1 NPC project detection? Using the tp2 will skip installation if the mod has been unpacked, but not installed.

This block from the BG1 NPC project seems to indicate that a different file should be used for detection:

BEGIN @1
/* Tells other mods BG1NPC Core is installed */
COPY ~BG1NPC/Core/X#component.xx~ ~override/X#BG1NPCCore.G3~

Maybe use ~override/X#BG1NPCCore.G3~ as your check file?

[pro5]

This was changed during which version?

One latest oficially released, v12-beta3, I believe.

pro5, may I respectfully suggest that a different file be used for BG1 NPC project detection? Using the tp2 will skip installation if the mod has been unpacked, but not installed.

It's not a file, it's installed component. I omitted details and specific component numbers which follow up, like:

//#2 Angelo notices Shar-teel////////////////////////////////
BEGIN @200
REQUIRE_PREDICATE (FILE_EXISTS_IN_GAME ~AMNSCENE.BCS~) @1
FORBID_COMPONENT ~Setup-BG1NPC.tp2~ 2 @3

That said, component numbers also tend to change (sometimes without intent), so I would also use the method you suggest instead.

[berelinde]

Ah, thanks for going into more detail. I see what you mean, now.

[cmorgan]

The move to flag files was to help with just this kind of thing - I am trying to drill down to specific components incompatibility, and may need to tweak this further to make sure everything is easier for other modders. Right now, each major component of BG1 NPC has its own flag file, used bith internally as a check for R_F and SUBCOMPONENT tp2 coding and as a reference file for conflicts. We even point out other mods with similar components. SCS, for example, has move components not coded in the BGT side of BG1 NPC, so the latest internal fail string directs BGT users to SCS-BGT for those components.

The SETUP-BG1NPC vs BG1NPC was retained from several earlier versions ( I am not sure what version deviated from this, but the default behavior has been set as just BG1NPC.TP2); the naming and placement of the file are holdouts for backwards compatibility (We don't want to move to a modern package with the .tp2 dropped into the folder, as a user who accidentally leaves an older .tp2 in the main directory will have that override the one nested further in).

As with anything, I would be very open to suggestions on how to make compatibility easy. Just let me know, and we can tweak some of this in BG1 NPC as well