Other things I've noticed Options

[horred the pl...]

I found a problem in player1.dlg. The variable VP_HrothgarInterjects is not being set from one to two in some NPC chained dialogs. I know for a fact it was not set in Dar's. This is a condition for one of your top-level blocks. What this does: with your dialog blocks as the top weight, the check never makes it past here, and none of the in-game blocks are firing. The whole scene with the Slayer change, for example. I manually set it to two and problems went away.

Also; is it really necessary to put a !Global("VP_InHlaruu","GLOBAL",1) check on the top of nearly every in-game script block inside of Baldur.bcs? I realize what this is doing for you--speeding up the execution of your additions, and to keep other events from firing in the past, while in Hlaruu(I know I'm butchering the spelling, I forget how it was )

But your (true) additions are mostly of the EXTEND_TOP variety. Why not just put a Global("VP_InHlaruu","G",1) check on your blocks? If you really don't want the rest of the BALDUR script to fire while there, you could add a single block at the end of yours:

CODE

IF
 Global("VP_InHlaruu","GLOBAL",1)
THEN
 RESPONSE #100
   NoAction()
END

Just be absolutely sure that this is set to something besides one, for any possible option, when leaving the Academy for good. Not only will this prove quicker in the long run (parsing-wise), it keeps all the in-game blocks from unnecessary adulteration. We both know what a dodgy file BALDUR.BCS is already, without any assistance.

[horred the pl...]

Well, this is how I picture it.

{All your NeJ blocks}
--These all have condition: Global("VP_InHlaruu","GLOBAL",1) at the top of their block

{Here go any blocks you might want to execute during Hlarru as well, but could happen anywhere}
--These you leave as-is; no Hlaruu check

{Then, finally, a "catch block". This shuts down the entire remaining Baldur.bcs, while your Hlaruu Global is at 1}

CODE

IF
Global("VP_InHlaruu","GLOBAL",1)
THEN
RESPONSE #100
 NoAction()//Alternatively, you can use the infamous RESPONSE #100~END approach here as well
END

{And below all this is the rest of Baldur.bcs, as-is}


And there it is. Your script is all that is being dealt with while your mod is running, you don't have to add an extra condition to all the other blocks. Less file-editting, less in-game content messed with--always good on both accounts. BW's blocks run faster, yours run faster. Win vs. win...

Oh, BTW--I saw a strange bug with the Yeti Pelt Bag. It will not hold books (I suppose Snow Barbarians don't read much ---but they might come in handy for firestarting. ). But the weird one was: it would not store the skeletal torso from the kangaxx quest. The arms and legs stuffed in just fine. ???

This post has been edited by horred the plague: Jan 19 2006, 07:03 AM