31 replies to this topic

[Beleg33]

I don't know why I didn't think of it sooner but

Spoiler

!Kit(LastTalkedToBy(Myself),WILDMAGE)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_ABJURER)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_CONJURER)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_DIVINER)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_ENCHANTER)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_ILLUSIONIST)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_INVOKER)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_NECROMANCER)
!Kit(LastTalkedToBy(Myself),MAGESCHOOL_TRANSMUTER)

works just as good. What do you think A64?

[Ascension64]

I was trying to avoid the "everything else" trigger, but that might have to do if restricting checks too much causes incompatibility with Refinements.

[Jarno Mikkola]

Was this ever fixed, I wonder? I see no new release of BGT even though it has been months.

Well, the fix usually involved not installing mods that cheese the few files that are needed. The BG2 Tweak pack component is redone in the current v9.xx version which will make the component compatible with BGT... it's been a long time that the problem has been known, and it's in the compatibility notes.

As for the 0x0000 kits, the fix was reported the bigg and should be in the fix phase on the mods that it affects... and added to the BWS fixpack...

Edited by Jarno Mikkola, 24 November 2012 - 08:18 AM.

[Jarno Mikkola]

I started this thread some time back and the culprit turned out to be that Refinements changed around a few things, confusing BGT. I had expected (since it's a complete game-breaker) that it would be fixed by now, but I see no update on BGT, so therefore i ask what happened with this

Well, it turned out that the Refinements mod is correct... and the Kit.ids file should be changed to be 0x4000 0000 and 0x8000 0000 for barbarian and Wildmage, like the Refinements mod does... and if the other mods do not botch this, the BGT should work with that, as it should takes just the correct number, not the false ones.

[Lollorian]

- Aurora mod used to mess this up, but is fixed now or in BWP Fixpack?
- Level1npcs used to mess this up but is fixed now or in BWP Fixpack?

Neither fixed in the mods nor included in the BWPFixpack yet The latter would probably happen earlier though whenever this batch of files gets included into the BWPFixpack

Your best bet would be to open your KIT.IDS using NearInfinity (it opens like a normal text editor) and change whatever BARBARIAN and WILDMAGE values you have to 0x40000000 BARBARIAN and 0x80000000 WILDMAGE respectively

PS: Make sure you're using ToBEx

Edited by Lollorian, 24 November 2012 - 07:37 PM.

[Lollorian]

Now that I've read the entire thread, I'm kinda under the notion that the problem you have and the thing Jarno linked to are unrelated

Can you just check your KIT.IDS for what value magetw has please? Better yet, export your KIT.IDS using NearInfinity or DLTCEP and attach it somewhere

[Lollorian]

Jarno wasn't off the thread as it turns out His link was probably related to the entirely different issue you pointed out here

As for the Refinements-BGT Start Spell borkage, Beleg33's solution would work awesome I've also replaced all instances of:

Kit(LastTalkedToBy(), 0)

with

Kit(LastTalkedToBy(), WILDMAGE)

So that the ToBEx-enabled expanded Kits can be used (if ToBEx is installed ofcourse Otherwise, WILDMAGE would still default to 0 )

Attached Files

•  BGT_Refinements_Beleg33_mage_spell_selection_fubar.7z   2.95K   141 downloads

Edited by Lollorian, 27 November 2012 - 08:56 PM.