Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 2 months ago
All versions
1.7.17
Release
MobsToEggs 1.7.17last year 595
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.4–1.21.7
Platforms
Paper
Purpur
Changes
UPDATED:
- Fixed support for Custom Model Data on capsule and spawn eggs (now entered as a string).
- Added Custom Model Data capsule validity check (like name and lore checks).
- Changed "item-cost" check to allow both 'none' or an empty value to disable per mob.
- Reworked how sounds are handled through the plugin (hopefully fixing any previous issues some people were having).
- Updated MobsToEggs spawn egg spawn cancelling when clicking on blocks that have an interact option (like a check or furnace).
- Made edits to default config.yml wording to add more clarity.
- Fixed inventory holding entities not having inventory/items held/armor saved.
- Fixed potion effects not being saved to entities.
- Added 1.21.6+ support with happy ghast (new data-tag for happy ghasts).
- Changed capsule "item" value to support being empty.
- Fixed extra '}' added at the end of the plugin update message in console.
- Updated to Kotlin 2.2.0.
- Updated internal dependancies.
- Changed MobsToEggs spawn egg spawning to better mimic a vanilla spawn egg.
- Fixed spawners not changing the spawner type if the spawn egg item is not a mob spawn egg.
- Added an auto config updater to auto update default sound values in the config.yml (values updated in 1.7.16).
- Fixed bug with mob egg material value throwing an error if the material name wasn't uppercase.
- Fixed cat variants throwing an error if another plugin/datapack added new variants.
This version only supports Paper and Paper forks.
1.21.5+ support can be found in the files below or by manual plugin changes.
Supplementary resources
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:ODULpGTh:xoP3s6iy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ODULpGTh:xoP3s6iy"
}

