Links
Tags
Creators
Details
5.0.0.0
Compatibility
Required content
Changes
[1.18.1] EmbellishCraft 5.0.0.0
- Required Forge version: 39.0.0 and above
- Required mods: Mapper Base 4.0.0.0
This is the first release for Minecraft 1.18.1.
While it has been tested on client + server without any encountered problem it may be possible to find new bugs as the mod went through a rewrite. In this case please report them.
This build was tested against the latest 1.18.1 version of Forge, after 1.18.2 versions started being distributed.
Changelog
Updated to Minecraft 1.18.1
The mod now runs on Minecraft 1.18.1. It is basically the same mod than the 1.17.1 version with a few changes to accommodate the new version.
Ore gen changes
In this version the various rocks generate this way:
- basalt now generates in the deepslate
- slate and gneiss generates the same way than before
- marble now generates above sea level, it is mostly found in hills and mountains
- jade generates above sea level in small pockets
- larvikite now only generates in colder biomes
Remember a config file exists to change how the rocks are generated.
Temporarily disabled contents
Due to changes in Minecraft and lack of time some contents were disabled since 1.17.1. They may return later in future updates (probably only on 1.18+ versions).
Fancy chests and the locker were disabled, those blocks need a complete rewrite as the existing code is a huge mess.
The ability to sit down on chairs, couches and suspended stairs is disabled, the code also needs to be rewritten.
Other changes
Fixed missing fancy bed recipes.
Fancy beds made with Nether woods can't be used as furnace fuel anymore.
Please report bugs to GitHub.
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:OYTC1n5i:ILMZnQU1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OYTC1n5i:ILMZnQU1"
}

