10 replies to this topic

[ronin69hof]

CamDawg note: I just wanted to clarify that the conflict between QP and Fixpack is between the Core Fixes of BG2 Fixpack and Revised Hell Trials of Quest Pack.

The fixpack changes ar2904.bcs using this code:

COPY_EXISTING ~ar2904.bcs~ ~override~
  DECOMPILE_BCS_TO_BAF
	REPLACE_TEXTUALLY ~Global("PaladinGone","AR2904"~ ~Global("AbyssPaladinGone","GLOBAL"~
	REPLACE_TEXTUALLY ~Global("RangerGone","AR2904"~  ~Global("AbyssRangerGone","GLOBAL"~
	REPLACE_TEXTUALLY ~\(OpenState("DOOR03",TRUE)\)~ ~\1 Global("OpenedDoor1","AR2904",1)~
	REPLACE_TEXTUALLY ~\(OpenState("DOOR04",TRUE)\)~ ~\1 Global("OpenedDoor2","AR2904",1)~
	REPLACE_TEXTUALLY ~\(OpenState("DOOR05",TRUE)\)~ ~\1 Global("OpenedDoor3","AR2904",1)~
	REPLACE_TEXTUALLY ~\(OpenState("DOOR06",TRUE)\)~ ~\1 Global("OpenedDoor4","AR2904",1)~
  COMPILE_BAF_TO_BCS
  BUT_ONLY_IF_IT_CHANGES

Its part of the "other scripting fixes" part. The questpack also tries to patch that .bcs file and cant find any matching blocks with the below code:

COPY_EXISTING ~ar2904.bcs~ ~override/ar2904.bcs~
  REPLACE_BCS_BLOCK ~questpack/helltest/data/d2a_1.baf~ ~questpack/helltest/data/d2a_2.baf~
  REPLACE_BCS_BLOCK ~questpack/helltest/data/d2b_1.baf~ ~questpack/helltest/data/d2b_2.baf~
  REPLACE_BCS_BLOCK ~questpack/helltest/data/d4a_1.baf~ ~questpack/helltest/data/d4a_2.baf~
  REPLACE_BCS_BLOCK ~questpack/helltest/data/d4b_1.baf~ ~questpack/helltest/data/d4b_2.baf~
  REPLACE_BCS_BLOCK ~questpack/helltest/data/d6a_1.baf~ ~questpack/helltest/data/d6a_2.baf~
  REPLACE_BCS_BLOCK ~questpack/helltest/data/d6b_1.baf~ ~questpack/helltest/data/d6b_2.baf~

Is there any way to fix this so that the helltest portion of questpack will work like its supposed to?

*** edit ***

This fix is only needed if you install the "Other Scripting Fixes" component of the fixpack v1.

fixed it myself by doing the following:

you have to edit the 4 .baf's that have the warnings and add:

Global("OpenedDoor4","AR2904",1) to the d6a_1.baf and d6b_1.baf
Global("OpenedDoor2","AR2904",1) to the d4a_1.baf and d4b_1.baf

making the block look like this for the d4a_1 and d4b_1 .baf's:

IF
	OpenState("DOOR04",TRUE)
	Global("OpenedDoor2","AR2904",1)   //this is the line you need to add
	Global("OpenedDoor4","AR2904",0)
	Global("OpenedDoor5","AR2904",0)
	Global("OpenedDoor6","AR2904",0)

and for the d6a_1 and d6b_1 .baf's:

IF
	OpenState("DOOR06",TRUE)
	Global("OpenedDoor4","AR2904",1)  //this is the line you need to add
	Global("OpenedDoor5","AR2904",0)
	Global("OpenedDoor6","AR2904",0)

then reinstall the component.

@Sim, if your not happy with this quick fix so people can continue to enjoy your questpack feel free to delete my post.

ronin

Edited by CamDawg, 16 February 2008 - 09:00 AM.

[ronin69hof]

I am going to *bump* my own post so that maybe other people that have this problem see the resolution.

And also so maybe Sim will see it and release an update (or not)

ronin

[Salk]

ronin69hof, on Nov 24 2006, 11:03 AM, said:

And also so maybe Sim will see it and release an update

ronin

It would be very very nice to see an excellent mod like Quest Pack updated but I fear Sim is so very busy in these days. Also all activity at the BG1 UB is gone missing since May/June...

[ronin69hof]

Guest, on Dec 4 2006, 01:45 AM, said:

sorry, is this incompatibility connected with the whole mod or only the AI component? if i left AI compoent out, would i still have to edit?


thanks

It only affects the Hell Trials component of the Questpack and then only if the "other scripting fixes" from the fixpack is installed.

ronin

[CamDawg]

Guest, on Jan 30 2007, 07:39 PM, said:

By re-install the component, you mean the fixpack component, or the quest pack revised hell trials component?

The Revised Hell Trials.

[Salk]

Hello!

Is this workaround still required even after release of version 2 of the Fixpack ?

If not, then the Read Me needs to be corrected accordingly.

If yes, is it because the problem can be solved only by update of the Quest Pack mod ?

Thanks!

[CamDawg]

This is a change that Quest Pack needs to make, yes. All of the incompatibilities we can address on Fixpack's end, we do.

[SimDing0]

For whatever reason, this thread seems to be a bit of an intermittent spam magnet. I'm gonna lock it and see if that stops it. I've seen this anyway, and it's fixed for QP v3.