For anyone struggling to get this working, make sure the winrar archive you made for your merge includes the merge folder with the JSON files that zmerge produced alongside the esp and other files. Mergemapper uses this to function. You can also just drop the merge file into the data folder, or include it in your archive.
I hadn't included these in my zip file, so MergeMapper wasn't functioning.
As I understand it, this enables us to merge SPID mods together so they still work. I tried merging an SPID mod as a test but it stopped working after merged. I later realized that particular mod relies on Keyword item distributor too, and that's probably why it isn't working. Or does mergemapper support KID, or will it in the future?
It's the other way around I think. KID has to add support for MergeMapper. The basic FormID redirection should work with KID, but I'm not sure if filtering by only plugin in KID has MergeMapper integration. If so it would depend on the ini whether everything would still work when zMerged. What mod isn't working for you?
it's this mod https://www.nexusmods.com/skyrimspecialedition/mods/88349
I believe it's assigning the keyword to all the armors from another esp. I imagine I can just rewrite the KID script to point to my merged esp and it should work. I'm reverse engineering this mod and others to get an idea of how I might make my own.
Keyword = Minidress|Armor|Tiwa44 Minidresses Standalone SSE.esp gives the keyword "Minidress" to all armor items from the mod "Tiwa44 Minidresses Standalone SSE.esp". It's safe to assume that mod only contains armor that would be considered minidresses. I believe the "all items in an esp" filter does not currently take into account the possibility of zMerged plugins. This is a limitation of KID's MergeMapper support, although the author of KID may be able to change it; I'm not certain.
If you created a merge of mods that only contain "minidress" armors then this should be fine: Keyword = Minidress|Armor|My Minidress Merge.esp but if your merge contains other armors that aren't minidresses then this: Keyword = Minidress|Armor|My Armor Merge.esp would give the "Minidress" keyword to ALL armor in that merge, even non-minidresses.
To rewrite the original KID code so that it works properly with zMerged mods, instead of the "all items in an esp" filter, use the "each individual item" filter using either FormID (which has MergeMapper support in KID) or EditorID (which shouldn't change whether the mod is zMerged or not). Example A: Keyword = Minidress|Armor|0x800~Tiwa44 Minidresses Standalone SSE.esp,0x801~Tiwa44 Minidresses Standalone SSE.esp,0x802~Tiwa44 Minidresses Standalone SSE.esp,0x803~Tiwa44 Minidresses Standalone SSE.esp Example B: Keyword = Minidress|Armor|Tiwa44Minidress01,Tiwa44Minidress02,Tiwa44Minidress03,Tiwa44Minidress04 (These are example FormIDs and EditorIDs so you would need to change the filters to the actual IDs used in the mod.)
Maybe I'm doing something wrong, but I don't think KID's "get all items in a mod" filter takes into account merged plugins.
How to reproduce: Take 2 simple mods such as Valkyrja and Pirates Wield Cutlasses. `valkyrja.esp` has 1 weapon record: Valkyrja "Valkyrja" [WEAP:0xD63~valkyrja.esp]. `Pirates Wield Cutlasses.esp` also has 1 weapon record: DES_Cutlass "Cutlass" [WEAP:0xD63~Pirates Wield Cutlasses.esp].
Control: `valkyrja.esp` and `Pirates Wield Cutlasses.esp` are enabled as well as `zMerge Test_KID.ini` with this line: Keyword = TestWeaponCutlass|Weapon|Pirates Wield Cutlasses.esp Resulting KID log. As expected, this distributes the keyword `TestWeaponCutlass` to 1 weapon.
Test: Use zMerge to merge `valkyrja.esp` and `Pirates Wield Cutlasses.esp`. Then disable `valkyrja.esp` and `Pirates Wield Cutlasses.esp` and enable the merged mod `TestMerge1.esp`, which now has 2 weapon records, one from each mod. Keep `zMerge Test_KID.ini` enabled with the same line: Keyword = TestWeaponCutlass|Weapon|Pirates Wield Cutlasses.esp Resulting KID log. One might expect the keyword `TestWeaponCutlass` to still be distributed to 1 weapon, the one from `Pirates Wield Cutlasses.esp`. However it's erroneously distributed to 2 weapons, the one from `Pirates Wield Cutlasses.esp` and the one from `valkyrja.esp`. This could result in unexpected behavior.
Again, if I'm not doing something wrong, I think that's just how it works right now. I'm not sure if po3 can change the implementation of that KID feature to take in to account the possibility of a merge or if that's even possible at the moment.
Edit: The result is the same using either clean or clobber merge methods.
Using FormID still works as expected with merged mods. EditorID also shouldn't be affected by a merge as far as I know. Keyword = TestWeaponCutlass|Weapon|0xD63~Pirates Wield Cutlasses.esp Resulting KID log.
I think in this case MergeMapper is effectively rewriting Keyword = TestWeaponCutlass|Weapon|Pirates Wield Cutlasses.espinto Keyword = TestWeaponCutlass|Weapon|TestMerge1.espAt least as far as I can tell, that's how KID is treating it.
Edit 2: In mabezard's case I think they're having a problem because that mod's KID ini falls under this specific scenario. Keyword = Minidress|Armor|Tiwa44 Minidresses Standalone SSE.esp SPID isn't having a problem because that mod's SPID ini only uses fully working features. Spell = 0xAA01~WenchOutfits.esp|ActorTypeNPC|lalawench_generalwench_faction|NONE|F|NONE|100
Actually, you're right. KID would need to address this use case where the keywords was being assigned to everything in an esp. Due to the way zmerge works, we have to assume anything without a formID in zmerge is just in the target merge. This particular use case isn't accounted for and would result in what you described. It may not be possible to solve this at run time since zMerge's log does not necessarily list all formIDs that were compacted.
so the logs are saying my merges are being detected yet other mods i have that have integration with the merged mods dont detect them in the mcm, but if i relink scripts in zmerge they do get detected
So how exactly does this mod work in dumb people terms? Do i just make a merge and it will automatically make mods point to the merge that has the master?
If you have MergeMapper installed as well as a zMerge mod (plugin and log file output), then it will automatically redirect any FormIDs that were changed in the merge to the new FormIDs and plugin name.
However it only handles redirecting FormIDs for 1) Papyrus scripts and 2) SKSE DLLs that have implemented support for MergeMapper. You will still need to properly handle esp/esl/esm plugins and possibly other files yourself with zMerge or manually.
I have a question about why MergeMapper is turning off (for KID, SPID, etc.).
The relevant mods SKSE logs say: [01:49:22:065] Failed to dispatch message to MergeMapper [01:49:22:065] INFO - MergeMapper not detected
MergeMapper says: [2023-09-19 01:49:19.196] [Global] [info] [67148] [MergeMapper.cpp:101] Searching for merges within the Data folder [2023-09-19 01:49:19.197] [Global] [info] [67148] [MergeMapper.cpp:182] No merges were found within the Data folder [2023-09-19 01:49:19.197] [Global] [info] [67148] [Main.cpp:203] MergeMapper disabled because no merges found. [2023-09-19 01:49:19.197] [Global] [info] [67148] [Main.cpp:207] MergeMapper has finished loading.
SPID can't find MM because it's turning itself off. Am I doing something wrong?
If you don't actually have any zMerged mods MergeMapper turns itself off because it's not needed. No need to worry about it unless you're sure you're using a zMerged mod.
Sorry for bother, tyvm for mod, endorsed ofc. I use it rather long but couple days ago while i was checking spid log for some ini, i noticed tht spid log says mergemapper not detected Oo. Formlistmanipulator log says same. I rechecked req for Mergemapper and description but didnt not notice something i could miss. I use AE 1.6.640. 1st time i noticed this error i was using version 1.4, now i use 1.5 , same error. Mods which req Mergemapper works (but i not sure already ^^ ).
EDIT. Just realised i needed to post Mergemapper log probably, my bad sorry
Have you used zMerge to merge any plugins? Not really an error otherwise. The logs are just saying no merges are detected so it doesn't have to do anything.
Hi, do you know where I can find the logs? I did a merge using ZMerge (after having enabled MergeMapper in Vortex), but cannot find the logs others mentioned earlier that confirm detection.
I tried SkyrimSE/Data/, SkyrimSE/Data/SKSE, and the default save file location (there's also a SKSE folder) but can't seem to find anything (except the plugin itself). Can you point me in the right direction? Thank you!
EDIT: Maybe I was dumb... Is this mod intended for VR users only, and for the mods listed in the requirements section only? I did see that this was mainly for VR users, but can non-VR users of zMerge also benefit?
So After installing this mod is it ok to disable the relinker output mod? I checked the map merger logs in the skse folder an it looks like it got all of my merges ( I have alot of merges in this load order 850+ mods merged down to 253) It would be so nice if VR could utilize .esl's :(
Yes, it's intended to allow you to disable it. Do report if anything break unexpectedly though. I have noticed that you can't merge things with MCM because sometimes the MCM is generated based on the esp name.
I've sent the PR to fix MCM Helper apps. Parapets hasn't merged it so no idea. I'm not sure I'm going to try to fix MCMs that don't use that framework though.
I noticed that some mods' MCM still show up after being merged and only some don't. Can I just ignore that if I don't need the MCM anyway or could it break more in the background?
Upon further testing, merged mods with MCMs still work fine as long as they don't have a MCM folder with JSON files, because that means they rely on MCM helper. If you merge these, you will just get an entry with the name of your merge in the in-game MCM menu with no settings and an error message inside.
I have this installed on 1.6.659 (AE GOG), but get logfile messages from all kinds of mods saying mergemapper not detected. Wonder if i should just remove it, since apparently it's not working or doing anything on 1.6.659. Speaking of which, i hate it when developers write crap like "working on all versions". All what? Do they have premonition into the future of every game version released until the end of time? What a bunch of bollocks.
This should work for any of SE/AE/GOG/VR. I far as I understand VR users are just the most likely to have merged mods because VR doesn't have esl flags.
70 comments
I hadn't included these in my zip file, so MergeMapper wasn't functioning.
I believe it's assigning the keyword to all the armors from another esp. I imagine I can just rewrite the KID script to point to my merged esp and it should work. I'm reverse engineering this mod and others to get an idea of how I might make my own.
Keyword = Minidress|Armor|Tiwa44 Minidresses Standalone SSE.esp
gives the keyword "Minidress" to all armor items from the mod "Tiwa44 Minidresses Standalone SSE.esp". It's safe to assume that mod only contains armor that would be considered minidresses. I believe the "all items in an esp" filter does not currently take into account the possibility of zMerged plugins. This is a limitation of KID's MergeMapper support, although the author of KID may be able to change it; I'm not certain.If you created a merge of mods that only contain "minidress" armors then this should be fine:
Keyword = Minidress|Armor|My Minidress Merge.esp
but if your merge contains other armors that aren't minidresses then this:Keyword = Minidress|Armor|My Armor Merge.esp
would give the "Minidress" keyword to ALL armor in that merge, even non-minidresses.To rewrite the original KID code so that it works properly with zMerged mods, instead of the "all items in an esp" filter, use the "each individual item" filter using either FormID (which has MergeMapper support in KID) or EditorID (which shouldn't change whether the mod is zMerged or not).
Example A:
Keyword = Minidress|Armor|0x800~Tiwa44 Minidresses Standalone SSE.esp,0x801~Tiwa44 Minidresses Standalone SSE.esp,0x802~Tiwa44 Minidresses Standalone SSE.esp,0x803~Tiwa44 Minidresses Standalone SSE.esp
Example B:Keyword = Minidress|Armor|Tiwa44Minidress01,Tiwa44Minidress02,Tiwa44Minidress03,Tiwa44Minidress04
(These are example FormIDs and EditorIDs so you would need to change the filters to the actual IDs used in the mod.)Hope this helps.
i'm in skyrim VR so merging is starting to become big necessity.
How to reproduce:
Take 2 simple mods such as Valkyrja and Pirates Wield Cutlasses. `valkyrja.esp` has 1 weapon record: Valkyrja "Valkyrja" [WEAP:0xD63~valkyrja.esp]. `Pirates Wield Cutlasses.esp` also has 1 weapon record: DES_Cutlass "Cutlass" [WEAP:0xD63~Pirates Wield Cutlasses.esp].
Control:
`valkyrja.esp` and `Pirates Wield Cutlasses.esp` are enabled as well as `zMerge Test_KID.ini` with this line:
Keyword = TestWeaponCutlass|Weapon|Pirates Wield Cutlasses.esp
Resulting KID log. As expected, this distributes the keyword `TestWeaponCutlass` to 1 weapon.Test:
Use zMerge to merge `valkyrja.esp` and `Pirates Wield Cutlasses.esp`. Then disable `valkyrja.esp` and `Pirates Wield Cutlasses.esp` and enable the merged mod `TestMerge1.esp`, which now has 2 weapon records, one from each mod. Keep `zMerge Test_KID.ini` enabled with the same line:
Keyword = TestWeaponCutlass|Weapon|Pirates Wield Cutlasses.esp
Resulting KID log. One might expect the keyword `TestWeaponCutlass` to still be distributed to 1 weapon, the one from `Pirates Wield Cutlasses.esp`. However it's erroneously distributed to 2 weapons, the one from `Pirates Wield Cutlasses.esp` and the one from `valkyrja.esp`. This could result in unexpected behavior.Again, if I'm not doing something wrong, I think that's just how it works right now. I'm not sure if po3 can change the implementation of that KID feature to take in to account the possibility of a merge or if that's even possible at the moment.
Edit:
The result is the same using either clean or clobber merge methods.
Using FormID still works as expected with merged mods. EditorID also shouldn't be affected by a merge as far as I know.
Keyword = TestWeaponCutlass|Weapon|0xD63~Pirates Wield Cutlasses.esp
Resulting KID log.I think in this case MergeMapper is effectively rewriting
Keyword = TestWeaponCutlass|Weapon|Pirates Wield Cutlasses.espintoKeyword = TestWeaponCutlass|Weapon|TestMerge1.espAt least as far as I can tell, that's how KID is treating it.Edit 2:
In mabezard's case I think they're having a problem because that mod's KID ini falls under this specific scenario.
Keyword = Minidress|Armor|Tiwa44 Minidresses Standalone SSE.esp
SPID isn't having a problem because that mod's SPID ini only uses fully working features.Spell = 0xAA01~WenchOutfits.esp|ActorTypeNPC|lalawench_generalwench_faction|NONE|F|NONE|100
If you have MergeMapper installed as well as a zMerge mod (plugin and log file output), then it will automatically redirect any FormIDs that were changed in the merge to the new FormIDs and plugin name.
However it only handles redirecting FormIDs for 1) Papyrus scripts and 2) SKSE DLLs that have implemented support for MergeMapper. You will still need to properly handle esp/esl/esm plugins and possibly other files yourself with zMerge or manually.
The relevant mods SKSE logs say:
[01:49:22:065] Failed to dispatch message to MergeMapper
[01:49:22:065] INFO - MergeMapper not detected
MergeMapper says:
[2023-09-19 01:49:19.196] [Global] [info] [67148] [MergeMapper.cpp:101] Searching for merges within the Data folder
[2023-09-19 01:49:19.197] [Global] [info] [67148] [MergeMapper.cpp:182] No merges were found within the Data folder
[2023-09-19 01:49:19.197] [Global] [info] [67148] [Main.cpp:203] MergeMapper disabled because no merges found.
[2023-09-19 01:49:19.197] [Global] [info] [67148] [Main.cpp:207] MergeMapper has finished loading.
SPID can't find MM because it's turning itself off. Am I doing something wrong?
EDIT. Just realised i needed to post Mergemapper log probably, my bad sorry
I tried SkyrimSE/Data/, SkyrimSE/Data/SKSE, and the default save file location (there's also a SKSE folder) but can't seem to find anything (except the plugin itself). Can you point me in the right direction? Thank you!
EDIT: Maybe I was dumb... Is this mod intended for VR users only, and for the mods listed in the requirements section only? I did see that this was mainly for VR users, but can non-VR users of zMerge also benefit?
It should work on v1.6.659 (AE GOG).
A shame