Usage1 can be either the amount of available charges for the 1st extended header (for items with charges), or number of items in a stack (for stackable items). It's similar to how the CLUAConsole:CreateItem() command works - using CLUAConsole:CreateItem("wand02",10,0,0) should create you Wand of Fear with 10 charges, while CLUAConsole:CreateItem("misc07",10,0,0) will create a stack of 10 gold pieces.

You get wrong Jaheira (BG1 one not BG2 one).

Problem with Jaheira when she's returning from Harpers (before Galvarey). You get wrong Jaheira (BG1 one not BG2 one). So all local variables, experience and so on are gone (causes stuttering because she tries to initiate some? dialogue).
 
This problem happens if you don't have Jaheira in party when transition from BG1 to BG2. Script at AR0602.BCS adds JAHEIR7.CRE, JAHEIR8.CRE, JAHEIR11.CRE or JAHEIR12.CRE (depending on CHARNAMEs level) to GAM-file.

I don't know how this can be fixed. Maybe importing Jaheira from BG1 even if she's not in party or deleting BG1 Jaheira from GAM-file.

EE only uses new formats for GUI files (+worldmap mos I think) though. And it will work fine with v1 bam and mos files too. So unless you intend to modify the new gui, there really is no reason to wait. Unless I'm missing something.

The following TP2 code will copy all V2 files in the game into "BAMBATCH/V2" subfolder if you want to check out a complete list of what's "uneditable":

COPY_EXISTING_REGEXP GLOB ~.*\.bam~ ~override~
	READ_ASCII 0x4 ~version~ (2)
	PATCH_IF ~%version%~ STRING_EQUAL_CASE ~V2~ BEGIN
		INNER_ACTION BEGIN		
		COPY_EXISTING ~%SOURCE_FILE%~ ~bambatch/v2~
		END
	END
BUT_ONLY

COPY_EXISTING_REGEXP GLOB ~.*\.mos~ ~override~
	READ_ASCII 0x4 ~version~ (2)
	PATCH_IF ~%version%~ STRING_EQUAL_CASE ~V2~ BEGIN
		INNER_ACTION BEGIN
		COPY_EXISTING ~%SOURCE_FILE%~ ~bambatch/v2~
		END
	END
BUT_ONLY

so where one would find updated tools?

http://sourceforge.n...es/DLTCEP 7.6g/

