If the next word starts with a vowel sound then use 'an' prior

Thanks. That should be possible to keep in mind. Updated.

Hey, now wait a minute, that "F" stands for Fran's, you wouldn't say "an Fran's" would you??

OK, based on popular demand I've updated that quick guide a bit. Thanks for the suggestions. This might hopefully be slightly less confusing:



EDIT: Or is it an FCOM setup? I'm always a bit unsure on the rules regarding that..

Hey, now wait a minute, that "F" stands for Fran's, you wouldn't say "an Fran's" would you??

That's not how it works; it relates to vocalised sounds, not the written alphabet. If the article is to be followed by a vowel sound, 'an' is used, otherwise 'a' is used. FCOM, whether you pronounce it 'eff-com' or 'eff see oh em', starts with a vowel sound, therefore it's 'an FCOM setup'. If you pronounced it 'fuh-com', it would be 'a FCOM setup'.

...and EpF, above this post, is right.

How many of you have ever said FCOM out loud? If so it means you're lucky enough to know someone personally who mods oblivion.
How many of you have ever said FCOM out loud and then regretted it because the explanation of what it actually is just makes you sound like an uber geek?
So we're deciding on an FCOM setup - brilliant!

Notes:
- How to add a bash tag to a mod: highlight it in the Mod window > right-click in the Bash Tags window in the lower right > choose appropriate tag.
- "All FCOM mods" means select FCOM, Frans, OOO, MMM, WarCry in that patch section but take note of exceptions.

EDIT: Or is it an FCOM setup? I'm always a bit unsure on the rules regarding that..

Arkngt, users should not have to manually add tags to Mods now, if they right click on bash tag window and select Automatic Tagging the tags should get added has needed to all FCOM ..If they are using Bash 2.78 or Higher. Has I included Bash Tags for nearly all overhaul in taglist.txt that Bash uses..If using BOSS has well that does the same if automatic tagging is turned on. I will make sure the 2.86 release of bash has the taglist.txt updated with new tags has well.

So you're saying that the "Tag FCOM_Convergence.esp with ForceAIPackages." etc. parts of the Quick Guide can be removed? That it works automatically with 285? In that case the guide needs to be updated. I thought it was updated for 285. As long as those manual tags are needed I think a quick guide on how to do it is in order,

Bash 285 taglist.txt is still using older version of taglist.xt. So it does not have updated tags in it like forceaipackages, etc for the Overhaul yet.

So users will still need to tag FCOM_Convergence.esp with ForceAipackages Manually until then.

All other tags should get added automatically to them if using automatic tagging or boss.

OK, so I'll remove "Tag Oscuro's_Oblivion_Overhaul.esm and Oscuro's_Oblivion_Overhaul.esp with graphics." for Import Graphics then. I'll keep the note on how to do it as long as manual tagging is needed.

:whisper:

If you remove graphics tag from OOO

then Warcry will overwrite OOO potions with It Varations instead

graphics tag is needed on OOO to prevent this

What version of Wrye Bash are you using and what options are you choosing for your bashed patch? I could be wrong, but messed up AI with such a small load order of widely used mods sounds like a bashed patch issue to me.

gothemasticator

Now that's what I call a core FCOM set up. I have to say that I'm stumped when it comes to your issue, though. It shouldn't be AI overload with that mod list and your rig. Which seems to indicate something else going on - perhaps faulty installs or the Bashed Patch, as gothemasticator said. But basically I have no idea what it might be.

EDIT: If I understand it correctly, you are starting from a save before exiting the sewers for the first time? That should be ideal as you shouldn't have to worry about waiting for a respawn. But that is my question otherwise - you are waiting for a respawn when trying out your different mod lists, right?

EDIT 2: Have you tried with just Oblivion and SI to ensure that the vanilla game is working fine?

I'm trying to do a FCOM/OOO patch to "Tales from Elsweyr Anequina" and I will PM it to Corepc.

I think I've found the problem. It's in OOO. I tested without any plugins bar SI; issue gone. Installed UOP; issue gone. Installed OOO; issue returned. I didn't use the bashed patch for either of those tests. I'm redownloading OOO now, just to make sure I'm using an issue-free version. I won't use the pyffied meshes, and I'll install without using BAIN. If that goes ok, I'll update my BAIN package and use the bashed patch. At that point I'll let you know what my bashed patch settings are. ...

Anyway, hopefully this will sort it out...

Yes, I hope it works out. Both OOO 1.33 and 1.34 beta5 are very stable overall - in fact I can't recall this issue being reported for OOO in itself.

OK, based on popular demand I've updated that quick guide a bit. Thanks for the suggestions. This might hopefully be slightly less confusing:



EDIT: Or is it an FCOM setup? I'm always a bit unsure on the rules regarding that..

Hello,

Should I also tick FCOM and OOO on Import Spells?

Thanks!

Dagnabit! The problem is back! WTF?! Any suggestions would be very welcome!

So you get totally weirdly acting enemy NPC's with a freshly installed patched vanilla game with only OOO 1.34 beta5 installed? Like:

Oblivion.esm
OOO.esm
OOO.esp

Yes, I do! Though I have SI installed too. At this point I think I'll start from scratch, with no OBSE and just the vanilla patch - no SI - and then add OOO again and check. What do you think?

Frankly, I have no idea what might be causing it. As said, I can't even recall it being reported for OOO - and I've played it since 1.31c IIRC. What I do when I start over is I start from scratch (i.e. complete uninstall/delete), install the game, patch it, check, install OOO, check, install core FCOM, check - and go from there.

Yes, I do! Though I have SI installed too. At this point I think I'll start from scratch, with no OBSE and just the vanilla patch - no SI - and then add OOO again and check. What do you think?