Fix for Allison

[Leomar]

By Allison is a mistake in allison\scripts\r#aldrow.baf. UNHAPPY_BREAKING must be UNHAPPY_BREAKING_POINT.

Code:

--- allison\scripts\r#aldrow.baf Fri Sep 28 21:22:26 2007
+++ C:\BWP Patchstudio\patched files\allison\scripts\r#aldrow.baf Sat Feb 09 07:16:12 2008
@@ -16,7 +16,7 @@
   SetPlayerSound(Myself,@1,HAPPY)
   SetPlayerSound(Myself,@2,UNHAPPY_ANNOYED) // ~Why do I waste my time with fools?~
   SetPlayerSound(Myself,@3,UNHAPPY_SERIOUS)
-  SetPlayerSound(Myself,@4,UNHAPPY_BREAKING)
+  SetPlayerSound(Myself,@4,UNHAPPY_BREAKING_POINT)
   SetPlayerSound(Myself,@5,LEADER) // ~Females truly are the superior sex.~
   SetPlayerSound(Myself,@6,TIRED) // ~We should stop to rest, *now.*~
   SetPlayerSound(Myself,@7,BORED) // ~Why are we standing around? I demand we do something!~

Greetings Leomar

[Rastor]

The WeiDU Readme has the constant UNHAPPY_BREAKING set at 0184.  UNHAPPY_BREAKING_POINT is not listed.  What compiler are you using?

[Leomar]

Hmm, we're using WeiDU v210. It could be that the readme is not updated in this point and that since 2005. In this thread you can read about this change.
http://forums.pocketplane.net/index.php/topic,18276.0.html

I'll report that in the WeiDU forum. Thanks.

Greetings Leomar

[Rastor]

Sounds like both are valid now, according to that thread.

[Leomar]

Sounds like both are valid now, according to that thread.

Yes, it is right if you use the command in the TP2, but it is not so easy to use it in baf file. For baf files you should take UNHAPPY_BREAKING_POINT (for easier handling) otherwise you get this message in your setup-allison.debug file:

Code:

Compiling 1 script ...

[allison/scripts/r#aldrow.baf] PARSE ERROR at line 19 column 1-44
Near Text: )
[SetPlayerSound] argument [UNHAPPY_BREAKING] not found in [SNDSLOT.IDS]
Processing 1 dialogues/scripts ...
Extending game scripts ...

So you need to change UNHAPPY_BREAKING to UNHAPPY_BREAKING_POINT.

Greetings Leomar

[Fennek t.B.]

Allison's Setup doesn't update itself anymore automatically to new weidu. The mod can stop BWP installations for hours...

[Rastor]

Allison's Setup doesn't update itself anymore automatically to new weidu. The mod can stop BWP installations for hours...

That's a WeiDU bug, not an Allison bug.

I could try to write a workaround though.  No promises, though.

[Fennek t.B.]

How about substituting /updating the current setup_allison.exe with a new, renamed weidu.exe and uploading it (maybe as a new version)?

[Rastor]

I just downloaded the mod onto a fresh install of BG2 and ran the installer.  It updated itself just fine.

I can repackage it with a new version of WeiDU and see if that makes a difference.

I should say though - when I ran it, it updated itself to v215 which is not the newest one (it's the newest that I had in my BG2 directory).

If you delete everything related to Allison, then could you download the mod right off the RPG Dungeon homepage and run it.  I want to see if it updates for you.

[Fennek t.B.]

We (well, not me, Dabus) developed the BWS a bit further and it should be able now to do the update and to kill all processes of Allison in the tray or whereever. That was actually the problem, weidu-processes staying active after unpacking.