Included content
| Name | |
|---|---|
![]() | BetterConfig |
Relates to #51. This PR adds a seed explorer map (perhaps long overdue, for a mod called SeedMapper 😄). The map can be opened in-game by pressing
m(keybind is configurable) or by executing the/sm:seedmapcommand. The background texture is determined by the biomes (at sea level), where each biome has been given a colour. The colours are from Cubiomes. On top of the biomes, a few additional things are drawn: structures/features, ore veins, and the player's position in the world. What features will be displayed can be configured by toggles at the top of the screen. The map is infinitely explorable by dragging the mouse, and can be zoomed in/out by using the scrolling wheel. Moreover, you can copy the coordinates of the mouse's position by right-clicking. By default, four pixels will be drawn per biome quart pos (a quarter chunk pos), which equates to one screen pixel per in-game block. Note that the precision of biomes is limited to biome scale (so up to quart pos) for efficiency.As the map can be opened through a command, you can make use of the
/sm:sourcecommand to completely change what parameters the map uses. For example, to view the biomes as they were in Minecraft 1.0, you can do/sm:source versioned 1.0 run sm:seedmap. You can similarly change the seed and dimension.The map is intended as a quick way to explore a seed, similar to ChunkBase. As such, it is not my intention to make the map as feature complete as Cubiomes Viewer. This is also because the map runs alongside Minecraft, which makes rendering/UX much more complicated than with a standalone application, and means the map will not be as performant because the game runs in the background.
I am planning to release this as a beta version of SeedMapper, because I would like to receive some feedback before I make a full release. So if you find bugs or have any suggestions, please let me know!
![]()
| 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 | |
|---|---|
![]() | BetterConfig |
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:6QKlOPF0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C4GbEnuY:6QKlOPF0"
}