Do Harper-Zhent fight occurs normally in TUTU?

[Ashara]

Following up the bug report on troubles with initiating JA-KH-MO-XZ fight:

Running: TUTU4+ V4; variations of events:

on clean install of TUTU and V6 I can see the Jaheira-Xzar dialogue

"Do you claim to fight evil when you are diabolic yourself"
Xzar: "Why must you goad us..."

In some cases as per Bio it ends there, in some cases (randomly) it goes to:

Jah: I know not your goals... etc
Xzar: I begin to see your true nature...

At which point the fouresome goes purple and nothing happens (no fight)...


Once I uninstalled BG1NPC and run "clean" TUTU/V4 (by replacing Override, dialogue.tlk and deleting WeiDU.log: I can get the same banter between Jaheira and Xzar, or the one b/w Khalid and Montaron starting with:

Khalid: Usually everyone proves themselves...
Montaron Do not make light of me! ...
Khalid: I had though none could be...
Montaron: I have suffered yer company....

again, at the end of full exchanges,  the fouresome goes purple and... nothing happens.

Once these guys stuck in "purple" mode they are stuck... I was unable to return them to "green" status by:

- killing their opponents,
- kicking out and rejoining them...

The question: is it a known issue with TUTU and does it normally occurs under a TUTU install?

[Ghreyfain]

Now that I think about it, I know the cause of this bug.  In BG1, the engine would allow script actions to interfere with a character who was MakeUnselectable()'ed (that is, purple-circled).

For some weird reason they changed that for BG2, so once a creature is purple-circled, it will perform the actions already in its queue, and that's it and that's all.

I'll add it to the list of things to do.  I expect we'll have to remove them from the party and have them fight, like the conflicts in BG2.

[SimDing0™]

Can't we ActionOverride them? Or do what I do and have the entire cutscene in the dialogue actions.

[Ashara]

Thank you Ghrey! I thought it can be something like that

[Ghreyfain]

Can't we ActionOverride them? Or do what I do and have the entire cutscene in the dialogue actions.

Once they've been MakeUnselectable()'ed, you can't do any script actions on them until they're selectable once more.  As for having all the actions from the fight in one block, that'll work.  That's what we do with Kelsey and Anomen.

Code: [Select]

THEN
  RESPONSE #100
    SetGlobal("J#AnomenKelseyFight","GLOBAL",2)
    EquipMostDamagingMelee()
    MakeUnselectable(19)
    Spell(Myself,WIZARD_STONE_SKIN)
    AttackOneRound("Anomen")
    Spell("Anomen",WIZARD_FLAME_ARROW)
    AttackOneRound("Anomen")
    Spell("Anomen",WIZARD_FLAME_ARROW)
    AttackOneRound("Anomen")
END

Heheh.

[SirLancelot]

I´m going to check the scripts by myself and see if simply deleting MakeUnselectable(19) resolves the issue in my game. What do you think about it? Any chance to work? 

Heh, now i´m wonder if Tutu could suffer the same problem in all fights BG1 has between party NPC´s .   

[Uncle Gerhardt Jansen]

I am still getting this 'going purple, but not fighting' issue with v.13 of tutufix. Is there any way to get around fixing this myself, or do I have to wait for v.14 hopefully fixing it?

[Culain Mainframe]

I also had the purple problem, was it already suposed to be fixed?

[Uncle Gerhardt Jansen]

Well, have you finally fixed this in v.15?

[Ghreyfain]

Not that I'm aware of.

[WizWom]

I have worked out the correct fix.

Change
MakeUnselectable(5000)
TO
MakeUnselectable(6) // 1 round
Continue()

This allows the character to make a decision for the round, do it, and then do the same next round.

Of course, to test, I still needed to put in a FightTweak to force the Interact between Jaheira and Xzar.

[Moog]

Has this been added to any of the fixes yet?

[cmorgan]

I don't know if it fixes every instance of this, but The BG1 NPC Project has attempted to do so using WizWom's Fight Fix:

Code: [Select]

  ACTION_IF FILE_EXISTS_IN_GAME ~FW0100.are~ THEN BEGIN
  /* WizWom's Tutu NPC Battle fix: not compatible with BGT scripts */
  COPY_EXISTING ~%EDWIN_BCS%.bcs~ ~override~
                ~%ELDOTH_BCS%.bcs~ ~override~
                ~%SHARTEEL_BCS%.bcs~ ~override~
                ~%JAHEIRA_BCS%.bcs~ ~override~
                ~%KAGAIN_BCS%.bcs~ ~override~
                ~%KHALID_BCS%.bcs~ ~override~
                ~%KIVAN_BCS%.bcs~ ~override~
                ~%MINSC_BCS%.bcs~ ~override~
                ~%MONTARON_BCS%.bcs~ ~override~
                ~%QUAYLE_BCS%.bcs~ ~override~
                ~%TIAX_BCS%.bcs~ ~override~
                ~%VICONIA_BCS%.bcs~ ~override~
                ~%DYNAHEIR_BCS%.bcs~ ~override~
      DECOMPILE_BCS_TO_BAF
      REPLACE_TEXTUALLY ~MakeUnselectable(5000)~ ~MakeUnselectable(6) Continue()~
      COMPILE_BAF_TO_BCS
    BUT_ONLY_IF_IT_CHANGES
  END
You will need to replace the crossplatform variables  like %DYNAHEIR_BCS% with their values if you want to just run it on your game without BG1 NPC:

the values are here:

Code: [Select]

    /* Tutu NPC override script compilation */
    OUTER_SPRINT "ALORA_BCS" "_ALORA"
    OUTER_SPRINT "AJANTIS_BCS" "_AJANTIS"
    OUTER_SPRINT "BRANWEN_BCS" "_BRANWE"
    OUTER_SPRINT "CORAN_BCS" "_CORAN"
    OUTER_SPRINT "DYNAHEIR_BCS" "_YNAHEIR"
    OUTER_SPRINT "EDWIN_BCS" "_EDWIN"
    OUTER_SPRINT "ELDOTH_BCS" "_ELDOTH"
    OUTER_SPRINT "FALDORN_BCS" "_FALDO"
    OUTER_SPRINT "GARRICK_BCS" "_GARRI"
    OUTER_SPRINT "IMOEN_BCS" "_IMOEN2"
    OUTER_SPRINT "JAHEIRA_BCS" "_JAHEIRA"
    OUTER_SPRINT "KAGAIN_BCS" "_KAGAIN"
    OUTER_SPRINT "KHALID_BCS" "_KHALID"
    OUTER_SPRINT "KIVAN_BCS" "_KIVAN"
    OUTER_SPRINT "MINSC_BCS" "_MINSC"
    OUTER_SPRINT "MONTARON_BCS" "_ONTARON"
    OUTER_SPRINT "QUAYLE_BCS" "_QUAYLE"
    OUTER_SPRINT "SAFANA_BCS" "_SAFANA"
    OUTER_SPRINT "SHARTEEL_BCS" "_HARTEEL"
    OUTER_SPRINT "SKIE_BCS" "_SKIE"
    OUTER_SPRINT "TIAX_BCS" "_TIAX"
    OUTER_SPRINT "VICONIA_BCS" "_VICONIA"
    OUTER_SPRINT "XAN_BCS" "_XAN"
    OUTER_SPRINT "XZAR_BCS" "_XZAR"
    OUTER_SPRINT "YESLICK_BCS" "_YESLICK"
WizWom tested it locally, but I have no reports from installed user base saying "yes it worked" or "no it didn't", I assume because few folks put the right set of characters together for long enough.