Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated last week
All versions
4.0.0+26.1
Release
trinkets 4.0.0+26.1last month 7,793
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Fabric
NeoForge
Supported environments
Client and server
Changes
- Added new events:
- TrinketModifySlotCountCallback - Allows you to easily modify the Trinket inventory's slot count dynamically. Server only!
- TrinketSlotCountChangedCallback - Triggered after slot count was changed!
- TrinketEquipmentAttributeModifiersCallback - Allows to provide additional attributes for a given trinket item.
- New TrinketInventory methods:
- #updateSlotCount() - Triggers update of the amount of available slots for given inventory.
- #addSlotCountModifier(AttributeModifier) - Adds slot count attribute modifier.
- #removeSlotCountModifier(Identifier) - Removes slot count attribute modifier.
- New TrinketSlotUtils class with these utility methods.
- #createSlot(TrinketSlotAccess access, int x, int y) - Creates standalone slot for given slot access.
- #mayPlace(TrinketSlotAccess, ItemStack) - If item can be inserted into given slot.
- #mayPickup(TrinketSlotAccess, ItemStack) - If item can be picked up from given slot.
- #isSlotCompatible(TrinketSlotAccess, ItemStack) - Checks if given slot is logically compatible with stack.
- #isEquipable(TrinketSlotAccess, ItemStack) - Checks if given stack can be equipped.
- Added
/trinkets <entity> <slot> modifierscommand, allowing you to easily modify amount of slots at runtime. - Added compatibility with Just Enough Items, Roughly Enough Items and Reliable Recipe Viewer's exclusion areas.
- Fixed removing NBT data with /data command not clearing out Trinkets slots correctly.
- Added support for exclusion areas for Just Enough Items and Roughly Enough Items.
- Deprecate TrinketRendererRegistry#getRenderer for removal.
- Added TrinketRendererRegistry#registerRenderer variant that take a Function<EntityRendererProvider.Context, TrinketRenderer> as it's argument.
- Command text is now translatable.
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:XaT8sLP6:BcSmZVfF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XaT8sLP6:BcSmZVfF"
}

