Whether or not include version IDs of game snapshots when browsing profiles Every option is explained in the table below. It contains all the settings controlled from the launcher, and is saved in the settings section.
This is one of the most important sections in the file. Launcher version keys are explained below:
#Block launcher pro download update
This section allows better compatibility between launcher versions as well as update checking. Every time a specific version of a launcher is ran, those values are updated to fit the latest-used launcher. It has a couple of values which contain information about the currently used build of the launcher. The launcher version is saved in its own section in the JSON file ( launcherVersion). This map will contain the UUID of the account, and contain the display name of it. The token which saves the log-in sessions. Every logged in user has its own key which is then used in saving things like the currently selected user, etc.Įvery authenticated key consists of a couple of values, which are explained in the figure below. 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
#Block launcher pro download iso
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. Those are used locally by the launcher for managing and tracking sessionsĬontains the UUID-hashed account and the UUID of the currently selected userĮvery Map structure will be explained in its own section below. 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)
