64 replies to this topic

[King Diamond]

Will the BG1 Baldurdash fixes install only when BGT is already installed?

Yes. BGT has some bg1 fixes already incorporated but not for 100%. v1.2 covers the rest.

[cujo]

Will the BG1 Baldurdash fixes install only when BGT is already installed?

Yes. BGT has some bg1 fixes already incorporated but not for 100%. v1.2 covers the rest.

Thanks King Diamond I'll do a new install of all the WeiDU mods over the weekend. :thumb:

[King Diamond]

Next update.

HUNDREDS of incorrect resources references fixed (to non-existing BAMs, ITMs, CREs, WAVs, SPLs etc.).

Both BGT and ToB.

[King Diamond]

Small fix for Oublek's dialog (Prism and Brage quest).

[King Diamond]

Fix for nearly 160 original ToB scripts with invalid Dead("....") triggers added + fix for several invalid scripts included in BIF in already compiled form (but compiled code is invalid).

Those triggers contained various BS like:

!Dead("astSeenBy())")
!Dead("astSeenBy(Myself))")
!Dead("astHeardBy())")
!Dead("astHeardBy(Myself))")
!Dead("yself)")
!Dead("astAttackerOf(")
!Dead("astAttackerOf(LastSeenBy(Myself)))")
!Dead("astTrigger)")
Dead("astTrigger)")~

that were cloned by some hired Microsoft programmers all over there....

Edited by King Diamond, 13 April 2005 - 07:19 AM.

[Vlad]

Fix for nearly 160 original ToB scripts with invalid Dead("....") triggers added + fix for several invalid scripts included in BIF in already compiled form (but compiled code is invalid).

I have made this fix in TS some time ago. It's very simple:

APPEND ~TRIGGER.IDS~
~0x4051 Dead(O:Object*)~

[King Diamond]

I have shown original syntaxis: there was Dead("astSeenBy())"), not Dead(LastSeenBy()).....

[CamDawg]

I don't think Dead(O:Object*) would work anyway. Dead("foo") works by checking that the value of the global variable SPRITE_IS_DEADfoo is > 0. Using a generic object fails because the global SPRITE_IS_DEAD is never set AFAIK. Even if it was set, it would not be unique.

The Fixpack solved this by altering the Dead triggers which use objects to use custom StateChecks, in addition to the numerous typo fixes.

edit: Dead() checks if SPRITE_IS_DEAD is greater than 0, not equal to 1 as I originally stated.

Edited by CamDawg, 14 April 2005 - 04:36 AM.

[Vlad]

KD, if you take a look into original ToB TRIGGER.IDS, you'll see the following offset:

0x4051 Dead(S:Name*)

The programmers had nothing to do to this problem. It's a pure scripting issue because name always means "Name" or in other words "STRREF". The scriptors of the game just mixed two triggers Dead(S:Name*) and Died(O:Object*). Where it is "STRREF" argument there should be Died(O:Object*). It's obvious. What I suggest is to add to the TRIGGER.IDS to the same offset the correct trigger:

0x4051 Dead(O:Object*)

Then the program would recognise the both cases.

The same you may do with the following broken area flag 1 OUTDOOR in AREATYPE.IDS:

APPEND ~AREATYPE.IDS~
~1 OUTSIDE~

I don't think Dead(O:Object*) would work anyway. Dead("foo") works by checking that the value of the global variable SPRITE_IS_DEADfoo is > 0.

This is exactly the issue here. Are you sure what I suggested doesn't work? It just works fine for me. But of course you may always use just Die() trigger and be on the safe side if you are not sure about either Dead or Died.

Edited by Vlad, 14 April 2005 - 06:37 AM.

[horred the plague]

KD, if you take a look into original ToB TRIGGER.IDS, you'll see the following offset:

0x4051 Dead(S:Name*)

The programmers had nothing to do to this problem. It's a pure scripting issue because name always means "Name" or in other words "STRREF". The scriptors of the game just mixed two triggers Dead(S:Name*) and Died(O:Object*). Where it is "STRREF" argument there should be Died(O:Object*). It's obvious. What I suggest is to add to the TRIGGER.IDS to the same offset the correct trigger:

