All versions
1.2.3
Release
Items Filter - Plugin Inspiration 1.2.35 months ago 17
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Paper
Changes
v1.2.3
🇬🇧 English
- "Chunk-based" Philosophy: The filter is now active if and only if its chunk is loaded. The plugin no longer forces chunk loading by default (unless the
keep-chunks-loadedoption is enabled), significantly freeing up CPU resources. - Performance Enhancements: Removed the
pause-when-no-playerscheck from the tick task. The existingisChunkLoadedcheck is now sufficient to handle CPU load optimally. - Command Updates:
/if help: UI updated to reflect version v1.2.3, added the new/if chunkloadcommands, and included a new explanatory section regarding the "chunk-based" model.
- Configuration:
pause-when-no-playersis now deprecated inconfig.yml.
- Backward Compatibility:
- 100% compatible: no filters need to be recreated, no data migration required.
🇫🇷 Français
- Philosophie "Chunk-based" : Le filtre est désormais actif si et seulement si son chunk est chargé. Le plugin ne force plus le chargement des chunks (sauf option
keep-chunks-loadedactivée), ce qui libère des ressources CPU. - Performances : Suppression du check
pause-when-no-playersdans la tâche de tick. Le checkisChunkLoaded(déjà existant) suffit désormais à gérer la charge CPU de manière optimale. - Mises à jour des commandes :
/if help: Interface mise à jour avec la version v1.2.3, l'ajout des commandes/if chunkloadet une nouvelle section explicative sur le modèle "chunk-based".
- Configuration :
pause-when-no-playersest désormais déprécié dans leconfig.yml.
- Compatibilité :
- Rétrocompatibilité 100% : aucun filtre à recréer, pas de migration nécessaire.
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:XwPvF2Dk:YXZID6Gi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XwPvF2Dk:YXZID6Gi"
}

