Hello Galactic Survivalists! The way clients download a SharedData folder is changing! We will be introducing a better way to handle SharedData downloads that doesn't use any dedicated server bandwidth on log in. Code: SharedDataURL: https://drive.google.com/file/d/1xxxxxxxxxxK/view?usp=sharing If you don't provide the new URL field then the old way is used. Yours, Eleon Game Studios team.
It would be great if you could also remove the IP address of the server from the name of the cache directory and only use the ID of the savegame. Because if you run an empyrion server behind a (daily) changing IP address of a private internet connection, the directory does not have to be transferred to the clients every day.
This is indeed something that will help against the disconnect issues on season starts or when there are bigger game/scenario updates. We already implemented something like this on Anvil and it solved the disconnect issues in those occasions completely. If its not too late though, i'd like to suggest a few additions/extensions to this, unless something like this was already considered or implemented. A few assumptions: * shared data can have ~1000 files, of which most are pretty small, and just a few ones have several MB (assets) * downloading 1000 files from a http server takes way longer and consumes way more resources than a single zip file * most of the files in the shared data folder change very seldom in game or scenario updates * servers running scenarios (RE for instance), do update their scenario pretty often per season. On season starts or for new players that have to download everything from the server, having the client download a full zip from a different location is a good idea. For players that have already done that though, it would be amazing if the client only downloads the changed files (as before), without the server owners having to deactivate that feature - also optionally from a separate location where the shared data files can be downloaded separately (like the old way, but not from the game server itself). This would enable server owners to set the urls up once and forget about the issues completely, and the players would only download whats needed or what has changed, minimizing the resource efforts on server and client. E.g. like this: Code: SharedDataUrlZip: http://myserver.com/shareddata.zip # A SharedDataUrl: http://myserver.com/uncompressed_shareddata/ # B If the http client supports HTTP E-Tags, it should be pretty easy to add that to the implementation of the "old way".
It will not work that way. You will only be able to provide a zip file. If the SharedData changes then you have to set a new download URL to the server with a new zip link The full zip will be re-downloaded. We tried it with our own server shared data what is way larger then RE's shared data and it took 30 seconds to download, unzip and connect So for players its not a problem when the data has to be re-downloaded due to changes. If you want the way like you descripe then you will need the current (old) way as the system works now. They dont set a link and it will be downloaded from the server side.
