You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported by CajunAzn on G3 forums, in BGEE if you put the familiar in the pack and release it, the familiar doesn't show up—and dissappears from the bag (and you can't summon again)!
The reason this is happening is that baldur.bcs is not getting patched with the code from newfam.baf, which handles the global variables set when the "Release Familiar" ability is used. In the setup-wtpfamiliars.tp2, the installer looks for the block of code in oldfam.baf to replace with the code in newfam.baf.
However, the replacement search fails because of the line for BG2:EE's baldur.bcs:
Yes, it's weird that WeiDU will care what the comment string is for REPLACE_BCS_BLOCK 🤷, but I created a modified setup-wtpfamiliars.tp2 and oldfam.bat that fixes this (and the other two bugs I reported).
- Fix incorrect/missing strings for BGEE (Black-Wyrm-Lair#8)
- More consistent summoning checks for BG(2)EE (Black-Wyrm-Lair#9)
- Allow patching of BGEE `baldur.bcs` for "Release Familiar" item ability (Black-Wyrm-Lair#10)
*Switched to IESDP labels for game versions (without semicolon)
artifoxel
added a commit
to artifoxel/WTPFamiliars
that referenced
this issue
Jul 11, 2022
- Fix incorrect/missing strings for BGEE (Black-Wyrm-Lair#8)
- More consistent summoning checks for BG(2)EE (Black-Wyrm-Lair#9)
- Allow patching of BGEE `baldur.bcs` for "Release Familiar" item ability (Black-Wyrm-Lair#10)
*Switched to IESDP labels for IE game variants (without semicolon)
As reported by CajunAzn on G3 forums, in BGEE if you put the familiar in the pack and release it, the familiar doesn't show up—and dissappears from the bag (and you can't summon again)!
The reason this is happening is that
baldur.bcs
is not getting patched with the code fromnewfam.baf
, which handles the global variables set when the "Release Familiar" ability is used. In thesetup-wtpfamiliars.tp2
, the installer looks for the block of code inoldfam.baf
to replace with the code innewfam.baf
.However, the replacement search fails because of the line for BG2:EE's
baldur.bcs
:MoveGlobalObject("fampsd",Player1) // Pseudo-dragon
is changed in BG:EE's
baldur.bcs
to:MoveGlobalObject("fampsd",Player1) // Pseudo Dragon
Yes, it's weird that WeiDU will care what the comment string is for
REPLACE_BCS_BLOCK
🤷, but I created a modifiedsetup-wtpfamiliars.tp2
andoldfam.bat
that fixes this (and the other two bugs I reported).https://github.com/artyfox/WTPFamiliars/archive/refs/heads/master.zip
Hope you enjoy! 🐕
The text was updated successfully, but these errors were encountered: