Jump to content

Skyrim Revisited Pre-Release Feedback


Recommended Posts

Hi, i don't want to use CACO, because i'm using PerMa. I'm wondering if there's any way to remove CACO as a "Master" from the Conflict resolution patch that Neovalen made.

the easy way I know is to download CACO to enable the SR conflcit to load into TES5Edit and then remove the records from the Patch Neo made (other long winded option is to do the CR yourself missing out records CACO).

Edited by Darth_mathias
Link to comment

the easy way I know is to download CACO to enable the SR conflcit to load into TES5Edit and then remove the records from the Patch Neo made (other long winded option is to do the CR yourself missing out records CACO).

Are these files i highlighted "Records"? All of the filed i highlighted have CACO conflicts in them. Can i just Right click > Remove? (Or just delete the whole container file)

5cdfcf3b68.png

Link to comment

Yes these are the ones. You can delete the entire container section if it contains only the conflicting records with CACO.

After you delete them, right click in the SR Conflict Resolution esp -> Clean Masters; then right click again in the SR Conflict Resolution esp -> Sort Masters and you are good to go.

 

Thing is that I cannot remember (not in my gaming rig now) if the "Container" records are the only ones that address CACO patching... :unsure:

Link to comment

the easy way I know is to download CACO to enable the SR conflcit to load into TES5Edit and then remove the records from the Patch Neo made (other long winded option is to do the CR yourself missing out records CACO).

 

 

Yes these are the ones. You can delete the entire container section if it contains only the conflicting records with CACO.

After you delete them, right click in the SR Conflict Resolution esp -> Clean Masters; then right click again in the SR Conflict Resolution esp -> Sort Masters and you are good to go.

 

Thing is that I cannot remember (not in my gaming rig now) if the "Container" records are the only ones that address CACO patching... :unsure:

Thank you both. I might have died if i had to do all of the CR myself (And just not include CACO). And yes, "Container" only has CACO conflicts :)

Link to comment

Are these files i highlighted "Records"? All of the filed i highlighted have CACO conflicts in them. Can i just Right click > Remove? (Or just delete the whole container file)

 

 

Yes these are the ones. You can delete the entire container section if it contains only the conflicting records with CACO.

After you delete them, right click in the SR Conflict Resolution esp -> Clean Masters; then right click again in the SR Conflict Resolution esp -> Sort Masters and you are good to go.

 

Thing is that I cannot remember (not in my gaming rig now) if the "Container" records are the only ones that address CACO patching... :unsure:

 

by the picture posted, it looks like another esp (skyrim coin replace redux) also has those records. probably means that it makes changes to those records as well, though I can't see any in the picture. but if you were to scroll down then there might be some changes from the coin replacer mod. if that's the case and those are the only records that caco shares with the conflict resolution esp, then I would think it would just be a matter of removing caco as a master, no? someone please tell me if I'm wrong!

 

edit: well, I think I should've said "it would just be a matter of removing caco's changes within the records and THEN removing caco as a master," right?

Edited by danielleonyett
Link to comment

Well...the patching in SR Conflict Resolution.esp exists because CACO conflicts with Skyrim Coin Replace Redux in "Container records" in the first place. So basically, by removing these records from the CR you remove from SR CR.esp any reference made to CACO. The patching wouldn't exist in the first place if CACO wa not present. So if someone does not want to use CACO and still wants to use SR CR.esp then it is absolutely safe to remove these records and then clean -> sort masters.

 

Then CACO can be removed from mod list and for these specific records it will be only Skyrim Coin Replace Redux conflicting with..."nothing"!  ::):

So actually we are back to how SR:LE was before Neo added CACO in the guide and CR  :;):

Edited by Astakos
  • +1 1
Link to comment

Hopefully mergeable with CACO patches. Dammit I am seriously having to get mercenary with my non-SRLE mods at this rate to avoid plugin overload :P

it looks like it can atually be merged with Bathing in skyrim (thus maintain compatability with SR conflict) need to test to confirm.

 

I was able to merge without any issues with Neo's bathing in skyrim merge it didn't flag up any errors now to see what happen in game.

 

well it appears a least in my game this merge works without issue

 

the order I Merged it in was as follows:

 

Bathing in Skyrim - Main.esp

CACO_Bathing in Skyrim.esp

Bathing in Skyrim - Realsitic Room Rental.esp

Bathing In Skyrim - Followers Only.esp

 

named as Neo instruts in his guide.

 

Well no Conflict with SR Conflict Resolution either so Neo it might be worth having a look yourself and seeing if it actually worth adding to your guide.

Edited by Darth_mathias
  • +1 1
Link to comment

Darth , i decided to try out the same Mods as you are using  in your mod list on top of  SRLE .

 

Could i make a request for a downloadable version of your  conflict resolution  file ?  

 thanks in advance  .

try this link https://copy.com/LB2umWxiL48tqUMU

this CR is still a work in progress and should be placed after Neo's patch, and if you find anything i've missed then please let me know. also in future if you could we please use the page I have created for request on this subject that way we can keep it seperate.

Edited by Darth_mathias
Link to comment
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.