All versions
1.0.23
Release
Create - Xaero's map 1.0.232 months ago 3
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Changes
New stuff:
- Propellers, wheels, rudders and other bearing-mounted parts now show up on the map with the rest of the craft, instead of just the hull
- Spinning parts update live on the map instead of jumping every 2 seconds
- Motion blur! Fast moving blocks smear along their path, and props spinning fast enough turn into the classic see-through prop disc. Blade tips blur while the hub stays solid, wheels get it too. Tunable in MapConfig
- Contraptions running in the normal world (windmills, propeller bearings on a base, elevators...) now render on the map while assembled. Vanilla Xaero just drops them since their blocks technically leave the world
- Stuff that's physically above a craft (bridges, tree cover, terrain) now draws over it on the map instead of the craft always painting on top
- Full cave map support: crafts inside the cave layer show correctly, cave walls/ceilings hide them per column, and anything above the layer gets cut away like the rest of the world
Fixes:
- Fixed crafts randomly vanishing from the map (one bad coordinate from a mid-assembly contraption could yank the whole image off the map)
- Fixed idle propellers not rendering after the bearing stopped (stale chunk data on the client)
- Fixed vertical/gyroscopic props never rendering at all
- Fixed prop blur drawing on top of terrain it was actually under
- Fixed belly-mounted props smearing blur over their own hull
- A failed map refresh now keeps the last good image instead of blanking the craft until the next one succeeds
- Added proper debug logging for the map renderer, if something disappears the log will now tell you why
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:kLbFYiWn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hqI03twF:kLbFYiWn"
}

