Incompatible with 1.21.1
ColonalLive opened this issue ยท 9 comments
Workaround until this is fixed:
- Extract the jar file
- Open
fabric.mod.json
inside the unzipped directory - Remove the line that contains
"minecraft": "1.21"
- Rezip the contents (make sure that you don't have a nested directory in the zip!)
- Rename the .zip to .jar
or use my file where I already did this:
entityculling-fabric-1.6.6-mc1.21.jar.zip (GitHub only supports .zip files so you have to extract the .jar file!)
Recommended fix for the future from my side:
Instead of depending
on a version simply recommend
it.
Basically remove this line:
And add
"recommends": {
"minecraft": "${minecraft_version_range_fabric}"
},
instead.
This doesn't cause a hard crash and instead shows a warning inside the log.
Workaround until this is fixed:
1. Extract the jar file 2. Open `fabric.mod.json` inside the unzipped directory 3. Remove the line that contains `"minecraft": "1.21"` 4. Rezip the contents (make sure that you don't have a nested directory in the zip!) 5. Rename the .zip to .jar
or use my file where I already did this: entityculling-fabric-1.6.6-mc1.21.jar.zip (GitHub only supports .zip files so you have to extract the .jar file!)
Recommended fix for the future from my side: Instead of
depending
on a version simplyrecommend
it. Basically remove this line:And add
"recommends": { "minecraft": "${minecraft_version_range_fabric}" },
instead. This doesn't cause a hard crash and instead shows a warning inside the log.
https://github.com/Razuuu/EntityCulling/releases/download/1.6.7/entityculling-fabric-1.6.7-mc1.21.jar
My release fixes start with 1.21.1 - just download and paste it
There are no major changes, it's like 1.20.5 to 1.20.6, use a dependency override for now
I even changed the files and in them the versions from 1.21 to 1.21.1 but I still have the same problem
I'm not at home currently. Also noteworthy that this only affects fabric(forge/neoforge treat 1.21.1 as 1.21) and that there is no reason or benifit to update clients to 1.21.1. So for now till I have time to roll out updates to all mods, just ignoring 1.21.1 is the solution. (or dependency override/changing the json, if you really want to use 1.21.1 for whatever reason)