DavidW

Then the AI would need to be sensitive to whether this modification to Entropy Shield is present. Admittedly, it would be in keeping with SCS design principles just to assume it is, but in my judgement the advantages of doing so aren't large enough to justify the inconvenience of not just relying on the existing detect-SI-abjuration code. It gets installed as 318 on classic games. (Give me some credit for intelligence, please.) What if I just install "Smarter General AI"? Guess PRIORITY_DISPEL and the like aren't used at all in this case...? What if I just install "Initialize AI"? I know, it doesn't make any sense and shouldn't happen, but still, it's a possibility, so.. Then, in either case, it's harmless.

That one I have no information on.

1. It's being flagged as equivalent to Spell Immunity: Abjuration because from a combat AI point of view, it's very nearly equivalent, and I don't want to needlessly use up real estate in splstate.ids. But it's a bug that it's labelled with SPELL_IMMUNITY_ABJURATION, not SI_ABJURATION. I must have misremembered the name, and a downside of ds_resolve_stat is that it can't warn you if the spellstate doesn't exist. (I should probably have a must_exist variable in it.) 2. I'm not sure I understand. The point of the initialise component is (inter alia) to install the detectability system that all other AI components rely on. Why wouldn't PRIORITY_DISPEL be set here?

See my suggestion above (which possibly you missed, since I edited it in a couple of minutes after originally posting).

Can you say more about the use case you have in mind? In cases I can think of, you'd get weird behaviour if you dispelled the previous instance, e.g. if both party and enemies used a spell or if the new one and the old one only slightly overlap. That said, if you do want to do it, I think you can just use the Zone of Sweet Air opcode, but with a custom 2da in place of CLEARAIR.2da. At least, the IESDP thinks you can (I don't think I've ever tried it myself).

One-round 206? Ends in time for the next pulse, but blocks rival copies?

'ignore center' flag on the projectile?

Come to think of it, how about General Sovaalidaas? (I generally assume Throne of Bhaal is the redheaded stepchild that no-one wants to mod, so you can have free reign, but I don't want to break anyone's content gratuitously.)

If I kill Elhan at the start of Throne of Bhaal (as part of Wheels of Prophecy) am I going to spoil anyone else's content? (e.g., does he have a ToB cameo in someone's NPC mod?)

SCS ignores DR completely. (I think some earlier versions made limited concessions to it, but they caused more harm than good.)

I haven't really played with Divine Remix, but (many years ago) I played quite a lot of pen-and-paper AD&D using the sphere system. In my experience it's extremely difficult to balance it properly - the spheres are in no way equal in power, and so creating two equivalently effective cleric kits has to be done manually and is very hard to get right. There is a reason why it got entirely abandoned in third edition D&D. I think the DR mod is a pretty faithful implementation of the AD&D second edition system - and, as such, suffers from a lot of the same problems. They're probably made a bit worse by the smaller number of spells in BG(2), but the basic issue comes from the AD&D system, not from its CRPG implementation.

That's (probably) not a bug. Party-summoned fiends attack anything, including other fiends. That's vanilla-game behaviour, and SCS basically replicates it. (Baatezu will actively prioritise tanar'ri and vice versa; that's intentional.)

Interesting. The IWD description text is grabbed directly from IWDEE, but perhaps something's going wrong with it. Will see what I can do.

Can you give more details? Do you mean: fiends summoned by the party?

I'll consider, but it's unlikely to happen soon. You can do it for yourself by editing "stratagems/spell/extra_healing.tpa" in a text editor.

Almost certainly highest level.

Initial tests reveal that the game hangs on the Gorion/Sarevok cutscene, which basically goes on forever. I left it running overnight, and came back twelve hours later to find that Gorion and Sarevok had decided to take a breather and were sharing a bottle of whiskey and reminiscing.

I think the general consensus in BG2 modding circles is that 'cheating' isn't really a meaningful notion in a single-player game. Some mods, like IR, make the game easier. Others, like SCS, make it harder. Choose your own preferred playstyle and difficulty level. If using IR is making the game too easy for you, try installing SCS. If that becomes too hard, lower its difficulty. Concentrate on a playstyle that works for you.

OK: if I hardcode an initial pass through spells/items to identify damage effects, rather than relying on the CLONE_EFFECT function, I can get the loop time down from three minutes to about three seconds (with another 15 seconds to go back through the list and actually apply the effects). @subtledoctor: if you want to try it out on your install (which would be helpful), grab the copy of pf_trolls from the SCS repo.

It takes 3 minutes on an all-of-SCS, otherwise-basically-unmodded BG2EE, which, yeah, is kind of on the long side. I'll have a look at whether the loop can be optimized. (It needs to patch every fire damage effect in the game, hence the need for a loop like that.)

It's a typo in the readme. It installs fine on EET. Are you sure it wasn't offered? I've just installed it on 33.1 fine, and the relevant install code hasn't changed since 32.6.

No, Jarno is right. We're talking about original BG1 here, not BGEE. There are no 2da files controlling trap xp, that functionality isn't in the original BG1 engine.

Why not?

It would be relatively easy to fix the SCS-compatibility - but in any case, Oversight's version isn't really a restoration, it's a reimagining. Thanks for the offer of inclusion: I haven't decided what to do with it yet but I'll keep it in mind. UB is clearly at least one natural place to put it.

That should be exactly the right way to do it. Good idea - I'll try to remember to include it in the next release.