How to keep Cosmos from deleting non-Cosmos AddOns

[Gryphon]

For every non-Cosmos AddOn that you have create a .nopatch file to keep Cosmos***** from deleting it while "Keep Interface Directory Clean" is enabled. You should really have this enabled to keep Cosmos as clean and error free as possible.

To create a .nopatch file, create a new .txt file and change newtxtfile.txt to <foldername>.nopatch (<foldername> is the name of the AddOn folder you are protecting).


Examples:


Let's say you install "BankStatement", you would have:
Interface\AddOns\BankStatement
Interface\AddOns\BankStatement.nopatch


Or:


Let's say you install "Enhanced Trade Skills", you would have:
Interface\AddOns\TradeSkillFrame
Interface\AddOns\TradeSkillFrame.nopatch


You can even protect a specific file, say if you made a small edit to a Cosmos file:


Interface\AddOns\AddOns\Sky\Sky.lua
Interface\AddOns\AddOns\Sky\Sky.lua.nopatch



That should be it, if it isn't working, make sure that your known file types are not hidden and that you are not actually creating <foldername>.nopatch.txt on accident. You can also use blank folders instead of blank text files.

Why does Cosmos***** do this? Because if the Cosmos devs delete AddOns\Clock from the Cosmos package they want Cosmos***** to remove it. But why does it clean non-Cosmos addons? Because Cosmos***** doesn't know if that non-Cosmos addon is an old deleted Cosmos file or if it is a custom AddOn, all it knows is that it does not match the Cosmos package and might be an old Cosmos file. Why doesn't Cosmos have a master list of it's mods? It does have a master list of it's mods, however it does not have a list of every file that has been renamed or deleted since the beginning of Cosmos which is what would be necessary to do in order to make sure that someone using Cosmos version 1 gets all their old files deleted when updating to Cosmos version 753.

There are no current plans to change the way Cosmos***** handles AddOn management. The devs acknowledge that there have been many suggestions on how to change this behavior, however with proper use Cosmos***** works as it is.

Be prepared though: Some AddOns which are in the Cosmos package that you love today may not be there tomorrow and they will get deleted. Always read the patch report when Cosmos***** patches and make note of what is happening.

[Cappyoak]

Not to be a snapper head, but where do I create the nopatch files??

[morbid_o]

1 of 3 places.

AddOnName.nopatch as an empty text file in the \AddOns\ directory
nopatch as an empty text file in the \AddOns\YourAddOnName\ directory
AddOnName.nopatch as an empty directory in the \AddOns\ directory

the capilatization on the nopacth file should match that of the addon

[screw579]

1 of 3 places.

:wink: But is that not a bit risky?

[mat_de_b]

How do u get a whole folder to be recognized as a patch??? do u need to create seperate ones for each file or just one for it all

[PleegWat]

How do u get a whole folder to be recognized as a patch??? do u need to create seperate ones for each file or just one for it all

See the first 2 examples

[Ulgard]

I have tried using all three ways and Cosmos still deletes BGInvite on me everytime it patches. Can anyone give me some advice?

[morbid_o]

can you post a screenshot of your Addons directory showing the BGInvite.nopatch file?

also, check your folder options and make sure that you aren't hiding file extensions (meaning that what you see is BGInvite.noptach, and it actually is BGInvite.nopatch.txt)

[Payn]

Ok, I promise i've read the sticky threads, but i'm still kind of lost. I'm not the most computer savy person out there.

Ok, I've had cosmos for quite some time now, works great.

But I just recently made a Rogue Char....and want to use some addons that arn't cosmos.

And of course cosmos deleted them everytime i started it up, ...i read on why it does that and how to prevent that....but i'm kind of confused on the step...

"To create a .nopatch file, create a new .txt file and change newtxtfile.txt to <foldername>.nopatch (<foldername> is the name of the AddOn folder you are protecting). "

1) first of all, how do I create a "new .txt file"

2) once i create that file... do i put that file into the folder of the new addon? or do i put it in the Main WoW Addon folder with the directory of "D:\Program Files\World of Warcraft\Interface\AddOns" for example?


basically the part i'm stuck on is creating the new txt file, i think once i know how to do that i can probably figure out the rest.....so any help would be greatly appreciated, ty in advance

[morbid_o]

firstly, make sure you have windows set to show filename extensions (ie, for a word document, everything ends in .doc)