0x4051 Dead(O:Object*)

Then the program would recognise the both cases.

The same you may do with the following broken area flag 1 OUTDOOR in AREATYPE.IDS:

APPEND ~AREATYPE.IDS~
~1 OUTSIDE~

I don't think Dead(O:Object*) would work anyway. Dead("foo") works by checking that the value of the global variable SPRITE_IS_DEADfoo is > 0.

This is exactly the issue here. Are you sure what I suggested doesn't work? It just works fine for me. But of course you may always use just Die() trigger and be on the safe side if you are not sure about either Dead or Died.

I've said it a dozen times over the years, or more. Adding Dead(O: Object*) to trigger.ids will cause a major problem in existing scripts. I wished it did work, it makes logical sense--but it doesn't. It works in all subsequently made scripts, but will cause all the existing scripts that have a proper name in the slot to self-destruct. I tried it once, and all the Dead(e.g, "Keldorn") type triggers were fubar'ed. The most reliable procedure I've found is a simple hit point check: HPLT(LastSeenBy(Myself),1). The last I knew, zero or less hit points in BG2 means you're dead meat. It's what I've used in every script I've done for BP. And I'm 100% sure that it works.

[SimDing0]

How does adding Dead(O:Object*) break existing scripts? It'll probably stop them decompiling correctly, which could be fixed by renaming the new trigger to something like Dead2(O:Object*). Not that it matters, since I'm sure that Dead(O:Object*) doesn't work.

[horred the plague]

How does adding Dead(O:Object*) break existing scripts? It'll probably stop them decompiling correctly, which could be fixed by renaming the new trigger to something like Dead2(O:Object*). Not that it matters, since I'm sure that Dead(O:Object*) doesn't work.

Actually, you're right. It doesn't break previously compiled scripts, but it prevetns any changes from being made to them, ever again. At least, working changes...

[Kamui2040]

found the following error regarding baldurdash v1.2 weidu installation upon a clean soa+tob+official patch from bioware
ERROR locating resource for 'COPY'
Resource [CULTASS.CRE] not found in KEY file:
[./chitin.key]
Stopping installation because of error.
i checked the override folder as well as the chitin.key and this creature is not to be found.

[King Diamond]

found the following error regarding baldurdash v1.2 weidu installation upon a clean soa+tob+official patch from bioware
ERROR locating resource for 'COPY'
Resource [CULTASS.CRE] not found in KEY file:
        [./chitin.key]
Stopping installation because of error.
i checked the override folder as well as the chitin.key and this creature is not to be found.

Thanx. Fixed. It is BG1 creature and it was mistakenly placed in the main TP2 section.

[King Diamond]

Some BG1 items removed from the patching - BGT installation will make those fixes obsolete.

[King Diamond]

Another small update for some BG2 items on the start of the game (undroppable key and IGIBBER with morale 1).

[King Diamond]

Version updated to 1.3: updated to WeiDU v183 (no more nasty .dlg.dlg's left in override; overall performance optimized; bg1 removed after they've been implemented in BGT-WeiDU, so it's pure BG2 from now; few minor fixes added as well).

[GekkeR]

I've been wondering if bdash should be installed before or after the BG2 mods (like ascension, tdd-weidu, etc).

[Ascension64]

Thanks for removing BG1 fixes from BDash and allowing them to be included into BGT-WeiDU. It makes much more sense from a user perspective to only install one thing.

[King Diamond]

I've been wondering if bdash should be installed before or after the BG2 mods (like ascension, tdd-weidu, etc).

It better be installed after all other mods because they could overwrite some fixes.

And plz notice that the 2nd part of it (Text Updates) is English only.

P.S>
2Asc
As for BGT-WeiDU there's one known issue.
AATAQAH.DLG. You may notice that there's 1 warning message about it during BGT-WeiDU installation when it patches it for "Imoen2" deathvar. It is because it contains some bad Dead(..) trigger spelling that is getting fixed by BDash for BG2.
There's nothing wrong btw - WeiDU recovers from that situation by quoteing invalid object name and that allows to continue current BGT and further BD installations.