Subscribe to download
Thumbs.db

This mod contains only a Thumbs.db file.

Thumbs.db is hidden file produced by windows in order to store thumbnail information so that you can view pictures in a folder without opening them individually.

Unfortunately, Thumbs.db has a nasty habit of getting packed into mods unintentionally when people add an addonimage to their mod. This then causes the in-game addon browser to spit out conflicts, even though this thumbnail database file is the only conflicting file. The conflicts can be safely ignored. However, it is still annoying to see them, and it means that you have to explain to all kinds of people why, for example, your hunter reskin conflicts with a cola pills mod or with a translucent helicopter glass mod.

That’s where this addon comes in. With this addon enabled, you can quickly tell if you have accidentally packaged a Thumbs.db in your mod.

This is how to get rid of it:

Step 0: Go to “folder options” in the windows control panel and go to the “view” tab. Uncheck the box that says “Hide protected operating system files (Recommended)”. You should now be able to see Thumbs.db files wherever they exist.

Step 1: Go to the not-yet-packaged folder of your mod. Make a backup copy of addonimage.jpg by saving a copy somewhere else.

Step 2: Delete both your addonimage.jpg and Thumbs.db at the same time from your mod's folder.

Step 3: go to “folder options” in the windows control panel and go to the “view” tab. Check the box that says “Always show icons, never thumbnails”.

Step 4: Put the backed-up version of your addonimage.jpg into the folder.

Step 5: Repackage your mod using “vpk.exe”. Then check your packaged mod to make sure there is no Thumbs.db file in it.

Step 6: Change the folder options back to what you want them to be.

In the future, you can avoid this issue by always changing your folder options to “Always show icons, never thumbnails” before you add any *.jpg to your mod.

I know this is a bit cumbersome, but at least it works. If someone could find a way to modify vpk.exe so that it ignores *.db files, that would be a much more elegant fix.