Scary Wrye Bash error for a mod.

[Noobsayer]

So alteration armor spells drive me bonkers. The magic overhaul I use makes it better, but it's incompatible with stuff I've found that makes the mage armor spells toggles. I'd rather not add another scripted thing like Smart Cast to autocast it for me, so I turned to ...

 

DUN DUN DUNNNNN

 

.. a cheat ring. Specifically, the Mage Armor only one.

 

Unfortunately when I went to build a bashed patch after adding it, Wrye Bash gave me a scary error. D: Is this gonna bork my game? I don't understand at all what it means.

 

[EssArrBee]

Remove it when generate a bashed patch.

[Noobsayer]

OK. So it's not some wtfGAMEBREAKING bug then. I've gotten too far in this playthrough to wanna bork it. :)

[EssArrBee]

If you have gotten that far into the playthrough STOP messing with the load order. Don't update mods, don't add new ones, don't do anything. Just play until you are ready to stop this playthrough and then update or change everything.

 

Also, no it isn't game breaking, just that Bashed Patch isn't developed fully for Skyrim.

[Noobsayer]

I don't add major things, but normally adding a single ring wouldn't be a big deal partway through a playthrough.

 

Anyway, I usually set up a mod list, do a lot of testing with everything running, then start a new game and gradually add them in as I play as an extra stability safety net. I admit though, this was a "if I have to cast Ironflesh one more time I'm going to scream" thing. I don't usually play armorless mages so I had no idea how effing annoying it would get.