eurolite Posted July 5, 2015 Share Posted July 5, 2015 (edited) I just made a merged patch and I don't understand why some things were excluded from the patch. Take a look: http://i.gyazo.com/cb574be83bd3803cbf5f2744e50ab7f8.png It is my understanding that the last plugin to load needs to have every other change in the record in order to not have conflicts. This picture contradicts this. Take a look at the first Leveled List Entry. The Merged Patch has it coloured yellow, which means it will overwrite without conflict. But how so? If it's blank for the merged patch, wouldn't that mean that it's deleting what WMK has put in? Why wouldn't the merged patch include that entry in the first place? Is it because it assumes that the ITM is unwanted because FWE deleted that entry (even though it's before WMK in the load order.) The same applies for the third entry. The fourth entry is confusing. It has the same exact values as the entry above except for the Level value. It seems that this is an entry for how much ammo this weapon will have. WMK had it at 16, but the FWE patch for WMK tones down the value to 8 for balancing purposes, correct? If so, why are the two entries considered different in FO3Edit? This also doesn't make sense because the previous entries we talked about have that blank spot for the merged patch and the colour is yellow, but the colour for this entry is red. What's going on here? Edited July 5, 2015 by eurolite Link to comment Share on other sites More sharing options...
MotoSxorpio Posted July 5, 2015 Share Posted July 5, 2015 Loose files take priority. If you have loose files in your data folder, those files will take precedence. IIRC, timestamps help. FOMM has archive invalidation feature, which will timestamp the bsa's, Wrye Bash actually timestamps all files from Oblivion up, I think. So..for Fallout3-NV 1-Load order2-Timestamp3-loose files ^priority. I could be confusing it a little, but basically, this. I might have the priority for 1 & 2 mixed, but you get the idea? You could research here for historical accuracy: http://forums.nexusmods.com/index.php?/topic/583662-important-load-order-and-you/ Good Luck! Link to comment Share on other sites More sharing options...
eurolite Posted July 5, 2015 Author Share Posted July 5, 2015 (edited) I understand conflicts in general, I just need to understand the specific case I listed here. I have quiet a few like this that are not behaving the way I would expect them to. Edited July 5, 2015 by eurolite Link to comment Share on other sites More sharing options...
blove Posted July 5, 2015 Share Posted July 5, 2015 Section 4.9 The Conflict Detection Algorithm of the Fallout3 Training Manual for FO3Edit by Miax should set you straight. But, since you already have a compatibility patch for the two mods in question, which includes the leveled item list in question, you should just delete that LVLI from your merged patch and let the "WeaponModKits - FWE Master Release.esp" be the winner. As for 16 versus 8, that is the level, "calculate from all levels less than or equal to PC" flag, which that component of the LVLI becomes active. Link to comment Share on other sites More sharing options...
eurolite Posted July 5, 2015 Author Share Posted July 5, 2015 Section 4.9 The Conflict Detection Algorithm of the Fallout3 Training Manual for FO3Edit by Miax should set you straight. But, since you already have a compatibility patch for the two mods in question, which includes the leveled item list in question, you should just delete that LVLI from your merged patch and let the "WeaponModKits - FWE Master Release.esp" be the winner. As for 16 versus 8, that is the level, "calculate from all levels less than or equal to PC" flag, which that component of the LVLI becomes active.I couldn't follow that explanation unfortunately. You didn't really answer the first part about the ITMs (unless the manual was supposed to do that.) Are those entries going to be loaded still or delete due to the blank space in the merged patch? Why does the merged patch not add these entries? I don't understand what the flag does at all. Why are the entries separate even though they have the same LVLI? Care to explain? And if you have time, I was having another issue that I couldn't figure out: http://i.gyazo.com/fabc73fd8ddec9706d5dbbcd74ef9678.png The RH WMK bridge deletes the first three entries from WMK since there are blank spaces there, right (or can the entry still get through despite the blanks)? Is this intentional, or do I have to merge both records together? I can't tell because some stuff is missing, but at the same time the bridge does copy over a few entries from WMK, meaning that if the bridge needed the other entries, it would have copied them over as well. It also doesn't help that I don't know what any of these records or entries mean. I should try to read up on that. The third plugin here has WMK as its master. The entire record is olive or grey, so that means it's a complete ITM. However, if I try to clean ITMs, FO3Edit will not find any. Link to comment Share on other sites More sharing options...
blove Posted July 5, 2015 Share Posted July 5, 2015 The manual answered the why, they will not be loaded if not in the LVLI in your merged patch, but due to already having a compatibility patch between the only two conflicting mods for that LVLI you can safely remove that entire LVLI from your merged patch. A leveled item list is a list of possible results. The level of each entry with respect to the rule imposed by the flag determines whether it is active when the LVLI is asked for a result. You have a weapon modded by WMK, then modded for ironsights, and then overridden by UWR with no ironsights. You cannot merge those alternate textures due to mismatched 3d indexes which is how they are meant to be. Link to comment Share on other sites More sharing options...
Recommended Posts