Hey team,
I was wondering if there was a future feature planned to export the data recorded by the tracker, and then re-import the file(s) with a new feature, in order not to lose many statistics when you have to reinstall the software.
It happened to several of my friends who, due to problems or external factors, found themselves reinstalling the tracker or the operating system, or even changing devices, and, without a feature like the one indicated above, all the historical statistics were lost, such as games played with other players, statistics on operators/weapons, history of games, etc.
I have seen similar topics in which they ask for the possibility of exporting the data, but with the aim of using them for other “personal trackers” or information collections without having to go through the Ubisoft APIs like your tracker does.
This is not what I am asking for. It would not be bad, but I could understand why you do not want to provide the collected data to others in a clean way. As per my topic, I only ask for the possibility of “saving” in one way or another an importable copy of the data, as a sort of backup.
Thanks,
have a good evening.
As I mentioned 2 weeks ago:
[…] “saving” in one way or another an importable copy of the data […]
I’ll enrich the discussion by bringing an alternative that may be preferable.
The simple “import”/“export” method, which essentially generates, perhaps in compressed format, a copy of the data collected up to now, may not be the choice appreciated by the development team if they want to “avoid the diffusion” of this data for purposes other than backup. I’m not saying it’s impossible, but it could be more difficult to keep everything under control.
The alternative I propose is to use the in-cloud storage offered by various providers.
Using the Google Drive APIs to create a “dedicated to an application” storage (which if I’m not mistaken should be available for free) allows you to occupy the storage space provided to the user without the user being able to actually read or modify that portion of data (at most delete it and lose the connection).
This solution is often used by services like yours because it is a sort of bilateral guarantee: the user does not have access to the data in the raw format, so he cannot abuse it, and the application does not have access to the entire user’s drive but only to the portion dedicated to his files.
Obviously this option would be viable only if the possibility of connecting a Google account to his own TRN account via OAuth was implemented.
(Note: I do not know if this type of service is also offered by other in-cloud hosters like iCloud or MS-Azure)
In my opinion the option of a simple local import/export seems the easiest to implement, but clearly if you want to avoid data dissemination as mentioned above, a sort of encryption should be managed so that only the tracker can regain the exported information.
This procedure could be avoided by managing it with the alternative proposed above, which however clearly involves other factors.
Thanks for everything to everyone,
I hope I can actually contribute to what I think is one of the few shortcomings of your tracker.