mc-launcher.tayou.org

The table on mc-launcher.tayou.org is a feature matrix: each row is a Minecraft Java Edition launcher and each column is a comparable attribute — license, look & feel, supported platforms, implementation languages, core toolkits, and modloader/CurseForge support. Read it by first filtering to the launchers you're considering, then scanning across those rows for the attributes that matter to you. Treat the data as a starting point rather than a verdict: the site itself notes the list is community-maintained and will get outdated.

What the columns mean

The two columns that need explanation

Modloader support

The site defines this narrowly: it means a way to install the modloader through the launcher directly, without downloading it separately. So a launcher marked as supporting this lets you pick a modloader version inside the app and have it set up for you. A launcher without it isn't necessarily unable to run modded Minecraft — you'd just handle the modloader installation yourself. If your workflow is "install a modpack and play," favor launchers with this feature.

CurseForge blocked downloads

CurseForge lets creators opt out of downloads from third-party platforms, so that ad revenue is generated when content is downloaded through CurseForge itself. Platforms therefore have to work around that restriction to properly support CurseForge content. In practice, this column tells you how well a given launcher copes with that restriction — a launcher that handles it well will still let you install affected content, while one that doesn't may fail or require manual steps for those specific mods and modpacks.

A practical reading order

1. Filter by platform. Remove every launcher that doesn't support your OS. This usually cuts the list the most.
2. Filter by license if open source matters to you.
3. Check modloader support and CurseForge handling if you play modded — these two determine how much manual work modpack installs will cost you.
4. Compare look & feel and toolkits last, as tie-breakers between launchers that already meet your functional needs.

For example, if you're on Linux, want an open-source launcher, and install modpacks regularly, steps 1–3 will narrow the table to a handful of rows, and the remaining columns only decide which of those you prefer to look at every day.

Caveats before you decide

• The site states the list is maintained mostly by its author plus random contributions, and that data will inevitably get outdated. Verify version-specific or recently changed details (especially license and platform support) against the launcher's own site before committing.
• The table compares features, not quality — two launchers can both "support" a feature with very different reliability. Use the table to build a shortlist, then try the top candidate on your own setup.
• The page also exposes a theme selector and a filter/reset control for the launcher list; these change how the comparison is displayed, not the underlying data.

mc-launcher.tayou.org compares 14 Minecraft Java Edition launchers and, for each one, lists a license, supported platforms, look-and-feel options, implementation languages, and core toolkits. The license column is where you check open-source status: entries range from GPLv3 and LGPL-2.1 to MS-PL, AGPL3, "source available," and proprietary. The platforms column tells you whether a launcher runs on Linux, Windows, or MacOS, and in a few cases Android or iOS. Use these two columns together — a permissively licensed launcher is only useful to you if it runs on your operating system.

What the license column actually tells you

The site lists licenses per launcher rather than grouping them by type, so read each row individually. Based on the comparison table, the entries fall into these groups:

Two distinctions matter when you read this column. First, "source available" is not the same as an open-source license: QWERTZ Launcher's code can be viewed, but the site does not label it with an OSI-style license the way it does for the GPL entries. Second, the GDLauncher rows are split into "Carbon" and "Legacy," and both carry the same GPLv3-or-newer label — the difference between them shows up in the language and toolkit columns, not the license.

If open-source status is a hard requirement for you, the GPL, LGPL, MS-PL, and AGPL rows are the ones to shortlist. If you only care that a launcher works, the license column is informational and the platforms column becomes the deciding factor.

Checking platform support before you commit

The platforms column is the practical filter. Every launcher in the table lists Linux, Windows, and MacOS except where noted, and the exceptions are worth knowing:

• PoJavLauncher is the only entry listing Android and iOS instead of desktop operating systems.
• QWERTZ Launcher lists Windows and Linux but not MacOS.
• Technic Launcher lists Windows, Linux, and MacOS.
• Vanilla Launcher (old) lists Windows and MacOS but not Linux, while the current Vanilla Launcher lists all three.

