Profiles¶

A profile is a complete, fixed setup: a Minecraft version, a loader, and a list of components with exact versions and checksums. You never configure Forge yourself in a Xol profile.

Xol keeps five things apart: the Minecraft version, the loader and its version, the optimization components, the Xol modules, and the performance preset. A preset only writes video settings; it never changes what is installed.

At a glance¶

A profile named Forge + Optimization 1.8.9 exists in the manifest but is not offered in the picker. See below.

What Preview means¶

The profile manifest gives every profile one of four states. The launcher turns them into words like this:

No profile is verified yet. Each profile also carries a note per platform, which the launcher shows under the profile name. Today those notes read:

The full matrix is on Supported versions.

Xol 1.8.9¶

"Xol's HUD and settings on Forge 1.8.9. Performance tuning is still in progress."

Xol does not ship its own optimization for 1.8.9 yet. No performance claim is made for this profile; see Benchmarks.

Xol 1.7.10¶

"Xol's HUD and settings on Forge 1.7.10, with a fixed set of performance mods. Their effect has not been measured yet, and OptiFine can't be added alongside them."

The four third-party mods are downloaded from Modrinth's CDN at exactly these versions. Size and SHA-256 are pinned in the manifest and were cross-checked with Modrinth's API when the manifest was built. Sizes are on What gets downloaded.

The manifest records each mod's role and licence but no description of what each one changes, so none is given here. Each project documents itself on Modrinth.

OptiFine is not offered for this profile. Hodgepodge replaces the same rendering code and declares a conflict with OptiFine; the game does not start with both. The launcher says so in Settings ▸ Instance instead of showing the import. If you want OptiFine on 1.7.10, use the OptiFine 1.7.10 profile.

Forge-only profiles¶

"Forge on its own, without the Xol client, for your own mods."

Forge 1.8.9 and Forge 1.7.10 install the same pinned Forge build as the Xol profiles and nothing else. Put your own mods into the instance's mods folder. These profiles report Forge's own client brand (fml,forge), not Xol.

Forge + Optimization 1.7.10¶

"Forge 1.7.10 with the same performance mods as Xol 1.7.10, without the Xol client."

The same four pinned mods as Xol 1.7.10, minus the Xol client. It has not been launched on its own in testing; its stack is the one Xol 1.7.10 was tested with.

Why there is no Forge + Optimization 1.8.9¶

The manifest says: "Not available yet: there is no set of performance mods for Forge 1.8.9 whose files Xol can check before installing them. Use the OptiFine profile, or Xol 1.8.9 with OptiFine added." Xol only installs third-party files whose exact version and checksum can be pinned, and it does not install mods that download unpinned code of their own at first launch.

OptiFine profiles¶

"Minecraft with OptiFine. Its licence doesn't let launchers include it, so you download it and Xol checks the file. Not started with a real OptiFine file yet."

OptiFine 1.8.9 and OptiFine 1.7.10 run vanilla Minecraft with OptiFine's own tweaker through launchwrapper 1.12. There is no Forge and no Xol client in these profiles, so they report the client brand vanilla. The profile cannot start until you import the OptiFine file. The whole flow is on OptiFine.

Mods you add yourself¶

Every instance has a mods folder, and you can put your own mods into it. The launcher lists files it did not install under Settings ▸ Instance ▸ Mods Xol did not install. It never deletes or changes them.

If one of your files conflicts with a component of the profile, the launcher marks it "conflicts with …" and refuses to start: "Incompatible mod in this instance: … Move it out of the mods folder or use Repair." The check works on file names, against the conflicts listed above (for example OptiFine or FastCraft in a profile that contains Hodgepodge).

Where profiles come from¶

A profile manifest ships inside the launcher. With a valid access key, the launcher may also receive a newer manifest from the Xol service. A remote manifest is only a selection of things the installed build can already do. It is used only if it passes the same validation as the bundled one, its revision is not older than the one in use, and every bundled component hashes to a jar that ships in this build. Otherwise the launcher keeps what it has. Settings ▸ Support ▸ About shows the revision in use and whether it is the bundled or the remote one.