Author Topic: Why is the cache.db so important?  (Read 1420 times)


Stuff you download from other servers going into that.

I've seen people post things like "Try deleting your cache.db" in the help section a few times.

My guess is that it fixes stuff.

No, but really i think it holds the add-ons you've downloaded from other servers.

I think it keeps track of what add-ons you have downloaded from other servers so that you won't have to re-download them.

When you connect server, you receive a list of files from the server, and this is checked with file servers that Badspot has set up. Missing files are downloaded from the file servers, and those that aren't on the file servers are downloaded from the server itself.

When new files are added, they are placed in cache.db for future use in the current server and other servers. Cache.db covers various things from music, models, interiors, terrain, but not images.

In addition to non-default content, default content is downloaded if needed to be repaired, replaced, or changed in case of an update or modification of game files. This, however, caused problems with custom client themes.


There were a few goals in having this:
 - Avoid cluttering add-on folders with files downloaded from servers as it makes no sense to store content-only add-on pieces in there.
 - Grab files from a server very close to you at a faster speed, removing slow file loads and lifting the strain from the server you're connecting to
 - Since they are not tied by name in cache.db, files that are the same but named differently across different servers are not downloaded again
 - Idiot-proofing: since duplicate files aren't downloaded, idiots who repackage pre-existing content instead of just referring to the add-on, (like repackaging the jeep as the drifting jeep, by using the model in the new add-on) this can no longer force clients into downloaded duplicated files. Power to prevent idiots doing poor packaging like that lies only in the hands of add-on distribution areas now.
« Last Edit: April 17, 2012, 04:04:58 PM by Kalphiter »

Idiot-proofing: since duplicate files aren't downloaded, idiots who repackage pre-existing content instead of just referring to the add-on, (like repackaging the jeep as the drifting jeep, by using the model in the new add-on) this can no longer force clients into downloaded duplicated files. Power to prevent idiots doing poor packaging like that lies only in the hands of add-on distribution areas now.
Rage much about poor add-ons?


You can't make anything idiot proof, only idiot resistant.

You can't make anything idiot proof, only idiot resistant.
Make it idiot proof, and someone will make a better idiot.

Rage much about poor add-ons?

With good reason. If you were here for v8, you would have been the shambles it was when it came to handling addons lol.

I wish the launcher didn't write/update to the cache.db, deleting gigabytes of server files wouldn't lead to the redownloading of blockland.

I wish the launcher didn't write/update to the cache.db, deleting gigabytes of server files wouldn't lead to the redownloading of blockland.
It doesn't?

I wish the launcher didn't write/update to the cache.db, deleting gigabytes of server files wouldn't lead to the redownloading of blockland.

You can always backup your cache you know.

You can always backup your cache you know.
because backing up a gig is really worth it when all it does is reduce loading speed

The launcher doesn't do anything to the cache file as far as I can tell.