Tags
Creators
Details
Licensed GPL-3.0-only
Published 10 months ago
All versions
1.4.0+26.1.x
Release
Heirlooms 1.4.0+26.1yesterday 4
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
!! back up your world before updating from another minecraft version !!
new
- tooltip expansion keybindings are now configurable
- added "Bought by" and "Looted by" acquisition paths
- added "First named by" component for the first time an unstackable item is named
- acquisition, first-naming, and enchantment events now record their coordinates and dimension
- display rack and case HUDs now show expanded data with date and dimension-specific location icons
- enchanting an item with an enchanted book in an anvil now records the enchantment component, like the enchantment table already did
- location lines in display block HUDs are hidden when
/gamerule reduced_debug_infoistrue
changes
- adding an item to a display rack or case in Creative Mode now copies the item instead of consuming it
- removed the 1.20.1 tooltip NBT-to-data-component migration code. If upgrading an Heirlooms world from 1.20.1, upgrade it to 1.21.x first and always make a backup.
fixes
- items in Display Cases now render with the correct rotation
- block items in Display Cases now default
BlockStateProperties.ATTACH_FACEtoAttachFace.FLOOR - display rack and case reject automatic item insertion properly
- enchantment capture mixin is now broader, should work properly with mods like apotheosis
technical
- renamed two data components:
heirlooms:crafted_by→heirlooms:acquired_byheirlooms:crafted_timestamp→heirlooms:acquired_timestamp
- existing 1.21.11 items using the old components migrate when moved through a player inventory
- legacy items stored in display racks and cases migrate automatically when loaded or placed
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:E1ZTThzs:ikSa7m7k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E1ZTThzs:ikSa7m7k"
}

