BACKND File System
This function is used to handle locally stored data stored when using BACKND SDK 5.0.0 or later.
The following information is stored locally using the BACKND file system: In SDK versions earlier than 5.0.0, data is stored/loaded using Unity's PlayerPrefs function.
- Information on access token
- Information on guest login account
- BACKND chart
- Information on blocking of BACKND chat
Location of storage / Name of stored file
Name of the stored file is backend.dat.
Locally stored data stored will be stored in Application.persistentDataPath/Backend.dat.
Application.persistentDataPath is a permanent data directory path provided by Unity.
For more information, refer to the Unity developer documentation.
|C:/Users/userprofile/AppData/LocalLow/Company Name/Game Title/backend.dat
|~/Library/Application Support/Company Name/Game Title/backend.dat
- Company Name refers to the 'Company Name' designated in Unity PlayerSetting.
- game title refers to the 'Product Name' designated in Unity PlayerSetting.
- userprofile refers to the name of the account logged into Windows.
- guid refers to the file name generated randomly.(e.g., 055811B9-D125-41B1-A078-F898B06F8C58)
- If you set to store the game data in external storage in Android, the storage path may be changed.
Generally, it is recommended to not change the ClientAppID.
Data stored using the BACKND file system is encrypted using the ClientAppId entered in Unity's BACKND Inspector window.
If the ClientAppID is changed in the Unity BACKND Inspector window, you cannot access the existing backend.dat.
In this process, the existing data is deleted and an encrypted backend.dat is generated using a new ClientAppID.
In this case, all locally stored pieces of data, including users' token information, chart information, and guest login information, are deleted.
When calling BACKND functions, the BACKND file system is called to load data in necessary cases.
The developer cannot arbitrarily load data except for the BACKND chart function.
- The developer may arbitrarily load BACKND charts stored in backend.dat.
When calling BACKND functions, the BACKND file system is called to save data in necessary cases.
The developer cannot arbitrarily store data.