All versions
1.20.1-0.1.5
Alpha
[Forge 1.20.1] Create Ore Excavation Deposits 0.1.5last month 11
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
0.1.5
Added
- Fluid deposits (COE Extractor). A deposit can now yield a fluid instead of (or alongside) items, harvested with Create Ore Excavation's Extractor rather than the Drill. Add an inline
fluid:block to aconfig/coedeposits/deposits.jsonentry (fluid,amountmB/cycle,ticks,stress,drill_tag) and theBundledRecipePacksynthesises acreateoreexcavation:extractingrecipe bound to the type's vein. Placement, distance, biome filter and theper_chunk_unitsbudget all work exactly as for a solid ore — COE's Extractor and Drill share the same vein-consumption logic. - In-game fluid picker. The editor's Fluid field opens a picker that lists registered source fluids by their own texture (tinted sprite) + name, with search and click-to-select — not bucket items. (YACL has no fluid controller, so this is a small dedicated screen.)
- Bundled example. Ships a ready
coedeposits:example_waterdeposit — a finite "Underground Spring" ofminecraft:waterextracted with the Extractor — so the fluid path works out of the box. Generates in overworld swamp/plains atweight: 50; disable it from the editor (or an{"enabled": false}overlay) if unwanted.
Changed
- Config validation now counts an
extractingrecipe as making a vein harvestable, so a fluid-only deposit no longer false-warns "can't be mined".
Internal
DepositTypecodec split into two flattenedMapCodechalves joined withCodec.mapPair(DataFixerUpper'sgroup(...)caps at 16 fields; the type now has 17). The on-disk JSON schema is unchanged.
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:XfN8l56o:k5FJbFK8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XfN8l56o:k5FJbFK8"
}





