Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last year
All versions
1.0.1
Release
v1.0.12 years ago 559
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.4
Platform
Data Pack
Changes

Additions:
- Added a failsafe feature (if the function that runs every second failed to reschedule due to an update, the pack will now reschedule it & start working properly again)
- Added a sound for Totems of Revival being consumed (it's the Totem of Regeneration sound from 'Minecraft: Dungeons')
- Added sounds for Allay & Vex conversions (Vex sounds (3) from 'Minecraft: Dungeons', Allay sounds (8) from 'Minecraft:Legends')
- Added Modrinth to pack download page links
Changes:
- Updated to 1.21.4 ('Mob Tweaks' items obtained in v1.0 no longer work - to update the items hold them in either hand; Totems of Revival now always save the effects you had before activation)
- Changed the 'CHANGELOG' button in resources to 'CHANGELOGS' (you will now be able to select between the v1.0 and v1.0.1 changelogs)
- Updated structure & skylight detection (in theory, some mod/DP structures that replace vanilla Mineshafts/Mansions/Strongholds should support 'Mob Tweaks' spawning changes)
- Allay health detection is now more accurate (the particles will be displayed if the Health value is below the max_health attribute value; if the Health value is higher the particles won't display even if the Allay is healing)
- Totems of Revival no longer work in Creative
Fixes:
- Fixed Totems of Undying being consumed while holding the Totem of Revival in the offhand & being withered
- Fixed undead mobs in Trial Chambers being able to pick up items (this is actually a vanilla Minecraft bug)
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| [RP] 'Mob Tweaks' v1.0.1 (1.21.4).zip | Required resource pack | 617.53 KiB |
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:XxFP0BZI:2rSFr7Hv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XxFP0BZI:2rSFr7Hv"
}