So if you are on Linux and want the official launcher, the table points you to the current Vanilla Launcher rather than the old one. If you are on MacOS and were considering QWERTZ Launcher, the table says it is not an option there.

The site's own explanation adds a caveat you should carry into any decision: the list is maintained mostly by one person plus random contributions, and the data "will inevitably get outdated over time." Treat the license and platform entries as a starting point to verify against each launcher's own project page, especially for fast-moving projects.

How look-and-feel, language, and toolkit columns add context

These columns are secondary but help you interpret the license and platform data.

Look & Feel describes how customizable the interface is. Most launchers are marked "Custom," with several noting "(configurable)." MultiMC and Prism Launcher are marked "System (configurable)" and "System (mostly)" respectively, and Vanilla Launcher is "Minecraft Official." This column does not affect licensing or platform support, but it tells you whether a launcher's UI can be reshaped to your preferences.

Languages lists the implementation stack, and it is the clearest signal of how a launcher is built:

• Java-based: ATLauncher, MultiMC, Technic Launcher, Vanilla Launcher, Vanilla Launcher (old)
• Web-tech stacks (HTML, JS, CSS, often with Rust or Java): CurseForge App, FTB App, GDLauncher Carbon, GDLauncher (Legacy), Modrinth App, QWERTZ Launcher
• C++: Prism Launcher
• Java and C: PoJavLauncher

Core Toolkits and Libraries goes one level deeper — Swing for ATLauncher, React and Next.js for CurseForge App, and so on. For most users this is background information; it matters mainly if you want to contribute to a project or judge how actively its stack is maintained.

A practical way to use the table

1. Filter by platform first. Find the rows that list your operating system. This immediately removes launchers that cannot run for you.
2. Then check the license. If you need open-source code, keep only the GPL, LGPL, MS-PL, and AGPL rows. If you need to avoid proprietary software, drop CurseForge App and both Vanilla Launcher entries.
3. Use look-and-feel and language columns to break ties. Among launchers that pass steps 1 and 2, pick based on whether you want a configurable UI and whether the implementation stack matters to you.
4. Verify before installing. Because the site warns its data can go stale, confirm the license and platform list on the launcher's own repository or download page.

The site also includes a theme selector (tayou, light, dark, and many named themes such as nord, dracula, and synthwave) and a filter for launchers, but these are display options for the comparison page itself, not properties of the launchers being compared.

The site accepts corrections and updates through the GitHub repository linked in its header. The comparison page itself states that the list is "maintained mostly by me and random contributions," that data "will inevitably get outdated over time," and that updates and corrections are always welcome. There is no on-page submission form or email address mentioned, so GitHub is the documented route. Because the site does not describe its contribution workflow, check the linked repository for the current process (issues, pull requests, or another channel) before submitting.

What the site says about its data

The page is explicit about the limits of its own accuracy:

• The launcher list and feature table are maintained mostly by one person, supplemented by random contributions.
• Data is expected to become outdated over time.
• Updates and corrections are welcomed, with the GitHub link in the header given as the place to go.

This matters when you spot an error: the site already anticipates that entries will drift, so a specific, verifiable correction is the kind of input it asks for.

What a useful correction looks like

The comparison table is organized by launcher (rows) and feature (columns). A correction is easiest to act on when it names both, states the current value, and gives the corrected value with a source.

The same pattern applies to other columns visible on the page, such as Look & Feel, Platforms, Languages, and Core Toolkits and Libraries. For a missing launcher, say which row should be added and supply the same feature values so it can be placed in the table consistently.

Step-by-step: submitting through GitHub

1. Open the GitHub link in the site header. This is the only contribution route the page names. Confirm which repository it points to before doing anything else.
2. Check for an existing issue or pull request covering the same launcher or feature. Duplicates slow down review, and an existing thread may already contain the maintainer's position.
3. Choose the channel the repository actually uses. If issues are enabled, an issue describing the correction is the lowest-friction option. If the repository expects pull requests for data changes, edit the relevant data file and open a PR. The site does not specify which, so follow what the repository shows.
4. Write the change as a before/after pair. Include the launcher name, the exact column, the current text, the proposed text, and a source link. Keep it to one topic per issue or PR where practical.
5. Verify the result. After the change is merged, reload the comparison page and confirm the row or column now shows the corrected value. If the page caches content, a hard refresh may be needed before the update appears.

