MadGenuis

Huh, right you are, though in effect it appears to make very little difference. Even moving them to the right place, it still produces the 1220 lines of errors, just with a slightly different path when tracking the errors.

Despite having never worked on anything related to CaptivityEvents before, I decided to have a look at this and see if I could maybe figure out an easy way to get it working again, since I know it has worked in the past. Many of its functional files are just neatly formatted .xml, after all, and should be fairly easy to read and understand. I had a look at a few of its files, determined that I had no way of knowing which tags were and were not valid without documentation to refer to, and so I figured I would just install it, fire up Bannerlord and see if I could identify at least one event that didn't work so I at least had an idea of where to look. Immediately on loading I noticed an error message in the log saying that BCCaptor_Text.xml failed to load and that CaptivityEvents had generated an error log, which I was immediately delighted with since this meant I would have errors to work from. Unfortunately the error log turned out to be 1220 lines long, with all but 59 of those being due to BC Captor (those last 59 were from zCEDefaults), but are the same type of errors as from BC Captor. Going through the BC Captor files and trying to manually fix all these errors would be unbelievably painful and liable to break it even more, and I don't currently have the necessary familiarity with the CaptivityEvents engine to figure out why it no longer supports what has broken, so I will put my own efforts on hold for now. I will leave the contents of my LoadingFailedXML.txt here in case someone more knowledgeable can more readily do something about it: EDIT: Actually, given that these errors occur with zCEDefaults as well and refer to elements like "base" not being declared in CEEventsModal, the issue may be with CaptivityEvents itself rather than BC Captor. Just a thought.