Are you absolutely sure they\'re all the same? I just re-tested and \"mirror 1\" gives consistently different component file sizes to mirrors 2 & 4, and they overwrite each other. Maybe I\'m just not understanding...
For a simple, quick illustration, I ran the updater multiple times in a row, but terminated each update as soon as it began on deathrealm.zip. But files up to that point should at least have been updated. What\'s important is the file sizes...
If it uses \"mirror 3\", it downloads the zipped repository, attempts to unzip it and then consistently says \"Error getting zip entries from file.\" It\'s been doing this for days. So that\'s as far as I can test that particular mirror.
If it uses mirror 1, after previously having used mirror 2 or 4, I get:
Updating root(5816 bytes of data)...Done
Updating data(14369 bytes of data)...Done
Updating docs(0 bytes of data)...Done
Updating support(0 bytes of data)...Done
Updating art(8750032 bytes of data)...AR: art/world/deathrealm.zip
If I restart and it then uses mirrors 2 or 4, I get:
Updating root(6034 bytes of data)...Done
Updating data(14592 bytes of data)...Done
Updating docs(0 bytes of data)...Done
Updating support(0 bytes of data)...Done
Updating art(18030634 bytes of data)...AR: art/world/deathrealm.zip
These file sizes are consistent between attempts, when an incompatible mirror has been run just previously. So it really looks like mirrors 2 & 4 are carrying different data to mirror 1 (and mirror 3 is totally screwed up).
If I use the same mirror twice in a row, or mirrors 2 and 4 one after the other, it doesn\'t find anything new to update before it reaches deathrealm.zip (which I never let finish, so it\'ll always want to be updated). So the updates for the one mirror are consistent.
I would assume that mirrors 2 & 4, having the larger file sizes, are more likely to be the up-to-date ones, but of course I can\'t be certain of that.