Wargaming download strategy causing range caching to store more cached data than usual

[chong601]

A few years back, Wargaming released Wargaming.net Game Center (WGC) which unifies the separate game launchers that each game does.

Wargaming game content are either fetched using torrent or HTTP, where the latter is used if tracker and DHT is unusable.

However, WGC changed the download strategy where the request ranges now do not follow fixed ranges (it will dynamically select between 16 KB to 18 MB ranges during download, possibly depending on network congestion) which causes the cache to slowly be filled up with more data due to overlapping range requests between different download iterations

Currently I'm still investigating if slice ranges would be suitable for this use, or to retain existing configurations and to add a note that Wargaming cache folder may increase in size in the readme section.