![]() ![]() Mostly because both tend to break things a little if they aren't up here. I'm still annoyed that CE overwrites vanilla bases to do what it does however.) (I should note that CE itself is not overly to blame for the "patches for your patches" bit, as the first set of patches is usually done by other people who might not know exactly what they're doing. If you want to use it cool, but I highly recommend building the rest of your modlist first and adding CE and it's patches at the end of the process.ĬE now houses a ton of patches internally for many mods, due to the hard work of the latest team to take it on.I'd still prefer it not need to do that in the first place, but it would require a rewrite of most of the code, so the workaround is at least nice.Īlso if you are adding CE, and you have not checked that every mod you add EXPLICITLY states, via CE or the mod itself, that it is compatible Your errors will be no one's fault but yours.Īlso note that people are starting to make mods that do things CE does, without the coding issues you are not locked to CE just because you like a thing it does. It's a cool idea, I just wish it's execution was better. If running Combat Extended, it is theorized that it should go right above Third Age, patch to both goes right below both.ĬE is a compatibility mess that can more than double your modlist based on patches for mods, and then patches for those patches, alone.THEN immediately after libraries, What the Hack (this mod is a silly one that way) and then. ![]() It's also an overhaul mod, so if you are using it with a large modlist you'll probably get a lot of red errors and things breaking. Examples include Misc Core, Turret Extensions, and a few others.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |