Google drive bandwith concerns

Hi,
With the latest updates that Google has pushed, bandwidth is no longer a issue. The real problem is that the WebService that is used to get access to the Spreadsheet without having to store the User/Pass in your game hasa daily time constraint.
Google allows a WebService script to run for no more than 90 min a day.

That's why its adviced to have the update frequency to DAILY, WEEKLY, etc. instead of ALWAYS.
That setting, determines when the plugin decides it has been long enough since the last check. But if the couta is exceeded and the plugin can't access google spreadsheet, then it will try to access it every time the game opens, until it can get access.

That means that if you make a change to the Spreadsheet, a batch of users will download it the first day, then another similar batch the day after, and so on, until everyone gets updated.

Said that, even with big spreadsheets, the time the WebService is ran to send the data is just a few milliseconds (for the app it can take seconds to download the data depending on your connection, but the webservice only runs for an small amount of time).
So, 90 min a day allows for several hundred thousands of users to download the update.

If you game needs faster updates and you are having several millions users, then hosting the CSV yourself maybe more convenient.

Here is an example script on how to download the CSV from your own hosting, and import it into the game at runtime:
inter-illusion.com/assets/I2Localization...portingaCSVfile.html

Please, notice that to avoid downloading the CSV everytime the game runs, you may want to also have another file that keeps the latest time the spreadsheet was updated. That way the game only needs to download that small manifest, and only get the big CSV file if it has changed.

Hope that helps,
Frank

I like that. Will add it to the next update

Thanks for the suggestion.
Frank

When the game is built, it has all the data in the I2Languages.asset.
If on the first time, the user is not online or the asset is up-to-date with the spreadsheet, then it will use the data in the asset.

If there is a change, the spreadsheet is downloaded and saved into a local file.

From that point on, if the user is Online or Offline, it will never use the data in the asset, instead, it will use the one from the cache (i.e. the downloaded file)

If later there is a new update, the local file is overritten with the new data.