Notso

The readme should be fixed then. Currently, the readme packaged with v4beta18 reads: This wording implies that it is the optional component that changes Deva and Planetar weapons. Unless I'm misunderstanding you, and there are other changes to the summoning spells in the core component (aside from these weapon changes).

Hm okay. Anyway, when I install: EET > SRR (without Mirror Image Fix and Spell Deflection blocks AoE) > EET_Tweaks > EET_end > SCS I no longer get any .CRE files with warnings. I guess the Mirror Image fix and Spell Deflection tweak are interacting poorly with Holy Smite? And SCS is assigning those spells to some mages and that's why I get warnings? I don't really understand why Bartimeaus isn't getting the same issues when he installs the same mods though. Edit: FWIW I don't believe this to be an SRR-specific problem. I was seeing these warnings in SCS installs before I switched from SR to SRR.

I tried doing an even more minimal install without any of the core EET components (so no EET_setup or EET_end, only EET_Tweaks), and this time I get one warning with SCS' Initialise AI components: WARNING: no effects altered on sppr313.spl I don't know if this warning is important, or what this file is, but I checked which mods were altering it: Mods affecting SPPR313.SPL: 00000: /* created or unbiffed */ ~SPELL_REV/SETUP-SPELL_REV.TP2~ 0 0 // Spell Revisionsv4 Beta 18 (Revised v1.3.900) 00001: ~SPELL_REV/SETUP-SPELL_REV.TP2~ 0 20 // Mirror Image Fixv4 Beta 18 (Revised v1.3.900) 00002: ~SPELL_REV/SETUP-SPELL_REV.TP2~ 0 55 // Spell Deflection blocks AoE spellsv4 Beta 18 (Revised v1.3.900) 00003: ~STRATAGEMS/SETUP-STRATAGEMS.TP2~ 0 5900 // Initialise AI components (required for all tactical and AI components)34.3 When I installed SRR without Mirror Image Fix and Spell Deflection blocks AoE, this warning went away.

The more I look into this the more confused I get. I did a minimal install with just EET > SRR > EET_Tweaks > EET_end > SCS, and I still get many of the same type of warning, but they are for totally different .CRE files (except for DW#LICH1.CRE which gets a warning this time too).

I did see the warning (it was why I ended up using terminal, otherwise I would have ended up assuming merge did what I expected it to), just thought I'd post the solution for macOS that I found, as it'd save people having to ask and wait for a reply, and save you having to make an archive for them every time

Thanks, that's reassuring. I haven't modded these games since the late-2000s, so my memory of how much of a pain it can be to get everything working is very hazy (though they are starting to return to me ). I will continue with my modded game as-is for now Could it be that there's a spell to all these .CRE files have in common which is causing the issue, but which is not widely used by other enemies?

Ah, thanks. I get this now (and it's the same three mods for all the other files that got a warning): [weidu] WeiDU version 24900 Mods affecting BAZEYE01.CRE: 00000: /* created or unbiffed */ ~SPELL_REV/SETUP-SPELL_REV.TP2~ 0 0 // Spell Revisionsv4 Beta 18 (Revised v1.3.900) 00001: ~EET_TWEAKS/EET_TWEAKS.TP2~ 0 2052 // XP for killing creaturesDecrease to 50%1.12 00002: ~STRATAGEMS/SETUP-STRATAGEMS.TP2~ 0 5900 // Initialise AI components (required for all tactical and AI components)34.3 00003: ~STRATAGEMS/SETUP-STRATAGEMS.TP2~ 0 6000 // Smarter general AI34.3 00004: ~STRATAGEMS/SETUP-STRATAGEMS.TP2~ 0 6030 // Smarter Mages34.3 00005: ~STRATAGEMS/SETUP-STRATAGEMS.TP2~ 0 6100 // Potions for NPCs34.3

Thanks for the reply. This is exactly the kind of shortcut I was hoping for. When I search my game directory for files with the name (for example) BAZEYE01.CRE, I see that there are multiple. I tried the command on all of them and according to WeiDU no mods were affecting it, for example the one in the override folder: [weidu] WeiDU version 24900 Mods affecting /OVERRIDE/BAZEYE01.CRE: The others are located in /weidu-external/backup/stratagems/XXXX/ or /EET_Tweaks/backup/XXXX/ and gave the same empty output. As a side note, I would be rather surprised if it were the 3.5 mods causing the problem. They are quite small in scope and edit very few files. Edit: In fact, it seems like any file I test in /override/ has an empty change log. Am I doing something stupid?

Sorry if this is the wrong subforum to ask for help on this. I have a megamod EET install (install order below, WeiDU.log attached for completeness) and when I install SCS I get a lot of warnings like the one below: List of .CRE files that had the same warning: I'm kind of hoping I've just missed a well-known incompatibility, since it seems like the easiest way to determine which mods are causing this is to do 30 installations, each with a single mod removed. I plan to start doing this in the meanwhile, but I do hope to be saved by someone more knowledgable Mods installed: WeiDU.log

I have done another reinstall with my full mod list (though it's slightly pared down compared to what I posted earlier), and have noticed that it's not just HLLAYEN.CRE that is getting the warning, but also DW#LICH1.CRE and others, so I doubt it's Cowled Menace to blame. I will move my request to help find the cause to the SCS subforum.

Just thought I'd post this here: for macOS users, do not use Finder to merge the folders. MacOS' "merge" feature (which can be accessed by holding Option when the dialogue box asking if you want to replace the folder in the destination with the new folder) does not merge subfolders. Instead, we have to use the following command in terminal (press Cmd+Space, then search for "Terminal"): cp -R /path/to/item_revisions_revised/item_rev/* /path/to/item_revisions/item_rev This should, as far as I can tell, merge the folders in the same way File Explorer does in Windows (overwriting items in the destination folder with incoming files if they share a name). If, like me, you find typing out entire paths to directories tedious, drag IRR's item_rev folder into the terminal window once you've typed "cp -R", remember to add "/*" and a space to the end of the path, then drag IR's item_rev folder into the terminal window.

Well that explains that. Weird mod to be incompatible with, though. Edit: Thanks a lot @Alywena, got it working Didn't even know that IRR existed!

Spell Revisions' Celestial component is optional, so shouldn't this mod work with the rest of Spell Revisions if one chooses not to install the Celestial component? From Spell Revisions' readme: Spell Revisions can be installed after PnP Celestials (though I can't confirm if it actually works in game). Weirdly however, when I try to install PnP Celestials after Spell Revisions, PnP Celestials throws warnings (log attached). When I tried the latter order in an installation with dozens of mods, the install of PnP Celestials failed completely (log also attached). WeiDU-warnings.log WeiDU-failed.log

Note that it's not an error, just a warning. It popped up during the installation of SCS' mage component, but didn't cause the installation to fail, so is easy to miss (and the component was still listed as successfully installed). Unfortunately, I no longer have the WeiDU.log of the installation where I'm sure I saw the warning, it was just one of many installations I've been playing with over the last week. I've done a quick installation of just EET, The Cowled Menace and SCS' mage component, and attached the WeiDU.log, and I'm not even sure the installation this time threw the warning as the terminal output is so fast. I used the (as far as I can tell) best practice install order; EET_setup, Cowled Menace, EET_end, SCS. I'm on macOS Monterrey with an M1 chip, using MWL v7, if that matters. WeiDU.log

Not sure if this will lead to an issue in game but SCS is throwing a warning during installation about not knowing how to patch HLLAYENE.CRE. This is on EET, SCS v34.3 and Cowled Menace v1.0.1. Unless some other mod from the (admittedly long) list below is changing Layene.