Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 4 months ago
All versions
0.1.0
Alpha
create-ore-excavation-deposits 0.1.05 months ago 24
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
0.1.0 — initial release
First public release. Multi-chunk ore deposits add-on for Create Ore Excavation on NeoForge 1.21.1.
Generation
- Multi-chunk Perlin-shaped deposits (2–40 chunks per blob).
- Distance-from-spawn log curve drives blob size, per-chunk units, and type eligibility.
- Per-chunk gradient: core peak fades to
edge_amount_mul × peakat the edges. - Per-type budget via
per_chunk_units(independent of COE's globalfiniteAmountBase). - Biome-tag filtering per type.
- Two placement modes per type:
managed(our blob algorithm) orcoe(vanilla COE places, we track for the map).
Visibility
- Xaero World Map overlay: coloured diagonal-striped chunks with hover tooltip (name, location, per-chunk
remaining / initial). - Compact 16×16 toggle widget on the map + Options → Controls keybind.
- Four reveal policies:
always/on_discovery(walk near) /on_proximity(visible while close) /on_prospect(Vein Finder must reveal). Per-player tracking.
Multi-dimension
- Default
enabled_dimensions = [overworld, the_nether, the_end]. - Per-dimension SavedData + per-dimension
depositSeedoverride for reproducible patterns across worlds. - Bundled overworld (11) + nether (3) ore defaults; end ready for user-defined entries.
Admin commands (OP-only)
/coedeposits tier/list/here/scan/regenerate [seed]/seed./coedeposits refill [all]/delete here|chunk./coedeposits place [<type> [<pos> [<amount> [<chunks>]]]].
Compatibility
- Required: Create Ore Excavation.
- Soft: Xaero's World Map (overlay), Xaero's Minimap (waypoints).
- No conflict with Create: Steam 'n' Rails (button position configurable to avoid UI overlap).
- Third-party COE veins coexist via
placement: "coe"delegation path.
Optional dependencies
Any compatible version
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:XfN8l56o:A9Ki3OUB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XfN8l56o:A9Ki3OUB"
}

