CamDawg

For an at-will (delayed or otherwise) it's op 172 paired with op 171, not 147. Op 147 adds spells to your spell book so that you can memorize them, it won't bring it back for another casting.

Yes, that's the at-will method I mentioned.

Spell/opcode-wise, not really. You can do it via scripting with a combo of RemoveSpell + AddSpecialAbility. If it doesn't need to be tied to a specific time or event, you can always make it an at-will innate like the Pocket Plane ability (spin649).

The WeiDU documentation has a lot to say on this. There's a general concept of dialogue files bit as well as a specific tutorial on CHAIN.

I suspect GROUPs bypass this mechanic. I think ask-only is based on the same code that prompts WeiDU to ask 'ask about components that are already/not installed'. Using GROUP disables those prompts, so it looks like it also does it to ask-only. If you're just looking to install, or reinstall, one component, --force-install-list works fine and is what I use for testing. --force-uninstall-list (for a selected list) or just --uninstall (for everything) work for removing it.

Yes, you got it. Take advantage of the fact that you have five script slots.

Yes, the scripts are processed in a hierarchy. In a script cycle, the engine will process the Override script looking for a true condition, then Class, Race, General and Default. So you can put your NPC-specific stuff in a dedicated script assigned to the override slot and then give a creature a general mageXX (or priestX or whatever) in the class script to handle combat and a wtasight in the default slot for safety. If it's just a combined script, SCS will ignore it in the interests of not breaking your mod since it has no way of knowing it's a lightly-modified cloned script. G3 Anniversary does this, BTW. The finale with is against multiple mages using default AI scripting (mageX scripting). It's already a bit of a fun battle, but with the SCS upgrades it becomes a pretty good challenge.

Also some free advice: do the array compare inside the copy as a patch action. As it is now, you're going to copy the area for every entry in the array. File operations are slow. E.g. COPY_EXISTING ~cm3376.are~ ~override~ READ_LONG 0x70 cont_off READ_SHORT 0x74 cont_number FOR (i = 0; i < cont_number; i += 1) BEGIN READ_ASCII (cont_off + (i * 0xc0)) cont_name PATCH_PHP_EACH cont_table AS old_name => new_name BEGIN PATCH_IF ~%cont_name%~ STRING_EQUAL_CASE ~%old_name%~ BEGIN WRITE_EVALUATED_ASCII (cont_off + (i * 0xc0)) ~%new_name%~ #32 END END END BUT_ONLY

And now both of you get to go away and do something more productive, huzzah!

Right, so if you (the general you, not a you in particular) believe you've made sincere attempts at communication and--for whatever reason you wish to believe--they didn't work, I presented a second option. Perhaps it's time to explore that instead.

Or we could make sincere attempts at communication without rancor, or move on to more productive ends.

At this point, if a mod isn't there it's because we either don't have permission or the author hasn't done it yet.

To the guest poster from yesterday: your message got flagged as spam and deleted since it was just a link, but I think it may have been legit. If you want to try and post again I'll get it past the filter.

Added Gellan edits from The Calling.

The redundant barb flags were actively added in the EEs so that they'd get picked up for the item descriptions.