Blockland Forums > Help
The CDN forgets over updating add-ons ...!
DontCare4Free:
--- Quote from: Bushido on October 30, 2011, 04:46:59 PM ---client... download... network?
it's this big add-on database badspot implemented to speed up download times with the client
--- End quote ---
Content Delivery Network.
Badspot:
--- Quote from: Bushido on October 30, 2011, 04:46:59 PM ---whenever someone tries to join my server, they freeze up at some point and can't load a file. i've boiled it down to the tier+tactical tier 1 package, which i have recently updated with new sounds, models, etc: but since this package is not what the CDN has, they get a hash error and can't download the file
thus, downloading ceases and the client just sits around doing nothing
client... download... network?
it's this big add-on database badspot implemented to speed up download times with the client
--- End quote ---
The way it works, it doesn't matter if you modify files. The files are identified to the client by hash, filenames are not considered. The whole point of the system is for the client to get the exact same files the server is using, no matter what they are. If it could not handle modified files the system would not work at all.
What has happened here is this:
[*]Client connects to your server
[*]Your server tells client that file with hash fff027101a560f8a9c175ac091aa1 767c29718c2 is needed
[*]Client checks the CDN for the file ( http://cloud.blockland.us/blobs/fff027101a560f8a9c175ac091aa1767c29718c2 ) - it isn't there. This is fine. Any file that isn't on the CDN can be downloaded directly from the server you're connecting to.
[*]Client asks your server to send the file
[*]Client receives some data from your server
[*]Client hashes the data it received from your server and gets 1027f0ff8a0f561ac05a179c6717a a91c21897c2, which is not the correct hash
[*]Client concludes that your server said it was going to send one file and instead sent a different one. Error.
I don't really know how this can happen but here are some guesses:
[*]Your cache.db file has become corrupted somehow (deleting cache.db may solve the problem)
[*]You have directly modified the data in the cache.db file
[*]You are modifying the files after server has loaded
[*]You or the client are somehow running v19 or earlier of Blockland which had a different hashing function
[*]Other software is actively interfering with the file transfer
If you figure out what is wrong, please post what the solution was.
Bushido:
i got rid of cache.db, problem solved
back to business!