Entity Culling
Installez Entity Culling localement sur votre ordinateur, pas sur le serveur.
- Téléchargements
- 160,317,134
- Versions supportées
- b1.7.3, 1.7.10, 1.8.8, 1.8.9, 1.12.2, 1.16, 1.16.1, 1.16.2, 1.16.3, 1.16.4, 1.16.5, 1.17, 1.17.1, 1.18, 1.18.1, 1.18.2, 1.19, 1.19.1, 1.19.2, 1.19.3-pre1, 1.19.3-pre2, 1.19.3, 1.19.4, 1.20, 1.20.1, 1.20.2, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2
- Catégories
- optimization
Entity Culling: Cutting Client-Side Rendering Load
Entity Culling uses async path-tracing to hide blocks and entities that aren't actually visible to the player, trimming unnecessary rendering work. With over 130 million downloads, it's one of the most established optimization mods in the Fabric and Forge space — and it is strictly client-side.
Since it only affects local rendering and never touches server logic, there's no reason to put it in your server's mods folder. Recommend it to your players instead, especially on busy servers with large farms, mob spawners, or crowded builds where lots of entities are on screen at once.
Pairing tip: Combined with ImmediatelyFast and Sodium, Entity Culling rounds out a solid client-side trio against FPS drops in entity-heavy areas — none of the three do anything for the server itself.
Plan the rollout and operation
Entity Culling is a local optimization and should be evaluated in difficult locations rather than only at the main menu. Test large storage rooms, many item frames, animals, particles, and transparent blocks with the mod enabled and disabled. If objects disappear too early, adjust the client configuration or remove it from the profile first. Copying it to the server improves neither world tick rate nor server memory use.
For a clean rollout, create a separate client profile and record the Minecraft, loader, and mod versions. Start without other optional mods, join the server, and check menus, the resource pack, dimension travel, and the actual feature. Add rendering, interface, and convenience mods back one at a time afterward. Publish the tested combination as a recommendation, not a server promise, because hardware and local settings differ. After an update, compare logs and behaviour with a fresh profile before reusing old configuration files. Keep the mod out of the server directory while its project page explicitly classifies it as client-side. On failure, the world remains untouched: the affected player disables the local file or returns to the documented version. For support, request a screenshot of the active profile instance, latest.log, and a list of other graphics mods; these show whether the loader, driver, or an overlap is responsible instead of the server.