Tags
Creators
Details
All versions
1.4.0
Release
NamedChest-1.4.03 months ago 101
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.2
Platforms
Paper
Purpur
Changes
[⭐] New Features and Improvements
- DecentHolograms Integration: Added full support for the DecentHolograms API.
- Visibility Settings: Added the
ignore-passable-blocksparameter toconfig.yml. Storage names and holograms will now be displayed through passable blocks (e.g., tall grass and fluids). - Audio Feedback: Introduced an audio response system for player actions. Added
error-soundandsuccess-soundparameters toconfig.ymlto configure sounds for successful and failed actions. - Minecraft 1.21.9 Blocks: The default configuration has been updated and now includes all the new blocks introduced in version 1.21.9.
- Advanced Version Control and Security: Completely overhauled the update checker system. Server administrators will now receive notifications when critical patches are released. Also added an emergency shutdown mechanism (kill-switch), allowing the plugin to automatically deactivate if a critical bug or vulnerability is detected by the developer.
[🛠] Fixes and Adjustments
- Cooldown Unification: Reworked the cooldown logic. Cooldowns are now global and synchronized across the usage of commands, name tags, and anvils.
- Anvil Fixes: Resolved issues related to applying colored names via the anvil, and added permission checks as well as cooldowns.
[⚙️] Technical Changes
- Global Refactoring: The project has been completely rewritten from scratch. The new codebase is significantly cleaner, more transparent, and easier to maintain.
- Migration to Okaeri Configs: The plugin now uses the Okaeri Configs library for configuration management, ensuring a more robust structure and data serialization.
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:Cw0apxhH:kj2CwWgK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Cw0apxhH:kj2CwWgK"
}

