8 replies to this topic

[X-Calibar]

BGT-WeiDU is partially compatible with:
Imoen Romance v1.20 or above
Install ONLY just before reaching Irenicus' Dungeon, or use BG2 game only - destroys Imoen's joining/leaving dialogue (goes to Copper Coronet) and causes problems when forcing dialogue with Imoen during Baldur's Gate and Tales of the Sword Coast; Irenicus' dungeon-specific banters do not work

In response to asking about this and http://www.shsforums...showtopic=21336 :

Ho-humm, I am not really certain at all about these issues. The SoA mod does use WeiDU and, by default, there shouldn't be any problem; but BGT is a big thing and it might tamper with stuff the mod relies on. The same for changing Imoen's character sheet: depending on the way it's done, it could affect the workings of the mod and give you the infamous Imoen Disappears bug.

I guess that the only way to know is to install the SoA romance last (if possible) and hope for the best, heh.

I'd love to see Imoen Romance fully compatible with BGT... However I have little or practically no experience with Weidu, and yet I'd like this to happen! In an effort to reduce or eliminate any new bugs I might introduce in my learning curve, is there anyone who could take over this effort to create full compatiblity? Or are there any glaringly obvious issues I need to address, [maybe Continue() blocks?] in Imoen Romance mod? Imoen Romance uses an old version of Weidu, wondering if there is an issue in the automatic conversion...?
Imoen Romance v1.201 is the latest version...

In any case, please some good news Or point me in the right direction [preferably not pointing down]
Thanks!

[OldVeteran]

I've had no problems with Imoen using BGT+BP so far when I installed it last. Only issue was with the bracelet quest but thats fixable in game.

Haven't tried installing it before entering BG2 yet though (actually I have but with my worldmap problem that killed it)

[pro5]

As I recall, the main conflict problem between Imoen Romance and BGT is the lack of Global("ENDOFBG1","GLOBAL",2) checks in script and dialogue triggers. This may cause the issues described in first quote in your post - dialogues from BG2 part firing in BGT part instead.

Unfortunately, it's not too easy to add them now: you'll have to make copies of every script and every dialogue file, go through them manually and add the line in bold above to each trigger; then modify the TP2 to compile different versions (with or without such triggers) depending on whether BGT installation was detected or not.

[seanas]

i've never had any issues between the Immy Romance and BGT - i trust Asc's skill more than my own, so i assume there is some issue with Immy, but i've never had any myself. Immy and BG1NPC - for sure, heaps; all those missing GlobalLT("ENDOFBG1","GLOBAL",2) checks in BG1NPC which cause BG1NPC dialogues to endlessly initiate instead of Immy Romance dialoges in AR0602 and AR0603; but never any issues between Immy and BGT.

none of the Immy Romance dialogues need Global("ENDOFBG1","GLOBAL",2) checks, as the dialogue conditions are already sufficiently precisely described that they won't initiate other than in the correct (BG2) places (caveat: or at least this has been my repeated experience).

[OldVeteran]

For Imoen dialogues in BG1 to initialize, you would need the Imoen BG2 dreams which you only get after exiting Irenicus dungeon.
The only thing I noticed ever by playing with Imoen in BG1 is that if you initiate talk with her, you get the 2 options from the romance:
-You don't talk enough
-Nothing
Both of which won't do anything.

[cmorgan]

And thanks to Chevalier and pro5 checking things out, if you PM me for the pre-release Beta4 of BG1 NPC, there should be no problem with BG1 NPC (we added all of those endofbg1 global checks to everything in BG1 NPC, and pro5 ran down/ran over most or all of the interjecting into incorrect BGT states).

Of course, the PID options may conclict, because they are no-condition always-true states until the end of BG1, so if something is like that in the Imoen Romance they will conflict - if recoding isn't possible, just don't install the BG1 NPC Project PIDs.

Edited by cmorgan, 28 January 2007 - 02:20 PM.

[Kulyok]

Of course, the PID options may conclict, because they are no-condition always-true states until the end of BG1, so if something is like that in the Imoen Romance they will conflict - if recoding isn't possible, just don't install the BG1 NPC Project PIDs.

Why? We can always add ~IsGabber(Player1) !Global("EndOfBG1","GLOBAL", something)~ to every NPC's PID, can't we?

[Chevalier]

I think it would be best if modders would add it where needed, but some don't want to.

[cmorgan]

ummm - Kulyok, thank goodness you have a brain, because I certainly don't -- you are 100% correct. I already fixed this. The PID's should also be compatible as long as you use the pre-release Beta 4 where all of pro5's fixes are incorporated -- the code we use for all PIDs on the BGT side is

APPEND ~IMOEN2J~

IF ~IsGabber(Player1) !Global("ENDOFBG1","GLOBAL",2)~ THEN BEGIN IMCH
SAY @1970
++ @1971 EXIT

+ ~GlobalLT("Chapter","GLOBAL",7) Global("IMCHdone","GLOBAL",1) RandomNum(4,1)~ + @1972 + IMCHFailure1
+ ~GlobalLT("Chapter","GLOBAL",7) Global("IMCHdone","GLOBAL",1) RandomNum(4,2)~ + @1972 + IMCHFailure2
+ ~GlobalLT("Chapter","GLOBAL",7) Global("IMCHdone","GLOBAL",1) RandomNum(4,3)~ + @1972 + IMCHFailure3
+ ~GlobalLT("Chapter","GLOBAL",7) Global("IMCHdone","GLOBAL",1) RandomNum(4,4)~ + @1972 + IMCHFailure4

etc, etc, for the massive number of lines here...