Moving on

multimc

PolyMC emerged out of frustration with the MultiMC project and therefore brought controversy with it.
In short, the original founders of PolyMC had disagreements with the maintainer of MultiMC and the project's direction.
These disagreements were turned into a takeover of packaging on Arch Linux by the PolyMC founders, something that, understandably, the MultiMC maintainers took as sabotage.
After MultiMC dropped support for third-party packaging, the seeds for PolyMC were laid.

As a side note, we want to mention that we do not approve the actions of community members that used these controversies as a basis to harass MultiMC developers.
Please refrain from brigading other communities.
It only causes harm on both sides.

PolyMC's inception is very controversial by its very nature.
The founders have decided to sublicense PolyMC under the terms of the GNU General Public License 3 (GPL-3), which made it impossible for MultiMC to take contributions, without re-licensing to GPL-3 as well.
As a result the MultiMC team have decided to burn bridges with PolyMC.
This was manifested after access to the metadata service, provided by MultiMC, was blocked for all PolyMC users.
All versions prior to 1.0.6 do not work anymore, as they try to reach MultiMC servers instead of our own.

In an effort to prepare for our upcoming 1.1.0 release, we wanted to contact the MultiMC maintainer to see, if they want to be credited in our documentation.
Sadly, our request was dismissed, and most of our team members were banned from the official MultiMC Discord server for being associated with PolyMC.

Screenshot of public chat with MultiMC maintainer

This has sparked many internal discussions both at PolyMC and MultiMC.
In the end, we concluded that we will be moving on from our origins as a packaging-friendly fork of MultiMC.

In our upcoming 1.1.0 release, you will be able to use new features that will differentiate PolyMC from MultiMC.
The major new feature is the integrated mod downloader that supports Modrinth and CurseForge mods.
We also plan to clean the codebase, remove obscure or old features and cruft in an effort to make it easier for new contributors to start working on PolyMC.

Additionally, we have reorganized PolyMC since its inception to be more community-centric.
One of the founders has stepped down as a maintainer, and we have formed the PolyMC Core Team.
You can read more about it in this blogpost.

We want to decouple this project from its controversial origins and start work on a powerful Minecraft launcher.
While we are working on getting 1.1.0 out, check out our future plans:

Sneak peek of future plans:

If you want to be involved in PolyMC, check out the following links:

Never dig straight down!

~ PolyMC Core Team

Comment Rules

By submitting a comment, you agree to uphold the Prism Launcher Code of Conduct.

✅ What user-contributed comments are for

  • Share additional information relevant to the article.
  • Mention a workaround for a common issue.
  • Link to useful third-party resources that are relevant to the current page, such as tutorials or articles.
    • It is allowed to occasionally link to resources you've created. When doing so, you must disclose your affiliation with the resource in some way. However, linking to resources you've created should not represent the majority of your interactions with user notes. Excessive self-promotion is not allowed and will be moderated away.

🚫 What user-contributed comments are not for

Comments not following the above rules will be removed.

Licensing of user-contributed comments

Launcher contributors may occasionally go through the comments and may incorporate information from them in the documentation. By submitting a comment, you accept that it may be incorporated in unmodified or modified form in the launcher and/or documentation, subject to the GPL-3.0 license for the launcher and AGPL-3.0 license for the documentation.