Fork of PollyMC to add custom login support
Go to file
Matej Kafka 7da2fd5b8b
Update BUILD.md
Extended description of Windows build process based on about 6 hours wasted on trial and error.
2020-10-25 03:54:59 +01:00
.github Remove travis-ci and github actions leftovers 2019-11-26 21:09:37 +01:00
api NOISSUE remove obsolete TODO comment from SolderPackInstallTask 2020-10-13 22:20:28 +02:00
application NOISSUE give technic icon a darker outline 2020-10-13 22:35:43 +02:00
buildconfig GH-3095 New FTB platform support 2020-08-21 02:24:29 +02:00
cmake NOISSUE get rid of remaining tabs 2018-08-02 01:01:55 +02:00
libraries NOISSUE add 'java.vendor' to the checker and display/log the value 2020-09-07 22:28:41 +02:00
.gitattributes NOISSUE reorganize unit tests to be placed next to the code they test. Nuke more dead tests. 2016-05-01 00:02:15 +02:00
.gitignore NOISSUE remove some dead things 2019-09-26 20:08:47 +02:00
.gitmodules NOISSUE tabs -> spaces 2018-07-15 14:51:05 +02:00
BUILD.md Update BUILD.md 2020-10-25 03:54:59 +01:00
changelog.md NOISSUE update version number, changelog and credits in about dialog 2020-03-29 03:12:57 +02:00
CMakeLists.txt GH-3234 Add support for custom meta URLs at build time 2020-07-18 16:22:05 +02:00
COPYING.md Remove some old forge hacks 2020-05-19 15:13:16 +02:00
README.md NOISSUE Attempt to add build status and test teamcity build reporting 2019-11-27 00:35:42 +01:00

MultiMC logo

MultiMC 5

MultiMC is a custom launcher for Minecraft that allows you to easily manage multiple installations of Minecraft at once. It also allows you to easily install and remove mods by simply dragging and dropping. Here are the current features of MultiMC.

Development

The project uses C++ and Qt5 as the language and base framework. This might seem odd in the Minecraft community, but allows using 25MB of RAM, where other tools use an excessive amount of resources for no reason.

We can do more, with less, on worse hardware and leave more resources for the game while keeping the launcher running and providing extra features.

If you want to contribute, either talk to us on Discord, IRC(esper.net/#MultiMC) or pick up some item from the github issues workflowy - there is always plenty of ideas around.

Building

If you want to build MultiMC yourself, check BUILD.md for build instructions.

Code formatting

Just follow the existing formatting.

In general:

  • Indent with 4 space unless it's in a submodule
  • Keep lists (of arguments, parameters, initializators...) as lists, not paragraphs.
  • Prefer readability over dogma.

Translations

Translations can be done on crowdin.

Forking/Redistributing

We keep MultiMC open source because we think it's important to be able to see the source code for a project like this, and we do so using the Apache license.

Part of the reason for using the Apache license is we don't want people using the "MultiMC" name when redistributing the project. This means people must take the time to go through the source code and remove all references to "MultiMC", including but not limited to the project icon and the title of windows, (no MultiMC-fork in the title).

Apache covers reasonable use for the name - a mention of the project's origins in the About dialog and the license is acceptable. However, it should be abundantly clear that the project is a fork without implying that you have our blessing.

License

Copyright © 2013-2019 MultiMC Contributors

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this program except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Build status

Linux (Intel32)

Build: Deploy:

Linux (AMD64)

Build: Deploy:

macOS (AMD64)

Build: Deploy:

Windows (Intel32)

Build: Deploy: