Releases: Juuxel/unprotect
Releases · Juuxel/unprotect
Unprotect 2.0.2
Fixed
- NeoForge classes are no longer transformed since it's not needed and it breaks running the server (architectury/architectury-loom#305)
Unprotect 2.0.0
Changed
- Unprotect is now split into separate jars for the library and Java agent, the ModLauncher plugin and the FancyModLoader class processor
Unprotect 1.4.0
Added
- Compatibility with FancyModLoader 10+
Changed
- There is now a log message saying which backend is used
- NeoForge classes are transformed to match Forge behaviour
Unprotect 1.3.1
Fixed
- Compatibility with new versions of NeoForge's FancyModLoader that have inlined the ModLauncher code into FML
Unprotect 1.3.0
Added
- Support for running Unprotect as a Java agent
Unprotect 1.2.0
Added
- System property
unprotect.mappingsfor specifying mapping zip location
Changed
- Minimum Log4J API downgraded to 2.11.0
Unprotect 1.1.0
Added
- System property
unprotect.target(UnprotectLaunchPlugin.TARGET_SYSTEM_PROPERTY`) for configuring how to apply Unprotectall: enabled for every class (default behaviour in 1.0)minecraft+forge: enabled for Minecraft and Forge classes only (new default behaviour in 1.1)- This is determined based on Tiny v2 mappings located on the classpath at
/mappings/mappings.tiny, or if that is absent, based on the package namesnet.minecraft.*andcom.mojang.*.net.minecraftforge.*is always included.
- This is determined based on Tiny v2 mappings located on the classpath at
none: completely disabled
Changed
- Unprotect jars are now multi-release jars
- module-info is now in
META-INF/versions/16 - module-info now contains the Unprotect version
Fixed
- Applying to mod classes by default, causing issues with hot swap