1.0.0
Compatibility
Changes
Xaero's Map plugin
Keep your Xaero's maps separated between worlds and servers.
Xaero's Map plugin is a lightweight plugin for servers using Xaero's Minimap and Xaero's World Map. The plugin prevents different worlds from sharing or overlapping map data, ensuring that every world maintains its own unique map.
Features
- Prevents map data from merging between worlds
- Each world gets its own separate Xaero map
- Supports Xaero's Minimap
- Supports Xaero's World Map
- Lightweight and performance-friendly
- Works automatically with no player setup required
Velocity Support
Running multiple servers behind a Velocity proxy?
Xaero's Map plugin can be installed directly on your Velocity proxy to prevent map data from being shared between backend servers.
If you are using Velocity, you only need to install the plugin on the proxy.
There is no need to install it on every backend server.
This ensures that:
- Maps do not merge between servers
- Map regions remain unique per server
- Players do not experience overlapping map data
- Different gamemodes can maintain separate maps
Perfect For
- Multi-world servers
- Survival networks
- SkyBlock networks
- RPG servers
- Custom dimensions
- Velocity proxies
- Any server using Xaero's Minimap or Xaero's World Map
Why Use This Plugin?
Xaero's mods identify maps using world information. On some server setups, multiple worlds or backend servers can end up sharing the same map data.
Xaero's Map plugin solves this by providing unique identifiers for worlds and servers, ensuring every map remains completely separate.
Result
- Cleaner maps
- No unwanted map merging
- Better player experience
- Full compatibility with Xaero's mapping mods
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:QR1TvZfX:ANgZlttk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QR1TvZfX:ANgZlttk"
}

