Tags
Creators
Details
All versions
1.0.3
Release
Sophie's Alloys 1.0.32 years ago 47
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Overview 1.0.3
New blocks, balancing tweaks, and no more No Fruit Sapling!
WARNING: NO FRUIT SAPLINGS NO LONGER EXIST!!
Removed Content
- No Fruit Saplings have been replaced with the No Fruit Bush. No Fruit Sapling blocks and items will disappear from your world!!
New content
New Items
- Lead Bars: they're just like Iron Bars, except they're made of lead.
- Dusty Lamps: a brand new redstone component that can only be directly turned on and off by the player with an empty hand. When on, they work like a weaker Redstone block, and has varying levels of outputs depending on what type of dust was used on the lamp. Crimson Coal will output a signal strength of 6 while Amethyst will output a strength of 12.
- No Fruit Bush: Similar to Azalia Bushes, it must be bone mealed to grow into a tree, and will no longer become one passively.
Textures
- The appearances of Dusty Lamps correspond to their redstone strength output.
- Slightly changed how the Funky Quingum Mixture/Gummies textures work to no longer leave behind black pixels in inventory GUIs.
Recipes
- Tweaked a few recipes to have a little bit better balance. Also, you can no longer negate alloying Lagomite by crushing Crushed Lagomite to make Lagomite Dust.
- Lagomite tools can now be smithed from Foxite instead of Diamond, cause why would you downgrade your armour?
Misc
- Dusty Faunathyst Lamps can be used as compost advancers with Farmer's Delight.
- Altered netherite recipes from Farmer's Delight, Quark, and Create to make them consistent with Sophie's Alloys.
- Dusty Lamps and Iron & Lead Bars are able to be picked up with Create's Wrench
- Buffed Quingum even more so it actually makes sense
Fixes
- No Fruits can now be picked up with Silk Touch instead of always turning into other fruits.
- Properly fixed netherite recipes. I thought I did, but I didn't actually check the proper naming schemes, nor did I directly check the recipes themselves in-game
Optional dependencies
Any compatible version
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:dkuKyRt9:eajY0i50"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dkuKyRt9:eajY0i50"
}