Expected result: your correction is either merged into the table or discussed with the maintainer, and the public page reflects the agreed value.

Common sticking points

• No visible contribution instructions on the site. The page points to GitHub but does not spell out the process. Treat the repository's own README, issue templates, and contribution guidelines as the authoritative instructions.
• Corrections without sources. Because the maintainer cannot independently verify every launcher, a correction backed by an official project page, license file, or release note is far more likely to be accepted than an assertion alone.
• Disagreements about definitions. The page defines terms such as modloader support ("a way to install the modloader through the launcher directly, without downloading it separately") and explains CurseForge blocked downloads. If your correction depends on a different definition, quote the site's definition and explain why the entry does not match it.
• Scope creep. A single issue that rewrites many rows is harder to review than several focused ones. Split unrelated corrections.
• Stale local copies. If you are comparing against a saved copy of the page, re-check the live table first; the entry may already have been fixed.

When GitHub is not the right route

If the header link is broken or the repository has issues and pull requests disabled, the site offers no alternative contact method in the material shown. In that case, the practical options are to wait for the maintainer to reopen a channel or to keep your correction documented with sources so it can be submitted once a route exists. Do not assume an unlisted email or form is monitored.

Minecraft Launcher Comparison is a community-maintained reference site that puts Minecraft Java Edition launchers side by side in a single feature table. It is useful when you are choosing a launcher and want to compare licenses, supported platforms, interface style, and implementation details without visiting each project's site. It is not an official Mojang or launcher-vendor resource, and its own note warns that the data will get outdated over time and that corrections are welcome via the GitHub linked in the header.

What the site covers

The site's stated purpose is to give "an overview over the various Minecraft (Java Edition) launchers and their features." The launcher list it presents includes:

• ATLauncher
• CurseForge App
• FTB App
• GDLauncher (Legacy) and GDLauncher Carbon
• Modrinth App
• MultiMC
• PoJavLauncher
• Prism Launcher
• QWERTZ Launcher
• Technic Launcher
• Vanilla Launcher and Vanilla Launcher (old)

The page also includes a theme selector (tayou, light, dark, and many named themes such as nord, dracula, and synthwave), which changes how the comparison table is displayed but not the underlying data.

The comparison dimensions

The feature table compares launchers across these attributes:

The site also defines two terms that matter when comparing launchers:

• Modloader support means the launcher can install a modloader directly, without you downloading it separately.
• CurseForge blocked downloads refers to CurseForge letting creators opt out of downloads from third-party platforms to protect ad revenue; launchers must work around that restriction to support CurseForge content properly.

How to use it when choosing a launcher

1. Open the site and use the launcher filter to narrow the list to the candidates you are considering.
2. Check the Platforms row first — this immediately rules out launchers that don't run on your operating system.
3. Compare License if open-source matters to you; the table distinguishes GPL-family and other open licenses from proprietary entries.
4. Read Look & Feel and Core toolkits if interface style or app performance/architecture is a priority.
5. Cross-check anything decisive against the launcher's own site, since the comparison page itself notes its data can become outdated.

A practical example: if you use Linux and want an open-source launcher with a configurable interface, the table lets you filter to Linux-capable entries and then compare their licenses and look-and-feel descriptions in one pass, rather than opening a dozen project pages.

What it is not

The site is a reference table, not a download host, tutorial, or support forum. It does not appear to offer accounts, pricing, or hosted services based on the available page content. Treat it as a starting point for comparison and verify current details — especially licensing and platform support — at each launcher's official source before committing.