Not a modding suite per se, but a game files editor (which is enough to do almost anything you'd want, including a total conversion of the whole game). Yes, it should be compatible with both EEs.

Area Tilesets use the PVR format (which is uneditable ATM) as well. BGII:EE also introduced 32-bit bitmap files which is a new format to the Infinity Engine and which NearInfinity can't handle yet (although DLTCEP might can).

Yes, but old TIS tilesets are still accepted and will work just as well (so there's no need to wait for new tools to create a new area for your modding needs). New tilesets can currently be loaded in latest DLTCEP (use "Load MOS..." option) and exported as bitmaps/TIS, although not without problems (resulting images/tilesets have visible graphical glitches aka "tears" at tile borders).

Item description images is the only serious problem I've hit in modding BG2EE - old BAMs aren't displayed at the moment, but as I understand this is going to be fixed in a future patch.

nope. I cannot open the new audio files in ANY way.

They're simple OGG files. Extract them from biffs with weidu (weidu.exe --biff-get whatever.wav), change extension to .ogg and play with any decent music player (foobar2000, winamp, windows media player, etc.) to see what's in them.

DLTCEP menu option Sound -> WAVC to WAV will also correctly extract and convert them to old-fashioned WAVs which will be recognized by non-EE games.

The One Drizzt is very unlikely to be compatible unless the author updates it, not much I can do about that - there are simply too many changes.

Also in v1.41 tp2 file of this mod, there is an error:

COPY ~THEONEDRIZZT/F_CATTIB.CRE~ ~override~
  SAY NAME1 @28
  SAY NAME2 @28
  SAY INITIAL_MEETING @29
  SAY BATTLE_CRY1 @30
  SAY DAMAGE @31
  SAY DYING @32
  SAY SELECT_COMMON1 @33
  SAY SELECT_COMMON2 @29
  SAY DIALOG_HOSTILE @34
  SAY BIO @35
  WRITE_ASCII 0x260 ~_TASIGHT~ #8
  WRITE_ASCII 0x268 ~_DPLAYER~ #8
  WRITE_ASCII 0x4a4 ~_CHAN07~ #8
  WRITE_ASCII 0x4b8 ~_BRAC04~ #8
  WRITE_ASCII 0x508 ~_POTN08~ #8

Those are Tutu item and script references, though the One Drizzt mod as far as I understand is BGT only (otherwise how it can make Drizzt continuous through RoT). Looks like the author copied these lines from Drizzt Saga Tutu install branch, not realizing there were two branches for BGT and Tutu.

Also I would request that you would make the biff-ing made in the "Areas.bat" file optional, so the BWInstall pack doesn't need to overwrite it. You should be able to ask Lollorian the exact details on that.

More details would be good, so far I can't find any place in BW installpack's bat files that overwrites area biffing in Drizzt Saga - only a small patch made to Sounds.bat to remove pausing the installation. Or are you referring to the fact that biffs created from .bat files cannot be later uninstalled with weidu and have to be deinstalled manually?

There's a folder with fixes included with the BWP Fixpack,
And the Russian Textpack includes a translation.

Thanks, I'll take a look at those.

Drizzt Saga mod is currently undergoing an update for BGEE compatibility, as well as repairing various existing problems, bugs and compatibility issues along the way.

This topic is a request for information on existing fixes and known problems for the current versions of this mod in a generic mega-mod / BWS setup.

I'm aware of these files currently hosted at SHS:

- Drizzt Saga WM (7 or later) patch (changes: area location coordinates on worldmap)

- Drizzt Saga for BGT/Tutu v2 (changes: Drizzt joins after Durlag's Tower is completed)

I'm planning to include these changes in the upcoming v3, so these files will no longer be necessary (v2 adaptation will be included as an optional component).

If there are any other existing fixes applied to Drizzt Saga in the current BWS / BWP setup, please let me know here so I can include them in the new version as well. Any outstanding issues and bug reports can be posted here too. A fair amount of problems I have already found and fixed, but if it's something new I'll investigate. Note that I can't change the mod's quest and dialog content since I'm not the original author (props to flysoup for creating it), I'm just upkeeping the technical side.

Cheers.

I have BG2EE installed and I can confirm SW2H21.ITM is definitely there, so the problem is somewhere else. Which folder are you running the install .exe from? It should be the same folder which contains the game's CHITIN.KEY file.

I assumed BG2EE, should've read more carefully. I didn't think it could be installed on anything except BG2[EE] or BG2+BGT.

Note that it's not just "buffs" - the consequences depend on the script and the creature, and in this case, Firebeard could cast for instance Melf's Acid Arrow. Which at level 1 in Candlekeep could, well, kill you. Not to mention such things are immersion-breaking.

Erhm, if that's so then who ever coded the MAA's casting script was unconsciously cheating, after all it's target needs first of all be visible to the caster--- as the LastSeenBy() by itself should never be used as the target ... but with an inner function, such as LastSeenBy(Myself) ---during the targeting phase. 
 

When I finish my second job of the day, after this job--if I'm not comatose, I'll dust off my copy and fire up BGT and give this a try. Forgive my skepticism but I need to see it for myself. It's very odd that a script that has been stable for 11 years suddenly acts up, when nobody has touched it.

Thanks, and I'm glad it solved your immediate problem. There's a larger problem with doing this on a grand scale however. The action NoAction() causes all script actions to end for that parsing round. So, no scripts after this, in the entire 5 slots available for creatures, will fire either. This in turn can break far more serious things, than cause something simple like casting a buff spell. To fix this exclusively would require special scripting for Firebeard, not a generic fix that would break dozens of other situations. Honestly, it's just a buff that happens to be visible. For the harm it causes (next to none), I'm not really sure it's worth the time and effort it would take to fix this on a grand scale. It would be easier to add an exclusion for Firebeard, let him keep his vanilla scripts, and be done with it.

IF
  OnCreation()
  OR(2)
  !Allegiance(Myself,EVILCUTOFF)
  !Detect([GOODCUTOFF])
THEN
  RESPONSE #100
    NoAction()
END

IF
  OR(2)
  !Allegiance(Myself,EVILCUTOFF)
  !Detect([GOODCUTOFF])
THEN
  RESPONSE #100    
END

IF
  OR(2)
  !Allegiance(Myself,EVILCUTOFF)
  !Detect([GOODCUTOFF])
THEN
  RESPONSE #100
END

IF
  OR(2)
  !Allegiance(Myself,EVILCUTOFF)
  !Detect([GOODCUTOFF])
THEN
  RESPONSE #100
    NoAction()
END

Use of continue in a script block will cause the parser to treater subsequent empty response blocks as though they contained a Continue() command - this parsing can be stopped by including a NoAction() in the empty response block.

However, @pro5 I greatly appreciate your diligence in reporting, your support and your code offer.

~BG2FIXPACK/SETUP-BG2FIXPACK.TP2~ #0 #0 // BG2 Fixpack - Core Fixes: v10
~BG2FIXPACK/SETUP-BG2FIXPACK.TP2~ #0 #1000 // BG2 Fixpack - Game Text Update -> GTU Light (by Wisp): v10
~SETUP-BGT.TP2~ #0 #0 // Baldur's Gate Trilogy - Core: 1.18 (28 Apr 13)
~SETUP-BGTMUSIC.TP2~ #0 #2 // Baldur's Gate Trilogy - Music -> Full Baldur's Gate/Shadows of Amn/Throne of Bhaal Music (WARNING: patches BGMain.exe)
~BP/SETUP-BP.TP2~ #0 #0 // Big Picture, core component (required for most subcomponents): v181-b4611
~BP/SETUP-BP.TP2~ #0 #10 // Patching all the existing innate spells, setting level to one.....: v181-b4611
~BP/SETUP-BP.TP2~ #0 #500 // Generic Mages: v181-b4611
~BP/SETUP-BP.TP2~ #0 #150 // Generic Creature & Script Processing: v181-b4611

So, on a whim, I assigned Firebeard the vanilla script equivalents of the BP scripts--mage6 and wtasight. Did you try this test? I had the same results as with the BP scripts. Firebeard still attacked. So, obviously there's something going on, but BP is innocent I say. I don't see anything in his CRE file to cause this either. Not sure what exactly to expect, but if you installed just bp and bgt like I did, and BP is not to blame, nor the vanilla game, what's left? tob-ex and bgt. I don't recall ever seeing this in the early days of bgt, before there was a tob-ex, so tob-ex is my suspect.

We eliminated all but one theory: the new GoG.com installation broke this function. The original vanilla scripts never use it, so maybe they totally overlooked its usefulness when recompiling the engine.

<<<<<<<< ...\p5-inlined\src.baf
IF
  OR(2)
	!Allegiance(Myself,EVILCUTOFF)
	!Detect([GOODCUTOFF])
THEN
  RESPONSE #100
END
>>>>>>>>

<<<<<<<< ...\p5-inlined\dest.baf
IF
    OR(2)
        !Allegiance(Myself,EVILCUTOFF)
        !Detect([GOODCUTOFF])
    Global("TOB_SUXX","LOCALS",0)
THEN
    RESPONSE #100
        SetGlobal("TOB_SUXX","LOCALS",1)
END

IF
    OR(2)
        !Allegiance(Myself,EVILCUTOFF)
        !Detect([GOODCUTOFF])
    Global("TOB_SUXX","LOCALS",1)
THEN
    RESPONSE #100
END
>>>>>>>>

SILENT
COPY_EXISTING_REGEXP GLOB ~BP.*\.bcs~ ~override~
	R_B_B ~...\p5-inlined\src.baf~ ~...\p5-inlined\dest.baf~
BUT_ONLY
VERBOSE

REQUIRE_PREDICATE MOD_IS_INSTALLED ~SETUP-DRIZZTSAGA.TP2~ ~0~ OR MOD_IS_INSTALLED ~SETUP-DRIZZTSAGA.TP2~ ~1~ ~Drizztsaga is not installed~

Don't work, tavern music start on GNoll Stronghold and Bandit Camp, and Imoen have wrong soundset.

Are you trying this on an existing save, by any chance? The changed TP2 from above won't affect areas already visited in your saved game. Imoen is not touched by BGTMusic at all, but messed up soundsets and strrefs are a common problem after loading a save made with a different mod setup/install order than the current one.

I think the easiest solution would be to make the .exe from the archive read-only. Right-click the .exe, set the read-only file attribute, click OK. It should fail to auto-update then. EDIT: Scratch that - testing shows WeiDU has no respect for that flag whatsoever, and updates anyway.

And I don't think this requires any other drastic action such as changing WeiDU ADD_MUSIC behavior - the change in v233 was logical and is actually useful, making it easier for "normal" mods to add their music into the game without creating duplicate entries in the .2da if the mus file already exists (i.e. added by another mod). Some other existing mods, or mods currently in development may rely on that behavior, and changing it could break more than just BGTMusic.

It is not a normal situation for a mod to add duplicate entries for the same MUS file to the songlist, in fact it's a very strange solution, I guess it was just chosen as a convenient shortcut. The ARE files should have been changed to refer to the same existing 2da entry instead.

Keep in mind WeiDU will auto-update itself if you run the old version .exe from same folder where you also have more recent versions.