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 serverYour server tells client that file with hash fff027101a560f8a9c175ac091aa1 767c29718c2 is neededClient 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 fileClient receives some data from your serverClient hashes the data it received from your server and gets 1027f0ff8a0f561ac05a179c6717a a91c21897c2, which is not the correct hashClient 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 fileYou are modifying the files after server has loadedYou or the client are somehow running v19 or earlier of Blockland which had a different hashing functionOther software is actively interfering with the file transferIf you figure out what is wrong, please post what the solution was.
