unified minecraft modding environment with support for legacy environments.
for details on usage, see USAGE.md
In order to better support buildscripts. when I plan on making big/breaking changes, I will leave an LTS branch behind. In effect, this means that I always support the previous minor version for bugfixes.
By consequence, seeing as it's only bugfixes, snapshots on the LTS branch are considered relatively stable as well.
- Fabric
- Quilt
- Forge
- Neoforge
- Modloader
- JarModAgent
- Flint Loader
- just plain jarmodding
- Rift
- Bukkit Derrivitives (at least paper)
- LiteLoader
- Sponge
- NilLoader
yes, this is possible, see PrcraftExampleMod and it's buildsrc dir.
- stop using artifactural
- rework mcpconfig runner to be more kotlin and less old version of arch-loom code
- Support for launch configs in other dev envs
- vscode
- eclipse
- support to login to minecraft in dev
- support to launch with the prod jar
- add datagen support
- forge datagen
- fabric datagen
- quilt datagen
- fix yarn on neoforge (these will probably be agents, possibly in separate projects and pulled like JarModAgent)
- inject remapper into ASMAPI
- reflection remapper (also for forge potentially, or in general).
- genSources should apply forge source patches (at least on fg3+)
- take one of the versions from testing
- remove
includeBuild('../../')
fromsettings.gradle
- put a proper version number for the plugin in
build.grade
- direct porting of arch-loom projects without changing the directory structure is possible.
- instructions pending...
- arch style: https://github.com/firstdarkdev/fdd-xplat or https://github.com/LegacyModdingMC/examplemod
- //todo: add more