Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 2 months ago
Updated last week
All versions
1.5.0+26.2
Release
VO: Camera Culling 1.5.0+26.2last month 177
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
[1.5.0+26.2]
Added
- Two-Tier Entity Immunity Blacklist (Client & Server Admin Enforcement):
- Client Personal Blacklist: Saved locally in
config/camera-culling.json(clientBlacklist: []). Players can add specific entity types (e.g.minecraft:wolf,minecraft:allay) they never want to be culled. - Server Admin Blacklist: Configured in
config/camera-culling-server.json(serverBlacklist: []). Server administrators / OPs can enforce server-wide immunity for specific mobs across all connected clients. - Strict Server Authority: Server-blacklisted entities are mandatory immune on all clients; players can add additional personal entities on top.
- Full Immunity Scope: Blacklisted entities are completely exempt from block occlusion culling, crowd overdraw culling, and distance texture LOD downscaling.
- Client Personal Blacklist: Saved locally in
- In-Game Commands (Strict ResourceLocations):
/cameraculling blacklist add <entity_id>— Add entity to personal immunity blacklist (e.g.minecraft:wolf)./cameraculling blacklist remove <entity_id>— Remove entity from personal immunity blacklist./cameraculling blacklist list— List all personal blacklisted entity types./cameraculling blacklist clear— Clear personal blacklist./cameraculling serverblacklist add <entity_id>— Add entity to server-wide immunity blacklist (OP/admin)./cameraculling serverblacklist remove <entity_id>— Remove entity from server-wide immunity blacklist./cameraculling serverblacklist list— List all server-wide blacklisted entity types./cameraculling serverblacklist clear— Clear server-wide blacklist.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ATX2NaJR:vhkQhYBb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ATX2NaJR:vhkQhYBb"
}

