Board Thread:General Discussion/@comment-32072804-20180209165324/@comment-26091666-20180222032844

The filesize looks just about right but the MD5sum is where it fails (to match). I was hoping that the filesize was different and instead contained HTML stuff.

When you were playing on your friend's account, how did you go about playing it? Specifically did you do anything different from when you are playing on your own account?

I still suspect the file is corrupt in some way during the transit (when your browser was grabbing that asset) and that probably cannot be solved by using VPN as there is potentially a host somewhere along the lines (potentially only traceable by using tools like  but that is a whole new different topic) where they potentially go through either one or more specific set of IP that probably hosts a proxy caching service is hosting the corrupt variant of the file.

For the potentially easier ways around this issue is to either: If those choices are no go and/or you do not trust with the idea of handing your account and password over to a public KC game caching service you can try to look into setting up your own proxy server (ideally locally) and make that your game go through that proxy server (in other words your browser). Though this is somewhat a complicated and technical step but presuming that you did not do anything specifically different when you played with your friend's account then this is ultimately the last resort.
 * Contact your ISP or whoever provides you internet connection and explain the situation to them. Hopefully this won't turn out to be a lengthy discussion over a browser game and how it may not comply with their content filtering policies.
 * Use something like OOI3 CDN service and hope that the same Chiyoda file does not get corrupted going through one or more specific hosts along the route.