The checks used are roughly the same as the ones proposed in the clang-tidy PR (except perhaps that I used modernize-* instead of listing them individually,though I don't think this caused any readability detriments). In ModrinthModel.cpp and FlameModModel.cpp I ignored the modernize-avoid-c-arrays one, mostly because making the sorts array an std::array would most likely increase the code complexity because of the virtual function. Aside from that, the static_cast warning from Application.h was not dealt with, since it's not in this PR's scope. |
||
---|---|---|
.github | ||
buildconfig | ||
cmake | ||
doc | ||
launcher | ||
libraries | ||
packages/nix | ||
program_info | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
BUILD.md | ||
CMakeLists.txt | ||
CODE_OF_CONDUCT.md | ||
COPYING.md | ||
default.nix | ||
flake.lock | ||
flake.nix | ||
LICENSE | ||
README.md |
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. The PolyMC community felt that the maintainer was not acting in the spirit of Free Software so this fork was made.
Installation
- All downloads and instructions for PolyMC can be found here
- Last build status: https://github.com/PolyMC/PolyMC/actions
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:
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.
For people who don't want to use Discord, we have a Matrix Space which is bridged to the Discord server:
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
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.md 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 infomation
To modify download infomation or change packaging infomation 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.