The authentication database consists of UUID-hashed keys for all the logged in users. Resolution info is saved in profile resolution mapĪuthentication database is saved in the authenticationDatabase section. The start-up resolution of the game window Whether the logging configuration is a XML file or not. This can be a XML file if the below setting is true The path to the logging configuration for the profile. Those can have tangible experience in the game performance. This is by default the system's Java directory. The Java directory that the game will run on.
The directory that this profile should use to save its content. Version IDs are determined in the version.json in every directory in ~/versions Types are custom (manually created by the user), latest-release (uses the latest stable release), and latest-snapshot (uses the latest build of Minecraft).Īn ISO 8601 formatted date which represents the time the profile was created.Īn ISO 8601 formatted date which represents the last time the profile was used.Īn Base64-encoded image which represents the icon of the profile in the profiles menu. Can include characters, numbers, punctuation, and whitespace A profile structure is explained in the table below: Profiles are saved in a map in the profiles section. The fail count for analytics Ĭontains the UUID-hashed account and the UUID of the currently selected userĮvery Map structure will be explained in its own section below. Those are used locally by the launcher for managing and tracking sessions Every account in this key contains a UUID-hashed map (which is used to save the selected user) which in turn includes the access token, e-mail, and a profile (which contains the account display name)Ĭontains the current launcher build name, format and profiles format. The main JSON keys are explained in the figure below.Īll the launcher profiles and their configurations.Īll the logged in accounts. Launcher_profiles.json uses JSON structures to save and retrieve data.
0 kommentar(er)
