Smarter general AI installation crashes at ARNSWR01.CRE. Iwdification and its "add high quality items" screws up the files.

[bearcattony00]

The high quality items of iwdification v5 apparently "doesn't exist" according to SCS when it hits ARNSWR01.CRE.

[jmerry]

It's not the high quality items that are the issue.

That IWDification component is fundamentally about randomization. Various creatures get their weapons replaced by random tokens, which evaluate to real weapons once that instance of the creature loads in. For example, gnolls get their halberds replaced by a token representing 60% halberd, 20% two-handed axe, and 20% long sword. With an optional 1/8 chance of upgrading to high quality, and those two-handed axes become halberds if you don't have that other component installed.

Needless to say, this does not play well with the SCS general AI routines that try to determine what sort of weapons creatures are using so their proficiencies can be redone.

Given that this IWDification component also redoes proficiencies for the affected creatures (giving them appropriate proficiencies in all weapons they might have), I'd have to recommend that it come after SCS in their current form.

Recommended change for SCS: better error handling. If you can't figure out what sort of weapon a creature is using (such as when it's actually a token), skip any proficiency adjustment.

[DavidW]

It's a little subtler than that. SCS does systematically allow for random-item tokens from IWDification (and indeed from IWD proper), assigning virtual proficiencies to them that resolve into multiple proficiency assignments. 

Checking over that code, I can find one bug in it: a typo meant that the half-ogre weapon token wasn't being processed properly. I don't think that is likely to be the problem, though. I don't know what 'ARNSWR01.CRE' is, since I can't find it in any of the vanilla games (typo for ARNWAR01.CRE, maybe?) but in any case 'Improved General AI' is installing cleanly over IWDification's randomizer when I try it. So I'm not sure what the problem is: @bearcattony00, maybe you could post the exact error message and/or stratagems.debug?

(I do agree error handling could be slightly better here, though it should be throwing a WARNING - I don't want bugs like this to be silent.)