Links
Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 2 weeks ago
All versions
1.4
Release
Resourceful Sheep 1.45 months ago 45
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
🐑 Resourceful Sheep - Update v1.4
This update introduces genetics, new machines, sheep crossbreeding, and greatly improves the mod's configuration!
🧬 DNA & Genetics
- New Syringes: Added syringes to extract DNA from mobs.
- Upgrade Template: Added a new Smithing Template to upgrade your iron syringes to Diamond and Netherite.
- DNA Sequencer: A new machine that allows you to analyze and store the DNA collected in your syringes.
- DNA Splicer: A new machine used to combine different DNA sequences to create brand new mutations.
- Suspicious Spawn Egg: Crafted by the Splicer, this mysterious egg spawns your new genetic creations.
- New Mutations: Added several new default sheep types, crossbreeding recipes, and mutations.
⚙️ Configuration Changes
- Tag Support: The "Dropped Items" and "Biome" fields in your configs now fully support Minecraft Tags.
- Smarter Textures: Dynamic texture generation is now much more accurate and only uses the exact blocks and items specific to that sheep variant.
- Validation & Logs: The mod now checks your configuration files on startup. It will warn you in the logs if you have invalid IDs (biomes, items, effects, blocks) or duplicate fields.
- JSON Updates: The
Resourcefield in the sheep configs has been officially renamed toSheepName.
📚 JEI, UI & Tools
- Crossbreeding Category: Added a brand new JEI category to show players exactly how to get specific sheep through DNA crossbreeding.
- Sheep Scanner Updates: The scanner now consumes FE to work and displays the exact name of the scanned sheep.
Optional dependencies
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:DzNeVTBJ:bqId9Sud"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DzNeVTBJ:bqId9Sud"
}


