MineSrcManager is a CLI tool for creating and applying patches to Minecraft's source code
MineSrcManager is a 'patching' tool that is capable of both exporting and applying modified code, assets, and binary data from a selection of minecrafts source code, allowing the user to rebuild the source code/build by simply reading 'instructions'.
-
Minecraft: Legacy Edition (full source code)
-
4jCraft (Custom Legacy edition fork, different source tree, linux support)
-
Minecraft: Pocket Edition 0.6.2 source code (sometimes refered to as 0.6.1 in source code)
-
Minecraft: Dungeons Prototype build (bedrock)
-
Minecraft: Dungeons source code (Unreal Engine)
-
Minecraft: Legends Prototype build (bedrock)
While everyone is contributing to forks and modifications of these source codes, one issue linger, sharing copyrighted code and assets. Sharing these files and code can risk the fork from being taken down my Mojang and Microsoft, and thus modding on these versions can be risky for a DMCA takedown. Now, some forks uses a method of requiring the source code to work, but this raises another issue, while this can minigate any unmodified code, the modified code still contain Microsoft's code, and thus can still be considered DMCA. My solution is using instructions files, only keeping track of what's been added and deleted in a file, and allowing users to 'patch' these instructions to their source code copy, getting the modified code in full. This allows forks to remain public while minimizing copyright infringement.
A full tutorial for applying and exporing patches is located in Tutorial.md, an .mcm file template is also located in /template
A: NO! This program does not contain any copyrighted source code. You must provide the source code yourself, you can either download all supported source code/builds, or you can only install the code/build that's needed for your personal needs
A: No, this project is not a mod launcher, it's a source code patch tool. A mod launcher can use this tool to make their mod launcher open source, but this project in of itself is not a mod launcher
A: 4JCraft not only allows the compiling of Linux (The main platform I use), but also has a completely different code structure, which can desync any regular Legacy patch and vise-versa
A: While least experimented on and source code unavailable, these builds can still be used for mods, like custom levels and assets
A: For any new asset/binary in the patch, they will just simply get duplicated, while binary is more on the grey side, assets should have the same rules as creating your own resource pack. Thus any modified assets and binaries will just be copied to both the patched codebase and the modified code
A: No, MSM only reads these files. Any and all modifications will take effect in the defined output directory
A: Nothing is guaranteed, Microsoft can take you down for any reasons, but using this patch system does reduce the risk by a long shot (unless they use AI for github moderation lol)
A: Yes, this is under the MIT license after all, all you need to do is just give credit somewhere. I also recommend a link to this project if someone wants to build it
A: Yes, however make sure you give credit! And keep in mind that your copy might get outdated in the future (if I continue to update this)
A: Put all bugs/features in the 'issues' tab on github
This project is under the MIT license
NOTICE: THIS PROJECT AND SOFTWARE IS NOT AFFILIATED NOR ENDORSED BY MOJANG, MICROSOFT, AND 4J STUDIOS
THIS SOFTWARE DOES NOT CONTAIN ANY LEAKED CODE FROM MICROSOFT, MOJANG AND 4J STUDIOS. THE SOURCE CODE MUST BE PROVIDED YOURSELF AND WAS MADE TO RESPECT THE MINECRAFT IP AS MUCH AS POSSIBLE. WE ARE NOT RESPONSIBLE FOR ANY LEGAL ISSUES YOU CAN FACE.