Polymerium vs Prism Launcher

Last updated on

Overview

Polymerium and Prism Launcher are both open-source Minecraft launchers that support multiple instances, mod loaders and modpack platforms, and both can customize an instance's launch data through patch or component declarations. They differ mainly in how an instance is stored and rebuilt.

Key Difference at a Glance

Feature Comparison

Storage & Disk Usage

Both launchers share Minecraft's assets, libraries and Java runtimes, so the practical difference is mod files rather than game files. Polymerium links every mod from one cache. Prism Launcher stores a copy per instance unless you copy an instance with its link or clone options; files installed from its Central Mods folder are copied too.

Instance Architecture

Polymerium's directory model:

instances/my-pack/
├── import/    ← Pack Source
├── persist/   ← Local Data you explicitly preserve
└── build/     ← Run Directory Minecraft writes to

This separation means:

• Modpack updates don't overwrite data you've placed in Local Data (persist/)
• Resets can delete saves stored only in the Run Directory (build/), so worlds must be moved to persist/saves/ before they are protected
• Reproducible game files in the Run Directory can be rebuilt from metadata and cache

Mod Loader Support

Prism Launcher additionally installs LiteLoader and can filter its mod browser by several legacy loaders (Ornithe, LegacyFabric, Rift, Babric, BTA), although those cannot be installed from the launcher either. Polymerium supports the four main loaders as first-class choices and covers other runtimes through patch documents.

GTNH & Cleanroom Support

GTNH and Cleanroom ship launch data that a Minecraft version and a mod loader cannot describe, and both are distributed for component-based launchers: GTNH publishes a Prism ZIP, and Cleanroom publishes a MultiMC instance. Prism Launcher is their intended target and consumes the component definitions directly. Polymerium is not the target, but it reads the same definitions and converts them into native patches, so these instances deploy and launch through the ordinary pipeline without per-modpack support code.

Modpack Import/Export

Account Management

Mod Management

A deployment rule in profile.json (setup.rules) looks like this:

{
  "selector": {
    "type": "and",
    "children": [
      { "type": "repository", "repository": "curseforge" },
      { "type": "kind", "kind": "dataPack" }
    ]
  },
  "destination": "datapacks/"
}

destination is a folder, and the file name is kept. Rules can also be edited from the instance's Setup page.

Advanced Features

Platform & Localization

Open Source & Licensing

When to Choose Each

Choose Polymerium if you:

• ✅ Want one mod file shared by every instance instead of a copy per instance
• ✅ Frequently switch between mod loaders or modpack versions
• ✅ Develop or maintain modpacks (Git-friendly workflow)
• ✅ Want to experiment safely (snapshots)
• ✅ Need third-party auth (Authlib Injector) or an offline or trial account
• ✅ Prefer Chinese localization
• ✅ Want AI agent automation (MCP mode)
• ✅ Need per-package deployment control (rules engine)

Choose Prism Launcher if you:

• ✅ Prefer a plain instance folder you can edit, copy and back up by hand
• ✅ Need GPL-3.0 licensing for your project
• ✅ Install legacy loaders such as LiteLoader
• ✅ Want link-based or copy-on-write instance copies
• ✅ Want file-based custom themes, icon themes and cat packs
• ✅ Want the launcher GTNH and Cleanroom are actually packaged for
• ✅ Want a mature, battle-tested launcher with a large translation community

Where Polymerium Differs

MCP Mode & AI Integration

Polymerium's trident --mcp server lets an AI agent create instances, inspect and add packages, and export modpacks. It does not expose snapshot, deployment, or game-launch tools: create snapshots in the desktop app, and deploy or launch from the desktop app or CLI. Prism Launcher has no MCP integration.

Snapshots & Diff

Save managed instance state before making changes, then restore or compare later. Great for:

• Testing mod updates
• Experimenting with configurations
• Debugging crashes
• Rolling back broken setups

Git-Friendly Modpack Development

Your instance source is clean: profile.json + import/ + icon + README + CHANGELOG. Add a .gitignore to exclude build/ and persist/, and you have a version-controlled modpack ready for collaboration.

Feature Matrix (Full)

Summary

Polymerium and Prism Launcher both manage Minecraft instances, loaders and modpacks, and both can customize an instance's launch data instead of shipping a fixed pipeline. The practical differences are where that data lives and how instances are stored.

• Polymerium keeps an instance as metadata plus a shared cache: mod files are linked rather than copied, Local Data is protected across updates, and instance state can be snapshotted and diffed. It also ships a CLI and an MCP server, and runs component-based instances such as GTNH and Cleanroom by converting their declarations into native patches.

• Prism Launcher keeps each instance as a self-contained folder. It is the launcher GTNH and Cleanroom are packaged for, installs LiteLoader, supports link-based and copy-on-write instance copies, and offers file-based custom themes and a large translation community.

Both are solid choices — pick the one whose instance model matches how you work.