Why point releases matter
Rendering code changes between Minecraft updates, even minor ones. A build compiled for 1.21.10 may call methods that were renamed or moved in 1.21.11. Mod loaders check declared version ranges, so a mismatched jar usually fails at launch instead of running badly, but it is still wasted time.
Finding a 1.21.11 or 1.21.10 build
When you browse the project's file list:
- Filter by the exact game version, not just "1.21".
- Filter by your loader. Fabric, Forge and NeoForge builds are separate files.
- Read the file name and the supported version list. Only use a file that names your version.
If no build lists your exact version yet, wait for one instead of forcing an older file. Updates for new game versions can take some time.
Keeping other mods in step
Entity Culling is often installed together with other performance mods. When you move from 1.21.10 to 1.21.11, update every mod in the profile together. A single stale jar, such as an old dependency, can produce errors that look like they come from Entity Culling.
A simple update routine
- Copy your profile folder as a backup, including saves.
- Install the loader version for the new game version.
- Replace each mod with its build for the new version.
- Launch a test world before opening your main world.
What about the source archive?
The download on this site is the repository's main branch source. It is a snapshot of ongoing development and may already target a later game version, or be mid-change. Treat it as source for building, not as a guaranteed match for 1.21.10 or 1.21.11. The installation guide covers both routes.
Common questions on 1.21
If a 1.21 profile crashes after adding the mod, the cause is usually a version or loader mismatch. The troubleshooting guide walks through reading the crash screen.
