All versions
1.0.6
Release
Birds-Eye, World-Map Optional-Minimap Update2 months ago 6
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
v1.0.6 — Minimap now optional
- Xaero's Minimap downgraded from a required to an optional dependency — the mod runs with just the World Map, rendering only on the full map.
- Minimap mixin split into its own non-required config + a config plugin that skips it when the minimap isn't installed (no crash).
v1.0.5 — True world-space birds-eye
- Sublevels are now rasterized from their real world orientation: each block is projected through the craft's rotation and the top-most block along the world vertical wins. A pitching/rolling ship shows what's genuinely on top from overhead.
- World-height slope shading; re-renders only when orientation changes (straight-line travel is free); interior blocks skipped.
v1.0.4 — Birds-eye projection (superseded by 1.0.5)
- First pass at flattening pitch/roll — rotated the flat snapshot rather than re-rendering it.
v1.0.3 — Sublevels now visible on the world map
- Fixed the core bug: the world map binds no lightmap, so the text shader discarded every pixel. Switched to a dedicated lightmap-free, depth-test-free render type. Works on both maps.
v1.0.2 / v1.0.1 — Diagnostics (dev only)
- Temporary logging and a solid test quad used to pin down the world-map failure; removed in 1.0.3.
v1.0.0 — Initial release
- Renders Sable sublevels (Create: Aeronautics craft, etc.) as live block imagery on Xaero's Minimap and World Map. Includes the world-map depth-buffer fix and build setup (Veil maven, Gradle 8.14 wrapper).
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:hqI03twF:pF5r5eTU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hqI03twF:pF5r5eTU"
}

