Issue Title
[Compatibility] ClassTweaker Namespace conflict on MC 26.1.2 (official vs intermediary)
Issue Description
Environment:
- Minecraft Version: 26.1.2
- Fabric Loader: 0.19.2
- Mod Version: 4.4.0 (modified
fabric.mod.json to bypass version check)
- Java Version: 25.0.1 (Microsoft)
Description:
I tried to force-run MapLink 4.4.0 on Minecraft 26.1.2. While the version check was bypassed, the game failed to launch during the Knot initialization phase due to a ClassTweaker error.
It seems that the mod's classTweaker file is explicitly looking for the intermediary namespace, but the current 26.1.2 runtime (or the environment provided by the launcher) is using the official namespace.
Error Log Snippet:
Caused by: net.fabricmc.loader.impl.lib.classtweaker.reader.ClassTweakerFormatException: line 1: Namespace (intermediary) does not match current runtime namespace (official)
at net.fabricmc.loader.impl.lib.classtweaker.reader.ClassTweakerReaderImpl.read(ClassTweakerReaderImpl.java:93)
at net.fabricmc.loader.impl.FabricLoaderImpl.loadClassTweakers(FabricLoaderImpl.java:532)
Additional Context:
I noticed Issue #108 mentions that build scripts for 26.1 are working. I'm reporting this to confirm that simply changing the fabric.mod.json dependencies isn't enough due to this mapping discrepancy. Looking forward to the official 26.1 update!
Issue Title
[Compatibility] ClassTweaker Namespace conflict on MC 26.1.2 (official vs intermediary)Issue Description
Environment:
fabric.mod.jsonto bypass version check)Description:
I tried to force-run MapLink 4.4.0 on Minecraft 26.1.2. While the version check was bypassed, the game failed to launch during the Knot initialization phase due to a
ClassTweakererror.It seems that the mod's
classTweakerfile is explicitly looking for theintermediarynamespace, but the current 26.1.2 runtime (or the environment provided by the launcher) is using theofficialnamespace.Error Log Snippet:
Additional Context:
I noticed Issue #108 mentions that build scripts for 26.1 are working. I'm reporting this to confirm that simply changing the
fabric.mod.jsondependencies isn't enough due to this mapping discrepancy. Looking forward to the official 26.1 update!