Tags
Creators
Details
neoforge-26.1.2-2.2.0
Compatibility
Changes
After taking way longer than I wanted, the update is finally here!
-
Added a tab to track released familiars. Their last known co-ordinates (or dimension if you aren't in the same one) will be shown above their render. You can recall them to the book if you're within render distance or their chunk is loaded!
-
Added a default check for ownable entities, which should cover some more modded creatures.
-
Removed the automatic check for invalid familiars option.
-
Added a possible fix for familiars bugging out when being stored while sitting on a chair.
-
Familiars with revival enabled should no longer drop items on death to prevent exploiting it.
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:iMn5Yv5Q:8GJAxdio"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iMn5Yv5Q:8GJAxdio"
}

