I like to think of this in two distinct problem categories:
- A) Do you want to modify content?
- B) Do you want to make the game fast, stutter free and “reliable”.
I think everybody wants B) … and some want A) on top of that.
For A) there is no other way then to get a readable set of files onto a local drive … and then be able to “layer” it on top of all the “default” content that comes from the system.
“If” the local caching strategy is “solid” then some “dependency and time aware most recently used” (layered?) caching would solve B) without any need for manual intervention.
Using the “install” option is basically a manual caching instruction saying “Use dedicated local caching space for the data of this group … and do not apply the normal no-longer-needed deletion logic of the Rolling Cache”.
As with all caching solution, they never are perfect but hopefully “good enough”. Right now it is far from “good enough” … this is easy to see … but there is no reason why a manual download of TB of data which I will never actually need should give better results then streaming plus a really sophisticated caching implementation.
Asobo will find a way. But it will take time and a few updates.
PS: I started to dig a little into the Rolling Cache and for example with the Marketplace it is very obvious that there is a lot of room for improvement: