File information

Last updated

Original upload

Created by

HyperspaceTowel

Uploaded by

HyperspaceTowel

Virus scan

Safe to use

36 comments

  1. GaiusMartius
    GaiusMartius
    • premium
    • 4 kudos
    Is the Owlbear cave bug still present after patch 8? Edit: I looked at the patch logs by Larian and they mention that the wound flare issues have been fixed. 
  2. BadWolfeRose02
    BadWolfeRose02
    • member
    • 0 kudos
    Do you know if the bug that's still not fixed applies to the dialogue option unique to a Cleric of Selune (she kills the Nightsong regardless of approval).
    1. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      That one hasn't changed, either
    2. Avendara
      Avendara
      • member
      • 0 kudos
      Oh this was a happy surprise in my latest playthrough LOL. I just sat there with the surprise pikachu face as Shadowheart went shish kabob without my expectations 
  3. GrajowiecPL
    GrajowiecPL
    • supporter
    • 8 kudos
    Can you also fix wound flares points, please?
    1. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      What's going on with her wound flares?
    2. GrajowiecPL
      GrajowiecPL
      • supporter
      • 8 kudos
      Since my english is not the best and the problem can be long to explain I'm sending SlimX video where he explains wound flares points and the bug, I marked the timestamp where he starts talking about wound flares
      video
    3. ViktoriaLanders
      ViktoriaLanders
      • premium
      • 53 kudos
      I think GrajowiecPL refers to 4:14 in the video where SlimX describes that this particular wound flare does not count and prevents future wound flares from being counted either. Which is a bug related to the Nightsong Points.



      Edit:
      There is another bugged wound flare when Shadowheart consumes the noblestalk, as detailed in 5:44.
    4. CreepingDarkness
      CreepingDarkness
      • member
      • 16 kudos
      on the wiki it says if you get the 4th wound flareup to trigger the conversation outside of dialogue it doesn't actually give the point also it breaks the rest of the points 
      edit : if you trigger the noblestalk point before the wound flareup point it also breaks the nightsong points for both by triggering the bugged wound flareup point
  4. realmoth
    realmoth
    • member
    • 0 kudos
    Hi, may I ask does patch 7 require this fix?
    1. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      Yep, the Nightsong Points bug is still present in Patch 7 (and below), but seems to be fixed in the Patch 8 stress test.
      The dialogue bug related to NS points is still present in Patch 8
    2. realmoth
      realmoth
      • member
      • 0 kudos
      Thank you, good day!
  5. NeonCount
    NeonCount
    • member
    • 0 kudos
    Load order with your other mod fixing the epilogue? I'm starting a new run and placed it above the epilogue fix but I think I have plenty of time to change. Thank you for your mod(s).
    1. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      Load order doesn't matter :)
  6. iamy0urdad
    iamy0urdad
    • member
    • 70 kudos
    Today I learned: the act 2 Nightsong dialog bug when Tav/Durge has low approval with Shadowheart (less than 100)

    Great work you're doing fixing all these bugs! You probably should consider compiling all your bugfixes in a "community bugfix patch" mod ;)
    1. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      Thank you! Yeah, I'm definitely going to package them all up at some point -- there are plenty of small dialogue bugs I still want to tackle but it'd be inconvenient for everyone involved to have a separate mod for each of them :p
  7. neohenry
    neohenry
    • member
    • 0 kudos
    Is this mod compatible with Really Shadowheart? https://www.nexusmods.com/baldursgate3/mods/11524
    1. ecc2ca
      ecc2ca
      • premium
      • 1 kudos
      Seconding this!
    2. iamy0urdad
      iamy0urdad
      • member
      • 70 kudos
      this is fixed in my mod since 1.4.8.3
      i will check if both mods are compatible (they probably are, most likely this is an osiris fix)

      Update: I stand corrected, my mod fixes this on her Selunite path only. The bug is still there on her Sharran path. This mod fixes the bug on both her paths

      Update 2: the mods are compatible
    3. neohenry
      neohenry
      • member
      • 0 kudos
      thank you boss for replying; love your Really Shadowheart mod
    4. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      Thank you for looking into it!
    5. Zanderat
      Zanderat
      • premium
      • 249 kudos
      So, in terms of load order, this should load after the Shadowheart mod?
    6. iamy0urdad
      iamy0urdad
      • member
      • 70 kudos
      load order doesn't matter
  8. lordsheogorath12
    lordsheogorath12
    • member
    • 0 kudos
    Does this work with Patch 6?
    1. zamarickz
      zamarickz
      • premium
      • 0 kudos
      I'd also love to know. My playthrough is on patch 6, and I'm about to enter act 3.
  9. Ryuuichi009
    Ryuuichi009
    • premium
    • 10 kudos
    This working with sharran shadowheart makes me so happy. Love that for my girl :D
  10. hannsvii
    hannsvii
    • supporter
    • 1 kudos
    Thanks for explaining and providing a fix for this bug! Out of curiosity what causes the NightSongPoints to prevent the ParentPoints flag from setting in the first place?  
    1. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      It's literally a single line of code, likely something that got copy-pasted and reused from the NightsongPoints check:

      PROC
      PROC_CounterIncreased("ORI_Shadowheart_ParentPoints", _Value)
      AND
      _Value == 2
      AND
      NOT DB_GlobalFlag((FLAG)ORI_Shadowheart_State_NightsongPoint_HasEnoughPoints_82893505-534a-461a-8dd5-0f4677dad6ce)
      THEN
      PROC_GlobalSetFlagAndCache((FLAG)ORI_Shadowheart_State_ParentPoints_HasEnoughPoints_1bbdd0b8-c2de-4b2f-8ce8-6740812deb59);


      So when you hit 2 ParentPoints, the game checks if the NightsongPoint flag is set instead of the ParentPoint flag. 

      For reference, here's the code that checks if you have enough NS points and sets the flag if yes:

      PROC
      PROC_CounterIncreased("ORI_Shadowheart_NightsongPoints", _Value)
      AND
      _Value == 4
      AND
      NOT DB_GlobalFlag((FLAG)ORI_Shadowheart_State_NightsongPoint_HasEnoughPoints_82893505-534a-461a-8dd5-0f4677dad6ce)
      THEN
      PROC_GlobalSetFlagAndCache((FLAG)ORI_Shadowheart_State_NightsongPoint_HasEnoughPoints_82893505-534a-461a-8dd5-0f4677dad6ce);
    2. JohnnyZippo
      JohnnyZippo
      • member
      • 2 kudos
      Thank you very much for this bugfix!

      Two questions:

      #1
      The correct code is then like this?
      PROC
      PROC_CounterIncreased("ORI_Shadowheart_ParentPoints", _Value)
      AND
      _Value == 2
      AND
      NOT DB_GlobalFlag((FLAG)ORI_Shadowheart_State_ParentPoints_HasEnoughPoints_1bbdd0b8-c2de-4b2f-8ce8-6740812deb59)
      THEN
      PROC_GlobalSetFlagAndCache((FLAG)ORI_Shadowheart_State_ParentPoints_HasEnoughPoints_1bbdd0b8-c2de-4b2f-8ce8-6740812deb59);

      #2
      _Value == 2Does this mean the number of parent points must be exact '2' or does it mean '2 and above' (i.e '2' and '3')?
    3. HyperspaceTowel
      HyperspaceTowel
      • premium
      • 151 kudos
      #1 - Lol yup

      #2 - It means 2 Parent Points is the threshold to set the ORI_Shadowheart_State_ParentPoints_HasEnoughPoints flag, which is the flag the game checks for later when you tell Shadowheart to do the right thing. No execute the last line if the flag is already set