Fork of PollyMC to add custom login support
Go to file
flow a99858c64d
refactor: move code out of ModIndex.h
Now it's in ModIndex.cpp
2022-05-23 14:43:07 -03:00
.github Merge pull request #614 from txtsd/ccache_release_fix 2022-05-22 16:16:14 +05:30
buildconfig
cmake
launcher refactor: move code out of ModIndex.h 2022-05-23 14:43:07 -03:00
libraries
packages/nix
program_info Fix default install location 2022-05-20 17:23:11 -04:00
.gitattributes
.gitignore
.gitmodules
BUILD.md
CMakeLists.txt chore: bump version 2022-05-22 22:56:52 +02:00
CODE_OF_CONDUCT.md
COPYING.md
default.nix
flake.lock
flake.nix
LICENSE
README.md

PolyMC logo PolyMC logo


PolyMC is a custom launcher for Minecraft that focuses on predictability, long term stability and simplicity.

This is a fork of the MultiMC Launcher and not endorsed by MultiMC. If you want to read about why this fork was created, check out our FAQ page.

Installation

Development Builds

There are per-commit development builds available here. These have debug information in the binaries, so their file sizes are relatively larger. Portable builds are provided for AppImage on Linux, Windows, and macOS.

For Debian and Arch, you can use these packages for the latest development versions:
polymc-git polymc-git
For flatpak, you can use flathub-beta

Help & Support

Feel free to create an issue if you need help. However, you might find it easier to ask in the Discord server.

PolyMC Discord

For people who don't want to use Discord, we have a Matrix Space which is bridged to the Discord server:

PolyMC Space

If there are any issues with the space or you are using a client that does not support the feature here are the individual rooms:

Development Discussion Github Maintainers News Offtopic Support Voice

we also have a subreddit you can post your issues and suggestions on:

r/PolyMCLauncher

Development

If you want to contribute to PolyMC you might find it useful to join our Discord Server or Matrix Space.

Building

If you want to build PolyMC yourself, check Build Instructions for build instructions.

Code formatting

Just follow the existing formatting.

In general, in order of importance:

  • Make sure your IDE is not messing up line endings or whitespace and avoid using linters.
  • Prefer readability over dogma.
  • Keep to the existing formatting.
  • Indent with 4 space unless it's in a submodule.
  • Keep lists (of arguments, parameters, initializers...) as lists, not paragraphs. It should either read from top to bottom, or left to right. Not both.

Translations

The translation effort for PolyMC is hosted on Weblate and information about translating PolyMC is available at https://github.com/PolyMC/Translations

Download information

To modify download information or change packaging information send a pull request or issue to the website Here

Forking/Redistributing/Custom builds policy

Do whatever you want, we don't care. Just follow the license. If you have any questions about this feel free to ask in an issue.

All launcher code is available under the GPL-3.0-only license.

Source for the website is hosted under the AGPL-3.0-or-later License.

The logo and related assets are under the CC BY-SA 4.0 license.