Tags
Creators
Details
Licensed LGPL-3.0-only
Published 9 months ago
Updated 5 months ago
All versions
0.20
Release
SeedMapper-CevAPI 2.23.0-CevAPI v0.205 months ago 147
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
- Added a Modrinth update checker (
Configs.UpdateChecker, default on) that runs on join and notifies in chat when a newer fork release exists. - Added stronghold portal-room details to
/sm:locate structure stronghold, including portal coordinates and eye count when available. - Added stronghold loot scanning into
/sm:locate loot(Overworld), so loot search now includes strongholds instead of only other loot structures. - Improved loot-location robustness by handling null loot table pointers and avoiding false “loot unavailable” hard-fails in some paths.
- Added direct ore debug command support:
/sm:highlight ore <ore> [chunks](dev mode), with ore-name argument parsing and suggestions. - Made highlight colors configurable via config (
BlockColors) and switched ore/vein rendering to use configurable per-block colors. - Extended
OreAirCheckbehavior from only air/lava checks to broader non-occluding block checks, reducing misleading highlights. - Improved config command UX and compatibility: supports fork config id, legacy fallback, and alias command
smconfig. - Migrated config storage to
seedmapper_cevapiand added automatic one-time copy from legacyseedmapper/config.jsonif present. - Improved datapack import validation with clearer failures: rejects non-
.zipURLs early and reports “no structures” more explicitly. - Added “no seed” fallback for
/sm:seedmap: opens map with temporary seed0plus current version/preset instead of failing outright. - Reduced SeedMap UI loot-option lag by no longer pre-scanning world structures just to populate item options; now uses parser catalog directly.
- Hardened Cubiomes string handling (
CubiomesCompat) across biome/version/structure/item/enchantment names to prevent null/invalid C-string crashes. - Fixed wording/specificity of unknown argument errors (
unknownBlockvsunknownOre) and added new stronghold portal localization strings.
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:2qXosh15:M7NvFXp7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2qXosh15:M7NvFXp7"
}