then to make a new TXT file, you can just right click in an empty spot inside of your windows explorer and go new->text file, then rename it accoridngly (you'll probably get a warning about changing a filename extension, but take that as a signal that you are on the right track)

[Zankarst]

What about all the Blizzard_*UI folders? :/

Gotta make a .nopatch for these as well, or just forget about it?

EDIT: Ah, just fiddled around with the Cosmos settings before playing WoW. It was a good idea to create an addon manager. For these that don't know what I'm talking about (ie new users to Cosmos) this is a screenshot to protect/unprotect your non-cosmos addons & blizzard addons.

http://img80.imageshack.us/img80/8061/cosmos8yh.jpg

[Parker]

I set Cosmos to protect all non-cosmos add-ons, and then when Wow started up, I checked "do not display this page again." That would have been great except I need to get to that Add-On Manager page again and unprotect ONE add-on, and I can't figure out how. If I run the executable again, I can't find it that way.

Does anyone have any suggestions? I'd really appreciate it. :D

[dormlock]

The addon manager window is under manage addons button on the main window.

The install window can be reshown by going into configure and enabling the option 'Show Installer Window'.

You don't have to protect Blizzard addons just make sure the option 'Clean Blizzard Addons' is unchecked.

I try to add options for things that would make sense to allow one to customize the updaters behavior.

[oddible]

By the way, when you create the MyAddon.nopatch file, it is Case Specific so make sure your .nopatch filename has the same capitolization as the folder you are trying to protect.

Example for Addon:

AddOns\CT_RaidAssist

Works:

AddOns\CT_RaidAssist.nopatch

Fails:

AddOns\ct_raidassist.nopatch

[RadioActiveLamb]

Two things...

1. I just updated the launcher from 3.something to 3.latest. With the upgrade, the launcher FORGOT that I wanted to protect a whole bunch of addons, and it cleaned them out. Is this going to happen between all versions? Is there a way to make the launcher/updater use the add-on protection that I assigned from a previous version?

2. I like to use some newer versions of addons than the ones included within the Cosmos package. The launcher tags things like the damage meter as a Cosmos addon, and it "updates" it with the older version every time. How do I tell Cosmos NO, do NOT manage the damage meter addon, since I have the latest one from the official website?

[Ebf18]

For some reason, patcher 3.9 keeps on deleting my non-cosmos addons even is I use the nopatch line. I have tried a dir with the addon name with nopatch, a file with the addon name and nopatch and it still deletes the addon. I made sure that the case is correct, but it still deletes it anyways. Any ideas?? Thanks

[Gryphon]

Manage Addons > Protect All Non Cosmos

[jgleigh]

Except that 3.9 seems to ignore it's own settings.

[Ebf18]

Manage Addons > Protect All Non Cosmos

I tried this also, but I noticed that if I drop in a new non-Cosmos addon, it doesn't get added to the "Protect All Non Cosmos" list automatically.

[x0Synergy0x]

Sorry, but this makes Cosmos very inconvenient to use. Now I have to reinstall & reconfigure all of my mods.

[vulcan]

Windows explorer? where do I find that?

I am sorry, and serious. I have had a hard time following this, and still don't understand about making a txt file.

It did mention that I could do a new folder. I know how to click on the new folder button.

I will use Rogue Focus for my example.

So, if I opened the wow folder, opened the interface folder, opened the add on folder, and then opened the non-cosmos addon, Rogue Focus.

I then click on the new folder button to make a new folder. I would then rename the folder
"Rogue Focus.nopatch"

Would that work, or would I need to take out the space between 'rogue' and 'focus'?

[xerty]

Vulcan,
This is a very old thread and there is now a much easier way.
Start the patcher (you must be using this or you would not be worried about this problem, lol).
Click "Cancel Patch".
Click "Manage AddOns".
Click "Protect All Non Cosmos".
Click "Done".
Job done.
HTH, xerty.

[vulcan]

LOL. That is way to easy.

Did it.

Thanks for replying.

[xerty]

Hehe Nice to see someone say something is too easy :D

[AnthonyK]

Is there a way to keep Cosmos from deleting on specific file? WWS stores a file called WWSA.zip right in the root AddOn folder and Cosmos keeps deleting it. It's nothing really huge, because WWS just re-downloads itself. It would make things a little quicker though if that file wasn't deleted every time I patch cosmos. :)

[xerty]

Is there a way to keep Cosmos from deleting on specific file? WWS stores a file called WWSA.zip right in the root AddOn folder and Cosmos keeps deleting it. It's nothing really huge, because WWS just re-downloads itself. It would make things a little quicker though if that file wasn't deleted every time I patch cosmos. :)

I would normally say to use the Manage AddOns option of the patcher. You can protect addons here to stop the patcher from deleting them.
But, I am unsure if a zip file would appear in this list.
Alternatively you can create a NoPatch.nopatch file in the addons folder. The file is just a notepad file with the name of the addon named in it.
Try opening notepad and type WWSA and save it as NoPatch.nopatch
If that does not work try using WWSA.zip
Hopefully one of these will work.
xerty.

[Gryphon]

If you do not use the consolidated nopatch file, create a file called "WWSA.zip.nopatch". This is the nopatch method I use, I am unsure how well the consolidated method works.

[xerty]

If you do not use the consolidated nopatch file, create a file called "WWSA.zip.nopatch". This is the nopatch method I use, I am unsure how well the consolidated method works.

Thanks for the clarification Gryphon.