Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 4 months ago
All versions
0.1.7
Alpha
NeoForge 0.1.75 months ago 150
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
0.1.7
Changed
- Friendlier, configurable discovery chat message. The old line printed the raw type id with a
[coedeposits]prefix ([coedeposits] discovered createoreexcavation:ore_vein_type/water at [...]), which read like debug output (reported in #3). It now resolves a friendly name — the type'sdisplay_namefromdeposits.json, otherwise a prettified id (createoreexcavation:ore_vein_type/water→ "Water") — and the whole line is a config templatediscovery_message_format(defaultDiscovered %name% at %pos%). Placeholders:%name%,%pos%(clickable /tp),%x% %y% %z%,%type%,%player%(the discoverer),%%;§colour codes work.
Fixed
- Deposits placed over already-explored terrain no longer read "depleted". COE's
OreData.populateruns once per chunk, so a deposit placed by/coedeposits regenerateor the prospect scanner over a chunk generated before the deposit existed never got its OreData applied. The depletion sweep now self-heals such chunks (no recipe and nothing extracted → re-apply) while leaving genuinely mined-out chunks alone. - ON_DISCOVERY reveals are snappy now — the walk-into sweep runs every second instead of every ten, so a deposit appears moments after you step onto it. The reveal-mode config option also finally documents what each of the four modes does.
Added
- ON_PROXIMITY now sends a personal "found it" chat line the first time a player comes within the proximity radius (same
discovery_message_format; once per player per deposit, persisted). Visibility is unchanged — still distance-based. - Discovery chat controls in the in-game config — the Reveal group now has a Discovery chat message toggle (off keeps the map marker / Xaero waypoint, just no chat line) and a Discovery message template field, alongside the
discovery_chat/discovery_message_formattoml options (#3). reveal_scopeconfig — per-player, team, or shared discoveries (#3). For the per-player reveal modes (ON_DISCOVERY/ON_PROSPECT):PER_PLAYER(default) keeps each player's discoveries private (COE's own behaviour);TEAMshares discoveries with the discoverer's party/team — Open Parties and Claims, else FTB Teams, else the vanilla scoreboard team (both mod integrations are reflection-based, no hard dependency). Team visibility is live: you see everything anyone currently on your team has discovered — joining a team shares past finds both ways, leaving un-shares them (your own finds always stay).GLOBALmakes the first player's discovery reveal the deposit for everyone. Online recipients get the marker + a chat line crediting the finder via the new%player%placeholder. Persisted in SavedData; surfaced in the Reveal config group. (No effect onALWAYS/ON_PROXIMITY.) Per-type override is not included yet — it's a mechanical follow-up.- Deposit sharing (#3). Players can share discoveries explicitly, in three ways:
/coedeposits share— posts a clickable [✚ Add to map] offer to chat (everyone in the dimension can click it to add the deposit to their map + Xaero waypoint);/coedeposits share <player>/share all <player>— share the deposit you stand in (or everything you've discovered) directly with one player; world-map keybind — bind "Share hovered deposit to chat" in Options → Controls, hover a deposit on the Xaero world map and press it to post the same clickable offer (the tooltip shows the hint once the key is bound). You can only share deposits you can see; the share/accept commands work without OP (admin subcommands remain OP-gated).
Optional dependencies
Any compatible version
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:xlEiKbOd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XfN8l56o:xlEiKbOd"
}

