
Notice that the package.mft file is in the "\Update\Patch" folder, which didn't even exist for the original vanilla game. They are now on their 6th expansion, which makes it version 7. For example, the "vanilla" version of World of Warcraft was version 1. Then patch 1 makes it version 2, and so on, until patch 11 makes it version 12. This is because the version the game shipped with is version 1. In my experience "Force Rescan" is only really needed if more DLC are added after first running the Mod Manager. The number will keep incrementing, if not adjusted back, when mods are added again.ī This is the second thing to try, after first repairing the Vanilla game with Origin, any mods will remain untouched, this usually fixes these new game loading errors. Mods are usually Patch 13, and if removed game can complain the save is for a "Newer version" of the game, and the fix is call Vanilla same version as the mods were, so usually 13, but check the mods Package.mft File, to be sure. That's not correct, it's actually update 11, which is also, confusingly called Patch 12, as the Package.mft file, inside the Vanilla Patch folder says Name patchĬonsequently the Patch_ModManagerMerge folders, Package.mft file, becomes Patch 13, as the "last update", and how it now works as a separate patch. Did you tick the "Force Rescan" option box?Ī.

Just to be clear, there is no such thing as Patch 12.
