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...]

Found a small typo in NeJAreasSounds.bat

oggdec hrot503a.ogg
oggdec hrot503b.ogg

should be:

oggdec hrot_503a.ogg
oggdec hrot_503b.ogg

To be honest, biffing doesn't really save much HD space. It merely saves override space, and improves game engine performance. Plus, it is better organized. I 100% agree that you do not want to biff your files until completed version is reached. We, the gamers, have different needs however.

I'm about 1/2 way done with the initial batch file. I'll send you/post the code when I'm done & tested. I think you'll see that this should be universal for any NeJ2 you produce. Unless you 1) combine NeJ and NeJ2 folders (unlikely), 2) add or remove tilesets (tiz files, actually--tis okay to add) from your package, 3) add or remove ogg files, or 4) add a HUUUUGE amount of any one type file to your package. #4 won't necessarily break my batch file, it will just produce a biff much larger than the others. I try to keep the size of each biff at 100MB, 150MB maximum. That's roughly the size that bioware used originally. The other three can be easily taken care of, as needed.

It also works 100% from the files that NeJ package already contains (tisunpack, oggdec). If anything, I would want to add tispack, for those two small tilesets you didn't package. And yes, I agree---that is being "over-particular" (I'll save you the American slang that describes this better, for me at least).