Included content
| Name | |
|---|---|
Added a seed-based minimap. The seedmap can be opened by pressing , or by entering the /sm:minimap command. The minimap is very similar to the seed map in what it shows. The minimap can be tailored to the user's preferences by various configs:
Added terrain generation highlighting. This is a debug feature that must be enabled by doing sm:config DevMode set true. This command could for example be used to uncover what the terrain used to look like before player modification. The command is /sm:highlight terrain [<chunks>].
Introduced support for large biomes, among other things. The user now has more control over the configured seed. Instead of a single world seed number, the seed config is instead a combination of values that identify a world seed. That is, now the seed config will consist of:
The second value allows the user to specify a Minecraft version that SeedMapper should use when using the seed. For example, if you play on a 1.19.4 server with the latest SeedMapper version, you can do /sm:config Seed <seed> --version 1.19.4. Now SeedMapper will always use this version for its calculations. Previously you had to prepend every command with /sm:source versioned 1.19.4 run. Of course, you can still use the /sm:source command to override the configured version.
The third value allows the user to specify certain generator flags. Currently, these are large_biomes, no_beta_ocean and force_ocean_variants. For example, you can do /sm:config Seed set <seed> --generatorFlag large_biomes to enable the large_biomes generator flag. The generator flags stack, so you can repeat the --generatorFlag argument to add more flags. Also the generator flags can be overridden by the /sm:source command.
| Mod JAR | Biome | Structure | Loot | Ore | Slime chunk | |
|---|---|---|---|---|---|---|
| 1.21 | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.20 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.19 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.18 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.17 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.16 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.15 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.14 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.13 | ❌ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| 1.12 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.11 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.10 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.9 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.8 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.7 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.6 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.5 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.4 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.3 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.2 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.1 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| 1.0 | ❌ | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
| Name | |
|---|---|
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.
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:C4GbEnuY:Tl6Y7U6E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C4GbEnuY:Tl6Y7U6E"
}