Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated last year
All versions
1.6.0+mod
Release
v1.6.0 - Old Gods2 years ago 3,356
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.2–1.21.5
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Server-side
Client and server
Changes
What's Changed
- ✳️ Added new "overlay" folder for the 1.21.4-compatible version of the datapack.
- This overlay will be automatically applied on versions 1.21.2-1.21.4, and ignored otherwise; Essentially, this means all compatible versions will now use the same file! :D
- The newly-created 1.21.4 branch will be thus deprecated. Oh well.
- 🐛 Fixed bug where the Seeker could not hurt any entities at all.
- ⭐ Added a new naturally-generated structure: the Dummy Altar:
- Generating throughout most of the Overworld, this mysterious structure features a strange block at its center, which activates when approached. When interacted with specific items, it has the ability to directly influence Dummy/Seeker entities around itself.
- 🔺 Reduced the volume of the sound from the Dummy/Seeker's death event.
- 🔺 Changed Seekers to no longer grant Purity scores when killed.
- 🔧 Introduced a new entity tag to indicate an entity should be in a "paralysis" state:
dummy_lib.dummy.paralysis - 🔧 Added failsafe to ensure DummyLib entities always have their own GUID.
- 🔧 Increased Dummy/Seeker's "obstacle" avoidance threshold by one block.
- This means they will now fall up to two blocks high, and climb obstacles up to two blocks tall when pursuing a target.
- 🔧 Changed Dummy/Seeker's gravity to be half as effective while underwater.
- 🔧 Changed Seeker's advancement to be only granted to the player who used its spawn egg.
- And even more technical updates...
See the full changelog on GitHub.
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:pXWM4MKR:UgfNDxE9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pXWM4MKR:UgfNDxE9"
}

