Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 years ago
Updated 2 years ago
All versions
1.4.0
Release
WhyMap 1.4.04 years ago 168
Compatibility
Minecraft: Java Edition
1.19.3–1.19.4
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Unavailable version
Changes
- Both 1.19.3 and 1.19.4 supported
- Minimap should display correctly on high-dpi displays
- Improved performance, minimap should affect fps/tps only a little bit
- Should be compatible with more mods and datapacks.
- If a mod or datapack you use adds non-vanilla blocks to the game, additional mappings will be created in
minecraft/WhyMap/mappings-customdirectory. If you use non-vanilla blocks and you want to share tiles with your friends, you'll need to share this custom mappings file as well.
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:g9qdEhvu:UGlKF2r8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:g9qdEhvu:UGlKF2r8"
}