The site compares 13 Minecraft Java Edition launchers in a single filterable table: ATLauncher, CurseForge App, FTB App, GDLauncher (Legacy), GDLauncher Carbon, Modrinth App, MultiMC, PoJavLauncher, Prism Launcher, QWERTZ Launcher, Technic Launcher, Vanilla Launcher, and Vanilla Launcher (old). For each one it lists license, look and feel, supported platforms, implementation languages, and core toolkits. Use it to narrow the field by operating system and by whether you want open-source code or a vendor-run app; it does not rank launchers or recommend one.

What the table actually covers

The site describes itself as an overview of Minecraft (Java Edition) launchers and their features. Two definitions sit above the table and matter when reading it:

• Modloader support means the launcher can install a modloader directly, without you downloading it separately.
• CurseForge blocked downloads refers to creators opting out of third-party downloads to protect ad revenue on CurseForge; platforms must work around that restriction to support CurseForge content properly.

The page also notes the list is maintained mostly by one person plus random contributions, so data will get outdated over time. Treat it as a starting point, then confirm current details on each launcher's own site.

Comparing launchers on the same dimensions

License: open source vs proprietary

If license terms matter to you — for auditing, redistribution, or contributing fixes — this column alone eliminates several options.

Platform support

• Windows, Linux, and macOS: ATLauncher, CurseForge App, FTB App, GDLauncher Carbon, GDLauncher (Legacy), Modrinth App, MultiMC, Prism Launcher, Technic Launcher, Vanilla Launcher (old).
• Windows only: QWERTZ Launcher and the current Vanilla Launcher.
• Android and iOS: PoJavLauncher is the only mobile option in the list.

So if you play on a Mac or Linux machine, cross off QWERTZ, the current Vanilla Launcher, and PoJavLauncher first.

Look and feel

Most entries offer a custom interface, several configurable: ATLauncher (custom, configurable), CurseForge App (custom), FTB App (custom), GDLauncher Carbon (custom), GDLauncher (Legacy) (custom), Modrinth App (custom), MultiMC (system, configurable), Prism Launcher (system, configurable), QWERTZ Launcher (system, mostly), Technic Launcher (custom), and Vanilla Launcher (Minecraft official). PoJavLauncher is listed as Minecraft-inspired, and Vanilla Launcher (old) as Java Swing.

The site's theme selector (tayou, dark, light, and many named themes such as nord, dracula, and synthwave) changes the comparison page's appearance, not the launchers themselves.

Implementation languages

The table lists what each launcher is built with — for example Java for ATLauncher and Technic Launcher, HTML/JS/CSS plus Java for CurseForge App, Rust and TypeScript for GDLauncher Carbon, C++ for MultiMC and Prism Launcher, and Python for QWERTZ Launcher. This is mainly useful if you plan to read or contribute to the code.

How to use the table to pick a launcher

1. Filter by your OS. Keep only launchers that list your platform.
2. Decide on license. If you want open source, keep ATLauncher, GDLauncher Carbon, Modrinth App, MultiMC, Prism Launcher, QWERTZ Launcher, or FTB App.
3. Check the feature you rely on. If you install modloaders regularly, confirm the launcher supports direct modloader installation; if you download from CurseForge, check how it handles blocked downloads.
4. Verify before committing. Because the page warns its data ages, confirm the current version, platform list, and CurseForge behavior on the launcher's own download page.

Quick matching by need

• Instance management on desktop: MultiMC and Prism Launcher are the entries built around managing separate instances.
• Mobile play: PoJavLauncher is the only Android/iOS option listed.
• Open-source with broad platform support: ATLauncher, Prism Launcher, MultiMC, Modrinth App, or GDLauncher Carbon.
• Official client: Vanilla Launcher (current, Windows only) or Vanilla Launcher (old) for the legacy client.

Common sticking points

• The table shows capabilities, not quality — a launcher appearing in it says nothing about performance or stability.
• "Source available" for GDLauncher (Legacy) is not the same as an open-source license; read the terms if that distinction matters.
• Platform lists change between releases; a launcher marked Windows-only here may have gained support since the page was last updated.
• The CurseForge blocked-downloads note affects what content a third-party launcher can fetch, so check that behavior for any launcher you choose primarily for modpack browsing.