With the last repo update for EU3 AWE, we had 16 GB of updated stuff thrown at us.
How A3Sync works is that it checks for folder names, so when it can't find the one from the repo server in your Arma directory, it is blind to everything else, even if it's just a tiny revision. So if you had ACE 3.6.0.0, then 3.6.1.0 comes along and changes a couple PBOs, the rest should be unaffected and the download would be a few MB at most to replace just those. But if the version number were in the folder name, A3Sync would look for @ACE_3.6.1.0, but only find @ACE_3.6.0.0, ignore it and proceed to download the entire mod again.
That's mildly annoying for small mods such as ACE, but absolutely infuriating in the case of RHS or CUP.
If you know about this, you can rename the mods in question yourself, but most players will either not be aware of it or do not comprehend the procedure. It's tedious as, if you mix up your dashes and your underscores, you'll have achieved nothing.
My proposal thus is to rename all mods with version numbers or otherwise variable names on the repo server itself. @CUP_Terrains_Core-1.3.0, for example, will then become @CUP_Terrains_Core. @ProjectOPFOR was re-downloaded because it now has an underscore in it, so if things like that remained consistent from now on, we could save a bit of traffic.
All future repo downloads of this week's magnitude would be cut down by gigabytes with a quick global change.
That's not to say to go out of your way to do so now. Perhaps just bear it in mind for the next update cycle.
Question
SkullCollector
With the last repo update for
EU3AWE, we had 16 GB of updated stuff thrown at us.How A3Sync works is that it checks for folder names, so when it can't find the one from the repo server in your Arma directory, it is blind to everything else, even if it's just a tiny revision. So if you had ACE 3.6.0.0, then 3.6.1.0 comes along and changes a couple PBOs, the rest should be unaffected and the download would be a few MB at most to replace just those. But if the version number were in the folder name, A3Sync would look for @ACE_3.6.1.0, but only find @ACE_3.6.0.0, ignore it and proceed to download the entire mod again.
That's mildly annoying for small mods such as ACE, but absolutely infuriating in the case of RHS or CUP.
If you know about this, you can rename the mods in question yourself, but most players will either not be aware of it or do not comprehend the procedure. It's tedious as, if you mix up your dashes and your underscores, you'll have achieved nothing.
My proposal thus is to rename all mods with version numbers or otherwise variable names on the repo server itself. @CUP_Terrains_Core-1.3.0, for example, will then become @CUP_Terrains_Core. @ProjectOPFOR was re-downloaded because it now has an underscore in it, so if things like that remained consistent from now on, we could save a bit of traffic.
All future repo downloads of this week's magnitude would be cut down by gigabytes with a quick global change.
That's not to say to go out of your way to do so now. Perhaps just bear it in mind for the next update cycle.
Cheers.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now