Deleted1212710User Posted April 29, 2009 Share Posted April 29, 2009 Just a few questions of which the answers seem to elude me. When using Wrye Bash how should I handle these. (same question for all plugins) - Should I merge into patch or not? Should it be virtually active? AND ...should it be active at the time of rebuilding the patch? ==Merge Patches== HrmnsOblivionScriptOptimization.esp ---- This one is my main concern, I assume to just leave it out, leave it active and at the front of everything. How would merging with the patch and having it vitually active effect it? What should I do with all the FCOM_compatibility.esp types? Weather Types? Spell Scripting types (LAME, Midas, Supreme)? - I would like fries and a coke with that. ==Import Cells, Factions, Graphic, Inventory, NPC Faces, Names, Relations, etc. etc.==Should I just put a check next to everything? EDIT:The other big concern is Deadly Reflex 5DR5 Timed BlockSM_DeadlyReflex (Supreme fix for DR5) In Bash, I have the 3 Deadly related .esp after the bash patch.esp I read that the patch won't affect files in the load order after it, but if I select SM_DeadlyReflex...when it's finished patching I am able to put SM_DeadlyReflex in virtually active mode. What do you think? Should I just be following my gut instinct on this one in saying that I should NOT be merging SM_DeadlyReflex.esp NOT DONE YET. I need just an opinion on something that has been bugging me. Are you LAME Supreme, or Supremely LAME. I'm serious...... which one do you give priority too, or does it matter? I've been putting Supreme over the top of LAME and using bgMagicEV_Conjuration_for_supreme_Magicka.esp..because I read somewhere in this maze of stuff that it was the way to go...but BOSS for some reason prefers to put LAME over Supreme. Thanks for your time. Link to comment Share on other sites More sharing options...
Frodric Posted April 29, 2009 Share Posted April 29, 2009 Just a few questions of which the answers seem to elude me. When using Wrye Bash how should I handle these. (same question for all plugins) - Should I merge into patch or not? Should it be virtually active? AND ...should it be active at the time of rebuilding the patch? ==Merge Patches== HrmnsOblivionScriptOptimization.esp ---- This one is my main concern, I assume to just leave it out, leave it active and at the front of everything. How would merging with the patch and having it vitually active effect it? What should I do with all the FCOM_compatibility.esp types? Weather Types? Spell Scripting types (LAME, Midas, Supreme)? - I would like fries and a coke with that. ==Import Cells, Factions, Graphic, Inventory, NPC Faces, Names, Relations, etc. etc.==Should I just put a check next to everything? EDIT:The other big concern is Deadly Reflex 5DR5 Timed BlockSM_DeadlyReflex (Supreme fix for DR5) In Bash, I have the 3 Deadly related .esp after the bash patch.esp I read that the patch won't affect files in the load order after it, but if I select SM_DeadlyReflex...when it's finished patching I am able to put SM_DeadlyReflex in virtually active mode. What do you think? Should I just be following my gut instinct on this one in saying that I should NOT be merging SM_DeadlyReflex.esp NOT DONE YET. I need just an opinion on something that has been bugging me. Are you LAME Supreme, or Supremely LAME. I'm serious...... which one do you give priority too, or does it matter? I've been putting Supreme over the top of LAME and using bgMagicEV_Conjuration_for_supreme_Magicka.esp..because I read somewhere in this maze of stuff that it was the way to go...but BOSS for some reason prefers to put LAME over Supreme. Thanks for your time. For the questions on Load order for L.A.M.E. I would post them in the Current release thread. The author is active in the thread and likely to answer your question himself. As for the SM_DR issue I don't think its an issue to leave it out so if in doubt don't merge it. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.